External Agent Sessions
Crispy discovers agent conversations created by external CLI tools — Codex CLI, Claude Code, Kiro CLI, OpenCode, and Pi — and shows them in a read-only view inside the Conversations panel. There’s nothing to import or configure: if you’ve used any of these tools on your machine, their sessions appear automatically.
Where to find them
Open the Conversations side panel. It has two tabs:
- ACP — your Crispy-owned agent conversations (see Conversation History).
- Terminal — external CLI sessions discovered on your machine, grouped by working directory.
Switch to the Terminal tab to browse discovered sessions.
Browsing sessions
Sessions are grouped into collapsible sections by working directory, sorted alphabetically, with the most recently active first inside each group. Tap anywhere on a section header (not just the chevron) to expand or collapse it. Each row shows the provider brand icon, the session title, a relative timestamp, and inline actions — the same compact styling as the ACP thread list.
Use the filter chips at the top to narrow by provider (All, Codex, Claude Code, Kiro).
Searching
Type in the search field. Search matches the session title for every provider, plus the transcript body for file-based providers (Codex, Claude Code, Kiro, Pi). It does not match the working-directory path — so searching vibe no longer returns every session that merely lives under a /crispyvibe/ folder. A body match shows a context snippet; a title-only match shows no extra snippet.
Previewing a session
Click any row to open the read-only preview, which shows the provider, project path, session ID, and timestamps in the header, the source file path, and the full transcript with role labels (User, Assistant, System, Tool). External sessions can’t be edited.
Resuming a session
Two ways to continue a discovered session in its original tool:
- Open in Terminal (inline action or right-click) — Crispy opens a new terminal tab at the session’s working directory in the focused project and runs the provider’s resume command for you.
- Copy Resume Command (header button or right-click) — copies the provider’s native resume command so you can paste it yourself:
| Provider | Resume command |
|---|---|
| Codex | codex resume <session-id> |
| Claude Code | claude --resume <session-id> |
| Kiro CLI | kiro-cli chat --resume-id <session-id> |
| OpenCode | opencode --session <session-id> |
| Pi | pi --session <session-id> |
The right-click menu also offers Copy Source Path.
Where sessions come from
Crispy scans each provider’s default location (read-only) and re-scans when you click the refresh (↻) button in the search bar:
| Provider | Location |
|---|---|
| Codex CLI | ~/.codex/sessions/ |
| Claude Code | ~/.claude/projects/ |
| Kiro CLI | ~/.kiro/sessions/cli/ |
| OpenCode | ~/.local/share/opencode/opencode.db (read via a read-only snapshot copy) |
| Pi | ~/.pi/agent/sessions/ |
💡 Tip: If a session shows a warning icon, some events in its file couldn’t be parsed — the rest is still displayed. Expand the diagnostics section at the bottom of the list (or check Developer Tools) for details.
Known limitations
- Read-only — external sessions can’t be edited or imported as native Crispy conversations; resume them via Open in Terminal or the copied command instead.
- Previews show at most 200 transcript entries.
- Sessions aren’t scoped to the current VibeSpace — all local sessions are shown.
- No persistent search index — search re-parses files each time.