Ferretlog
git log for your Claude Code agent runs — local, zero dependencies
Expert verdict
Skip
2-2The Panel's Take
Ferretlog is a zero-dependency pure Python CLI that treats your Claude Code session logs like a git repository. It parses the raw JSONL logs in `~/.claude/projects/` and gives you git-style history browsing, diff between runs, per-tool-call breakdowns, and cost/token stats — entirely locally, with no network calls and no configuration required. If you've been using Claude Code heavily, you've likely experienced the frustration of losing track of what changed across sessions, what tools were called how many times, and how much each session actually cost across sub-agent calls. Ferretlog makes that history explorable and comparable the same way `git log` makes code history explorable. This is an indie solo project from Eitan Lebras, submitted as a Show HN. It's genuinely useful as a power-user tool for anyone doing serious Claude Code work, especially those managing multi-session agent pipelines where debugging "what did the agent do last time?" is a real pain. The zero-dependency, local-only design means there's no trust surface and no setup friction.
Share this verdict
Ferretlog verdict: SKIP ⏭️ 2 ships · 2 skips from the expert panel Full review: shiporskip.io/tool/ferretlog-claude-code-session-git-log-cli-cost-diff-local
Weekly AI Tool Verdicts
Get the next verdict in your inbox
7 critics review a new AI tool every day. Weekly digest — free.
Similar Products
Compare Ferretlog with Others
Looking for Ferretlog alternatives?
Compare Ferretlog with every other Developer Tools tool reviewed by our panel.
See all Developer Tools alternativesEmbed this verdict
Tool makers can add a live ShipOrSkip badge to their site. Badge loads track impressions; clicks route back to this review.
<a href="https://shiporskip.io/api/badge-click/ferretlog-claude-code-session-git-log-cli-cost-diff-local" target="_blank" rel="noopener"><img src="https://shiporskip.io/api/badge/ferretlog-claude-code-session-git-log-cli-cost-diff-local" alt="Ferretlog Skip verdict on ShipOrSkip" width="360" height="90" /></a>[](https://shiporskip.io/api/badge-click/ferretlog-claude-code-session-git-log-cli-cost-diff-local)<iframe src="https://shiporskip.io/embed/ferretlog-claude-code-session-git-log-cli-cost-diff-local" title="Ferretlog ShipOrSkip verdict" width="360" height="260" style="border:0;border-radius:16px;max-width:100%;" loading="lazy"></iframe>The reviews
“If you run Claude Code daily, you need this immediately. Being able to diff two sessions like git commits and see exactly which tools fired and what they cost is something that should have existed from day one. Zero-dependency Python means it just works.”
“This is a niche tool for a niche user (heavy Claude Code power users) and the session log format Anthropic uses is undocumented and could change at any update. Tying workflows to internal log parsing is fragile infrastructure — treat it as a convenience, not a dependency.”
“Agent observability tooling built by the community, not the vendor, is how this ecosystem will mature. Ferretlog is primitive but it points at a real gap: we need git-style versioning and auditability for agent sessions, not just for code.”
“Terminal-only, Claude Code-specific, no visuals — this tool exists entirely outside my workflow. The underlying insight (session replay and cost tracking) is useful, but it needs a UI before it reaches anyone outside the developer community.”