Keep marketplace Superpowers plugin closer to upstream releases (stuck on 5.0.7 while 6.x is out)

Ideas Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

Please keep the Cursor marketplace build of the Superpowers plugin closer to upstream releases, or make the installed version / update lag more visible in the UI.

What we see today

On a current Cursor install (Windows), the cached Superpowers plugin reports:

  • package.json version: 5.0.7
  • Cache path: ~/.cursor/plugins/cache/cursor-public/superpowers/<hash>/
  • Local git HEAD around 2026-04-01
  • Still ships the pre-6.0 dual reviewer prompts (spec-reviewer-prompt.md + code-quality-reviewer-prompt.md)

Meanwhile upstream obra/superpowers has already released v6.0.0+ (latest around v6.1.1), which includes meaningful workflow changes (e.g. single task-reviewer with dual verdicts, plan pre-flight, forge-neutral finishing, cheaper review loop).

So teams that follow Superpowers docs / release notes for “v6” behavior are actually running a months-old 5.x marketplace build without realizing it.

Why this matters

We run multi-agent / end-to-end workflows and encode process rules against Superpowers concepts. Version lag causes:

  1. Agents follow outdated review patterns (more expensive / easier to game than v6)
  2. Docs and local skills disagree, so process design reviews give wrong advice
  3. No obvious UI signal that marketplace plugin ≠ latest upstream tag

Expected behavior

Any of these would help:

  1. Faster marketplace sync for Superpowers (days, not months)
  2. In Extensions / Plugins UI: show installed version and upstream latest, with an Update action
  3. Optional: allow pinning / installing from a specific upstream tag or git ref for power users

Environment

  • OS: Windows 10/11
  • Plugin: Superpowers via Cursor marketplace cache (cursor-public/superpowers)
  • Installed: 5.0.7
  • Upstream latest observed: v6.1.1

Thanks!

Operating System (if it applies)

Windows 10/11

5

Hey, thanks for the detailed report. You laid everything out very clearly.

There are basically two separate things here, and both are valid:

  1. The marketplace build is behind upstream. You’re right, the cursor-public/superpowers cache is on 5.0.7, while upstream is already on v6.x. We should sync that. I’ll flag the plugin for a re-sync to the latest version.

  2. There’s no UI signal that the installed version is not the latest upstream. Right now the Plugins UI really only has install and uninstall, with no installed vs latest info and no Update action. That’s a good idea for a durable fix. I’ll pass it to the team as a feature request. I’ll also note pinning or installing from a specific tag or git ref as a separate item.

As a temporary workaround for power users, you can install the plugin directly from the upstream git repo via your personal /add-plugin by specifying the ref you want. That will bypass the cached marketplace build. Just note that this path currently has some rough edges around pinning to a specific commit, so after a manual update please double-check the actual version in the cache.

A similar marketplace-behind-upstream issue is discussed here: Cursor marketplace installs/offers outdated version of Open VSX extension despite latest version being available upstream. I’m linking it as related.

I can’t share an ETA for a fix yet, but the request is logged. Let me know if the /add-plugin workaround doesn’t work.