opencode-acp-control

What This Skill Does

The opencode-acp-control skill provides an essential interface for your AI agent to interact directly with OpenCode via the Agent Client Protocol (ACP). By enabling this skill, your agent gains the capability to initiate a standalone OpenCode server session, manage conversation contexts, and execute complex coding workflows. This skill acts as a bridge, translating your agent's instructions into the JSON-RPC 2.0 format required by OpenCode, allowing it to handle file editing, command-line execution, and iterative code development independently. It manages the full lifecycle of a session—from initialization and session creation to active prompting and final teardown.

Installation

To install this skill, use the ClawHub CLI tool in your terminal. Ensure your environment meets the dependency requirements for running OpenCode as a background process. Run the following command: clawhub install openclaw/skills/skills/studio-hakke/opencode-acp-control-2 Once installed, ensure your agent has the necessary permissions to spawn subprocesses and read/write to the project directories where the OpenCode sessions will be hosted.

Use Cases

This skill is perfect for automated software engineering tasks. Use it when you need your agent to:

1. Refactor large codebases by sending specific architectural prompts to OpenCode.
2. Debug runtime errors by initializing a session in a specific working directory and analyzing logs.
3. Automate feature implementation by having the agent generate and test code incrementally.
4. Manage long-running coding tasks where the agent needs to periodically poll for status updates while managing other system responsibilities.

Example Prompts

1. "Start a new OpenCode session in the current directory and ask it to refactor the authentication module to use JWT."
2. "Check the current version of OpenCode and list all existing sessions to see if there is an active session for the project /home/user/workspace/web-app."
3. "Send a prompt to the active OpenCode session to generate a comprehensive unit test suite for the newly created database utility functions."

Tips & Limitations

To maintain system stability, always ensure you track the opencodeSessionId correctly. Because this skill relies on polling, avoid setting polling intervals shorter than 2 seconds to prevent excessive CPU consumption. Note that this skill directly executes shell commands; always ensure that the paths provided to the tool are validated to prevent directory traversal or unauthorized file system modifications. If a session becomes unresponsive, use the provided session/cancel method before attempting to kill the underlying process to ensure a graceful exit of the OpenCode server.