Comparison
goose vs Roo Code
How the two compare on the things that decide whether your setup carries over: open standards, license, models and where they run.
| goose | Roo Code | |
|---|---|---|
| Maker | Block, now at the Agentic AI Foundation | Roo Code |
| License | Apache-2.0 | Apache-2.0 |
| Models | Many providers, including local models | See vendor docs |
| Runs in | Desktop, Terminal, API | IDE |
| MCP | MCP: supported | MCP: supported |
| Agent Skills | Agent Skills: supported | Agent Skills: supported |
| AGENTS.md | AGENTS.md: supported | AGENTS.md: supported |
| ACP | ACP: supported | ?ACP: not yet verified |
Key differences
- Both are open source (Apache-2.0 and Apache-2.0), so you can inspect and self-host either.
- goose also runs in Desktop, Terminal, API; Roo Code also runs in IDE.
- goose supports ACP; we have not verified it for Roo Code.
- Both support MCP, Agent Skills, AGENTS.md, so MCP servers, skills and repo instructions you set up carry over if you switch.
In their own words
FAQ
- Is goose or Roo Code open source?
- goose is open source under Apache-2.0. Roo Code is open source under Apache-2.0.
- Do goose and Roo Code support MCP servers?
- goose: yes. Roo Code: yes.
- Can I reuse Agent Skills between goose and Roo Code?
- Yes. Both read the open Agent Skills (SKILL.md) format, so the same skill folder works in both.
Set up MCP servers in either one
More comparisons
Reviewed Oct 5, 2026.