Skip to main content
Use Pluxx in OpenCode when you want a code-first OpenCode wrapper plus optional OpenCode review and refinement runs.

​
What OpenCode Consumes

Pluxx builds the OpenCode target into dist/opencode/. OpenCode consumes a code plugin, not a manifest-only bundle. Pluxx emits:
  • package.json
  • index.ts
  • skills/
  • commands/
  • scripts/
  • assets/
The generated index.ts wrapper registers:
  • plugin commands
  • MCP servers
  • hook handlers
  • instruction injection
  • permission mappings

​
Build And Install

npx @orchid-labs/pluxx build --target opencode --install
If you already built the bundle, install it directly: 
npx @orchid-labs/pluxx install --target opencode
Pluxx installs the local OpenCode plugin to:
  • ~/.config/opencode/plugins/<plugin>
If the plugin defines local hook commands, add --trust or confirm the trust prompt during install.

​
Agent-Driven Refinement

Build and install are deterministic. OpenCode only does model work when you explicitly run an agent pass: 
npx @orchid-labs/pluxx agent prepare
npx @orchid-labs/pluxx agent run review --runner opencode --no-verify
OpenCode is also the only Pluxx runner that supports attach mode: 
npx @orchid-labs/pluxx agent run review --runner opencode --attach http://localhost:4096 --no-verify

​
OpenCode-Specific Caveats

  • OpenCode plugins are programmatic wrappers. Hooks, MCP config, and instruction injection live in generated code inside index.ts, not in separate JSON manifests.
  • OpenCode runner model selection inherits the local OpenCode default unless you explicitly pass --model.
  • OpenCode permissions are compiled to native tool-level config.permission entries. Fine-grained selector rules, such as exact file globs or specific MCP tool names, are downgraded to coarse tool permissions.