OpenCode plugin for Claude Code
Use OpenCode from inside Claude Code for code reviews or to delegate tasks to OpenCode.
This plugin is for Claude Code users who want an easy way to start using OpenCode (any provider, any model — Anthropic, OpenAI, OpenRouter, local) from the workflow they already have. It mirrors the openai/codex-plugin-cc plugin's surface, with the delegate swapped from Codex to OpenCode.
What You Get
/opencode:review for a focused review of your current work/opencode:adversarial-review for a steerable challenge review/opencode:rescue, /opencode:status, /opencode:result, and /opencode:cancel to delegate work and manage background jobs
Requirements
- A working
opencode CLI with at least one provider configured (opencode auth login).
- Usage will draw on whichever provider OpenCode is configured to use.
- Node.js 18.18 or later
Install
Add the marketplace in Claude Code:
/plugin marketplace add mubeda/opencode-plugin-cc
Install the plugin:
/plugin install opencode@opencode-cc
Reload plugins:
/reload-plugins
Then run:
/opencode:setup
/opencode:setup will tell you whether OpenCode is ready. If OpenCode is missing and npm is available, it can offer to install OpenCode for you.
If you prefer to install OpenCode yourself, use:
npm install -g opencode-ai
If OpenCode is installed but has no provider configured yet, run:
!opencode auth login
After install, you should see:
- the slash commands listed below
- the
opencode:opencode-rescue subagent in /agents
One simple first run is:
/opencode:review --background
/opencode:status
/opencode:result
Updating an installed version
Refresh the marketplace catalog, then update the plugin:
/plugin marketplace update opencode-cc
/plugin update opencode@opencode-cc
Reload plugins to pick up the new version:
/reload-plugins
Usage
/opencode:review
Runs an OpenCode review on your current work using a provider-neutral review prompt. Output is whatever the configured model produces in Markdown.
[!NOTE]
Reviews of multi-file changes might take a while. It's generally recommended to run them in the background.
Use it when you want:
- a review of your current uncommitted changes
- a review of your branch compared to a base branch like
main
Use --base <ref> for branch review. It also supports --wait and --background. It is not steerable and does not take custom focus text. Use /opencode:adversarial-review when you want to challenge a specific decision or risk area.
Examples:
/opencode:review
/opencode:review --base main
/opencode:review --background
This command is read-only and will not perform any changes itself. The companion runs OpenCode with --dangerously-skip-permissions, but the review prompt explicitly tells the model not to modify files.
/opencode:adversarial-review
Runs a steerable review that questions the chosen implementation and design.
It can be used to pressure-test assumptions, tradeoffs, failure modes, and whether a different approach would have been safer or simpler.
It uses the same review target selection as /opencode:review, including --base <ref> for branch review.
It also supports --wait and --background. Unlike /opencode:review, it can take extra focus text after the flags.
Use it when you want:
- a review before shipping that challenges the direction, not just the code details
- review focused on design choices, tradeoffs, hidden assumptions, and alternative approaches
- pressure-testing around specific risk areas like auth, data loss, rollback, race conditions, or reliability
Examples:
/opencode:adversarial-review
/opencode:adversarial-review --base main challenge whether this was the right caching and retry design
/opencode:adversarial-review --background look for race conditions and question the chosen approach
This command is read-only. It does not fix code.
/opencode:rescue
Hands a task to OpenCode through the opencode:opencode-rescue subagent.
Use it when you want OpenCode to:
- investigate a bug
- try a fix
- continue a previous OpenCode task
- take a faster or cheaper pass with a smaller model
[!NOTE]
Depending on the task and the model you choose these tasks might take a long time and it's generally recommended to force the task to be in the background or move the agent to the background.
It supports --background, --wait, --resume, and --fresh. If you omit --resume and --fresh, the plugin can offer to continue the latest rescue thread for this repo.
Examples:
