OpenCode-CLI-Controller

What This Skill Does

The OpenCode-CLI-Controller is a sophisticated integration layer that transforms your OpenClaw agent into an expert-level Orchestrator for the OpenCode CLI. Instead of manually interacting with file systems or attempting to write code directly, this skill allows the agent to communicate with a running local web server API. It acts as the bridge between the user's intent and the execution power of the OpenCode engine. By adhering to a strict separation of duties—where the agent manages the workflow, session tracking, and reporting while OpenCode handles actual file I/O and implementation—this skill ensures that software development tasks are handled in a structured, observable, and efficient manner.

Installation

To install this skill, use the ClawHub command within your terminal or agent interface:

clawhub install openclaw/skills/skills/malek262/opencode-api-control-skill

Ensure that you have the required prerequisites met before execution. Specifically, verify that a config.json file is present in your root directory containing the base_url for your API and the projects_base_dir. You must also have the ./scripts/ directory populated, as these scripts are the primary mechanisms used to interface with the local server.

Use Cases

• Automated Project Scaffolding: Initiate large-scale project generation by sending high-level architecture requirements to the OpenCode API.
• Continuous Integration Monitoring: Use the skill to track active development sessions, ensuring that code changes are applied and verified without manual intervention.
• Quality Control: Leverage the get_diff.sh script integration to review changes proposed by OpenCode agents before final approval.
• Multi-Session Management: Orchestrate multiple development tasks concurrently, monitoring each session's status via the provided API endpoints.

Example Prompts

1. "OpenCode-CLI-Controller, please initialize a new project session for a React-based dashboard and track its progress until completion."
2. "Check the current status of the active OpenCode session and provide a summary of the latest file diffs."
3. "Start the OpenCode server, wait for initialization, and then initiate an auto-debug sequence for the current repository."

Tips & Limitations

• Initialization Latency: Always respect the 10-15 second buffer period after starting the server. Sending requests too early will result in connection errors.
• Orchestrator Mentality: Do not attempt to fix code manually. If a task fails, use the controller to query the logs and communicate the error back to the OpenCode engine.
• Operational Boundaries: You are prohibited from direct file manipulation. Always route your operations through the provided API scripts to maintain consistency with the OpenCode environment.