ACP session counters not reset on /new or /reset
Cluster 35823 · acp. Data as of
Nothing open on GitHub. Fix merged in #65538 on 16 Jul 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 #65538. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #65538. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members all concern the ACP adapter's slash reset handling (/new and /reset), where token or session counters may not be cleared and could leave stale context usage. One is an issue report and the others are fix-oriented pull requests, including one described as a salvage of an earlier change; the titles alone do not show their status or outcome.
Open issues0
Open PRs0
Fixes on record
-
#65538 fix(acp): reset session counters on /reset (#36045 salvage)
files:
acp_adapter/server.py,tests/acp/test_server.py
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#35823ACP adapter: _cmd_reset does not reset token counters, causing stale context usage after /new
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
- acp
- Merged PRs
- #65538
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 16 Jul 2026