| name | acp-bridge-caller |
| description | v0.9.2 — 通过 ACP Bridge HTTP API 调用远程 CLI agent。Usage: /cli <prompt> | /cli ko <prompt> (kiro) | /cli cc <prompt> (claude) | /cli qw <prompt> (qwen) | /cli oc <prompt> (opencode) | /chat ko (进入对话模式) |
| disable-model-invocation | true |
ACP Bridge Caller
Call remote CLI agents via ACP Bridge HTTP API.
All calls go through acp-client.sh in this skill directory:
ACP_CLIENT="${CLAUDE_SKILL_DIR}/acp-client.sh"
chmod +x "$ACP_CLIENT"
First Time Setup
If ACP Bridge is not yet installed or running, follow the full setup guide:
👉 AGENT.md — Agent Execution Guide
It covers environment diagnosis, installation, configuration, and service startup (Docker / systemd / nohup).
Note: OpenClaw is optional — only needed for async job push (Discord/Feishu) and tools proxy. The core agent API (/runs, /agents) works standalone.
Once the Bridge is running and you can reach its /health endpoint, proceed below.
Auth Setup
Before the first call, both ACP_BRIDGE_URL and ACP_TOKEN are required. If not set, stop and ask the user.
export ACP_BRIDGE_URL=<bridge_url>
export ACP_TOKEN=<token>
Never display the token in plaintext. If unauthorized, tell the user "the token may be incorrect".
Commands
| Command | Action |
|---|
/cli <prompt> | $ACP_CLIENT "<prompt>" |
/cli ko <prompt> | $ACP_CLIENT -a kiro "<prompt>" |
/cli cc <prompt> | $ACP_CLIENT -a claude "<prompt>" |
/cli cx <prompt> | $ACP_CLIENT -a codex "<prompt>" |
/cli qw <prompt> | $ACP_CLIENT -a qwen "<prompt>" |
/cli oc <prompt> | $ACP_CLIENT -a opencode "<prompt>" |
/chat ko [--cwd <path>] | Enter kiro chat mode |
/chat cc [--cwd <path>] | Enter claude chat mode |
/chat qw [--cwd <path>] | Enter qwen chat mode |
/chat oc [--cwd <path>] | Enter opencode chat mode |
/chat end | Exit chat mode |
/chat status | Show chat status |
Message Routing
Matched by priority, first match wins:
- Starts with
/chat → Chat command
- Starts with
/cli → Single CLI call
chat-state.json exists and active_agent is set → Forward to current agent- Fallback → Normal processing (no Bridge call)
Chat Mode
Once activated, subsequent messages are automatically forwarded to the agent without the /cli prefix.
Activate: /chat ko or /chat cc [--cwd <path>]
- Generate a deterministic session_id (UUID v5, same as
/cli mode)
- Write
chat-state.json (active_agent, session_id, cwd, started_at)
- Reply:
🟢 Entered kiro chat mode (session: xxx)
Forward: $ACP_CLIENT -a <active_agent> -s <session_id> [--cwd <cwd>] "<user message>"
Exit: /chat end → Delete chat-state.json, reply: 🔴 Exited chat mode
Status: /chat status → Read chat-state.json, output agent, session, cwd, and uptime
Switch: Run /chat cc directly to replace state; the old session is preserved on the server.
Session ID
- The script auto-generates a deterministic UUID (based on agent name); the same agent always reuses the same session
- Different agents use different session_ids to avoid conflicts
- Manual override:
$ACP_CLIENT -s <uuid> "<prompt>"
Additional Resources
