AI tool comparison
Ferretlog vs free-claude-code
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
Ferretlog
git log for your Claude Code agent runs — local, zero dependencies
50%
Panel ship
—
Community
Free
Entry
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.
Developer Tools
free-claude-code
Route Claude Code traffic to DeepSeek, OpenRouter, or local models
50%
Panel ship
—
Community
Free
Entry
free-claude-code is a lightweight proxy that intercepts Claude Code's Anthropic Messages API calls and reroutes them to six alternative backends: NVIDIA NIM, OpenRouter, DeepSeek, LM Studio, llama.cpp, and Ollama. From Claude Code's perspective nothing changes — the UX, tool calls, streaming, and reasoning blocks all work identically. Under the hood, you're spending almost nothing. The project supports per-model routing, so you can send Opus traffic to OpenRouter while Haiku goes to a local Ollama instance. It handles the full protocol stack: streaming completions, multi-turn tool use, thinking block pass-through, and request optimization for local hardware. An optional Discord or Telegram bot wrapper lets you trigger remote coding sessions from your phone. With 17K+ GitHub stars and still climbing, this is clearly scratching a real itch. The Anthropic gating of Claude Code behind Pro subscriptions created exactly the market condition this project was built for. Whether it stays ahead of API changes is the open question — but right now it's the fastest path to a near-free Claude Code experience.
Reviewer scorecard
“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 exactly what the indie dev community needed after Anthropic tightened Pro limits. The per-model routing is clever — I can push heavy reasoning to DeepSeek and let fast autocomplete hit a local 8B model. Setup took about 15 minutes.”
“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.”
“This is a proxy built around undocumented client behavior — any Claude Code update could break it silently. Running your codebase through third-party provider APIs also introduces real IP and data risk. For solo projects it's probably fine; for anything professional, think twice.”
“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.”
“The fact that 17K people starred this in days is a signal: developers want Claude Code's UX without the lock-in. This kind of proxy layer is how model pluralism actually happens in practice — not through official integrations but through community shims.”
“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.”
“If you're not deep in CLI-land, the setup friction is real. But for technical creators who've been priced out of Claude Code Pro, this is a legitimate workaround while the pricing landscape settles.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.