FleetCodevsUmaDev
Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.
FleetCode
built-by-as · Agent harness
OSSMCP
Panel
6.43 spec wins
- Reliability
- 6.2
- Usefulness
- 6.2
- Cost
- 8.2
- Longevity
- 5.2
“An Electron app whose entire job is to open terminals, which is the most modern thing to happen to the command line this year.”
UmaDev
umacloud · Agent harness
OSS
Panel
6.40 spec wins
- Reliability
- 6.5
- Usefulness
- 6.7
- Cost
- 6.8
- Longevity
- 5.5
“It assigns product, architecture, UI, frontend, backend, QA, security and DevOps seats, which is not a CLI flag, it is a reorganisation.”
Spec by spec
| Spec | FleetCode | UmaDev |
|---|---|---|
| Architecture | ||
| Category | Agent harness | Agent harness |
| Runs | local | local |
| Platforms | macos, linux, windows | macos, linux, windows |
| Context window | not documented | not documented |
| Protocols | ||
| MCP client | Yes | No |
| MCP server | No | No |
| Capabilities | ||
| Runs terminal commands | Yes | Yes |
| Multi-file edits | YesFile edits are made by the Claude Code or Codex session FleetCode spawns, not by FleetCode itself. | YesCode is generated and written by the base CLI UmaDev drives; the coordinator role plans and gates rather than editing files. |
| Git operations | Yes | No |
| Browser control | No | No |
| Sandboxed execution | No | No |
| Multi-agent orchestration | YesMultiple agent sessions run in parallel in separate worktrees; they do not coordinate with each other. | Yes |
| Headless / CI mode | No | No |
| Models | ||
| Backbone | Claude Code, Codex | Claude Code, Codex, OpenCode, Grok Build, Kimi Code |
| Bring your own model | Yes | Yes |
| Local models | No | NoAn optional local embedding model is used for retrieval only; the coding model always comes from the base CLI. |
| Cost | ||
| Pricing model | byok | byok |
| Starts at | $0/mo | $0/mo |
| Free tier | Yes | Yes |
| Bring your own key | Yes | Yes |
| Openness | ||
| Open source | Yes | Yes |
| License | ISC | MIT |
| GitHub stars | 424 | 260 |
Which one would each critic pick
| Critic | FleetCode | UmaDev | Pick |
|---|---|---|---|
| El Juez | — | — | not enough reviews |
| El Amigo | 7.3 | 6.8 | FleetCode — Pick it if parallel agents keep colliding in one checkout; pick a single branch and a terminal if you have never actually needed two at once. |
| El Crítico | 6.3 | 6.0 | FleetCode — The row records that the parallel sessions do not coordinate with each other, so multi-agent here means several agents unaware of each other rather than a team. |
| El Profesor | 6.5 | 7.0 | UmaDev — Roles exchange bounded artefacts and structured verdicts, and the tool reports incomplete work as incomplete rather than presenting every run as a success. |
| La Inversora | 6.0 | 5.8 | FleetCode — 424 stars, one author, no company and no paid surface: a worktree manager for two vendors' CLIs, which is a feature those vendors will ship themselves. |
| La Jefa | 5.3 | 5.8 | UmaDev — The coordinator leaves an audit trail, which is more than most of this category offers, and there is still no SSO and nothing tying that trail to a person. |
| El Hacker | 7.3 | 7.0 | FleetCode — ISC, and MCP servers register over stdio or SSE for the sessions it spawns, with a setup command running in the shell before the agent starts. |
Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.