The session area
The session area shows the selected session: the top bar, its terminal or transcript and your last message to it, along with its diff and preview panes when open.
The top bar
Section titled “The top bar”Click the harness conversation id in the top bar to copy it.


On the right, the git change counts open the diff, and toggles such as Auto start apply to draft, bug and refine sessions. Then its actions, shown only when they apply:
- Add agent (⌥AltZ) starts another agent in the same working copy, with a prompt you type, so it picks up the work in progress. It is offered while the session is still working.
- VS Code (⌥AltX) opens the session’s working copy in VS Code.
- Restart ends the agent and resumes its conversation in a fresh process, after asking. Its dropdown has Start over, which discards the conversation and starts a new one with only the session’s first prompt.
- Retry appears on a run session, running the command again, and on a backlog run that didn’t come back after the daemon restarted, starting it again.
- Star pins the session to the top of the sidebar. For a backlog run, the star belongs to the item, so it carries over to the item’s next session.
- Transfer, on a backlog run, moves the run to a linked node that has the repo, or from one back to this node. Uncommitted and unpushed changes go with it.
- Done (⌥AltC), on a backlog item’s session, marks the item done and ends the session, along with any dev server started from it. Hold ⇧Shift as you click it or press Enter to skip the confirmation.
- × closes the session, as on its card.
Pull request, review and server buttons appear for sessions that have them.
Commands an agent runs to act on its own card, such as /close and /rename, are on Session commands.
Skill suggestions
Section titled “Skill suggestions”Typing a word starting with / in a box whose text goes to the agent lists the skills and commands that match it. ArrowUp and ArrowDown move through the list, Tab or Enter puts the highlighted one in your text, and Esc closes the list. You can also click one.
The terminal
Section titled “The terminal”The terminal is the agent itself, such as Claude Code, running live. You give it prompts, answer its questions and approve its permission requests here, as you would in Claude Code in your own terminal. For a run session, it shows the command’s output.
- ⌘CtrlC copies the selected text. With nothing selected, it reaches the session as an interrupt.
- ⌘CtrlV pastes.
Claude (SDK) sessions
Section titled “Claude (SDK) sessions”A session on the Claude (SDK) harness has no terminal. Its live transcript takes the terminal’s place, with a composer under it for your messages, and its top bar carries an SDK badge.


In the composer:
- Enter sends. ⇧ShiftEnter, or Enter straight after a
\, adds a line break. - While the field is empty after a turn, it shows the prompt Claude expects you to send next. Tab or ArrowRight fills the field with it. On the phone, tap the suggestion above the reply field.
- Stop, or Esc, interrupts Claude’s turn.
- A message sent while Claude is working is queued until the turn ends. Hover a queued message to Remove it, or Edit it to take it back into the composer.


Click empty space in the transcript to put the cursor in the composer.
🙄 on Claude’s last reply asks it to say the same thing again, much more concisely.
Select text in the transcript to comment on it, as in the diff.
Shell commands
Section titled “Shell commands”Start a message with ! to run it as a shell command in the session’s working copy, as in Claude Code’s bash mode. Its output streams into the transcript without starting a turn, and is attached to your next message to Claude. Backspace in an empty field leaves shell mode.


Stop on a running command’s row, or Esc while it runs, stops it and keeps its output so far. × on a finished command’s row drops its output so it isn’t attached.
Your last message
Section titled “Your last message”Your last prompt to the session shows over the terminal, cut to one line. Hover to read all of it, or click to pin it open. Scrolling over it steps back through your earlier prompts, with a counter showing which one you’re on.
Transcripts
Section titled “Transcripts”Clicking an entry on the sidebar’s History tab shows its transcript here in place of the terminal. Click a tool call in a transcript to see its full command or path.
