Compare/Craft Agents vs Ferretlog

AI tool comparison

Craft Agents vs Ferretlog

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

C

Developer Tools

Craft Agents

Open-source desktop app for multi-session Claude agents with MCP & APIs

Ship

75%

Panel ship

Community

Free

Entry

Craft Agents OSS is an open-source desktop application built on Anthropic's Claude Agent SDK, offering a polished GUI for managing multiple AI agent sessions simultaneously. Built by Luki Labs and released under Apache 2.0, it fills the gap between raw API access and the full Claude.ai web interface — giving developers and power users a native desktop experience with serious capability depth. The app supports three permission modes that make it genuinely useful for real work: Explore (read-only, safe for exploring codebases), Ask to Edit (approval-based, for supervised automation), and Auto (unrestricted, for trusted workflows). It connects to MCP servers, REST APIs from Google, Slack, and Microsoft, and local filesystems, with real-time streaming responses and full tool call visualization. A multi-session workflow with Todo → In Progress → Needs Review → Done status tracking makes it feel more like a project management system than a chat interface. Built on Electron + React with encrypted credential storage and a headless server mode, Craft Agents is architecturally serious. It's available as a one-line installer for macOS, Linux, and Windows. With the Claude Agent SDK gaining traction, this is the first polished desktop client that treats agents as long-running workflows rather than single-turn conversations.

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
Craft Agents
Ferretlog
Panel verdict
Ship · 3 ship / 1 skip
Mixed · 2 ship / 2 skip
Community
No community votes yet
No community votes yet
Pricing
Open Source / Free (Apache 2.0)
Free / Open Source
Best for
Open-source desktop app for multi-session Claude agents with MCP & APIs
git log for your Claude Code agent runs — local, zero dependencies
Category
Developer Tools
Developer Tools

Reviewer scorecard

Builder
80/100 · ship

The three permission modes — Explore, Ask to Edit, Auto — is the right model for how I actually use agents. I want read-only exploration when I'm learning a codebase and auto mode when I'm in flow. That plus MCP server support makes this my new default agent UI.

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
45/100 · skip

Electron desktop apps for AI agents have a graveyard of predecessors — most people end up in the terminal or the browser anyway. The Claude-only model dependency is also a real limitation; when Anthropic changes their SDK or pricing, the whole platform needs to adapt.

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

Agent session management as a first-class concept is where the whole category is heading. Craft Agents is early proof that the IDE model — multi-session, persistent, project-aware — is the right UX paradigm for AI agents, not the chat-box model we inherited from GPT-3 days.

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
80/100 · ship

File attachments with automatic format conversion plus the Slack/Google API integrations mean I can finally have agents that work across my whole toolkit, not just the terminal. The one-line installer is the detail that will make this actually get adopted.

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

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