Parallel sessions

Run several agent sessions at once, switch between them, and see which one needs you.

Running more than one agent

Every session is a pane, and panes run at the same time. Each session has its own agent process, transcript and queue.

Switching between agents without losing your place

The sidebar lists your workspaces and their sessions. You can show only the current workspace or all of them, filter the list, pin sessions, and rename any session (clear the title to restore the automatic one).

⌘KCommand palette: sessions, workbench commands, and full-text transcript matches in one list
⌘1…through ⌘9 — jump to the Nth group (⌘9 is the last one)
⌥1…through ⌥6 — focus pane N inside the current group
⌘⌥←Cycle focus between panes (⌘⌥→ the other way)
⌃⇥Cycle groups (⌃⇧⇥ backwards)

In ⌘K, sessions waiting on you come first, then running ones, then the rest by recent activity. Typing searches session titles; from two characters on it also searches transcript text. Spaces separate terms that must all match, and "double quotes" keep a phrase together. Transcript matches are grouped by workspace.

Reading a running session

Each turn shows the agent's thinking, its tool calls and their results, any sub-agents it delegated to, and its plan. These are collapsed by default; expand them to see the detail.

What the transcript surfaces

Thinking / tool calls: The reasoning and every tool invocation with its result, expandable inline. Long output collapses with its character and line count.
Sub-agents: A delegated unit of work shown as its own block: the brief it was handed, the trail of what it did, the result it handed back.
Plan: The agent's own step list with live progress — how many steps are done, in progress, or not started.
Live usage: A per-turn line: how long the reply took, and the context used as a percentage and in tokens.
Notes and status: Give a session a status (Inbox, Active, Review, Done, Parked), record what it produced (Answer, Proposal, Implementation, Partial, Blocked, Conversation), and leave yourself a note.

Knowing which session needs you

Each session shows its current state. When a session has had no output for a while, it shows why.

Running: A turn is in flight.
Needs you: The agent asked a question, requested a permission, or needs a decision. Answer in place; the session does not restart.
Queued: Your next prompts are lined up behind the current turn.
Stalled: Nothing has moved for a while. The reason is shown: quiet for N seconds, a named tool still running, awaiting the model, or the process merely alive.
Done / failed: The turn finished, ended without a reply, or ended with an error.

A group tab pulses when a session inside it is running, and pulses differently when one is waiting on you.

Answering an agent mid-task

When an agent needs a permission or a choice, the question appears in the session, numbered if there are several. Pick one of its options, type your own answer, or skip it. The agent continues from where it paused.

From the command line: ui-cli answer --prompt-id ID --action select|text|skip|cancel.

Context, compaction, and long sessions

The ring beside the send button shows how full the context window is now, and each turn's footer shows what that turn used. When the window fills, the conversation is compacted (summarized to free room) automatically. To compact on demand, hover over the ring and choose Compact conversation, or run /compact from the composer's command list. The transcript records each compaction and how much it freed.

Ending and cleaning up sessions

Deleting a session lets you choose how much to remove. A deletion cannot be undone.

By default only the Mirasim record is removed. The agent CLI's own transcript stays, so you can still resume the conversation outside Mirasim.
"Also delete agent transcript" removes the agent's own jsonl / rollout files too, so the conversation is fully gone.
"Also remove this worktree" applies to a session that ran in one. Git refuses while the worktree has uncommitted changes.

A running session has to be stopped before it can be deleted. To continue a conversation in the agent's own CLI, choose "Copy resume command" in the session menu.

Something wrong or missing on this page? Tell us