Skip to content

[QUESTION] Agent default variant handling in TUI/Desktop (#7156) #22065

@CasualDeveloper

Description

@CasualDeveloper

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

coreAnything pertaining to core functionality of the application (opencode server stuff)

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions