NousResearch/hermes-agent

PM generations duplicating tool store binaries in Docker/snapshots

Cluster 136295 · environments. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #143404 on 23 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #143404. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #143404, then check it covers your case.

Read #143404 Pick up a Lab task

The members appear to share a theme around keeping the tool store (e.g., chromium/ffmpeg/node binaries) out of PM generations or workspace snapshots, with one bug report describing ~1.4 GB duplication per generation despite a shared runtime directory. One member also touches on plugin dependency restart messaging, which seems a related but secondary concern.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#143404 fix(plugins): say restart for plugin deps a running gateway can't import; keep the tool store out of PM generations

merged to main

files: apps/shared/src/gateway-contract.generated.ts, apps/shared/src/gateway-contract.openrpc.json, gateway/run_plugin_rewire.py, hermes_cli/plugins_activation.py, hermes_cli/plugins_loader.py, pm/workspace.py, tests/hermes_cli/test_plugin_dependency_restart.py, tests/pm/test_workspace_build_inputs.py, tui_gateway/contracts/tools_mcp_plugins.py

1 PR closed without merging

From the close comments: superseded by another PR 1

#136300 fix(pm): keep store binaries out of workspace snapshots in one-tree layouts · superseded by another PR → 73ce028, #143404

Closed issues · 1

Closed#136295[Bug]: Docker: cada generacion PM duplica chromium/ffmpeg/node (~1.4 GB) pese a HERMES_RUNTIME_DIR compartido

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: environments
Merged PRs: #143404
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 23 Oct 2026

For your agent

The same facts, typed.

cluster/136295.json
cluster/136295.md