ACP empty history and message edge case fixes
Cluster 10844 · acp. Data as of
1 open item. Fix merged in #109109 on 12 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 #109109. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #109109. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These issues and fixes address cases where empty message lists or explicit history resets were not being correctly passed through to ACP clients and sessions. The work focuses on ensuring empty or cleared state is preserved rather than ignored or overwritten.
Open issues0
Open PRs1
- PR#10882fix(acp): persist explicit empty history resets
Fixes on record
-
#109109 fix(acp): empty-string tool results and messages=[] reach ACP clients unchanged (#10845, #10844, salvage #10868)
files:
acp_adapter/events.py,acp_adapter/server.py,tests/acp/test_events.py,tests/acp/test_server.py
Closed issues · 1
- Closed#10844ACP sessions keep stale history when run_conversation returns messages=[]
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
- acp
- Merged PRs
- #109109
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 12 Sep 2026