# NousResearch/hermes-agent · Standalone gateway resolution after hosted-room activation

## Open now

- Nothing open on GitHub.

These items address a bug where activating a hosted room causes the standalone gateway to incorrectly continue or break resolution of API keys and models on subsequent turns. The fixes scope standalone gateway behavior after hosted activation occurs.

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

- #112878: \[Bug\]: Hosted-room activation breaks subsequent standalone gateway model resolution

## Prior & competing PRs

- **#113163: fix(gateway): standalone gateway turns keep resolving API keys after a hosted-room activation (#112878, salvage #112884)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/AGENTS.md`, `gateway/run_adapters.py`, `gateway/run_turn.py`, `tests/gateway/test_standalone_gateway_launch_scope.py`, `tui_gateway/launch_profile_policy.py`
- **#112884: fix(gateway): scope standalone turns after hosted activation**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `f2dc875a57`, `#113163`

## Fix status

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