Busabase for AutoClaw (澳龙)Connect AutoClaw (澳龙) to Busabase
Zhipu's desktop general-purpose agent: the first one-click local OpenClaw app, with 50+ built-in skills, MCP services, IM channels (Feishu, WeCom, WeChat, DingTalk, QQ), goal mode and agent clusters.
Paste this into AutoClaw (澳龙)
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
Skill format (SKILL.md vs proprietary) is not stated; the product is OpenClaw-based (SOUL.md/USER.md/MEMORY.md workspace files). Do the setup from the desktop app, not an IM channel.
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
- Zhipu AI (智谱)
- How it connects
- Plugin / Skill · busabase-cli · REST API
- Transport
- Unknown
- Authentication
- Unknown
AutoClaw (a one-click local OpenClaw desktop app) can fetch a URL and run shell commands, so the Skill path applies. Paste this into a chat with it: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review the commands it proposes (npx busabase-cli login --no-wait, npx skills add busabase/skills --skill busabase busabase-app-creator), approve the sign-in link in your browser, then ask it to verify the active Busabase account.
Prefer a connector?
In AutoClaw open Settings → MCP 服务 (MCP services), add a service, and fill in the name, connection type, service address (https://busabase.com/api/mcp) and any auth config; save, check the connection status, then enable it on the target Agent. AutoClaw's docs do not say which transports or auth modes (OAuth vs header token) the form supports, so treat the connector route as unverified for Busabase and prefer the Skill route.
Known gotchas
Skill page is marked 🚧 (under construction). The docs state cloud ('云龙虾') instances may not install from the Skill store directly; ask the agent to install it instead. High-risk-operation handling should stay 'Ask'; for tasks arriving from IM channels (no approval UI) the default should be 'Deny', which would block shell commands from IM.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | AutoClaw (澳龙) |  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 AutoClaw (澳龙)
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.