Skip to content

Releases: qwertyuiop97/hermes-loadout

Release list

Loadout for Hermes v0.1.0-alpha.1

Loadout for Hermes v0.1.0-alpha.1 Pre-release
Pre-release

Choose a tag to compare

View all tags
@qwertyuiop97 qwertyuiop97 released this 10 Sep 00:20
v0.1.0-alpha.1
e31ad58

Loadout for Hermes keeps a shared skill library without making every skill available to every agent. This is the first public alpha and is intended for careful use with reviewed changes and recoverable backups.

Included

  • Application-first skill controls with independent On/Off state and bulk actions
  • Named skill and MCP loadouts that do nothing until reviewed and applied
  • Read-only discovery plus reviewed imports into the Hermes skill library
  • Searchable setup for documented Global and Project client locations
  • Explicit handling for conflicts, protected entries, broken links, and shared-directory bypasses
  • MCP projection for Hermes, Claude Desktop, and Codex while preserving unrelated settings
  • Receipts, partial-failure reporting, timestamped backups, and reviewed undo
  • Responsive Hermes Desktop interface with a compact pane and full workspace

Safety

Discovery and ordinary-folder imports do not activate skills. Loadout refuses changed plans, unsafe paths, foreign links, and unmanaged files instead of overwriting them. Tests run against isolated homes and disposable client configurations.

The release was verified on Ubuntu, macOS, Windows, and Python 3.9, with the Hermes SDK contract and five interaction/rendering harnesses. A separate native Hermes Desktop walkthrough covered import, activation, named loadouts, conflict recovery, MCP preservation, and secret redaction.

Install

git clone --branch v0.1.0-alpha.1 --depth 1 \
  https://github.com/qwertyuiop97/hermes-loadout.git \
  ~/.hermes/plugins/hermes-loadout
hermes plugins enable hermes-loadout

Then enable Loadout for Hermes in Settings → Plugins, fully quit and reopen Hermes, and begin with Scan & import.

Alpha limitations

Documented client paths are not a certification of every client and operating system combination. Client trust rules, alternate discovery locations, and existing-session caches remain outside Loadout's control. Review the README and every change preview before applying it, and report reproducible problems through the alpha feedback issue template.

Loading