02 · RESUME
Resume an old conversation.
Find the right context in Swob, then continue in a supported client. Being able to read a transcript does not guarantee that its original agent can resume it.
From reading to working
- Find and open the session in Swob
Use the search workflow if you do not remember its ID. Read the last relevant turns and confirm the source and project. A logical conversation may include several physical continuations, so its displayed history and resume target can differ.
- Choose a supported Resume action
The usual path returns to that source’s terminal client. Install the original client and make sure the intended project and client configuration are available. Review any target, permission or recovery information before starting.
- Confirm the conversation in the destination
Check the project and prior messages before sending a new prompt. A terminal window opening or an App launching is not proof that the selected conversation resumed successfully.
Which clients can resume?
This table describes Swob’s v1.3.1 capability declarations and action code. Client installations and upstream behavior can change. “Available” describes a supported path, not a success guarantee for every stored conversation.
| Session source | Terminal path | Desktop boundary |
|---|---|---|
| Claude Code | Available: source-aware Claude Code resume. | Claude Desktop import is experimental and opt-in. It can rewrite a transcript; it is separate from continuing in Claude Code. |
| Codex | Available: Codex resume. | Codex App can receive a Codex thread link. It requires a valid Codex target and a client that recognizes it; it does not convert another agent’s conversation. |
| Cursor | Available for supported Cursor agent histories. | No verified per-session desktop deep link in this release. |
| OpenCode | Available for supported OpenCode histories. | No verified per-session desktop deep link in this release. |
| ZCode | Unavailable: no public CLI Resume path. | Experimental App/workspace opening only. It does not jump to the selected historical conversation. |
| Pi and CC-Mirror | Experimental mappings; not independently audited as reliable source-level resume paths. | No verified source-specific desktop session entry. |
Detection-only sources in v1.3.1 can appear as file metadata without readable message bodies. Do not treat detection or an experimental command mapping as verified resumability. For release details, see the versioned capability definitions. The current source matrix covers newer development code and may exceed the public installer.
Example: return to a Codex fix
Suppose you find the redirect discussion in the fictional sample-shop project. Open it in Swob and confirm that it came from Codex. Choose its Codex resume path, then check that the destination shows the expected project and history. If it opens an empty thread, stop there and investigate the target instead of assuming the old context was restored.
A Claude Code conversation about the same project remains a different source. Reading both conversations in one library does not make their native session formats interchangeable.
If the original files are gone
A readable archive and a resumable source are different things. Swob checks whether the source can be recovered when you actually invoke Resume. Where recovery is supported and sufficient archive data exists, that action can restore source files before launching the client.
Copy Resume Command and Resume Audit are read-only with respect to source recovery. Copying a command does not restore missing files, and an audit is not a repair. Keep your backups and read any recovery error before trying again.
Do not delete the archive, replace session IDs or move source files just to make a disabled action appear available. Use the displayed reason to identify what is missing.
If Resume fails
- Client unavailable: check that the intended source client is installed. Review the generated command and working directory; do not substitute a different agent’s command.
- Conversation unavailable: check the source, target ID and original project. A transcript visible in Swob may still be missing the files or client state needed to continue.
- Only the App opens: confirm whether the action promises a session or only a workspace. ZCode’s workspace-only behavior is a known boundary.
- Experimental action missing: use the supported terminal route where available. Claude Desktop import requires an explicit opt-in and does not support non-Claude Code histories.
- Recovery blocked: keep the archive and report the error category, Swob version and source. Avoid posting transcripts, credentials or private paths in a public issue.
For additional details, consult troubleshooting (中文), or contact support@swob.app.