- I searched existing issues and this has not been proposed before
What problem does this solve?
Hermes Desktop updates only plugins from the Hermes plugin catalog. A plugin installed from its Git URL, which is how superpowers is installed today, can't be updated from Desktop: the Plugins tab answers "'superpowers' is not a catalog install — update it via the CLI". Desktop users who don't use a terminal have no update path.
Proposed solution
Submit a catalog entry. Each entry is pinned to a commit a Hermes maintainer reviewed, and each version bump is a new reviewed PR (catalog-submission.md, rules 2–4). Desktop then shows an Update button, and asks again when a new version adds tools, hooks or capabilities. Admission takes a submission from the repository owner or a major contributor (rule 5), so a user can't open it on your behalf.
What alternatives did you consider?
Pinning the Git install and updating by hand after reviewing the diff, which we do now. That works only for someone who can run the CLI. Changing Hermes Desktop to update Git-URL installs runs against Hermes' decision that the catalog is its sole discovery system.
Is this appropriate for core Superpowers?
It affects every Hermes Desktop user of superpowers, regardless of project.
Environment (required)
| Field | Value |
|---|---|
| Superpowers version | 7.0.0 (bb92a77) |
| Harness (Claude Code, Cursor, etc.) | Hermes Agent (Desktop) |
| Harness version | v0.22.2 (2026.9.24), core d923a5eb48 |
| Your model + version | Claude Opus 5.5, which wrote this request after checking the Desktop update path in a real session |
| All plugins installed | superpowers, redline, honey, provenance-guard, you-should-know, plus four of the owner's own plugins |
Drafted by an AI agent (Claude Opus 5.5 running in Hermes Agent v0.22.2 on Windows 11) for the account owner, who reviewed this text before it is posted.
Activity
0No activity yet.