# NousResearch/hermes-agent · ACP multi-file patch path evaluation bug fix

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #116793. Verify it addresses your case.
- **Recommended:** read PR #116793 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-116793`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #115213: ACP auto-approve evaluates multi-file V4A patch paths as one joined string, letting sensitive and out-of-workspace writes bypass the prompt

## Prior & competing PRs

- **#116793: fix(acp): multi-file V4A patches hiding .env or out-of-workspace paths now hit the permission prompt (#115213, salvage #115215)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `acp_adapter/edit_approval.py`, `tests/acp_adapter/test_edit_approval.py`
- **#115215: fix(acp): evaluate V4A multi-file patch paths individually for auto-approve**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `f3e1ec6c76dd`, `#116793`, `#115213`, `#115215`

## Fix status

- Merged to main in PR #116793 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-20`.