Cairn
NousResearch/hermes-agent

MCP multiplexer profile and API server fixes

Cluster 100397 · hermes cli. Data as of

1 open item. Fix merged in #108352 on 11 Sep 2026. Check it covers your case.

The short answer

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

These items address bugs and behavior around multiplexed profiles, including API server pinning, MCP server naming, start/status/API_SERVER_KEY handling, and how Bot Mode agents interact with the default multiplexer.

Open issues0

No open issues.

Open PRs1

  • PR#100466fix(profiles): pin secondary api_server off under multiplex create

Fixes on record

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

  • #108352 fix(gateway,mcp): multiplexed profiles get their own same-named MCP servers, and start/status/API_SERVER_KEY honour the live multiplexer (#106005, #91654, #100397; salvage #99594/#104534)

    merged to main

    files: gateway/config_env.py, gateway/status.py, hermes_cli/cron.py, hermes_cli/gateway.py, hermes_cli/gateway_multiplex_served.py, hermes_cli/status.py, hermes_cli/subcommands/gateway.py, hermes_cli/web_routers/ops.py, tests/gateway/test_multiplex_secondary_port_binding_env.py, tests/hermes_cli/test_gateway_multiplex_served_record.py, tests/test_toolsets.py, tests/tools/test_mcp_multiplex_connection_keys.py, tools/mcp_tool.py, tools/mcp_tool_discovery.py, tools/mcp_tool_handlers.py, tools/mcp_tool_health.py, tools/mcp_tool_lifecycle.py, tools/mcp_tool_loop.py, tools/mcp_tool_registration.py, tools/mcp_tool_scope.py (+4 more)

Closed issues · 1
  • Closed#100397Bot Mode New Agent can clone API-server listener intent and be skipped by the default multiplexer
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
hermes cli
Merged PRs
#108352
Closed issues
1
Attempts
0 PRs closed without merging
Fix link checked
11 Sep 2026

For your agent

The same facts, typed.

cluster/100397.json
cluster/100397.md