AI tool comparison
Apfel vs dotclaude
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
Apfel
Tap the free AI already built into your Mac
75%
Panel ship
—
Community
Free
Entry
Apfel is a Swift 6.3 command-line tool that cracks open the on-device language model Apple ships with every Apple Silicon Mac running macOS 26 (Tahoe). Instead of requiring a Claude, OpenAI, or Gemini subscription, Apfel routes through Apple's FoundationModels framework and gives you three interfaces from a single brew install: a pipe-friendly CLI, an interactive chat with context management, and an OpenAI-compatible local HTTP server built on Hummingbird. Under the hood, every token is generated on your Neural Engine and GPU — nothing leaves your machine. The model is roughly 3B parameters with a 4,096-token context window, fast enough for scripting, summarisation, and quick Q&A without latency you'd notice. Pipe-friendly stdin/stdout, JSON output mode, and proper exit codes make it trivially composable with jq, xargs, and shell scripts. The OpenAI-compatible server mode is the killer feature for developers: point any tool that speaks the OpenAI API at localhost and it just works — locally, for free, with zero cold-start. The project is MIT-licensed, started by a solo developer on March 24, 2026, and hit 513 HN points within days of the Show HN post.
Developer Tools
dotclaude
Run multiple AI coding agents in parallel tmux panes — no extra API costs
50%
Panel ship
—
Community
Free
Entry
dotclaude is a lightweight workflow pattern (not a framework) for running multiple AI coding agents in parallel without incurring extra API costs. It exploits the CLI non-interactive resume mode of Claude, Codex, and Gemini — spinning them up in tmux panes and letting them iterate on different aspects of a codebase simultaneously. The project is explicitly positioned as a "practical workflow, not a polished framework." The core insight is that you can achieve multi-agent collaboration by composing existing CLI tools (tmux, agent CLIs, shell scripts) rather than building or buying dedicated orchestration infrastructure. Context is shared via files; agents communicate by reading and writing to the same working directory. It's rough around the edges and requires comfort with the command line, but the approach is genuinely clever: no new dependencies, no framework lock-in, and no extra API tokens beyond what you'd spend running each agent individually. The HN thread attracted developers interested in the minimal-overhead angle, particularly those already running multiple coding agents manually.
Reviewer scorecard
“The OpenAI-compatible server is a genuine unlock — I swapped my local dev config from Ollama to Apfel in two minutes and everything just worked. For Apple Silicon owners who want zero-latency local AI without model downloads, this is the move.”
“This is the kind of DIY cleverness that eventually becomes best practice. Using tmux + CLI resume mode to approximate multi-agent coordination is a zero-dependency solution that works with the tools most developers already have. Rough but real.”
“A 3B-parameter model with a 4K context window is impressive for on-device, but it's nowhere near Claude or GPT-5.5 quality. If your task needs real reasoning or long context, you're back to paying for API credits anyway. This is a neat party trick, not a replacement.”
“File-based agent communication breaks down fast when agents make conflicting edits. There's no conflict resolution, no proper state management, and no error recovery. This is a proof-of-concept that will frustrate you on any non-trivial project.”
“Apfel is the first glimpse of a world where capable on-device AI comes pre-installed, not downloaded. As Apple's model improves with each macOS release, tools like Apfel will inherit the upgrade for free. The distribution moat Apple is quietly building here is enormous.”
“The fact that developers are jury-rigging multi-agent coordination with tmux and shell scripts shows how strong the demand is for parallel AI workflows. The gap between what people want and what polished frameworks offer is still wide enough for creative workarounds like this to get traction.”
“I used it to batch-summarise 40 draft posts overnight with a simple shell loop — no API bill, no rate limits, no internet required. For content workflows that need a cheap first pass, it's already practical.”
“This requires serious CLI comfort and debugging patience. For creative workflows that involve coding, the productivity cost of managing tmux sessions and debugging agent conflicts outweighs the benefits for most people.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.