opencode-controller

Control Opencode sessions, agents, and models via slash commands.

588|41|Updated May 13, 2026
One-click install
npx skills add https://github.com/zai-org/Synapse --skill opencode-controller-zai-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-controller
Source: https://github.com/zai-org/Synapse/tree/main/.setup/skills/clawhub/skills/opencode-controller
Command: npx skills add https://github.com/zai-org/Synapse --skill opencode-controller-zai-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Coordinating Opencode-powered workflows across multiple projects is complex; this skill provides a centralized controller to manage sessions, models, and agents via a consistent slash-command surface, reducing context switching and errors.

Core Features & Use Cases

  • Unified command surface to manage sessions, select models, switch agents, and coordinate coding tasks.
  • Enforce a strict Plan → Build loop with explicit user confirmations and guardrails.
  • Enable session reuse and cross-workspace coordination for consistent project outcomes.

Quick Start

Begin by connecting to Opencode, then manage sessions, select a model, switch agents, and coordinate coding through slash commands.

Frequently Asked Questions about opencode-controller

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage coding sessions across multiple projects with workflow orchestration?

Workflow orchestration for coding sessions is managed through a centralized controller that applies slash commands to coordinate sessions, models, and agents across multiple projects. This enforces deterministic plan/build loops with explicit user confirmations as guardrails.

What is the best way to enforce a strict plan and build loop for engineering teams?

A strict plan and build loop is enforced by applying mode switching safeguards and explicit user confirmations before transitioning between phases. This ensures deterministic project outcomes and prevents errors during coding cycles.

How do I select models and switch agents during a coding task?

Models are selected and agents are switched using a unified slash-command surface that controls the workspace. Model authentication prompts are implemented as guardrails to ensure secure and explicit provider selection.

Does workflow orchestration support session reuse for cross-workspace coordination?

Workflow orchestration supports session reuse and cross-workspace coordination through established reuse policies. This enables consistent project outcomes by maintaining context across different workspaces without losing prior session state.

When do I need explicit user confirmations during workflow orchestration?

Explicit user confirmations are required during mode switching and model authentication steps within the workflow orchestration process. These guardrails prevent unintended actions and ensure deterministic execution of the plan/build loop.

Can I coordinate multiple engineering teams using a unified command surface?

Engineering teams can be coordinated using a unified command surface that manages workspace workflow orchestration via slash commands. This reduces context switching and errors by centralizing control over sessions, agents, and models.