# NousResearch/hermes-agent · Remote binary overwrite guard check fix

## Open now

- Nothing open on GitHub.

A bug was identified where binary overwrite protection for file tools was being checked on the controller host rather than the remote execution target. Multiple fix attempts address moving or improving this check to run against the correct target filesystem.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #124106. Verify it addresses your case.
- **Recommended:** read PR #124106 (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-124106`. 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.50`: 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

- #122662: bug(file-tools): host-only binary guard allows destructive remote overwrites

## Prior & competing PRs

- **#124106: fix(file-tools): check remote binary overwrites on the execution target, not the controller**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/tools/test_remote_binary_write_guard.py`, `tools/file_tools_write_guards.py`
- **#122663: fix(file-tools): probe remote targets before binary overwrites**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `952f65cb289eed7deb9024879e94a4f880cd304f`, `#124106`
- **#123293: fix(file-tools): decide binary overwrite checks on the execution target filesystem**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `952f65cb289eed7deb9024879e94a4f880cd304f`, `#124106`

## Fix status

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