NanoClaw 專屬的 Busabase把 NanoClaw 連接到 Busabase
NanoCo's open-source personal assistant that runs each agent in its own Linux container (Claude Agent SDK by default) and talks to you over WhatsApp, Telegram, Slack, Discord, iMessage and more.
把這段貼進 NanoClaw
請閱讀 https://busabase.com/SETUP_SKILL.md，並幫我設定好 Busabase。請照著文件一路做到完成，最後確認連線是否正常運作。
Busabase
把這一句指令交給你的 Agent
你得到的不只是一個連接器：busabase 技能還帶著完整的變更請求工作流程、CLI 與完整 API —— 之後每一次工作階段都在，不必再重新貼一次。
會先問你
Busabase Cloud 還是個人桌面版 —— 在動手之前，由你決定。
完成連線
幫你登入並自行儲存憑證，不需要手動複製 API 金鑰。
建立一個資料表
建立並填入你的第一個資料表，讓工作區一開始就不是空白畫面。
安裝技能
busabase 與 busabase-app-creator 會永久安裝，之後每一次工作階段都能直接使用。
此 Agent 的注意事項
Agents run in ephemeral per-group containers; the docs do not say whether skills installed by `npx skills add` or the `busabase-cli` login state persist across container spawns. Outbound HTTPS goes through the credential gateway, so busabase.com must be reachable from it. NanoClaw's own skills are SKILL.md folders (container skills at `container/skills/`, per-template `skills/<name>/SKILL.md` with `name` + `description` frontmatter, Agent Plugins 1.0.0 format); the `.claude/skills/` host skills are for the coding harness customising NanoClaw, not for the agent.
比較想用連接器？
如果你不想讓 Agent 自行安裝技能，而是想把 Busabase 當作 MCP 工具接進來，可以使用下面這個伺服器網址。
一覽表
- 廠商
- NanoCo
- 連接方式
- 外掛／技能 · busabase-cli · REST API · MCP + API 金鑰
- 傳輸方式
- Streamable HTTP
- 驗證方式
- API 金鑰
- 設定檔
- Per agent group, in NanoClaw's central DB (container config `mcp_servers`); set with `ncl groups config add-mcp-server`. Template form: `mcp.json` -> `mcpServers`.
git clone https://github.com/nanocoai/nanoclaw.git nanoclaw-v2 && cd nanoclaw-v2 && bash nanoclaw.shNanoClaw agents run Claude Code (or another provider) inside a container with a shell and web access, so the Skill path applies: paste the prompt above into any channel your agent is paired with.
Prefer a connector?
NanoClaw can register a remote Streamable HTTP MCP server per agent group. It has no documented OAuth sign-in for MCP; credentials are injected by the host's credential gateway (OneCLI Agent Vault), never stored in the MCP entry.
- In Busabase, open Settings -> API Keys and create a key with the smallest permission and a finite expiry.
- On the NanoClaw host, store it in the vault for the Busabase host, then grant it to the agent group:
onecli secrets create --name Busabase --type api_key --value "$BUSABASE_KEY" --host-pattern busabase.com
- Register the server (no secret in the command) and restart the group:
ncl groups config add-mcp-server --id <group-id> --name busabase --url https://busabase.com/api/mcp
ncl groups restart --id <group-id>
- Ask the agent to call
auth_verify.
已知的注意事項
Remote MCP URLs must be HTTPS and must not embed credentials; the legacy `sse` transport is not supported; custom headers are for non-secret values only. Secrets live in the OneCLI vault and are matched by host, so the key must be registered for busabase.com and granted to the agent group. Host-side `ncl` and container-side tools differ: `ncl` write commands run from inside a container are approval-gated.
能力比較
與目錄中其他已收錄的 Agent，並列比較連線能力。
| 能力 | NanoClaw |  Claude Code |  Cursor |
|---|---|---|---|
| 類型 | Agent 平台 | 終端機 Agent | AI 編輯器 |
| 推薦路徑 | Agent Skill | Agent Skill | Agent Skill |
| 連接方式 | 外掛／技能 · busabase-cli · REST API · MCP + API 金鑰 | MCP + OAuth · 外掛／技能 | MCP + OAuth · 外掛／技能 |
| 傳輸方式 | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| 驗證方式 | API 金鑰 | OAuth（動態註冊） | OAuth（動態註冊） |
把這段貼進 NanoClaw
請閱讀 https://busabase.com/SETUP_SKILL.md，並幫我設定好 Busabase。請照著文件一路做到完成，最後確認連線是否正常運作。