The conversation view

A thread's conversation view is a single scrolling stream: your messages, the agent's replies, and everything the agent did to produce them. This page covers what you'll see in that stream. For what a thread is and how its lifecycle works, see threads.

A conversation: a user message, a collapsed Explored activity group, an expanded edit call with an inline diff, and the end-of-turn changed-files rollup

Screenshot coming soon

/images/docs/interface-conversation.png

Your messages

Each message you send renders as a bubble on the right. Long pastes (over 20 lines) collapse automatically with a Show more toggle. Hovering a message reveals the send time and a Copy button, which works. An Edit button is also visible next to Copy.

Agent replies

The agent's turn can contain several kinds of content, in the order the agent produced them:

• Text — rendered as markdown.
• Thought — a collapsible reasoning block. It streams as the agent thinks and collapses to a one-line preview once the agent moves on.
• Tool activity — see below.
• Images, audio, and linked resources the agent's underlying provider returns as part of its output.

Tool activity

Every action an agent takes — reading a file, running a command, editing code — is a tool call. LinkCode renders a run of consecutive same-kind calls as a single collapsed row instead of one row per call, so a burst of file reads doesn't flood the transcript. The three groupings you'll see most often:

• Explored — file reads and searches
• Ran commands — shell/terminal execution
• Edited files — edits, deletes, and moves

(Web fetches and explicit "thinking" tool calls group the same way, under their own labels.)

Click a grouped row to expand it into its individual calls. Each call shows a kind badge (Read, Edit, Delete, Move, Search, Run, Think, Fetch, or Tool) and, where relevant, an expandable body: raw input, a live terminal block, or an inline diff. A call that's gated behind a permission request is never folded into a group — it always renders as its own row so you don't miss it.

Diffs. An edit call's expanded body shows a per-file diff — added/removed lines with a +/- count. When a turn finishes, LinkCode adds a rollup card below it summarizing every file the turn touched, with a total insertion/deletion count and a per-file breakdown (the first three files, with the rest behind a Show more toggle).

Plan progress

When the active agent reports a step-by-step plan, LinkCode pins a collapsible Plan card above the composer showing the current step (for example "Step 2/5") and, expanded, the full list with each step's status. It stays pinned until the plan completes or the agent stops reporting one.

Permission prompts

When an agent needs your approval to proceed, LinkCode pins a permission request above the composer instead of burying it in the transcript. You can answer with the keyboard — number keys, arrows, and Enter all work. See approvals for how approval policies and permission requests relate, and keyboard shortcuts for the exact key bindings.

Artifact cards

When a tool call produces a file — for example an edit or a move — LinkCode shows a small card for it under the call, up to four per call. Clicking a card opens the file in the Files panel. This is one of two ways content produced by an agent can surface in the conversation; see artifacts for the other (content that renders inline, like diagrams).

Copying a reply

Every agent turn ends with a small action bar. Copy copies the turn's text and is the one action there that works today (the others are covered in the callout above).