You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: SDK Messages cause switch back to default model #4901
The plugin adds context that ddev is used by executing:
awaitclient.session.prompt({path: {id: currentSessionId},body: {parts: [{type: 'text',text: `➡️ DDEV environment is used. Execute commands inside the DDEV container like this: \`ddev exec --dir="${containerWorkingDir}" bash -c <command>\``,},],noReply: true,},});
This causes a user message to be written back in the context. After that message the session switches back to using the primary agents model instead of the one choosen manually using /models
Funnily enough, i noticed this during the recording of my screencast for my ddev plugin so it can be seen in action here: https://cap.so/s/xvrarkbtk9yw6qh
OpenCode version
1.0.120
Steps to reproduce
Create session
Switch model using /models
Let the sdk write a message via a custom plugin
See the session using the default model of the primary agent again
These issues describe the exact same problem where SDK messages (via plugins using noReply: true) cause the session to switch back to the primary agent's default model instead of maintaining the manually selected model.
Feel free to ignore if your specific case differs from these reports.
Activity
github-actions commentedon Nov 29, 2025
This issue might be a duplicate of existing issues. Please check:
noReplypattern broken in 1.0.69+ (agent loop refactor regression) #4431: Bug:noReplypattern broken in 1.0.69+ (agent loop refactor regression)These issues describe the exact same problem where SDK messages (via plugins using
noReply: true) cause the session to switch back to the primary agent's default model instead of maintaining the manually selected model.Feel free to ignore if your specific case differs from these reports.