Browser session leaks under multiplexing, cleanup fixes
Cluster 86402 · agent. Data as of
Nothing open on GitHub. Fix merged in #101255 on 2 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #101255. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #101255. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where multiplexed browser sessions are not properly reclaimed or closed during inactivity, causing Chromium process leaks. The work involves fixes to idle session cleanup and broader multiplexing infrastructure including per-profile hooks and scoped threads.
Open issues0
Open PRs0
Fixes on record
-
#101255 fix(gateway): per-profile hooks, MCP discovery, webhook skills, and scoped browser/Hindsight threads under multiplex (#92672 #95518 #86402 #92608 #67277, salvage #92682 #95542 #86472)
files:
agent/outbound_webhooks.py,agent/shell_hooks.py,agent/skill_commands.py,agent/skill_utils.py,contributors/emails/[redacted:email],gateway/platforms/webhook.py,gateway/run.py,hermes_cli/plugins.py,plugins/memory/hindsight/__init__.py,tests/agent/test_outbound_webhooks.py,tests/agent/test_skill_commands.py,tests/gateway/test_multiplex_adapter_registry.py,tests/gateway/test_multiplex_mcp_discovery.py,tests/gateway/test_webhook_adapter.py,tests/hermes_cli/test_plugins.py,tests/plugins/memory/test_hindsight_provider.py,tests/tools/test_browser_cleanup.py,tests/tools/test_mcp_lazy_start.py,tools/browser_tool.py,tools/mcp_tool.py(+2 more)
1 PR closed without merging
From the close comments: merged via another change 1
-
#86472 fix(browser): reclaim idle multiplexed sessions before Chromium leaks · merged via another change →
bd81bf0,#101255
Closed issues · 1
- Closed#86402[Bug]: browser inactivity cleanup thread never closes a session under multiplexing (UnscopedSecretError) — leaks one Chromium per stuck session
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.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
- #101255
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Sep 2026