AI tool comparison
Ferretlog vs Voker
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
Voker
Analytics platform built specifically for AI agents
75%
Panel ship
—
Community
Free
Entry
Voker (YC S24) is an analytics platform that does for AI agents what Mixpanel did for web products — transforms raw agent conversations into structured, queryable insights without requiring a data engineering team. It auto-classifies user intents, detects when agents fail to resolve requests, surfaces knowledge gaps, and tracks performance regressions when you update your prompts. The platform integrates with OpenAI, Anthropic, Gemini, LangChain, CrewAI, and Vercel AI SDK via lightweight Python and TypeScript SDKs. Non-technical team members — PMs, analysts, support leads — can query conversation timelines, track satisfaction trends, and measure business impact without needing SQL or engineering support. The free tier covers 2,000 events/month, which is generous for small projects. Paid plans start at $80/month for 20K events. The core pain point is real: most teams today do spot-checks by hand to debug agent behavior at scale, which doesn't scale past a few hundred conversations. Voker automates that loop.
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.”
“The pain point is totally real — debugging agent behavior in production today is a nightmare of manually reading transcripts. Intent detection + resolution tracking as first-class primitives is exactly what's missing from the current toolchain. The SDK integration is clean.”
“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.”
“The 2,000 event free tier sounds decent until you realize a mid-size chatbot burns through that in a day. And at $400/month for 2M events, you're paying a premium for what's essentially LLM-powered log analysis. Full-featured observability tools like LangSmith and Langfuse are closing this gap fast.”
“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.”
“Agent analytics is going to be a massive category — every company deploying autonomous AI will need to instrument it like software. Voker is positioning early in a space that'll see consolidation. The 'resolution rate' metric alone could become the north-star KPI of the agent era.”
“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.”
“The self-service angle for non-technical teammates is underrated. Content and community teams using AI agents to handle engagement finally get visibility into whether those agents are actually helping users — without filing a Jira ticket to find out.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.