AI tool comparison
Ferretlog vs Google ADK Python 1.0
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
Google ADK Python 1.0
Google's production-ready framework for building AI agents
75%
Panel ship
—
Community
Free
Entry
Google's Agent Development Kit (ADK) Python hit v1.0.0 stable on April 17, marking it production-ready for teams building and deploying AI agents at scale. ADK is a modular, code-first framework that applies standard software engineering principles to agent development — graph-based workflow execution, structured agent-to-agent delegation via a Task API, native MCP support for tool integration, and built-in evaluation tooling. Unlike LangChain's general-purpose orchestration or CrewAI's role-based crews, ADK leans into composable determinism: you define explicit graphs of agent behavior that are auditable, testable, and deployable directly to Google Cloud's Vertex AI Agent Engine. It supports Python, TypeScript, Go, and Java, making it one of the few multi-language agent frameworks in production. The 1.0 stable label matters. Google has been iterating ADK roughly every two weeks, and teams that held off on building with it due to API instability now have a stable target. With Vertex AI providing the deployment layer and Agent Engine handling orchestration at scale, this is Google's full-stack answer to the agent infrastructure question.
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 1.0 stable tag finally gives us something to build on. The graph-based execution engine is exactly what I want for deterministic multi-step pipelines where I can't afford unpredictable LLM routing. Native MCP support means my existing tool ecosystem plugs straight in without adapter layers.”
“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.”
“ADK's tight coupling to Vertex AI is a genuine lock-in concern. The 'production-ready' badge comes with an implicit 'on Google Cloud' qualifier. For teams running on AWS or Azure, the deployment story is clunky. LangGraph and CrewAI are more cloud-agnostic and have larger community ecosystems right now.”
“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.”
“Google going stable on a multi-language agent framework signals they're treating this as core infrastructure, not a demo. The Agent-to-Agent (A2A) protocol work alongside ADK hints at Google's real play: defining how agents communicate at internet scale, the same way HTTP defined how documents communicate.”
“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.”
“For no-code and low-code builders who want to graduate to real agent workflows, ADK's structured graph model is more approachable than writing raw LangChain chains. The TypeScript version in particular opens this to a much wider pool of front-end developers who want to add agentic features to their apps.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.