Stopping an agent ends its running CLI process but keeps the agent in Solo. If Solo has captured the provider's session ID, you can resume that exact conversation later instead of starting over.
Stop an agent
There are two ways to stop a running agent:
- Right-click the agent in the sidebar and choose Stop.
- With the agent selected and the sidebar focused, press
Susing the default shortcut.
Solo asks for confirmation by default. You can suppress future stop and restart confirmations for that agent from the confirmation prompt.
After the process stops, the agent stays in the sidebar. Stopping does not remove files the agent changed or undo work it already completed.
How saved sessions work
Each supported agent provider gives a conversation its own resume ID. Solo detects and validates that identity, then stores the full ID with the agent row. Providers that use UUIDs keep the complete UUID; the four-character suffix shown in some menus is only there to help you recognize the conversation.
With the Saved session terminal pin enabled, the top-right badge shows Session saved when Solo has an exact resume ID. Open it to see the provider, resume ID, and the command Solo will use. You can copy the full ID or command from there.
If the badge says Resume unavailable, open it and choose Check again. Solo makes one bounded attempt to recover the ID from the current run. It will not save an ID when the available evidence is stale, invalid, or ambiguous.
Resume support depends on the agent tool:
| Agent | Saved identity | Exact resume | Session picker |
|---|---|---|---|
| Claude | UUID | Yes | Yes |
| Codex | UUID | Yes | Yes |
| Amp | Thread ID | Yes | Yes |
| Gemini | UUID | Yes | No |
| OpenCode | Session ID | Yes | No |
| Copilot | UUID | Yes | Yes |
| Kimi | Session ID | Yes | Yes |
| Antigravity | Conversation UUID | Yes | No |
Custom agent tools do not get automatic resume actions unless Solo recognizes them as one of these built-in tool types.
Resume the last session
Once an agent is stopped and has a saved resume ID, you can continue it in any of these ways:
- Select the stopped agent and choose Resume last session in the terminal pane.
- Right-click it and choose Resume last session (xxxx). The suffix is the last four characters of the saved ID.
- Open the Session saved control and choose Resume session.
- Start the stopped agent normally and choose Resume when Solo asks whether to resume or start fresh.
Solo passes the full saved ID to the provider. Resuming keeps that same conversation associated with the agent row.
Resume a different session
For tools with a session picker, right-click a stopped agent and choose Choose session to resume.... Solo launches the provider's own picker so you can select a different conversation.
Once the provider identifies the selected conversation, Solo saves that ID as the agent row's current resume ID.
Start a new session
Choose Start new session in the stopped-agent pane, or choose Start fresh when Solo asks how to start the agent. The new run does not reuse the previous conversation, and Solo replaces the row's saved resume identity when it captures the new session.
Starting fresh does not delete the old conversation from the provider's history. If the tool has a session picker, you may still be able to choose it later.
Stopping vs. removing
Stopping keeps the agent row and its saved resume identity. Remove agent removes the row from Solo and deletes Solo's association with that saved session.
Solo stores the provider's resume ID, not a permanent copy of the conversation. Whether a conversation can still be resumed ultimately depends on the provider keeping it in its own history.
If you are switching to a different agent or provider instead of resuming the same conversation, capture the project state first with the long-running work handoff.