NousResearch/hermes-agent

Browser/computer-use cache isolation by profile

Cluster 110032 · agent. Data as of

1 open item. Fix merged in #110286 on 13 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 #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
0 issues and 1 PR.

These items address a bug where browser and computer-use caches are keyed only by session ID, allowing one profile to receive another profile's session or backend. The fix scopes these caches to the owning identity so multiplexed secondary profiles maintain proper isolation.

Open issues0

No open issues.

Open PRs1

  • PR#110264fix(browser): scope browser/computer_use caches by owning hermes home (#110032)

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

Closed issues · 1
  • Closed#110032browser and computer_use caches are keyed by session id alone, so one profile can receive another profile's session and backend
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
1
Attempts
0 PRs closed without merging
Fix link checked
13 Sep 2026

For your agent

The same facts, typed.