Compare/Extractor vs Ferretlog

AI tool comparison

Extractor vs Ferretlog

Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.

E

Developer Tools

Extractor

Robust LLM-powered web content extraction

Ship

100%

Panel ship

Community

Free

Entry

Extractor uses LLMs to reliably extract structured data from any webpage. Unlike traditional scrapers that break when HTML changes, Extractor understands the content semantically.

F

Developer Tools

Ferretlog

git log for your Claude Code agent runs — local, zero dependencies

Mixed

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.

Decision
Extractor
Ferretlog
Panel verdict
Ship · 3 ship / 0 skip
Mixed · 2 ship / 2 skip
Community
No community votes yet
No community votes yet
Pricing
Free (open source)
Free / Open Source
Best for
Robust LLM-powered web content extraction
git log for your Claude Code agent runs — local, zero dependencies
Category
Developer Tools
Developer Tools

Reviewer scorecard

Builder
80/100 · ship

Traditional web scraping is brittle. LLM-powered extraction that understands content structure is the right approach. Works on messy pages where CSS selectors fail.

80/100 · ship

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.

Skeptic
80/100 · ship

The LLM cost per extraction makes it expensive at scale. But for high-value data extraction where accuracy matters more than cost, it is worth it.

45/100 · skip

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.

Futurist
80/100 · ship

Web scraping becomes web understanding. As more AI agents need to read the web, tools like Extractor become essential infrastructure.

80/100 · ship

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.

Creator
No panel take
45/100 · skip

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.

Weekly AI Tool Verdicts

Get the next comparison in your inbox

New AI tools ship daily. We compare them before you waste an afternoon.

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later

Extractor vs Ferretlog: Which AI Tool Should You Ship? — Ship or Skip