Superpowers tutorial series · Updated October 20, 2026.
Install Superpowers in Claude Code, Codex, Cursor, or OpenCode
Claude Code uses a plugin marketplace; Codex uses its plugin interface; Cursor uses /add-plugin superpowers; OpenCode uses its own plugin configuration. Install separately in each agent you use.
| Agent | Installation entry | Verification |
|---|---|---|
| Claude Code | Plugin marketplace | Plugin installed, then skill loading in a fresh session |
| Codex app or CLI | Codex plugins | Superpowers appears in installed plugins |
| Cursor | Agent plugin command | Plugin visible in the marketplace/installed list |
| OpenCode | Version-specific config | Plugin logs and native skill discovery |
What is Superpowers?
Superpowers is a collection of development skills covering design, planning, debugging, testing, review, and verification. Its value is a repeatable process: understand a feature before implementing it, investigate failures with evidence, and verify results before declaring completion.
Those instructions run inside a coding agent. They do not create a universal permissions layer or guarantee that every model will follow every step. Repository instructions and the user’s requirements still matter.
If you meant Garry Tan’s gstack, use the gstack installation guide; the two projects have different installers and skill names.
Before you install
Update the coding agent you actually use and check its plugin support. Where an installation uses Git, verify git --version. Keep existing configuration and local skill customizations available for comparison.
Do not create a superpowers: block in a guessed YAML file. Use the agent’s supported plugin interface or the upstream instructions for your exact harness. Installing the plugin in Claude Code does not install it in Codex or OpenCode.
Platform 1: Install on Claude Code
The current upstream README lists Anthropic’s official marketplace:
/plugin install superpowers@claude-plugins-official
If you use the project’s own marketplace instead, its documented route is:
/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace
Choose one source rather than installing the same framework twice. Inspect Claude Code’s plugin manager to confirm that installation completed, then start a fresh session.
For a small verification task, ask:
Use the brainstorming skill to plan a comment feature for a static blog.
Explain the design first and wait before implementation.
Check for actual skill loading and a design tied to the request. Generic questions alone do not prove the plugin loaded. Update through the plugin manager for the marketplace you selected; check its result rather than assuming a restart upgraded the package.
Platform 2: Install on Cursor
In Cursor Agent chat, the documented command is:
/add-plugin superpowers
You can also search for Superpowers in Cursor’s plugin marketplace. Confirm the plugin is installed and enabled, open a fresh Agent session, and explicitly request brainstorming for the small task above.
The older /plugin-add superpowers spelling in this article was incorrect. If a command is unavailable in your Cursor version, use its marketplace interface and check the current upstream README. Changing unrelated auto-accept settings is not an installation fix.
Platform 3: Install on Codex
For the Codex app, upstream currently directs users to Plugins → Coding → Superpowers and the install control. For the Codex CLI, use the plugin interface:
/plugins
Search for superpowers and select Install Plugin. Check the installed-plugin entry, then open a fresh session and explicitly request one of its skills.
Older tutorials used a raw .codex/INSTALL.md URL and a manually linked skill checkout. That file returns 404 in the upstream revision checked for this update. Use the current official Superpowers installation section rather than copying a missing-file prompt or inventing ~/.codex/config.yaml settings.
If you previously used a manual installation, inventory its checkout and skill links before migrating. Avoid leaving two copies discoverable, and preserve any local changes. A missing plugin interface in an older CLI is a reason to check supported versions, not proof that the plugin has been installed.
Platform 4: Install on OpenCode
Check your OpenCode version first:
opencode --version
Merge the relevant entry into your existing opencode.json; keep the other settings intact. The current upstream installer distinguishes V1’s singular plugin from V2’s plural plugins.
For OpenCode V1:
{
"plugin": ["superpowers@git+https://github.com/obra/superpowers.git"]
}
For OpenCode V2, version 2.0.4 or later:
{
"plugins": ["superpowers@git+https://github.com/obra/superpowers.git"]
}
Restart OpenCode, then ask it to list available skills through its native skill tool and load brainstorming. The plugin should both load and expose its skills. A startup without errors is not sufficient if the skills never appear.
If you pin a dependency revision, use a compatible release: upstream requires Superpowers v6.4.1 or later for OpenCode V2. Some OpenCode/Bun versions retain a resolved Git dependency in a cache or lockfile, so restarting alone may not update it. Inspect the installed revision and follow upstream’s upgrade guidance before clearing anything.
For Windows and local-checkout installation, follow the OpenCode installer document. In particular, use its supported package-directory path; V2 2.0.4 and 2.0.7 reject a direct JavaScript-file path. Do not assume that a ~/... config string is expanded to your home directory.
Verify your installation
Verify in layers rather than asking the agent whether it “has superpowers” and accepting the answer:
| Layer | Evidence to look for |
|---|---|
| Installed | The correct plugin entry or OpenCode dependency is present |
| Loaded | A fresh session discovers and loads a named skill |
| Useful | A small design or debugging task follows that skill’s instructions |
| Integrated | The project’s own tests and review steps work when you later implement a real change |
Start with a planning-only request to avoid unnecessary file changes. Test debugging with a harmless reproducible failure in a disposable repository. Running a skill does not guarantee that tests were executed, that a worktree was created, or that a change was published; inspect each result separately.
Troubleshooting
| Problem | Likely check | Useful next step |
|---|---|---|
| Plugin installed, no skill behavior | Session started before installation | Open a fresh session and request a skill explicitly |
| Cursor command not recognized | Wrong command spelling or version | Use /add-plugin or the marketplace interface |
| Codex raw install link returns 404 | Retired installation document | Use the current plugin route |
| OpenCode plugin never loads | plugin versus plugins, version, install logs |
Match the config to V1 or V2 and inspect the reported error |
| OpenCode skill list is empty | Dependency loaded but skills were not registered | Inspect plugin logs and the upstream OpenCode guide |
| Duplicate/conflicting instructions | Old manual copy plus plugin install | Compare discovered sources and remove only the obsolete installation after preserving customizations |
Do not try to fix discovery by adding undocumented variables such as SUPERPOWERS_ENABLED, or configuration for caches and subagent limits that the installer does not define. Diagnose the actual loading path first.
Adopt one workflow at a time
Begin with brainstorming and writing plans. Once installation is clear, use systematic debugging for a real failure and require concrete verification before completion.
For a team, record the supported agent versions, installation source, and project instructions. Share a small acceptance task so teammates can distinguish “the plugin is installed” from “our workflow actually works.”
References
- Official Superpowers README
- Superpowers marketplace
- OpenCode installation and migration
- OpenCode integration details
Installation commands and configuration above were checked against upstream documentation; this article does not claim an end-to-end installation on all four agents.