# NousResearch/hermes-agent · Session-scoped /reasoning command override in gateway

## Open now

- Nothing open on GitHub.

These items all concern the gateway's /reasoning command and making reasoning effort apply to the current session rather than more broadly. They include a change to default to session scope, a --session override option, and a feature request for a session-only override.

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

- #9586: Feature: Session-only reasoning effort override via /reasoning command

## Prior & competing PRs

- **#15533: fix(gateway): make /reasoning session-scoped by default**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/run.py`, `tests/gateway/test_reasoning_command.py`, `tests/gateway/test_session_model_override_routing.py`, `tests/gateway/test_session_model_reset.py`
- **#15531: fix(gateway): add /reasoning --session override**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#9586`, `#14558`, `#15522`

## Fix status

- Merged to main in PR #15533 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-26`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.