Càrn – A TUI for browsing your Claude and Codex session archives
Session resumption actually reopens conversations in the original provider with correct working directory.
Local-first analytics dashboard for AI coding sessions. See what you built with Claude Code & Codex CLI.
LLM-titled sessions and one-click resume beat Claude's default first-sentence titles.
Developers who regularly use Claude Code CLI or Codex CLI
Claude and codex are incredible. But, there were a few problems I had with them. AgentGraphed pretty much solves for those.
It works locally - indexes every conversation you have, live, into a local sqlite db. With it, theres a lot we can render in a nice UX.
Among other things..
Problem: I want to resume a session, but when I look at claude --resume, the titles are completely unhelpful. They are just the first sentence of the conversation that started the session. Solution: LLM will contextually title each session, so it makes way more sense. Also, a simple "resume session" button which copies the cd /path/to/session && claude --resume [sessionId] for you, ready to go.
Problem: I go on vacation, and forget what I was working on when I get back. Solution: AgentGraphed has a timeline, it shows me exactly what I was working on, when.
Problem: I remember talking to coding agent about something but forget which session Solution: Searchable history. Every single session, ever.
Problem: I want to brag to my friends about how much I use claude. ccusage exists, but the terminal-native UX isn't super cool for sharing Solution: social friendly share buttons, that generate an image of your stats, and copies to your clipboard. (All local).
Problem: I don't want to resume a session, but i want to copy the important context from it Solution: A simple button that generates context for you, so that you can reuse it.
------
One thing I need to call out. The tool really is fully local, totally safe. BUT! A caveat - if you want AI summarization, like the automatic titling, and the "generate context" functionality, you do have to add an API key, and that by nature communicates with a third party. Those are totally optional, though.
I'm new to the OSS world. Usually everything I do is proprietary etc, so feel free to roast me and help me make it better.
Session resumption actually reopens conversations in the original provider with correct working directory.
Local vault captures AI session transcripts before they vanish into the ether.
Grep for agent memory without the noise of auto-injected vector embeddings.
One CLI for Claude and Codex sessions when each tool tracks them separately.
PreToolUse hooks block over-budget requests while SQLite tracks Claude Code spend locally.
Yet another session sharer in a space where screenshots already dominate.