Notify gateway users when compression summary generation fails
Cluster 16650. Data as of
Nothing open on GitHub. Fix merged in #16771 on 28 Apr 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 #16771. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #16771. That is separate from the fix event. - Still open
- Nothing open on GitHub.
All three members concern gateway users not being notified when compression summary generation fails and history is dropped. Two are pull requests with the same title (one marked as a salvage of #16333), and one is an issue describing the problem.
Open issues0
Open PRs0
Fixes on record
-
#16771 fix(compression): notify gateway users when summary generation fails (salvage #16333)
files:
agent/context_compressor.py,gateway/run.py,tests/agent/test_context_compressor.py,tests/gateway/test_compress_command.py,tests/gateway/test_session_hygiene.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#16333 fix(compression): notify gateway users when summary generation fails · merged via another change →
#16771
Closed issues · 1
- Closed#16650Gateway users not notified when compression summary generation fails and history is dropped
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
- #16771
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 28 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.