Repository navigation
[QUESTION] Agent default variant handling in TUI/Desktop (#7156) #22065
Description
Question
Would maintainers accept the remaining narrow client-side scope for agent-configured model variants in #7156?
The PR now only covers:
- app/TUI local-state and hydration behavior for selected vs configured variants
- shared helper/tests for selected / Default / agent-configured resolution
- prompt bar display of the effective variant
It intentionally does not add backend/session/API/SDK behavior. The broader backend pieces from the original #7138 discussion have already landed or are out of scope for this PR.
This is a replacement for auto-closed #7138 so #7156 stays linked to an open design/review thread.
Metadata
Metadata
Assignees
Labels
No labels
Activity
[-][QUESTION] remaining local-state scope from auto-closed #7138[/-][+][QUESTION] Remaining scope from adding variant support for subagents[/+]CasualDeveloper commentedon Apr 18, 2026
Rebased
#7156onto the latestdevagain and updated the branch to match current semantics.Verified locally with
bun turbo typecheck,bun --cwd packages/opencode test --timeout 900000 ./test/agent/agent.test.ts, andbun --cwd packages/shared test --timeout 900000 ./test/util/model-variant.test.ts.If maintainers want a different direction, happy to rework it.
[-][QUESTION] Remaining scope from adding variant support for subagents[/-][+][QUESTION] Adding variant support for subagents feature's remaining scope[/+][-][QUESTION] Adding variant support for subagents feature's remaining scope[/-][+][QUESTION] Adding variant support for subagents feature's remaining scope (#7156)[/+][-][QUESTION] Adding variant support for subagents feature's remaining scope (#7156)[/-][+][QUESTION] Agent default variant handling in TUI/Desktop (#7156)[/+]31 remaining items