Busabase for Deep Agents Code

Connect Deep Agents Code to Busabase

LangChain's terminal coding agent built on Deep Agents, with planning, subagents, filesystem tools, and MCP configuration.

Paste this into Deep Agents Code

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 Deep Agents Code 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.

Install the Busabase skills

npx skills add busabase/skills

For this agent

Deep Agents Code has terminal and filesystem tools, so let it follow SETUP_SKILL.md from the repository where you want Busabase configured.

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.

Deep Agents Code MCP documentation

At a glance

Vendor: LangChain
How it connects: Plugin / Skill · busabase-cli · REST API · MCP + OAuth · MCP + API key
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: ~/.deepagents/.mcp.json (user) / <project>/.deepagents/.mcp.json / <project>/.mcp.json; MCP policy in ~/.deepagents/config.toml

Run this

curl -LsSf https://langch.in/dcode | bash

Install Deep Agents Code with the official installer, start it in a trusted repository, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review the proposed commands, complete authentication, and ask it to verify the active Busabase workspace.

Prefer a connector?

Deep Agents Code's MCP tools page now documents remote MCP with OAuth (Dynamic Client Registration + Authorization Code/PKCE). Add Busabase to ~/.deepagents/.mcp.json (user level, all projects):

{
  "mcpServers": {
    "busabase": {
      "type": "http",
      "url": "https://busabase.com/api/mcp",
      "auth": "oauth"
    }
  }
}

Then run dcode mcp login busabase once and paste the redirected URL back into the terminal when asked. Tokens are stored under ~/.deepagents/.state/mcp-tokens/ and refreshed automatically. Header auth also works: string values in url and headers support ${VAR} interpolation.

Known gotchas

`auth: "oauth"` is mutually exclusive with an Authorization header on the same entry, and cannot be set on a stdio server. Project-level MCP servers are default-deny: interactive sessions prompt for approval (approvals are saved to ~/.deepagents/config.toml, scoped to project root + server name + a SHA-256 fingerprint of the definition; any definition change re-prompts), and non-interactive (-n) runs silently skip unapproved project servers unless --trust-project-mcp is passed. User-level ~/.deepagents/.mcp.json is always trusted. OAuth tokens live under ~/.deepagents/.state/mcp-tokens/ (dir 0700, files 0600, keyed by the first 16 hex chars of the SHA-256 of the server URL); on refresh failure the server is marked unauthenticated in /mcp rather than crashing — re-run `dcode mcp login <server>`. MCP tool calls time out after 120 s by default; set [mcp].tool_timeout in ~/.deepagents/config.toml (1–900 s) or DEEPAGENTS_CODE_MCP_TOOL_TIMEOUT. Per-server allowedTools / disabledTools are mutually exclusive and an empty list is rejected. Exceptions to the generic OAuth flow: GitHub hosts use the device-code grant and Slack uses a preseeded public client — neither affects Busabase.

How it compares

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

Capability	Deep Agents Code	Claude Code	Cursor
Type	Terminal agents	Terminal agents	AI editors
Recommended path	Agent Skill	Agent Skill	Agent Skill
How it connects	Plugin / Skill · busabase-cli · REST API · MCP + OAuth · MCP + API key	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	OAuth (dynamic registration)	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Nov 12, 2026

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 Deep Agents Code

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