Feature Description
It would be great if Command Code exposed an ACP-compatible entrypoint, for example:
Fallback
Even a minimal ACP adapter around existing Command Code sessions would be useful. command-code -p works for one-shot tasks, but it does not provide proper ACP session lifecycle or streaming/tool semantics.
Use Case
OpenClaw supports external coding agents through ACPX, and can already run harnesses like Claude Code, Codex, Gemini, OpenCode, Kimi, etc. Command Code looks like a strong fit for this because it already has:
a CLI
non-interactive mode with command-code -p
model selection
permission modes
MCP support
taste/memory/session concepts
Then it could be registered as an external ACP harness from OpenClaw/acpx, e.g.:
{
"agents": {
"commandcode": {
"command": "command-code acp"
}
}
}
Additional Context
No response
Feature Description
It would be great if Command Code exposed an ACP-compatible entrypoint, for example:
Fallback
Even a minimal ACP adapter around existing Command Code sessions would be useful.
command-code -pworks for one-shot tasks, but it does not provide proper ACP session lifecycle or streaming/tool semantics.Use Case
OpenClaw supports external coding agents through ACPX, and can already run harnesses like Claude Code, Codex, Gemini, OpenCode, Kimi, etc. Command Code looks like a strong fit for this because it already has:
a CLI
non-interactive mode with command-code -p
model selection
permission modes
MCP support
taste/memory/session concepts
Then it could be registered as an external ACP harness from OpenClaw/acpx, e.g.:
{ "agents": { "commandcode": { "command": "command-code acp" } } }Additional Context
No response