Honcho client cache cross-profile memory isolation bug
Cluster 69123 · agent. Data as of
Nothing open on GitHub. Fix merged in #85452 on 13 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #85452. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #85452. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where multiplexed gateway profiles share a single Honcho client due to first-config-wins caching, causing memory from all profiles to land in the first profile's workspace. The members describe the problem and proposed fixes to key clients per distinct profile identity.
Open issues0
Open PRs0
Fixes on record
-
#85452 fix(honcho): isolate clients per profile, resolve baseUrl/apiKey, enforce saveMessages containment
files:
agent/memory_manager.py,contributors/emails/[redacted:email],contributors/emails/[redacted:email],contributors/emails/[redacted:email],contributors/emails/[redacted:email],contributors/emails/[redacted:email],contributors/emails/[redacted:email],contributors/emails/[redacted:email],plugins/memory/honcho/README.md,plugins/memory/honcho/__init__.py,plugins/memory/honcho/cli.py,plugins/memory/honcho/client.py,plugins/memory/honcho/session.py,tests/honcho_plugin/test_async_memory.py,tests/honcho_plugin/test_client.py,tests/honcho_plugin/test_client_identity_isolation.py,tests/honcho_plugin/test_save_messages.py,tests/plugins/memory/test_honcho_cli_peers.py,tests/run_agent/test_primary_runtime_restore.py,tests/test_honcho_client_config.py(+2 more)
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
-
#69142 fix(honcho): cache clients per config identity so multiplexed profiles don't share the first-built workspace · superseded by another PR →
696470c,#69123,#74065 -
#83525 fix(honcho): isolate clients per profile identity — end cross-tenant memory bleed in multi-profile processes · merged via another change →
#85452
Closed issues · 1
- Closed#69123Multiplexed gateway: all profiles' Honcho memory lands in the first profile's workspace (client cache is first-config-wins)
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #85452
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 13 Aug 2026