Nothing open on GitHub. Fix merged in #116793 on 20 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 #116793. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116793. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug in ACP auto-approve caused multi-file V4A patch paths to be evaluated as a single joined string rather than individually, allowing sensitive files (e.g. .env) and out-of-workspace paths to bypass the permission prompt. These members address identifying and fixing that evaluation logic.
Open issues0
Open PRs0
Fixes on record
-
#116793 fix(acp): multi-file V4A patches hiding .env or out-of-workspace paths now hit the permission prompt (#115213, salvage #115215)
files:
acp_adapter/edit_approval.py,tests/acp_adapter/test_edit_approval.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#115215 fix(acp): evaluate V4A multi-file patch paths individually for auto-approve · merged via another change →
f3e1ec6,#116793,#115213,#115215
Closed issues · 1
- Closed#115213ACP auto-approve evaluates multi-file V4A patch paths as one joined string, letting sensitive and out-of-workspace writes bypass the prompt
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
- #116793
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026