Gateway auto-resume recovery note persistence issue
Cluster 86580 · gateway. Data as of
Nothing open on GitHub. Fix merged in #89558 on 18 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 #89558. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #89558. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address a bug where the gateway's auto-resume mechanism incorrectly persists recovery notes or empty user messages, which then triggers the pre-call sanitizer on subsequent turns.
Open issues0
Open PRs0
Fixes on record
-
#89558 fix(gateway): auto-resume stops leaving an empty user row that re-trips the sanitizer every turn (#86580, salvage #86789)
files:
gateway/run.py,tests/gateway/test_restart_resume_pending.py
2 PRs closed without merging
From the close comments: merged via another change 1 · other 1
Closed issues · 1
- Closed#86580Gateway auto-resume persists an empty user message that triggers Pre-call sanitizer on every subsequent turn
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
- gateway
- Merged PRs
- #89558
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 18 Aug 2026