Connect CodeAgentSwarm to Busabase
CodeAgentSwarm is a desktop Agentic Development Environment (macOS, Windows, Linux) that runs and supervises several coding-agent CLIs in parallel, including Claude Code, Codex CLI, Antigravity CLI, OpenCode and Cursor Agent.
Paste this into CodeAgentSwarm
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.
Give your agent this one instruction
You end up with more than a connector: the busabase skill carries the whole change-request workflow, the CLI, and the full API — available in every future session without re-pasting anything.
Asks first
Busabase Cloud or Personal Desktop — your call, before anything happens.
Connects
Signs you in and stores the credential itself. No API key to copy by hand.
Seeds a Base
Creates and fills your first Base, so the workspace is not an empty screen.
Installs the skills
busabase and busabase-app-creator become permanent, for every session after this.
For this agent
Skills are plain folders in each CLI's own skills directory. After the Busabase skill is installed for one agent, use **Settings → Skills → Installed → Export to agent** to copy it to the others instead of installing it again.
Other ways in
Busabase can't be added to this agent as an MCP connector, so there is nothing to wire in. These routes work instead.
At a glance
- Vendor
- CodeAgentSwarm
- How it connects
- Plugin / Skill · busabase-cli · REST API
- Transport
- Unknown
- Authentication
- Unknown
CodeAgentSwarm runs on top of the official coding-agent CLIs (Claude Code, Codex CLI, Antigravity CLI, OpenCode, Kimi Code, Grok Build, Cursor Agent, Muse Code, Pi and Devin CLI), and those agents can run shell commands, so the Skill path applies: open a terminal for an agent and paste the prompt above ("Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me"). CodeAgentSwarm's skills screen can then copy installed skills to your other agents.
Prefer a connector?
CodeAgentSwarm has an MCP marketplace for catalog integrations (GitHub, Notion, Supabase, Playwright and others), but it doesn't document adding a custom remote server. Add Busabase's MCP server (https://busabase.com/api/mcp) in the underlying agent instead: Claude Code, Codex, OpenCode.
Known gotchas
CodeAgentSwarm doesn't isolate parallel agents' file changes by itself; it recommends separate Git worktrees. Its MCP marketplace says available tools and options "depend on the selected agent and MCP server".
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | COCodeAgentSwarm |  Claude Code |  Cursor |
|---|---|---|---|
| Type | Desktop apps | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | Plugin / Skill · busabase-cli · REST API | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Unknown | Streamable HTTP | Streamable HTTP |
| Authentication | Unknown | OAuth (dynamic registration) | OAuth (dynamic registration) |
Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.
Let your agent do the setup
One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.
Browse every agentPaste this into CodeAgentSwarm
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.