Languages (16)
English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Español · Português (Brasil) · Français
Deutsch · Italiano · Русский · Türkçe · Tiếng Việt · Bahasa Indonesia · हिन्दी · العربية
Remember the work, but not which CLI held it? Search saved conversations across Copilot CLI, Claude Code, Codex CLI, Qwen CLI, Gemini CLI and Kimi. If you already know the provider and session, its native history may be enough.
Concept illustration with fictional rows, not an app screenshot. English labels.
- Find lost work: one search across retained CLI histories, including conversations started outside this TUI.
- Continue the original conversation: reopen its saved context through the installed provider CLI.
- Find its running Windows tab: attempt matching Windows Terminal tab focus; Linux/macOS users switch manually.
Have saved history, an installed/authenticated provider CLI reachable through its configured command, and an accessible original working directory. Use an interactive terminal. Default launchers: Windows wt (fallback cmd), Linux gnome-terminal, macOS osascript with Terminal; configure another launcher if unavailable.
Before launch: default remote grouping can automatically send session titles and working directories to a hosted service after discovery. It has no published third-party API contract. Core + wordmatch avoids that remote grouping, not provider-CLI networking. The optional semantic plugin may download models at initialization; start with Core without that plugin.
- Download the complete Core archive for your OS/CPU from Core archive filenames, not the source archive. Extract everything together: binary,
providers/,prompts/, generatedconfig.toml.example. Verify the exact asset digest; a match is not a signature or safety guarantee. Respect OS/org controls. For attestation-enabled releases, verify GitHub build provenance before extracting. This is not Windows code signing; older releases such as v0.3.2 are not retroactively attested. - For a fresh install, copy the generated example to
config.tomlbeside the binary; do not overwrite existing settings or rename the source template. In the copy, uncomment both# [grouping]and# engine = "remote", then change the value:
[grouping]
engine = "wordmatch"Keep other grouping options commented. If [grouping] already exists, change its engine rather than adding a duplicate. Check state_dir and command; save before launch. wordmatch is word overlap, not local AI.
- In the extracted folder, run:
# Windows PowerShell
.\agent-session-tui.exe# Linux/macOS
./agent-session-tui- Wait for the list. Press
/, type a literal title/project fragment from your own history, and inspect matches with↑/↓. Verify provider, title and directory; choose Resumable, then pressEnter. Expected: its CLI opens the selected conversation to continue. Search can miss; tested native CLI versions are unknown. coverage and evidence.
For Running/Waiting/Idle, Enter attempts Windows matching-tab focus, not process attachment. Repeating Enter promptly on the same running session can force resume instead; verify before doing so. Windows route.
No result? Check saved history/enabled provider/state_dir; for launch failures, check authentication, cwd and launcher. Troubleshooting.
Exit: Esc cancels search; then q exits, or Ctrl+C in the list or search without deleting histories or stopping other CLIs. Kill is unimplemented. Update, restore and removal.
Operating guide · Recorded demo · Contributing · Security · MIT license
Earlier section links → operating guide
Agent CLI Session TUI — Find an old coding-agent conversation and resume it
Private first search: Core + wordmatch
Before you launch: prerequisites and privacy
Install the complete release archive
First search and expected result
Secondary workflow: find a running Windows tab
Troubleshooting, update and removal
Coverage and evidence—not a live compatibility certificate