OpenCode V2 requires version 2.0.4 or later.
Use the existing V1 plugin configuration:
{
"plugin": ["superpowers@git+https://github.com/obra/superpowers.git"]
}
Use the V2 plugin configuration:
{
"plugins": ["superpowers@git+https://github.com/obra/superpowers.git"]
}
For a local V2 installation, configure the repository directory containing
index.js. OpenCode 2.0.4 and 2.0.7 reject a configured direct JavaScript-file
path. Discovered plugin symlinks remain supported.
Restart OpenCode. V2 uses the opencode command; opencode2 may be available
as an alias. The plugin installs through OpenCode's plugin manager and
registers all skills.
Verify by asking: "Tell me about your superpowers"
OpenCode uses its own plugin install. If you also use Claude Code, Codex, or another harness, install Superpowers separately for each one.
If you previously installed superpowers using git clone and symlinks, remove the old setup:
# Remove old symlinks
rm -f ~/.config/opencode/plugins/superpowers.js
rm -rf ~/.config/opencode/skills/superpowers
# Optionally remove the cloned repo
rm -rf ~/.config/opencode/superpowers
# Remove skills.paths from opencode.json if you added one for superpowers
Then follow the installation steps above.
Use OpenCode's native skill tool:
use skill tool to list skills
use skill tool to load brainstorming
OpenCode installs Superpowers through a git-backed package spec. Some OpenCode and Bun versions pin that resolved git dependency in a lockfile or cache, so a restart may not pick up the newest Superpowers commit. If updates do not appear, clear OpenCode's package cache or reinstall the plugin.
To pin a specific version, add a tag or commit to the spec (same form for the
V1 plugin key and the V2 plugins key):
{
"plugin": ["superpowers@git+https://github.com/obra/superpowers.git#v6.4.1"]
}
On V2, pin v6.4.1 or later; v6.3.0 and earlier releases load only on V1.
opencode run --print-logs "hello" 2>&1 | grep -i superpowers.
V2 loads plugins in the background server, so add --standalone:
opencode run --standalone --print-logs "hello" 2>&1 | grep -i superpowers,
or inspect ~/.local/share/opencode/log/opencode.log filtering for role=server.opencode.jsonSome Windows OpenCode builds have upstream installer issues with git-backed
plugin specs, including cache paths for git+https URLs and Bun not finding
git.exe even when it works in a normal terminal. If OpenCode cannot install
the plugin, try installing with system npm and pointing OpenCode at the local
package:
npm install superpowers@git+https://github.com/obra/superpowers.git --prefix "$HOME\.config\opencode"
Then use the absolute path of the installed package in opencode.json for your
OpenCode version. OpenCode does not expand ~; a ~/... entry is treated as a
package name, not a local directory.
V1:
{
"plugin": ["C:\\Users\\<you>\\.config\\opencode\\node_modules\\superpowers"]
}
V2 (2.0.4 or later):
{
"plugins": ["C:\\Users\\<you>\\.config\\opencode\\node_modules\\superpowers"]
}
skill tool to list what's discoveredSkills speak in actions ("create a todo", "dispatch a subagent", "read a file"). The plugin injects a flavor-specific mapping — check your OpenCode version:
V1 (opencode 1.x):
todowriteSubagent (general-purpose): template → task tool with subagent_type: "general" (or "explore" for codebase exploration)skill toolreadapply_patchbashgrep, globwebfetchV2 (opencode 2.0.4 or later; opencode2 may be available as an alias):
Subagent (general-purpose): template → subagent tool with agent: "general" (or "explore"); pass sessionID to continue a previous subagentskill toolreadpatch with patchText when available; otherwise use write to create or overwrite files, edit for targeted changes, and shell for deletionshell (command, workdir, timeout, background)grep, globwebfetchwebsearch