Overlap
Coding Agents for Rust
Coding Agents tools that run on Rust. The Catch for each, not a winner list.
5 tools · the Catch, not a ranking
- GooseLocal-first Rust agent with MCP at its core
General-purpose agent means you configure it for your use case. You bring the model—Goose is the runtime, not the intelligence. Documentation is still maturing.
- ZedGPL-3.0 GPU-accelerated editor with first-party agents
GPL-3.0 is copyleft, not MIT. Hosted agent features that talk to Zed's models are a product on top of the editor — no Cloud free tier to count on. Web is not shipped.
- Open InterpreterApache-2.0 terminal coding agent; Rust Codex fork for open models
Vs Claude Code / Cursor / OpenCode / Gemini CLI: this is open-model/BYOK terminal, not a hosted Max seat. 2026 rewrite — Rust Codex fork; classic Python AGPL lives at endolith/open-interpreter community fork. The old pip interpreter UX is no longer current upstream.
- OpenResearchMIT coding agents → research agents (Rust)
Vs Spec Kit (spec-driven coding workflow), DSPy (prompt/program optimizers), Promptfoo (eval/red-team): OpenResearch is a research-agent harness and experiment ledger around existing coding agents — not a spec kit, not a prompt compiler, not an eval suite. You still pay (or self-host) the coding agent and any remote compute you dispatch.
- Atlas (pacifio)MIT multi-agent change tracking — source control for agents
Vs Worktrunk/jj (git worktree / change-oriented VCS plumbing): Atlas is agent session+change tracking with shared memory, not a general VCS replacement. name collision with Ariga Atlas (slug `atlas`, schema-as-code) — this card is `atlas-agents` / pacifio only; never confuse with atlasgo.io.