NousResearch/hermes-agent

Gateway process discovery fix for inline bootstrap

Cluster 124318. Data as of

Nothing open on GitHub. Fix merged in #124965 on 27 Sep 2026. Check it covers your case.

The short answer

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

These items address a bug where the gateway's own process was not recognised during Hermes process discovery due to mismatched command forms. The fixes extend gateway identification to cover inline-source launchers across operating systems.

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.

  • #124965 fix(gateway): recognise Hermes inline-bootstrap gateways on every OS (salvage #123331)

    merged to main

    files: gateway/status.py, hermes_cli/gateway_windows.py, hermes_cli/update_cmd_windows.py, hermes_cli/update_fleet_scope.py, tests/e2e/core/windows_update/_machine.py, tests/e2e/core/windows_update/test_gateway_across_update.py, tests/e2e/core/windows_update/test_update_spares_other_installs.py, tests/gateway/test_gateway_inline_bootstrap_identity.py, tests/hermes_cli/test_update_windows_cross_install_gateway.py

1 PR closed without merging

From the close comments: done elsewhere 1

  • #133091 fix(gateway): identify the store launcher's inline source as the gateway · done elsewhere → 60e531c, 8afaab3, #124318
Closed issues · 1
  • Closed#124318[Bug]:Windows: the updater's own gateway is invisible to Hermes process discovery — runtime_command() emits `python -I -c …` while _gateway_command_subcommand() rejects that form (exit 1, and the next update is blocked at the gate)
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

Merged PRs
#124965
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
27 Sep 2026

For your agent

The same facts, typed.