OpenCode ACP Channel Plugin

Problem

OpenClaw already provides a chat entry point, but delegating complex coding work to OpenCode can still feel fragmented by external scripts, throwaway sessions, and manual context handoffs. The OpenCode ACP channel plugin attaches OpenCode to an ACP channel so a current chat thread can start, retain, and steer a code-task session with less manual tooling glue.

How It Works

• Session start: use /acp spawn opencode to create an ACP session and bind the current chat thread to the target OpenCode instance.
• Continued interaction: persistent sessions support /acp steer for follow-up commands, avoiding repeated context setup.
• Lifecycle control: the plugin covers session lifecycle management and permission configuration, which fits controlled code-agent invocation and debugging boundaries.

Notes

It acts mainly as a channel and orchestration layer, not a source of code-style, testing, or project rules. Outcomes depend on the OpenCode backend, model permissions, and repository context. If the environment lacks a usable backend, auth configuration, or permission policy, those prerequisites must be prepared before using it from a chat thread.