skl list, query, view, and continue come from txcript, Skillsync's open-source transcript library. txcript owns session discovery, parsing, conversion, and the compatibility matrix.
For current format internals and support added after your installed skl release, use the txcript documentation on GitHub.
Supported local sources
Current skl releases can discover sessions from these sources:
| Source | Agent ID | Default location | skl sync |
|---|---|---|---|
| Claude Code | claude_code | ~/.claude/projects/ | Yes |
| Cowork | cowork | Claude app data under local-agent-mode-sessions/ | Yes |
| Codex | codex | ~/.codex/sessions/ | Yes |
| OpenCode | opencode | ~/.local/share/opencode/opencode.db | Yes |
| pi | pi | ~/.pi/agent/sessions/ | Yes |
| Campfire | campfire | ~/.campfire/agent/sessions/ | Yes |
| Cursor CLI | cursor | ~/.cursor/chats/ | Yes |
| Cursor desktop | cursor_desktop | Cursor's user-data directory | No |
| Grok CLI | grok | ~/.grok/sessions/ | Yes |
| Hermes Agent | hermes | ~/.hermes/state.db | Yes |
| Amp | amp | ~/.local/share/amp/threads/ | Yes |
| Antigravity | antigravity | ~/.gemini/antigravity-cli/ | Yes |
Use the IDs above with --from and --with. Friendly aliases such as claude are also accepted, but canonical IDs are more reliable in scripts.
The last column is the set of sources Skillsync accepts from skl sync. Syncing any other source fails locally before a request is made.
Capabilities differ by source
Discovery, listing, search, and viewing work for sources with an available backing store. Continuing into another agent additionally requires txcript to write that agent's native format and the target agent to support resuming or importing it.
Amp and Hermes are source-only in the current CLI and cannot be continuation targets. Simple is an interchange document rather than a discovered local agent:
skl continue ./session.json --with claude_code
skl continue - --with codex
Cross-agent continuation creates a new session. The original transcript is never modified or removed.
Local by default
The CLI reads local stores and writes local target sessions when you run continue. A session leaves this machine only when you run skl sync on it; see /docs/session-sync.
Two other boundaries are worth noting:
skl mcpreturns local session data to the MCP client that invokes its tools. It has no sync tool.- Search uses a local SQLite cache containing session-derived searchable text. The cache lives in the platform cache directory and can be recreated.
Diagnose discovery
Start with a broad list, then narrow it:
skl list
skl list --from opencode
skl list --cwd /path/to/project
If a source is missing, confirm that its default store exists and that the current user can read it. See /docs/troubleshooting for common causes.