Real-profile browser execution timeout and output capture
Cluster 96731. Data as of
Nothing open on GitHub. Fix merged in #131988 on 3 Oct 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 #131988. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131988. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a severe timeout regression when running browser_exec with real profiles on Windows desktop, and two fixes addressing stale process calls and CLI output capture method.
Open issues0
Open PRs0
Fixes on record
-
#131988 fix(browser): stop real-profile agent-browser output capture wedging the tool call [risk 0.20]
files:
tests/tools/test_browser_real_profile.py,tools/browser_tool.py,tools/browser_tool_real_profile.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · superseded by another PR 1
Closed issues · 1
- Closed#96731browser_exec: 420s timeout on Windows desktop with use_real_profile (same path runs in ~7s standalone)
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
- Merged PRs
- #131988
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 3 Oct 2026