AI tool comparison
Ferretlog vs Remoroo
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
Remoroo
AI agent that remembers every run — built for long-running research and optimization loops
50%
Panel ship
—
Community
Free
Entry
Remoroo is an AI agent purpose-built for long-running autoresearch and optimization workflows. The core loop is simple: give it a codebase and a measurable target, and it iterates autonomously — patch → run → eval → repeat — while maintaining a persistent memory of every attempt. It directly attacks the most frustrating failure mode in agentic coding: the agent that forgets what it already tried and circles back to dead ends hours into a job. The memory architecture stores code style preferences, project context, experimental hypotheses, and outcome measurements across sessions. When an agent run is interrupted or the job takes multiple days, Remoroo picks up with full context rather than starting from scratch. This is particularly valuable for ML training optimization, benchmark improvement tasks, and code performance tuning where individual runs take hours and the value is in the accumulated learning across dozens of attempts. Remoroo surfaced on Hacker News and the Hugging Face forums with strong interest from ML researchers and engineers who've been struggling with the same problem in their own workflows. It's early-stage, but it addresses a gap that every team running long-horizon AI agents has hit.
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 patch-run-eval-repeat loop with persistent memory is exactly what's missing from existing coding agents. I've wasted days watching agents revisit approaches they already tried because they lost context. Remoroo's memory-as-infrastructure approach is the right abstraction. Would ship for any multi-day optimization task today.”
“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.”
“Very early — the website is sparse and there's no published information about the memory architecture, storage backend, or how context degradation is handled over hundreds of runs. The HN discussion is promising but the product itself is pre-documentation. Check back in three months.”
“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.”
“Persistent, searchable agent memory across sessions is one of the fundamental missing pieces for agents that operate at human research timescales. Remoroo's focus on measurable targets and outcome-based memory makes it more rigorous than naive conversation logging. This points toward agents that genuinely compound knowledge over weeks and months.”
“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.”
“Interesting for technical research workflows but the use case is narrow — it's optimizing code and ML runs, not creative or design work. The tool needs to demonstrate how it generalizes beyond quantitative optimization before it's compelling for broader creative applications.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.