Clay StudiovsDotCraft
Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.
Clay Studio
chadbyte · Agent harness
OSSMCP
Panel
6.82 spec wins
- Reliability
- 6.2
- Usefulness
- 6.8
- Cost
- 8.0
- Longevity
- 6.0
“It ships something called a Ralph Loop, which is the most honest name anybody has given an infinite while statement.”
DotCraft
DotHarness · Agent harness
OSSMCP
Panel
6.71 spec wins
- Reliability
- 6.2
- Usefulness
- 6.5
- Cost
- 7.8
- Longevity
- 6.2
“There is a NuGet package, so the agent can now be a dependency in a solution file, next to everything else nobody upgrades.”
Spec by spec
| Spec | Clay Studio | DotCraft |
|---|---|---|
| Architecture | ||
| Category | Agent harness | Agent harness |
| Runs | local | local |
| Platforms | macos, linux, windows, web | macos, linux, windows |
| Context window | not documented | not documented |
| Protocols | ||
| MCP client | Yes | Yes |
| MCP server | No | No |
| Capabilities | ||
| Runs terminal commands | Yes | Yes |
| Multi-file edits | YesClay browses, edits and diffs files in the workspace, but code changes are produced by the coding-agent runtime it dispatches to. | Yes |
| Git operations | Yes | No |
| Browser control | No | No |
| Sandboxed execution | No | No |
| Multi-agent orchestration | Yes | Yes |
| Headless / CI mode | No | No |
| Models | ||
| Backbone | Claude Code, Codex, Grok Build, Kimi Code, GitHub Copilot CLI, Qwen Code, Junie CLI, Antigravity CLI, OpenCode, Kiro CLI | OpenAI, Anthropic, ChatGPT subscription, any OpenAI-compatible endpoint |
| Bring your own model | Yes | Yes |
| Local models | No | YesAny provider speaking the OpenAI or Anthropic protocol can be configured, which covers a local server; no specific local runtime is named in the README. |
| 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 | MIT | Apache-2.0 |
| GitHub stars | 399 | 396 |
Which one would each critic pick
| Critic | Clay Studio | DotCraft | Pick |
|---|---|---|---|
| El Juez | — | — | not enough reviews |
| El Amigo | 7.0 | 6.8 | Clay Studio — Pick it if agent work in your team keeps meaning one person and nine spectators; pick a single-user harness if you are the only one who touches the repository. |
| El Crítico | 6.5 | 6.3 | Clay Studio — Permission prompts can be answered by whichever teammate is looking, which means the authority to let an agent act belongs to nobody in particular. |
| El Profesor | 7.0 | 7.0 | no preference |
| La Inversora | 6.3 | 6.3 | no preference |
| La Jefa | 6.0 | 6.3 | DotCraft — The AppServer edition means this becomes a service my platform team runs, which is a real cost, and there is still no single sign-on in front of it. |
| El Hacker | 7.8 | 7.5 | Clay Studio — MIT, ten agent CLIs behind one workspace, and MCP servers connected and managed from that workspace rather than configured ten times in ten different files. |
Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.