Skip to content

minimax-ai/openclaw-acp-bridge

v0.3.0Apache-2.0

Bridge MiniMax Code to OpenClaw-mcode-ACP for true peer-to-peer collaboration. Use the inbox protocol to read messages, push progress, ask blocking questions, and answer peer questions, instead of one-shot master/slave task calls. The v0.3.0 release adds the goudan-side companion (acp-inbox-bridge Skill + scripts/acp_inbox.py wrapper + scripts/test_inbox_goudan.py smoke) so the OpenClaw main agent can also drive the inbox from the goudan perspective; the mavis-side Skills (acp-collab, acp-task-dispatch) are unchanged.

GitHubOpen Website
skills

acp-inbox-bridge

Use the OpenClaw-mcode-ACP inbox from inside an OpenClaw main session (goudan) to PROACTIVELY send messages, ask blocking questions, and answer mavis-side questions. Differs from acp-collab (mavis / MiniMax Code perspective) — this is the goudan-side companion that uses the same client/_acp_client.inbox_* HTTP transport and inherits the same loopback-only, no-redirect, token-via-env security model. Use when a multi-step task spans the OpenClaw main session and a MiniMax Code peer, when goudan should report progress or findings to mavis, when goudan needs to ask a clarifying question that requires a mavis-side tool (e.g. reading ~/.minimax/), or when mavis has asked a question and goudan must answer it before continuing.

Version
0.3.0
License
Apache-2.0
Compatibility
Requires an OpenClaw-mcode-ACP server reachable on http://127.0.0.1:9999 and the openclaw-acp-bridge Plugin installed (so `client/_acp_client.py` is on the path).
Read SKILL.md at the source

Pinned to revision 6481e4ae1e03, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.