# Chat transcript: one agent reply is one bubble ## What this item changed `internal/` and `android/`, the brokered chat transcript. Three defects measured against the operator's own OpenCode (127.0.0.1:49374): - **Server, delta part ids.** `internal/protocol/chat.go` adds `ChatDeltaPartID(messageID, kind, ordinal)` (mirrored as `ChatProtocol.deltaPartId` in `android/.../data/protocol/Chat.kt`), and `internal/opencode/chat.go`'s `NormalizeChatEvent` keys a text or reasoning delta on it. OpenCode numbers one message's text and reasoning parts independently from 0, so the old `"%s#%d"` gave a message's first text delta and its first reasoning part the same id — the client appended the answer into the thinking block and the server's retained state re-collided on resume. - **Server, tool fields.** `NormalizeChatEvent` now takes a tool call's arguments from `session.tool.input.ended`'s `text` as well as `session.tool.called`'s `input` object (`toolInput`), and `internal/server/chat_hub.go`'s new `mergeChatToolPart` folds each tool frame onto the retained part so a later `progress`/`success` frame that omits the name or the input never blanks it. - **Android, transcript.** `ui/chat/ChatFormat.kt` adds the pure `ChatTurn` / `TranscriptRow` / `transcriptRows` fold (each run of assistant messages between two of the operator's messages is one agent turn), the kind-aware `deltaPartId` net and `mergeToolPart`; `ChatStore` folds deltas and tool frames through them; `ChatTranscript` renders one bubble per turn — one thinking block over all the turn's reasoning, then its tool chips, then one answer block of its text parts — replacing `AssistantParts`/`MessagePart` with `AgentTurnItem`/`UserMessageItem`. Tests: `internal/opencode/chat_v2_test.go` and `internal/server/chat_test.go` add the id-collision and tool name+input retention cases; `ChatReasoningTurnTest`, `ChatTranscriptTest` and `ChatRunningWorkTest` cover the turn fold, the text/reasoning collision and the tool lifecycle on the client. ## Shared documents this change makes stale `android/README.md` describes the surfaces this item changed. The note is written here rather than edited in place; the `docs-fold` writer should update it. - `android/README.md:6021` — the **Reasoning collapsed by default** bullet reads "`ReasoningBlock` is now one compact, muted line per part". It should say one block per *agent turn*: the transcript folds every consecutive assistant message between two of the operator's messages into one `ChatTurn`, so all the turn's reasoning is one collapsible block (labelled with its step count when it reasoned more than once) and the reply is one bubble, not one per model step. - `android/README.md:4669` — "`ChatScreen.MessagePart` now calls `MarkdownText(part.text)` for `PART_TEXT`; the assistant message stays one `SelectionContainer`". `MessagePart` no longer exists; the answer is `MarkdownText(turn.answer)` inside `AgentTurnItem`, where `turn.answer` is the turn's text parts joined in order. The one-`SelectionContainer`-per-bubble fact is still true. - `android/README.md:6040` — the test paragraph's "`ChatTranscriptTest`, 7 cases" is now 9 (the fold tests); `ChatReasoningTurnTest` and `ChatRunningWorkTest` gained the collision and tool-lifecycle cases. - `android/README.md:4786` — the **Grouped chips** bullet says "a run of consecutive `tool` parts in one assistant turn is now one `FlowRow`". The chips still group in one `FlowRow`, but the calls shown are now the whole folded turn's (`ChatTurn.tools`), across every step of the reply, not one assistant message's parts. Dates, counts and capture names in those dated records are past evidence and stay as they are; only the behaviour statements above are now stale. ## Not stale - `docs/cli.md`'s and `internal/author/skill/references/operations.md`'s brokered chat sections describe the `chat_*` surface and its retained per-session/per-message state and resync; that remains true. Neither documents the delta part-id derivation or the tool-field retention, so neither gains a wrong statement — the derivation now lives in the `internal/protocol/chat.go` comment. The docs-fold writer may add one sentence to the reference's retained-state paragraph if it documents part ids there, but nothing there is now false. - No packaged OpenCode skill reference documents the app's chat transcript, and no packaged template or `internal/author/` managed file names it. - `android/AGENTS.md` and `internal/server/AGENTS.md` list the files this item touched (`ui/chat/`, `internal/server/chat_*.go`, `internal/protocol/`, `internal/opencode/chat.go`); no file moved and no build/test step changed, so both maps stay correct.