watch_patterns notifications capped or over-firing
Cluster 93513. Data as of
Nothing open on GitHub. Fix merged in #93670 on 24 Aug 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 #93670. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where watch_patterns on background processes triggers notifications too frequently, stalling the event loop, alongside fixes that introduce or adjust a lifetime cap on how many times those notifications can fire.
Open issues0
Open PRs0
Fixes on record
-
#93670 fix(terminal): watch_patterns notifications hit a lifetime cap instead of firing forever (#93513, salvage #93532)
files:
tests/tools/test_watch_patterns.py,tools/process_registry.py,tools/terminal_tool.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#93532 fix(terminal): cap watch_patterns notifications over a process's lifetime · merged via another change →
#93670
Closed issues · 1
- Closed#93513watch_patterns on background processes repeatedly triggers full-context turns, stalling the event loop and detaching desktop sessions
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
- Merged PRs
- #93670
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 24 Aug 2026