Model selection: prefer session history over agent default (-m)

When a session's model is changed via the model picker, integrations that call session.prompt without an explicit model can still be forced back to the agent's default model (e.g. when started with -m).\n\nExpected: the session's currently selected model (last used for that agent) should be used unless the request explicitly supplies a model.\n\nCurrent: resolution order is input.model ?? agent.model ?? lastModel(sessionID), which makes -m effectively pin the model and ignore session selection.\n\nRepro:\n1) Start a session with opencode -m \n2) Switch model to in the session\n3) Submit a prompt from another caller that does not pass model\n4) It uses modelA instead of modelB

This issue might be a duplicate of existing issues. Please check:

Bug: SDK Messages cause switch back to default model #4901: SDK Messages cause switch back to default model
Plugins using noReply seem to cause model to switch to agent default #4475: Plugins using noReply seem to cause model to switch to agent default
Model selection is "lost" on continuation and Agent selection is "lost" on compaction #8349: Model selection is "lost" on continuation and Agent selection is "lost" on compaction
TUI: User selected agent/model is overwritten by server defaults when creating a new session #7948: TUI: User selected agent/model is overwritten by server defaults when creating a new session
Server API ignores agent's configured model when only agent parameter is passed #7099: Server API ignores agent's configured model when only agent parameter is passed
Subtask commands do not inherit model #6928: Subtask commands do not inherit model
Subagent with specific model results in model change in build and plan mode #6636: Subagent with specific model results in model change in build and plan mode
Selected model for agent in TUI doesn't stick between Agent Alternation #4344: Selected model for agent in TUI doesn't stick between Agent Alternation
Cycle through model do not work when a default model is set #4243: Cycle through model do not work when a default model is set
Feature Request: Retain current model and agent selection when switching sessions #4930: Feature Request: Retain current model and agent selection when switching sessions
Feature Request: Remember last used model/agent across sessions #10407: Feature Request: Remember last used model/agent across sessions
The selected model is not taken into account #7211: The selected model is not taken into account

Feel free to ignore if none of these address your specific case.

Likely same root cause as #4243 and #4901 (agent/default model taking precedence when a prompt doesn't explicitly pass model). PR #11332 proposes resolving session-selected model before agent default.

To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

Navigation Menu

Repository navigation

Model selection: prefer session history over agent default (-m) #11334

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Model selection: prefer session history over agent default (-m) #11334

Description

Activity

github-actions commented on Jan 30, 2026

rickross commented on Jan 30, 2026

github-actions commented on Apr 1, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions