Cairn
NousResearch/hermes-agent

Nous gateway and multiplexed profile browser routing errors

Cluster 108310 · agent. Data as of

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

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
A fix was merged to main in PR #110286. 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
1 issue and 0 PRs.

These items concern browser and backend routing errors in multiplexed secondary profiles, specifically around how the Nous gateway is looked up and applied when using managed gateways, real profiles, or cloud provider configurations. The work spans bug reports and a targeted fix for gateway picker resolution logic.

Open issues1

  • Issue#108310[Bug]: browser_exec with managed Nous gateway (cloud_provider: nous) + real-profile routes to direct-API with no creds, or launches a Chrome that dies pre-attach

Open PRs0

No open pull requests.

Fixes on record

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

  • #110286 Multiplexed secondary profiles keep their own memory-plugin identity, secret hydration and browser/computer-use backends (#108865 #108993 #108441 #108310 #110032)

    merged to main

    files: hermes_cli/env_loader.py, plugins/memory/byterover/__init__.py, plugins/memory/hindsight/__init__.py, tests/agent/test_env_loader_secret_sources.py, tests/plugins/memory/test_byterover_multiplex_child_env.py, tests/plugins/memory/test_multiplex_memory_identity_scope.py, tests/tools/test_browser_computer_use_profile_cache_keys.py, tests/tools/test_browser_use_cli.py, tools/browser_use_cli.py, tools/computer_use/tool.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #108328 fix(browser): resolve the Nous gateway from the picker selection, not only use_gateway · merged via another change → 62a56f4, 9e6a864, #110286, #108310
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
agent
Merged PRs
#110286
Closed issues
0
Attempts
1 PR closed without merging
Fix link checked
13 Sep 2026

For your agent

The same facts, typed.

cluster/108310.json
cluster/108310.md