Conversation View

  • Desktop, mobile and web
  • All plans
View as Markdown

What it does

Every agent pane has two faces: the raw terminal of the CLI, and the Conversation view, a chat-style rendering of the same session read from the transcript the CLI writes on disk. You switch between the two at any time; the CLI keeps running underneath whichever one is on screen.

The thread reads like a conversation, not a log. Your messages sit in a neutral bubble on the right; the agent's answers take the full width and are signed with the agent's face, name and time, exactly the line that shows "working" while it types. The thread uses the full width of the pane, like the terminal it replaces, markdown is rendered, and a burst of tool calls is folded into one block. Answers a full-screen CLI repainted over stay readable in full. This layout (bubbles, signed answers, folded tool calls) shipped in 1.178.0. Since the same version a question the agent asks with options (Claude Code's question tool) also appears in the thread as a card you can answer by clicking.

The view is also the way to work in a right-to-left language: Arabic or Hebrew text cannot be laid out on a terminal grid, so for those interface languages the pane opens on the conversation by default.

Where to find it

  • Agent pane header: the line that previews the first message you sent is a toggle between the conversation and the terminal (tooltip View the conversation / Back to the terminal).
  • Floating controls at the bottom right of the pane: the Conversation button, which becomes Terminal while the conversation is up.
  • Toolbar of the conversation: Summary, the tool-call filter (Hide tool calls / Show tool calls), Copy the conversation, Refresh.
  • Eye button (Hide tool calls…) that appears when you hover the header of a tool-call group in the thread: hides tool calls for good, at the scope you pick.
  • Settings > Terminal > Conversation view: Auto, Always or Never. The same choice exists per project under Project settings > Terminals.
  • Settings > Terminal > Tool calls in the conversation view: Shown or Hidden. The same field exists under Project settings > Terminals and in Edit agent, with a third option Inherit (the hint Currently: Shown / Currently: Hidden tells what the wider scope gives).
  • Phone: in the agent console, the floating dock has Show the conversation / Show the terminal, and the conversation screen has Back to the terminal.

How to use it

  1. Open an agent and click the first-prompt line in its header, or the Conversation floating button. The pane switches to the transcript, scrolled to the latest turn. Every message you send from the composer jumps the thread back to the bottom, even if you had scrolled up to read older turns.
  2. Read the thread. Tool calls between two answers are grouped under a header such as 3 tool calls, open by default: click the header to fold the group (folded, it lists the tool names), click one tool line to see it in full (Show in full / Back to one line). The toolbar filter hides all tool activity at once, for this pane only and until it is closed; Copy the conversation copies the whole thread; Refresh re-reads the file. To hide tool calls permanently, hover a group header and click the eye button (Hide tool calls…). The dialog Hide tool calls? asks where the choice lands: Only for <agent name> (saved agents only), For every agent of this project or Everywhere; click Hide. The dialog reminds you where to show them again: the toolbar of the view, Settings > Terminal, the project settings or the agent's settings.
  3. Hover a message for its actions: Copy, and on an agent answer Listen (read aloud). Select any text and the same selection bar as in the terminal appears: Summarize, Explain, Copy, Send to an agent, Quote in composer, Send to backlog, plus the pane actions.
  4. Answer a question card. When the agent stops to ask something with options, the card shows The agent is waiting for your answer, the numbered options with their description and, for a single-choice question, Other: write your own answer. One question with one choice is sent as soon as you click an option; several questions, a multiple choice or a typed answer end with Submit answers. The card then shows Sending your answer to the agent… and folds to Answered with your choice once the CLI has recorded it. A question closed in the terminal without an answer reads Question dismissed without an answer.
  5. Click Terminal (or the header line again) to go back. Your last explicit choice is remembered per agent for the rest of the app session.
  6. When the CLI needs you in its own interface (a permission prompt, a /model picker, a plan dialog, a full-screen screen), the pane hands itself back to the terminal so you cannot miss it, then returns to the conversation once the CLI is done. A question card is the exception: the pane keeps the conversation, since you can answer from there.

While the agent works, the Working line (or "<agent name> : working") floats above the composer whatever your scroll position. Very long sessions show Showing the last N messages.; the full history stays on disk.

Settings

  • conversationViewDefault (global, Settings > Terminal > Conversation view): which face a pane opens on. auto (default) opens the conversation for a right-to-left interface language and, since 2026-10-01, in the Simple interface mode (even for a brand-new agent); otherwise the terminal. on always, off never.
  • conversationViewDefault (project override, Project settings > Terminals): the same three values for one project; Follow the global setting again removes the override.
  • conversationToolCalls (global, Settings > Terminal > Tool calls in the conversation view): show (default, each burst of calls as a foldable group) or hide (the prose only).
  • conversationToolCalls (project override, Project settings > Terminals): the same two values for one project; Inherit removes the override.
  • conversationToolCalls (agent override, Edit agent): the same two values for one agent; Inherit falls back to the project, then the global value. The eye button in the thread writes the same setting at the scope you pick.

Agent tools (MCP)

  • settings_get / settings_set: read or write conversationToolCalls at the global, project or agent scope.
  • agents_save: accepts conversationToolCalls (show / hide, an empty string removes the agent's override).

The view itself is a reading surface; agents keep working in their own CLI.

Providers

The view exists only for CLIs whose transcript AgentsRoom can read back: Claude Code, Codex, Grok Build, Mistral Vibe (since 2026-09-15), oh-my-pi (since 2026-09-25) and Antigravity CLI (since 2026-09-30). On any other provider the pane stays on the terminal, and the history panel lists only the messages you sent (This agent's CLI does not expose a transcript yet: only the messages you sent are listed.). Reasoning blocks are shown when the CLI saved them, and marked Reasoning not saved by the CLI otherwise.

The clickable question card is Claude Code only: it renders Claude Code's question tool (AskUserQuestion), the one CLI that records a question with options in its transcript. Codex records no such question, and the other CLIs record no question card either.

Permission prompts (since 2026-10-01): when Claude Code asks "Do you want to proceed?" or Codex asks "Would you like to run the following command?" / "Would you like to make the following edits?", the pane no longer drops back to the terminal. A card floats above the composer with the question, Allow, Deny and More choices in the terminal (for the CLI's other rows, such as "Yes, and don't ask again"). Allow types the CLI's own "allow once" key (1 for Claude Code, y for Codex), Deny types Esc, only after checking the prompt is still on screen. Antigravity's approvals and every other CLI prompt (model picker, plan, trust folder) still borrow the pane and give it back once answered. The answer travels through the CLI's own dialog: AgentsRoom replays the keystrokes a human would type, so the CLI sees a normal answer.

Mistral Vibe is a special case: its interface always runs full screen and has no plain-scrollback mode, so a long turn looks frozen in the terminal until the final repaint. The conversation view reads the session log Vibe writes in its own home folder, appended after every model turn, which makes it the live progress feed of a Vibe agent. Vibe does not announce its session id while it runs, so AgentsRoom attributes the newest session started in the agent's working directory after the console opened; the view stays empty until Vibe has saved its first turn.

oh-my-pi: AgentsRoom picks the session file of an oh-my-pi agent itself when it starts it, so the view knows where the conversation is from the first second, with nothing to guess even with several oh-my-pi agents in the same folder. oh-my-pi prints inline (no full-screen mode), so the terminal stays the default and the conversation view is a switch. When you rewind a session inside oh-my-pi (/tree, /branch), only the branch you are on is shown. An oh-my-pi agent started from a remote SSH host has no view (its session file lives on the host).

Antigravity CLI (agy, the Gemini models): the view reads the transcript agy writes for every conversation in its own folder (~/.gemini/antigravity-cli/brain/). agy saves the model's reasoning in clear, so the reasoning of each answer is shown. The view fills once agy has saved the first turn (within about fifteen seconds): AgentsRoom recognises the conversation the agent's own process holds open (macOS, Linux), or on Windows the one its launch message started. A conversation started by typing /clear inside agy is followed on macOS and Linux; on Windows the view keeps the previous one until the agent is restarted. An Antigravity agent started on a remote SSH host has no view.

Mobile

Present. The phone's agent console opens on the terminal stream and the dock's Show the conversation switches to the same transcript, read by the desktop and sent encrypted; the choice is remembered per agent while the app is open, like on the desktop. The thread looks the same: neutral bubble on the right for you, face and name for the agent, tool calls grouped under N tool calls (tap to fold, tap a line to see it in full), the same question card with the same words. Answering from the phone goes through the desktop, which types the answer into the CLI exactly as a click on the desktop card would; the card is clickable only while the agent's console is open on the desktop, otherwise it reads Answer this question in the terminal.

Phone-only differences: the time of your bubble is always visible (no hover), there is no hover action row, no selection bar and no read-aloud (copy through the native text selection), and no floating "working" line since the phone's conversation is read-only and sending stays in the terminal screen. The "tool calls" setting is not ported: the phone always shows the tool groups, has no toolbar filter and no eye button, and ignores the desktop, project and agent choice. Grok, Mistral Vibe, oh-my-pi and Antigravity answers are readable there since their transcript readers exist. When a CLI runs full screen, the console shows This agent runs full screen, which is hard to show here. with an Optimize for mobile button that relaunches the same session in the CLI's plain-scrollback mode; that button exists for Grok only, because Mistral Vibe has no such mode.

Limits

  • No transcript, no view: providers other than Claude Code, Codex, Grok Build, Mistral Vibe, oh-my-pi and Antigravity CLI cannot open it. Question cards: Claude Code only.
  • The question card drives Claude Code's own dialog with keystrokes, checked against Claude Code 2.1.274 and 2.1.276. If the CLI changes that dialog again, the card still shows the question but says The answer did not reach the agent. Answer it in the terminal.; the terminal is always there as the fallback. A multiple-choice question offers no Other free-text row.
  • Mistral Vibe: no session resume, so the attributed session id lives only as long as the console is open; a second live Vibe agent in the same project folder is not attributed, to avoid mixing two conversations.
  • The remembered per-agent choice lives in memory only; restarting the app returns to the configured default.
  • The view reads the CLI's own file, so an answer the CLI did not persist (some reasoning, some full-screen dialogs) cannot appear.

Common questions

  • How do I answer a question from the Conversation view? Click an option on the card. A single-choice question goes out on the click; otherwise pick your answers (or type one under Other: write your own answer) and click Submit answers. The card turns to Answered once the CLI records it. Works with Claude Code; on the phone the console must be open on the desktop.
  • I ticked several options and clicked Submit answers, but the terminal dialog stayed open with the boxes ticked. Fixed on 2026-09-18. Claude Code 2.1.276 changed its multiple-choice dialog: Enter on a row now ticks or unticks it, and only the button under the last row validates. The card now moves to that button before confirming, on the desktop and from the phone. If it happens again, answer in the terminal; the card says so when its answer did not go through.
  • Where do I see the detail of a tool call? In the N tool calls block under the answer: each line is cut to one line, click it (Show in full) to read it whole, click again (Back to one line) to fold it. The toolbar filter hides every tool call at once when you only want the prose.
  • How do I stop seeing tool calls for good? Hover a N tool calls header, click the eye button (Hide tool calls…) and pick Only for <agent name>, For every agent of this project or Everywhere. Or set Tool calls in the conversation view to Hidden in Settings > Terminal, Project settings > Terminals or Edit agent. The toolbar's Hide tool calls button only lasts while the pane is open.
  • I hid the tool calls and want them back. Click Show tool calls in the toolbar for this pane, or set the field back to Shown (or Inherit) in the settings screen where you hid them. Changing the setting anywhere also clears the toolbar's temporary choice.
  • Why does my pane keep dropping back to the terminal? The CLI asked something only its own interface can show (model picker, plan, trust folder, an Antigravity approval). Answer it and the conversation comes back by itself. A question with options, and a Claude Code or Codex permission prompt, no longer do this: they stay in the thread as a card.
  • The Conversation view stayed empty and my Claude agent closed by itself (home folder). Fixed on 2026-10-01: Claude asks "Accessing workspace… Yes, I trust this folder" at every launch in your home folder, with "No, exit" selected, and a message sent at that moment picked it. The view now shows a card The agent asks to work in this folder with Trust this folder, and a message typed meanwhile is held instead of closing the CLI.
  • Can I allow a command from the Conversation view? Yes, with Claude Code and Codex: the card The agent is waiting for your answer shows the question with Allow and Deny. For "Yes, and don't ask again", click More choices in the terminal. If you clicked Terminal yourself, the pane respects that until you switch again.
  • The Copy button of a message, or Copy in the selection bar, does nothing (seen on Linux). Fixed on 2026-09-26: when the system refuses the direct clipboard write, the copy now goes through a fallback, as the terminal already did. Update AgentsRoom.
  • My selection disappears before I can copy it while the agent is working. Fixed on 2026-09-28: the thread no longer rebuilds its text on every refresh, so a selection stays put while the agent writes. Copy it with Copy in the selection bar, Ctrl+C (Cmd+C on macOS), or the terminal shortcuts Ctrl+Shift+C and Ctrl+Insert, which now work in the Conversation view too.
  • Can I make every agent open on the conversation? Settings > Terminal > Conversation view > Always, or per project under Project settings > Terminals.
  • I set Conversation view to Always and my Claude agents still opened on the terminal. Fixed on 2026-09-22: the global choice now applies to Claude agents created from the new agent dialog, and the per-project choice is no longer ignored.
  • The agent asked a question with options and the pane went to the terminal instead of showing the card. Fixed on 2026-09-22: on a slow disk or a long transcript the pane handed itself to the terminal before the question was read back. It now waits for that read, so the card shows in the thread.
  • The view is empty on Copilot / OpenCode / Cursor. Those CLIs do not write a transcript AgentsRoom can read; use the terminal.
  • My Antigravity (Gemini) agent's Conversation view only showed my own messages, never its answers. Fixed on 2026-09-30: AgentsRoom now reads the transcript agy writes, answers, tool calls and reasoning included, on the desktop and the phone. Update AgentsRoom; the view fills after the agent's first saved turn.
  • My Mistral Vibe agent looks stuck in the terminal. Vibe paints its whole interface full screen, so nothing scrolls until the turn ends. Open the Conversation view (or Show the conversation on the phone): it follows the session log turn by turn.
  • Does switching views interrupt the agent? No. The CLI never notices; only what you see changes.

Related