Closed as not planned
Closed as not planned
Copy link
Description
Description
When reasoning/thinking effort is configured through model options in opencode.json, the web UI does not reflect that value for a new session.
For example:
{
"provider": {
"openai": {
"models": {
"gpt-5.4": {
"options": {
"reasoningEffort": "high"
}
}
}
}
}
}With this config, requests use the configured effort, but the web UI still shows Default instead of High.
What would I expect
- when creating a new session, the web UI should reflect the effective configured thinking effort
- the first user message should persist the corresponding variant
- refreshing the page should keep showing that same value for the session
What I get
- a new session shows
Default - the first user message is sent without a
variant - after refresh, the session cannot restore the configured effort from message history
This seems to happen because the web UI only considers explicit session/agent variants, but not model-level configured options that map to provider variants.
Plugins
No response
OpenCode version
v1.2.26
Steps to reproduce
- Create an
opencode.jsonwith a model-level reasoning effort override, for example:
{
"$schema": "https://opencode.ai/config.json",
"enabled_providers": ["openai"],
"model": "openai/gpt-5.4",
"provider": {
"openai": {
"models": {
"gpt-5.4": {
"options": {
"reasoningEffort": "high"
}
}
}
}
}
}- Start the web UI with
opencode web - Open the web session in the browser
- Create a new session
- Check the model/thinking effort control in the prompt area
- Send the first user message
- Refresh the page
Screenshot and/or share link
No response
Operating System
macOS 15.7.4
Terminal
No response
Reacted by Can Rau, Dante Oz, BoringBoredom, Oscar Serna, Chris Cowan and 杨森贵
Metadata
Metadata
Assignees
Labels
No labels
Activity
eloklam commentedon Apr 1, 2026
same issue
yangsengui commentedon May 8, 2026
same
github-actions commentedon Jul 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
Stihotvor commentedon Aug 21, 2026
same issue