Busabase for Agentastic.dev

Connect Agentastic.dev to Busabase

Agentastic.dev is a native macOS multi-agent IDE that runs coding-agent CLIs such as Claude Code, Codex, Gemini and Cursor side by side, each in its own git worktree, container or cloud VM.

Paste this into Agentastic.dev

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Read the Agentastic.dev Skills documentation

Busabase

Agent Skill

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

Agentastic also has its own skill library (Settings → Skills), which copies attached skills into the worktree for Prime Agent, Claude Code, Codex, Poolside, Droid and Amp. Its Install from GitHub "finds the first SKILL.md in the repo", so it may not pick the `busabase` skill from `busabase/skills`. The prompt above is the reliable route.

Prefer a connector?

If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.

At a glance

Vendor: Agentastic.ai
How it connects: Plugin / Skill · busabase-cli · REST API · MCP + API key
Transport: Streamable HTTP
Authentication: API key
Config file: Settings → Plugins → Add MCP Server (personal plugins stored under ~/Library/Application Support/Agentastic.dev/Plugins/; workspace plugins at .agentastic/plugins/)

Agentastic runs each provider's real CLI (Claude Code, Codex, Gemini, Cursor and 50+ more) in a terminal, so the Skill path applies: start an agent in Agent Home and paste the prompt above ("Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me"). The skill lands wherever that CLI keeps skills. For per-agent details see Claude Code, Codex or OpenCode.

Prefer a connector?

Agentastic can hand one MCP server to every compatible agent it launches. It documents URL + header servers, not an OAuth sign-in, so use a Busabase API key:

Create a key in Busabase Settings → API Keys with the smallest permission that works and a finite expiration.

Open Settings → Plugins → Add MCP Server.
Name: busabase. URL: https://busabase.com/api/mcp.
Add a header Authorization with the value Bearer <your Busabase API key>, and mark it as a credential so it's stored in the macOS Keychain.
Save, then launch a new Claude Code, Codex, OpenCode, Amp or GitHub Copilot agent and ask it to call auth_verify.

Other agents don't get MCP from Agentastic yet. Add Busabase in their own config, or use the Skill path.

Agentastic docs: Plugins & MCP

Known gotchas

macOS only. Plugin MCP servers only reach Claude Code, Codex, OpenCode, Amp and GitHub Copilot; Agentastic says every other agent has "No MCP channel yet". New plugins apply to agents launched after you connect them, not to sessions already running. Agentastic doesn't document an OAuth sign-in for plugin MCP servers, so use an API-key header.

How it compares

Connection capabilities side by side with other agents already in this directory.

Capability	Agentastic.dev	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 + API key	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	API key	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsNo check date recorded

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.

Where these steps come from Official site

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 agent

Paste this into Agentastic.dev

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.