OpenCode

OpenCode plugin support for teams that want that CLI inside the same orchestration layer.

Agent guide

OpenCode lets teams keep a non-default coding agent inside the same orchestration surface without treating it as a second-class shell command or a one-off experiment.

Binary: opencodeAliases: open-code, open_codeBest for alternate fleet paths

Primary binary

opencode

Known aliases

open-code, open_code, opencode

Good fit

Non-default fleets, multi-agent experiments, and CLI-specific dispatch.

​

Set up OpenCode in Conductor

1. Install OpenCode

   # install opencode in your environment
   
2. Complete any vendor setup

   Make sure the CLI runs successfully in the target shell before binding a repository to it.

3. Launch Conductor

   npx --yes --registry=https://registry.npmjs.org conductor-oss@latest
   

   Choose OpenCode for the repositories or experimental paths that need it.

4. Configure the repo default

   projects:
     my-app:
       agent: opencode
   

​

Model selection in Conductor

OpenCode keeps its own provider and model configuration.

• leave agentConfig.model unset when OpenCode should inherit its current default
• add an explicit override only if your OpenCode setup supports it and a repo needs that behavior fixed
• prefer per-repo defaults over per-task model switching so review history stays attributable

​

Why teams pick OpenCode

• keeps alternate agent experiments inside one board
• preserves plugin-native routing
• useful when only specific repos should use OpenCode