Model/Agent selection on the intro screen not applied

[Nindaleth]

Description

After starting OpenCode, the intro screen allows switching the model and/or agent, however the first request is always done with the Build agent and the model configured in opencode.json. Sending the request, immediately interrupting and then switching the model/agent works as expected.

If I remove the "model" setting from opencode.json, I still get some other model than the one I asked for.

This is problematic in two ways:

• wasting GH Copilot premium request even at the times when I don't need the premium model
• running the read-write agent even when I asked for a read-only one

OpenCode version

v1.0.126

Steps to reproduce

1. In opencode.json, configure a model (e.g. "model": "github-copilot/claude-sonnet-4.5")
2. Start opencode
3. Switch agent from Build to Plan or switch the model (I used ctrl+x m) from the default to other one
4. Type in a prompt and submit - other combination processes the request

Screenshot and/or share link

After sending the request we can see a different model/agent is processing:

Operating System

No response

Terminal

No response

[github-actions[bot]]

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

• #4901: Bug: SDK Messages cause switch back to default model - Describes the same issue where model selection reverts to the primary agent's default model after certain operations (in that case, SDK messages with noReply)
• #4475: Plugins using noReply seem to cause model to switch to agent default - Similar issue where plugin tools cause the session to revert to the default model instead of retaining the manually selected model
• #4930: Feature Request: Retain current model and agent selection when switching sessions - Related request about model/agent selection persistence

These issues all relate to the model/agent selection not being retained after certain operations. Feel free to ignore if your specific case differs from these.

[Nindaleth]

After seeing #4475 and #4901 - both these issues and this issue I just created very possibly describe the same thing. I'm using obra/superpowers plugin which does use noReply: true.

[Nindaleth]

Confirmed, without using plugins the first message respects my agent/model selection.

[Andrewske]

I also had this issue and was using superpowers and removing it solved the issue

[rekram1-node]

ill close this as a duplicate and get the bug addressed soon, waiting on Daxs branch to merge in