# NousResearch/hermes-agent · Bot mode refusal detection by reason code

## Open now

- Nothing open on GitHub.

These items address a bug where bot delivery or bot-mode logic was detecting target-busy or active-session refusals by matching message wording rather than checking the structured reason code. The work involves classifying refusals based on SESSION_NOT_OWNED or equivalent reason codes directly.

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

- #104784: bot_mode_dm target_busy detection depends on the wording of the refusal message, not the SESSION_NOT_OWNED reason code

## Prior & competing PRs

- **#104898: fix: bot delivery recognizes refusal codes independently of wording**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `cli.py`, `hermes_cli/active_sessions.py`, `tests/tools/test_bot_mode_refusal_contract.py`, `tools/bot_mode_dm.py`, `website/docs/user-guide/bot-mode.md`
- **#104829: fix(bot-mode): classify active-session refusal by reason code**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `549e6aab38c`, `#104784`

## Fix status

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