The session view
Anatomy of a running session: transcript, tools, file edits, terminal, and the composer.
- Desktop
- Web Portal
- Mobile
Once a session is running, the center pane is where you watch the agent work. The layout is the same across desktop and portal; mobile adapts to a single-column view.
The three panes
The session view has three main regions:
Sessions sidebar — on the left. Lists every session on the current host, sorted by recent activity by default (other sort options include project, agent, status, name, and changes). Each item shows the session title, the agent it’s running, current status, and live counts for unsaved changes if you’re editing files.
Transcript — the center. The full conversation, interleaved with tool calls, file edits, and command output. Long blocks (file diffs, command output) are collapsible. New events stream in at the bottom; the view auto-scrolls unless you’ve scrolled up.
Composer — the bottom strip. The text area where you send a follow-up. Drop files in to attach them, or use the / menu to switch the agent or insert a slash-command the agent supports.
Status dots
Each session has a colored dot:
- Teal pulsing — running, the agent is actively producing output.
- Teal solid — ready or completed.
- Amber — waiting for your input, or interrupted.
- Violet — paused.
- Gray — stopped.
- Red — failed. The last error message is shown when you hover.
What you’ll see in the transcript
Every event from the agent shows up as a distinct block:
- Messages — the agent’s reasoning and replies. Markdown is rendered.
- Tool calls — when the agent invokes a tool (read file, run command, search, etc.). The arguments and result are both visible. Risky tools trigger an approval card; see Permissions and approvals.
- File edits — shown as a unified diff. Click to open the file in the built-in editor and apply, modify, or revert.
- Command output — standard output and error from shell commands the agent ran.
- Questions — if the agent needs information from you, a question card pins to the top of the transcript with the choices. Answers send through encrypted; the relay never sees the text.
Sending follow-ups
Type in the composer and press Enter to send. Shift+Enter inserts a newline. The agent picks up the new message on its next turn.
You can also drop a file or paste an image into the composer. Both are attached to the message and (for images) sent through the relay encrypted.
The session header
Above the transcript, the header offers:
- Interrupt — cancel the current turn so you can redirect the agent without killing the subprocess.
- Stop — end the session cleanly.
- An overflow menu for renaming and other session controls.
Side panels for git, files, and terminal can be opened from the right rail of the session view rather than from the header.
On mobile
Mobile shows the chat / transcript by default, and gives you tabs to switch to git, files, or terminal side panels for the same session. The phone layout shows one panel at a time; tablets in landscape can show two.
Compose a follow-up by tapping the message bar at the bottom. Voice input is supported; see Mobile > Voice input.
On the portal
The portal layout matches desktop. Some heavier features (full editor, file browser, multi-pane git) are linked from the session toolbar and open as right-side sheets so the transcript stays visible.