Get Started with Agents

Use this page as the universal starting point for Codex, Claude Code, Cursor, Gemini CLI, or another coding agent. You only need to make three decisions: where Busabase runs, which agent setup matches your client, and whether you want the optional MCP connection.

Read https://busabase.com/docs/codex-plugin and complete the Busabase plugin installation and environment initialization for Codex. Verify the Busabase connection when finished.

codex mcp add busabase --url https://busabase.com/api/mcp
codex mcp login busabase --scopes mcp
codex mcp list

Copy a prompt from the Base or Skill Node

When the job concerns a particular Base or Skill Node, open that node and choose Agent prompts. A Skill Node opens on this tab; for a Base, use its More actions (···) → Agent prompts menu or the node's sidebar menu. Select a built-in or custom scenario, click Copy, and paste it into the external agent you already use.

Public Demo screenshot. Its Space and node IDs are examples; open the node in your own workspace before copying.

The copied text names the target node and Space, asks the agent to check its connection, and includes the setup guide if it is not connected yet. A Skill Node's Use this skill scenario also tells the agent to read that node's SKILL.md. This is the quickest way to hand over a task in existing workspace data. Dashboard → Agent Skills remains the general, Space-level starting point when you have not chosen a node yet.

Send results back from work done elsewhere

Once your agent is connected, it can do the work in another tool and use its installed Busabase Skill to bring the result back for your team to review. Busabase does not watch that other tool automatically: the agent or an integration must submit each result.

1. In your target Space, open Agent Skills and copy its space-specific setup prompt into the coding agent that runs the task. Complete the onboarding, then ask the agent to verify the Space it connected to. For Codex or Claude Code on Cloud, the Codex plugin or Claude Code plugin installs the Skill and MCP connection together. Other coding agents can follow the setup prompt. A hosted chat product needs the MCP connection instead of a shell-based Skill installation.
2. Create a Task results Base with a stable external task ID, source system, latest run status, attempt count, finish time, concise result, evidence URL, and review status. Keep full logs and files in the external system; link to the exact run so reviewers can open them. If every retry needs its own history, add a linked Task attempts Base with one record per run ID.
3. Give the agent a changeRequest-level key or OAuth permission when results must wait for a person. Ask it to look up the source system and task ID before proposing a create or update, so retries update the same task instead of making duplicates. Include a meaningful change message and the evidence link. The result waits in Inbox → For review until someone checks, approves, and merges it. It will not appear as a live progress update before that merge; use a separately authorized status-writing path if live progress is required.

You can give the connected agent this first task:

Use your installed Busabase Skill to find the correct Space. Create or find a Task results Base. For external task SYNC-428, find an existing record by source system and task ID before proposing a change. Record the latest outcome, attempt count, short summary, and a link to the exact run. Submit the result for human review; do not approve or merge it. Read back the Change Request link.

The Skill handles the Busabase workflow for an agent that can run tools. If you are building a connector inside another product, use MCP + OAuth or the REST API to submit the same reviewable change. The Change Requests guide explains the review boundary.

What to read next

Other ways to connect: Integration overview · CLI · SDK · MCP · OpenAPI / REST · Agent Skills · Webhooks