Agent conversation search (cs)

Tool roles, alternatives, selection tradeoffs, and compatibility caveats.

Tool roles, alternatives, selection tradeoffs, and compatibility caveats.

Agent conversation search (cs)

John uses: cs — his personal conversation-search CLI (cs <term> --recent -n 20) over all local Claude/Codex/Grok session history; section 00's fact-check of a month-old field guide against ~1,978 oracle sessions ran on it. We could not find a public repo for cs; treat it as personal/unreleased.

Alternative What it is How it differs License
cc-sessions-viewer Viewer for Claude Code/Codex/Antigravity/OpenCode sessions: global search, token stats, resume, HTML export Closest public match: multi-agent session search in a UI rather than a grep-style CLI none listed
claude-conversation-extractor Extract clean conversation logs from Claude Code's internal storage Extraction/export only — pipe the output into ripgrep for search; check current repository activity MIT
llm logs (Simon Willison) Every llm CLI prompt/response logged to SQLite; `llm logs -q` full-text search Only covers conversations you run through llm, but the SQLite pattern is the most robust searchable-history design Apache-2.0
ripgrep over ~/.claude/projects and ~/.codex/sessions Both Claude Code and Codex store sessions as local JSONL — rg searches them directly The zero-tool option: `rg -l 'term' ~/.claude/projects` gets you 80% of cs today MIT/Unlicense
ccusage npx ccusage — analytics over Claude Code local session data Adjacent: usage/cost analytics over the same JSONL files, not content search NOASSERTION

Pick this if…

  • ripgrep — start here; it's 80% of cs with zero new tools.
  • cc-sessions-viewer — you want cross-agent search in a UI with resume/export (young project).
  • claude-conversation-extractor — you want clean markdown exports to feed other tools.
  • llm logs — you're building new habits and want history searchable by design.
  • ccusage — you want the cost/usage half of session mining.

Source references