External Agent Sessions
CrispyVibe discovers agent conversations created by Codex CLI, Claude Code, Kiro CLI, OpenCode, and Pi and shows them in a read-only view inside the Conversations panel. If these tools have sessions on your machine, CrispyVibe lists them without an import or configuration step.
Where to find them
Open the Conversations side panel. It has two tabs:
- ACP — your CrispyVibe 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. Directory sections start collapsed so a long history doesn’t flood the sidebar. Click anywhere on a section header (not just the chevron) to expand or collapse it. Each row shows the provider brand icon, session title, relative timestamp, and inline actions.
Use the filter chips at the top to narrow by provider: All, Codex, Claude Code, Kiro CLI, OpenCode, or Pi.
Searching
Type in the search field. Search matches the session title for every provider, plus the transcript body for Codex, Claude Code, Kiro CLI, and Pi sessions. OpenCode sessions match by title only. Search does not match the working-directory path, so searching vibe does not return sessions solely because they live under a /crispyvibe/ folder. A body match shows a context snippet; a title-only match shows no extra snippet.
While a search is active, directory sections that contain matches expand automatically so results and snippets stay visible. Clear the search to return to the sections you had expanded before.
If one Kiro conversation can’t be read, CrispyVibe reports a warning for it and still shows matches from your other conversations.
Previewing a session
Click any row to open the read-only preview. Its header shows the provider, project path, session ID, and timestamps. The preview also includes the source file path and up to 200 transcript entries 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) — CrispyVibe 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
CrispyVibe reads each provider’s sessions without modifying them, and rescans when you click the refresh (↻) button in the search bar:
| Provider | Location |
|---|---|
| Codex CLI | ~/.codex/sessions/ |
| Claude Code | ~/.claude/projects/ |
| Kiro CLI | The session list reported by your installed kiro-cli (see below) |
| OpenCode | ~/.local/share/opencode/opencode.db (read via a read-only snapshot copy) |
| Pi | ~/.pi/agent/sessions/ |
Kiro CLI sessions
CrispyVibe asks your installed kiro-cli for its session list, so both current and classic Kiro histories appear. Session content is read from these locations:
- Current sessions —
~/.kiro/sessions/cli/, or$KIRO_HOME/sessions/cli/whenKIRO_HOMEis set. CrispyVibe reads this folder directly if thekiro-clisession list is unavailable. - Classic sessions —
~/Library/Application Support/kiro-cli/data.sqlite3, ordata.sqlite3insideKIRO_DATA_DIRwhen it’s set. CrispyVibe reads a temporary copy instead of modifying the original database.
Sessions that CrispyVibe itself creates in Kiro CLI to generate conversation titles are hidden from the list. The hiding rule does not apply to your own conversations, even if they share a title with a hidden one.
⚠️ Note: Kiro session formats other than current and classic are skipped and reported as a diagnostic.
💡 Tip: If a session shows a warning icon, some events in its file couldn’t be parsed. The remaining events are still displayed. Expand the diagnostics section at the bottom of the list (or check Developer Tools) for details.
Troubleshooting
| Issue | Solution |
|---|---|
| No external sessions is shown | Confirm you’ve used a supported CLI on this Mac and that its session location exists. Click refresh (↻) to rescan. |
| Kiro sessions are missing | Confirm kiro-cli is installed and runs from your PATH. If you store Kiro data in a custom location, make sure KIRO_HOME or KIRO_DATA_DIR is available to CrispyVibe. |
| External sessions unavailable with “External session helper is unavailable.” | The bundled helper is missing, which can indicate a damaged installation. Reinstall CrispyVibe. |
| A section won’t collapse while searching | Matching sections stay expanded during a search. Clear the search field to collapse them. |
Known limitations
- External sessions are read-only and cannot be imported as native CrispyVibe conversations. Resume them via Open in Terminal or the copied command.
- Previews show at most 200 transcript entries.
- Sessions aren’t scoped to the current VibeSpace; all local sessions are shown.
- Search has no persistent index and re-reads sessions each time.