Resume AI Sessions
Browse past conversations from every agent and pick up exactly where you left off — including a whole team at once.
Your agents keep their conversations on disk. Resume AI Sessions reads them, shows you what each one was about, and starts a terminal that continues it.

Opening it
Session in the top bar, or the Resume entry in the command palette.
Sessions are listed most recent first and load progressively, so a machine with thousands of conversations still opens instantly and fills in as you scroll.
What you see per session
- The agent it belongs to, with its logo
- The conversation title
- A preview of the recent messages
- When it was last active
- The project or workspace it ran in
Select one to read the full conversation before deciding.
Supported agents
Claude, Codex, Gemini, Cursor, Antigravity, Cline, Grok, Hermes, Amp, OpenCode, Qwen — plus any custom agent presets and observed agents you have configured, with the correct names and icons.
Cursor conversations are listed with their titles and previews, and resuming one continues it like any other agent. Antigravity sessions show their workspace, title, recent messages, and full conversation detail.
An agent that has no separate editable memory store says so plainly rather than showing an empty generic view.
Resuming a whole team
Sessions that ran as one linked team are marked as such, and a banner offers to bring every member back in one confirmation. Members carry a team chip so collaborative sessions are easy to tell from solo ones.
Once the terminals are running, Mission Control's Resume team reconnects the links between them.
Already-open sessions
Resuming a conversation that is already open takes you to the existing terminal, marked with an Open badge, instead of creating a duplicate tab. This works on the desktop and in Remote Control.
Changing agent on resume
You can resume a conversation into a different agent — hand a Claude session to Codex for a second opinion, for example. The transcript travels; the new agent picks it up from there.

Customizing the resume command
If your agent needs a specific invocation to resume, you can edit the command 1DevTool uses per agent.

Adopting sessions started elsewhere
Conversations you started outside 1DevTool — in Ghostty, iTerm, or an editor's terminal — are discoverable too, so a session does not have to have begun here to be resumable here.
Terminals no longer borrow a session that is not theirs: a Claude or Codex conversation running in the same folder outside 1DevTool cannot be mistaken for the terminal you opened, and later evidence repairs an incorrect binding.
Related
- Session Persistence — what survives a quit without resuming
- Agent Teams & Swarms
- Run an AI Agent