NousResearch/hermes-agent

Multiplex migration config key mismatch bugs and fixes

Cluster 110683. Data as of

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

The short answer

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

These issues and PRs address a bug where the auto-multiplex migration opt-out declares one configuration key but reads a different one, and a related missing declaration in DEFAULT_CONFIG. A fix and a broader gateway migration patch are included.

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.

  • #111062 gateway migrate --multiplex keeps the system unit's User=, rolls back or resumes instead of stranding the fleet; opt-out reads the declared key (#110850, #110683, salvage #110854 #110685)

    merged to main

    files: hermes_cli/config_defaults.py, hermes_cli/gateway_migrate.py, hermes_cli/gateway_migrate_guards.py, tests/hermes_cli/test_config.py, tests/hermes_cli/test_gateway_migrate_multiplex.py, tests/hermes_cli/test_profile_clone_channels.py, website/docs/user-guide/multi-profile-gateways.md

2 PRs closed without merging

From the close comments: merged via another change 2

  • #110685 [Bug]: declare gateway.auto_multiplex_migration in DEFAULT_CONFIG · merged via another change → 8c82e93, #111062
  • #111065 fix(config): declare the multiplex migration opt-out · merged via another change → #110685, #110683, #111062
Closed issues · 1
  • Closed#110683[Bug]: the auto-multiplex-migration opt-out declares one config key but reads another
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.50: 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
#111062
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
14 Sep 2026

For your agent

The same facts, typed.