Repository navigation
Releases
v0.2.0 — First-Turn-Routing auf jedem Provider-Request
v0.2.0 — First-Turn-Routing auf jedem Provider-Request
Die Werkzeugflaeche wird jetzt im ersten Provider-Request einer Session
verengt, nicht erst ab Turn 2. v0.1.x konnte den ersten Turn nicht erreichen:
der Hook, der die Flaeche kuerzt, feuert bevor das Modell ein Werkzeug gewaehlt
hat — und genau diese Werkzeugwahl ist die einzige Wissensquelle.
Was diese Version enthaelt
- First-Turn-Routing ueber die
llm_request-Middleware, inklusive
Anthropic-Tool-Format. - Session-sticky Surface: die Verengung bleibt ueber die ganze Session
bestehen. - Der Router routet tatsaechlich. In v0.1.x wurde der Agent ueber einen
Stack-Walk aufgeloest; der Hook laeuft auf einem Daemon-Worker, dessen
Aufrufer-Stack abgeschnitten ist. Der Agent wird jetzt ueber die Session
aufgeloest — ohne globalescurrent_agent, damit parallele Sessions nie
einen Agenten teilen. - Das flache Plugin-Payload ist wieder importierbar. Ein relativer Import
ohne Package-Eltern scheiterte still; der Fallback liegt jetzt in der Datei. - Die Konfiguration laedt nicht mehr mit einem harten
import yaml.
PyYAML fehlt im Hermes-Host (er bringtruamel.yamlmit); der Loader
probiert jetztyaml→ruamel.yaml→hermes_yaml. - Backups duerfen nicht als zweites Plugin geladen werden. Hermes registriert
jedeplugin.yamlunter einem gescannten Plugins-Root. Ein Backup des
Plugin-Baums, das dort als Verzeichnis liegt, wurde deshalb als zweite
Instanz desselben Plugins geladen (gleicher Plugin-Key, eigener State).
doctor.shsucht das Backup jetzt an dem Pfad, denupdate.shtatsaechlich
beschreibt, und warnt, wenn eine zweite Instanz aufgetaucht ist.
Installation
hermes -p default plugins install Huy3ko/toolshed/runtime \
--ref ad0f1bf38bd9236c041cad55de385147608c024e
hermes -p default plugins enable hermes-token-router --allow-tool-overrideruntime/ bleibt gemaess ADR-0011 die einzige oeffentliche
Installationsoberflaeche. Ein Backup des Plugin-Baums gehoert als Datei
ausserhalb des Plugins-Verzeichnisses abgelegt — als Verzeichnis wuerde es als
zweites Plugin geladen.
Kompatibilitaet
Gebaut und validiert gegen Hermes v0.22.2. Die erste Verengung wurde an
echten Gateway-Turns gemessen (48 -> 11 tools).
Teststand
128 passed, 6 skipped
v0.1.7 — Hardening Refactor
[0.1.7] — 2026-09-01
Fixed
- Renamed the internal router helper module so the flat Hermes plugin loader
cannot shadow Hermes' top-leveltoolspackage. - Kept the routed tool surface session-sticky when Hermes exposes only the
pre_llm_callcompatibility hook. - Made profile/session agent-reference collisions fail closed instead of
selecting another live agent. - Preserved actual tool usage capture in observe-only
shadowmode. - Confined doctor profile paths to the documented profile-name format.
- Corrected v2→v2 rollback verification and kept Source/Runtime/flat-loader
copies aligned. - Added concrete recovery-schema and Hermes-loader registration coverage.
- Captured the original grant before recovery/narrowing and rejected
unauthorized expansions fail-closed. - Made shadow state profile/home-scoped, successful-usage-only, and
block-aware; aligned all config/template copies and removed invalid template
frontmatter. - Scoped the CI path scan to shipped source/documentation instead of ADR
history, and kept stale pre-built wheels out of release snapshots. - Made the wheel self-contained with package-relative telemetry imports and
declared PyYAML as a runtime dependency. - Made installer and updater
--jsonoutput a valid JSON array for one or
more profile records. - Resolved named profiles from Hermes' context-local home and aligned Doctor's
learning-state writability check with that active home. - Treated Hermes' per-run
on_session_endcallback as a block boundary while
preserving the live agent reference across turns; only a no-turn-id close
flushes the whole session.
Toolshed v0.1.6
Changelog
All notable changes to Toolshed are documented here.
Format based on Keep a Changelog;
versioning follows SemVer (0.x = pre-stable).
[0.1.6] — 2026-08-24
Fixed
- Community install no longer blocked by Hermes' security scanner.
A freshhermes plugins install Huy3ko/toolshedwas classified DANGEROUS
(external report, Termux): the scanner scans the whole cloned repo, and
development artifacts (ADRs mentioning~/.hermes/.env, CIpip install,
CONTRIBUTING) plus German comments inupdate.shreferencing/etc/passwd
andsudo -utripped critical/high patterns. Root cause: repo root was used
as the install surface.
Changed
-
Distribution v2: runtime payload moved to
runtime/. The public install
command is now:hermes plugins install Huy3ko/toolshed/runtimeHermes natively supports subdirectory installs and scans only that
directory. The runtime payload contains plugin.yaml, router code,
learning/telemetry stores, update.sh, doctor.sh and alayout_version: 2
marker — nothing else. The development tree at repo root is unchanged. -
Updater hardening (
runtime/update.sh), all findings from an adversarial
helper review, reproduced before fixing:- deterministic target context:
--home→ USER_HOME/TARGET_USER/HERMES_BIN
resolved from ownership, never from caller$HOME; fail-closed preflight; HERMES_HOMEexported explicitly on every privileged call (fixes wrong-
profile installs when invoked as root);- atomic v1→v2 migration: full-tree backup before anything is replaced,
verified rollback (tree restored, v2 marker absent, ownership intact) with
rollback failure as its own hard-fail state — no half-states; - config merge instead of overwrite: only documented user keys (
enabled,
expansion_mode,floor_toolsets) are carried into the fresh v2 config;
captured before the old tree is replaced; - strict profile allowlist
[A-Za-z0-9_-]+(no path traversal via
--profile); - collision-safe backup names (epoch+PID); backups cleaned up under the
target user's identity; - installer success requires exit code AND canonical success tokens, then a
post-installlayout_version: 2marker check.
- deterministic target context:
-
update.sh: updater comments translated to English; privilege drop uses
runuser(root)/setpriv(fallback).
Validation (helper canary, UID 1003, scanner ENABLED)
- Fresh install of
Huy3ko/toolshed/runtime→ scan clean → grant → enable →
doctor OK → routing smoke OK. - Migration v0.1.5 full-repo layout → v0.1.6 runtime layout: config, grants,
enabled/mode preserved; ownershiphermes_helper:hermes_helper; doctor OK. - Repeat update v2→v2 green; rollback path exercised and verified.
[0.1.5] — 2026-08-24
Fixed
v0.1.5 — Multi-User TH Resolution Fix & Unicode-Safe Success Detection
First release to run through the full Vela-Helper process: Helper finds → Vela reproduces → patch → helper counter-review → release → helper canary → rollout.
Fixed
- update.sh multi-user bug: Without
--home, the target home is now resolved from the TARGET user (--user, via getent) instead of $HOME of the caller. Hard exit 4 on unresolvable home. - Binary search path: Now covers both canonical install layouts (
~/.hermes/hermes-agent/git-install and~/src/hermes-agent/source-install), resolved against the target user's home — not the invoking shell's $HOME. - Success detection: Matches installer-owned tokens (
✓ Installed,Plugin installed:) instead of the broadInstalledsubstring (false positive on "Already installed") and without line anchors (the installer wraps output in Unicode boxes, so a^anchor had a 100% false-negative rate).
Credits
Three of the four fixes originate from findings in an adversarial agent review.
Toolshed v0.1.4 — multi-user ownership fix
Fixed
- Multi-user ownership:
update.shnow runs all write steps as the target user (--home/--usercontract) — root never owns plugin files - doctor
--home <path>: diagnose foreign Hermes homes (multi-user setups) - Robust
.hermesdir detection via structure markers - Supply-chain hygiene: pinned dev dependencies, unpinned pip refs removed from docs/CI
Added
infocheck level in doctor output
Validation: fresh-install canary on upstream Hermes b766607b/v0.20.5 (MiniMax-M3); multi-user migration on independent runtime (own venv + gateway); all agents productively running v0.1.2→v0.1.4 update path.
Toolshed v0.1.3 — multi-user doctor + hygiene fixes
Added
doctor --home <path>: diagnose foreign Hermes homes — proper multi-user support (D4)infocheck level in doctor output (neither fail nor warn)
Fixed
- doctor state-dir ownership detection for multi-user installs
- doctor global.enabled consistency check counts only the global block
- plugins-list check uses --plain + name-independent matching
Validation: hermes_christiane profile passes all checks (exit 0) after multi-user migration.
Toolshed v0.1.2 — closed operations loop
First version with a closed operations loop: install, diagnose, update, rollback and reinstall are proven as one connected user path on a fresh Hermes install.
Added
install.sh— guided installer: profile detection, explicit grant consent, routing activation, end-to-end verification (interactive + non-interactive with JSON output)update.sh— state-preserving update: backs up config, restores enabled/mode/floor after reinstall, verifies grant and routing (fixes D2)doctor.sh— 13-point diagnostic, human-readable + valid JSON output, exit codes 0/1/2- GitHub issue templates
Fixed
- Supply-chain hygiene: pinned dev dependencies in CI, removed unpinned pip references from docs (security-scan findings resolved)
- doctor stale-grant check no longer reads the global Hermes config
Known limitations
- Raw
hermes plugins install --forcecan still reset the plugin config (global.enabledfalls back tofalse). Use the includedupdate.shto preserve state. - Gateway-restart / learning persistence not yet fully validated in a systemd-user environment.
Validation: fresh-install canary on upstream Hermes b766607b / v0.20.5 with MiniMax-M3 — full cycle green. Measured input reduction: ~43% (fresh canary), 24–70% (controlled A/B). Results depend on workload and tool surface.
Toolshed v0.1.1
Compatible fix release.
- Single-source versioning (pyproject = truth; flat-loader
__about__and package copy both 0.1.1) - NOTICE: precise fork provenance from the archived upstream snapshot (upstream repo now 404); no unverified genealogical claims
- README: documents that
plugins install owner/repoinstalls the default branch, not the latest release tag — use--ref <commit-sha>for a specific release - README: documents the
global.enabled:trueactivation step (install ≠ activation)
Install:
hermes plugins install Huy3ko/toolshed
hermes plugins enable hermes-token-router --allow-tool-overridethen set global.enabled:true in the plugin config.yaml.
Toolshed v0.1.0
First public release.
An adaptive tool-surface proxy for Hermes — reduces repeated tool-schema overhead while preserving on-demand recovery.
Highlights
- Session-sticky tool-surface routing (deterministic + optional LLM classifier)
- Floor toolsets: critical capabilities are never pruned
- Dynamic MCP routing: any configured MCP server becomes routable automatically
- Monotonic recovery via
request_toolset(fail-open) - Profile-scoped state: multi-agent safe
- Explicit authorization: requires
--allow-tool-overridegrant; fail-closed without it
Measured
- ~31% input-token reduction on a fresh Hermes setup (identical tasks, ON vs OFF)
- 32–70% in earlier controlled paired workloads
- Results vary with tool count and workload — see docs/benchmarks for methodology
Install
hermes plugins install Huy3ko/toolshed
hermes plugins enable hermes-token-router --allow-tool-overrideThen set global.enabled: true in the plugin's config.yaml. See README for the full guide.
Known limitations
- Gateway-restart/learning persistence not yet validated in systemd-user environments
- Validated against Hermes upstream b766607b