NousResearch/hermes-agent

Numeric profile route IDs coerced to strings for matching

Cluster 86470 · gateway. Data as of

Nothing open on GitHub. Fix merged in #101248 on 2 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 #101248. 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.

These items address a bug where YAML-parsed integer IDs never matched string-keyed routes, and include a fix to coerce numeric profile-route IDs to strings. Additional gateway changes around voice state and session recovery are bundled in the larger PR.

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.

  • #101248 fix(gateway): per-profile /voice state, off-loop startup hydration, session-recovery owner fence, int route ids (#84872 #74285 #88381 #86470, salvage #99519 #70815 #85245)

    merged to main

    files: contributors/emails/[redacted:email], gateway/profile_routing.py, gateway/run.py, gateway/session.py, gateway/slash_commands.py, hermes_cli/platform_actions.py, hermes_state.py, tests/gateway/test_multiplex_adapter_registry.py, tests/gateway/test_multiplex_phase0.py, tests/gateway/test_profile_routing.py, tests/gateway/test_voice_mode_platform_isolation.py, tests/hermes_cli/test_platform_actions.py, tests/test_hermes_state.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #86815 fix(gateway): coerce numeric profile-route IDs to str so routes match (#86470) · merged via another change → ad8b9e0, #101248
Closed issues · 1
  • Closed#86470profile_routing: unquoted numeric IDs in YAML never match (int vs str comparison, silent)
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
gateway
Merged PRs
#101248
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.