Standalone gateway resolution after hosted-room activation
Cluster 112878. Data as of
Nothing open on GitHub. Fix merged in #113163 on 16 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113163. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113163. That is separate from the fix event. - Still open
- 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.
Open issues0
Open PRs0
Fixes on record
-
#113163 fix(gateway): standalone gateway turns keep resolving API keys after a hosted-room activation (#112878, salvage #112884)
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
1 PR closed without merging
From the close comments: merged via another change 1
-
#112884 fix(gateway): scope standalone turns after hosted activation · merged via another change →
f2dc875,#113163
Closed issues · 1
- Closed#112878[Bug]: Hosted-room activation breaks subsequent standalone gateway model resolution
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #113163
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Sep 2026