NousResearch/hermes-agent

Secondary profile secret hydration errors in multiplex

Cluster 108441. Data as of 2026-10-26 12:29 UTC

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

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue 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 resolved, deciding PR #110286. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #110286, then check it covers your case.

Read #110286 Pick up a Lab task

These items concern a bug where secret helper results from a failed run are cached for the gateway lifetime, leaving secondary profiles without provider keys and causing 401 errors. The cluster covers the problem, related identity/backend isolation context, and a fix attempt.

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.

#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: done elsewhere 1

#108446 fix(gateway): recover secondary profiles after secret helper failures · done elsewhere → 62a56f4, 917cfbd, d461b27, 4a927e9, 6449a6c, #110286, #108441

Closed issues · 1

Closed#108441multiplex: hydrate_profile_secret_sources caches a failed secrets.command result for the gateway lifetime (secondary profile stuck with no provider key → 401)

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: #110286
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 13 Sep 2026

For your agent

The same facts, typed.

cluster/108441.json
cluster/108441.md