hermes - 💡(How to fix) Fix [IMPROVEMENT] No version pinning for installed plugins in $HERMES_HOME [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#20350Fetched 2026-05-06 06:37:14
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Severity: Medium

Problem: After installing plugins (via hermes plugins install or deploy_hermes_provider.sh), there is no manifest or lock file in ~/.hermes/ that records which version was installed, from which commit/branch/tag, or when. Rollbacks are impossible — if a plugin update breaks behavior, there is no way to reconstruct the previous state.

Proposed fix: Create a ~/.hermes/manifest.toml written on every plugin install, recording name, version, source URL, and install timestamp. A hermes plugins rollback <name> command could then read it. Alternatively, a requirements-hermes.txt or pyproject.lock equivalent managed via pip/editable installs would achieve the same end.

extent analysis

TL;DR

Create a ~/.hermes/manifest.toml file to track plugin installations and enable rollbacks.

Guidance

  • Implement a mechanism to write the manifest.toml file during plugin installation via hermes plugins install or deploy_hermes_provider.sh, recording plugin name, version, source URL, and install timestamp.
  • Develop a hermes plugins rollback <name> command to read the manifest.toml file and revert to a previous plugin version.
  • Consider using an existing package manager like pip to manage plugins and generate a requirements-hermes.txt or pyproject.lock file for easier dependency tracking.
  • Verify the fix by installing a plugin, checking the manifest.toml file for correct information, and attempting a rollback to a previous version.

Example

# ~/.hermes/manifest.toml
[[plugin]]
name = "example-plugin"
version = "1.0.0"
source_url = "https://example.com/plugin.git"
install_timestamp = 1643723400

Notes

This solution assumes that the hermes command-line tool and plugin installation scripts have the necessary functionality to write to the manifest.toml file and read from it during rollbacks.

Recommendation

Apply workaround: Create a ~/.hermes/manifest.toml file to track plugin installations, as this provides a straightforward solution to the problem of tracking plugin versions and enabling rollbacks.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [IMPROVEMENT] No version pinning for installed plugins in $HERMES_HOME [1 participants]