# NousResearch/hermes-agent · Cross-machine bot reply waiter blocked by single-query policy

## Open now

- Nothing open on GitHub.

A bug and related fix attempts address the reply waiter process running as a bare Python invocation, which the default single-query approval policy denies, halting bot-to-bot conversations after one hop across machines.

## 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 #116724. Verify it addresses your case.
- **Recommended:** read PR #116724 (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-116724`. 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

- #115209: \[Bug\]: the cross-machine reply waiter runs as \`python -c\`, which the approval gate refuses under the default single-query policy — bot-to-bot conversations across machines stop after one hop

## Prior & competing PRs

- **#116724: fix(bot-relay): cross-machine replies wake the sender under the default single-query policy (#115209, salvage #115210)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/tools/test_bot_relay.py`, `tests/tools/test_bot_relay_windows_paths.py`, `tools/bot_mode_dm.py`, `tools/bot_relay.py`, `website/docs/user-guide/bot-mode.md`
- **#115210: fix(bot-relay): the reply waiter is a runner entrypoint, so it starts under single-query deny (#115209)**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `2dee1e4640c4`, `#116724`, `#115209`, `#115210`

## Fix status

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