Repository navigation
Web: sticky provider options win over stale thread selection #5421
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I am describing a concrete problem or use case, not just a vague idea.
Area
apps/web
Problem or use case
Changing Grok reasoning effort (or other provider options) on an existing thread often fails to reach sendTurn because thread-turn options stay sticky and draft options are empty.
Proposed solution
When per-thread draft has no options, fall back to cross-thread sticky provider options for send. Also drop obsolete Grok Early Access badge.
Why this matters
Composer UI shows the new effort but the server still receives the old one — silent lie.
Smallest useful scope
Options-only sticky fallback. Do not let sticky override thread/project selected model.
Alternatives considered
Force users to start a new thread for option changes — works but fights sticky model UX already used elsewhere.
Risks or tradeoffs
Incorrect activeSelection folding can steal the thread model from sticky — fixed scope is options map only.
Examples or references
PR #5426.
Activity
juliusmarminge commentedon Oct 2, 2026
Thanks for describing the selected-option mismatch. Orchestrator V2 has merged in #2829.
V2 records model selection on the server through thread.model-selection.set, replacing the V1 sticky-selection path targeted by this proposal. We are closing the old-path report as obsolete. An option that still fails to reach the provider should be reported against the new path.
If the problem persists on a build containing V2, please open a fresh issue with the T3 version, provider version, reproduction steps, and relevant logs, and link this report.