Gateway session reasoning setting not persisting across chat turns
Cluster 140446 · gateway. Data as of
Nothing open on GitHub. Fix merged in #140969 on 18 Oct 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 #140969. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members appear to concern per-session settings, especially a reasoning level choice, being acknowledged but then replaced by the profile's level on the next turn in a profile-following chat. Two are gateway fix PRs (one also mentions launch secrets) and one is a Bot Chat report; the exact relationship between them is not fully clear from titles alone.
Open issues0
Open PRs0
Fixes on record
-
#140969 fix(gateway): keep per-session settings and launch secrets that didn't stick (package 10 lane 3a)
files:
apps/shared/src/gateway-contract.generated.ts,apps/shared/src/gateway-contract.openrpc.json,gateway/run_agent_cache.py,gateway/run_turn_runner.py,gateway/run_voice.py,gateway/session_authority.py,gateway/session_cli_turn.py,gateway/session_commands.py,gateway/session_local_inventory.py,gateway/session_mutation_model.py,gateway/session_mutation_policy.py,gateway/session_mutations.py,gateway/session_policy.py,gateway/session_policy_refresh.py,gateway/session_setting_commands.py,gateway/session_state.py,gateway/session_tui_config.py,hermes_cli/cli_agent_setup_mixin.py,hermes_cli/cli_chat_turn_mixin.py,hermes_cli/cli_model_switch_mixin.py(+26 more)
1 PR closed without merging
From the close comments: done elsewhere 1
-
#140447 fix(gateway): keep a session's reasoning choice on a profile-following chat · done elsewhere →
2b2672b,#140969
Closed issues · 1
- Closed#140446Bot Chat: a reasoning change is acknowledged, then the next turn runs the profile's level
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
- Subsystem
- gateway
- Merged PRs
- #140969
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Oct 2026