Busabase for PaseoConnect Paseo to Busabase
Paseo is an open-source agentic development environment (desktop, mobile, web and CLI) whose local daemon runs coding-agent CLIs such as Claude Code, Codex, Copilot, OpenCode and Pi in parallel worktrees.
Paste this into Paseo
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.
Busabase
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 installed per underlying agent, not per Paseo. If you switch a task from Claude Code to Codex, make sure the Busabase skill is installed for both. Paseo's own `npx skills add getpaseo/paseo` installs Paseo's orchestration skills, not Busabase's.
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
- Paseo
- How it connects
- Plugin / Skill · busabase-cli · REST API
- Transport
- Unknown
- Authentication
- Unknown
Paseo doesn't connect to Busabase itself. It launches the coding-agent CLIs you already installed (Claude Code, Codex, GitHub Copilot, OpenCode, Pi, Antigravity, Muse Code and ACP agents), and each of them keeps its own config, skills and MCP servers. Those agents can run shell commands, so the Skill path applies: start an agent in Paseo and paste the prompt above ("Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me"). The agent installs the Busabase skill wherever that CLI normally keeps skills, and every later Paseo session with that agent can use it.
Prefer a connector?
Paseo doesn't document its own setting for adding a remote MCP server to the agents it launches. Add Busabase's MCP server (https://busabase.com/api/mcp) in the underlying agent instead, using that agent's page: Claude Code, Codex, OpenCode. Paseo says the agent's MCP servers "stay intact" when it runs the agent.
Known gotchas
Paseo only runs agents whose CLI is installed and signed in on the daemon host; install Busabase's skill on that host, not on the phone or browser client. For the Antigravity provider, Paseo says its own MCP tools are unavailable, but the agent's own `agy` MCP servers still work.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | Paseo |  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 Paseo
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.