agentboards.org
Compare/Arbor vs claude-code-router

Arborvsclaude-code-router

Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.

Arbor
penso · Agent harness
OSSMCP
Panel
7.2
4 spec wins
Reliability
7.0
Usefulness
7.0
Cost
8.7
Longevity
6.0

“It manages your repositories, your worktrees, your terminals and your processes, so the only unmanaged thing left in the room is you.”

claude-code-router
musistudio · Agent harness
OSSMCP
Panel
7.0
2 spec wins
Reliability
6.3
Usefulness
7.7
Cost
8.3
Longevity
5.8

“Its main job is pointing Claude Code at a model that is not Claude, and it is named after both of them.”

Spec by spec

SpecArborclaude-code-router
Architecture
CategoryAgent harnessAgent harness
Runslocallocal
Platformsmacos, linux, windows, webmacos, linux, windows, web
Context windownot documentednot documented
Protocols
MCP clientYesYes
MCP serverYesNo
Capabilities
Runs terminal commandsYesNoCCR is a routing proxy; the agent CLI behind it does the executing.
Multi-file editsYesNo
Git operationsYesNo
Browser controlNoNo
Sandboxed executionNoYesA documented docker compose deployment runs the router itself in a container; it does not sandbox the agents that call it.
Multi-agent orchestrationYesYesCCR fronts many agent CLIs at once (Claude Code, Codex, Grok CLI, Kimi CLI, Kilo Code, OpenCode, ZCode) but does not itself orchestrate agents against a task.
Headless / CI modeNoNo
Models
BackboneClaude Code, Codex, OpenCodeOpenAI, Anthropic, Gemini, OpenRouter, DeepSeek, SiliconFlow, Moonshot Kimi, Mistral, Z.AI, Bailian
Bring your own modelYesYes
Local modelsYesOllama appears among the providers Arbor can be pointed at. YesAny OpenAI-compatible endpoint can be added as a custom provider with its own base URL, which covers a locally hosted server; no named Ollama or LM Studio preset is documented.
Cost
Pricing modelbyokbyok
Starts at$0/mo$0/mo
Free tierYesYes
Bring your own keyYesYes
Openness
Open sourceYesYes
LicenseMITMIT
GitHub stars83137,511

Which one would each critic pick

CriticArborclaude-code-routerPick
El Juez——not enough reviews
El Amigo7.57.3Arbor — Pick it if you work locally and responsiveness matters to you; pick AgentsMesh if the work has to live somewhere your team can reach.
El Crítico6.86.3Arbor — The desktop app, the web interface and the command line all read one daemon, and nothing documents what an in-flight session does when it dies.
El Profesor7.57.0Arbor — The unit of work is an issue and the working tree is created for it, so the boundary of the task and the boundary of the checkout are the same boundary.
La Inversora6.86.5Arbor — 809 stars, a personal namespace and a documentation site on GitHub Pages: nothing to fund, nothing to fail, and nobody to answer the phone.
La Jefa6.36.5claude-code-router — Free for sixty, and the credential pool with key rotation is the first thing on this board that looks like something a platform team would actually want.
El Hacker8.38.8claude-code-router — MIT, and any OpenAI-compatible endpoint becomes a provider by writing its base URL into the config, which includes the server on my own machine.

Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.

Want a third column? The compare tool handles any two agents. Three-way comparisons are on the roadmap once the spec rows are all verified.