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
Models provided via ollama always respond that are read-only #2362
It look similar for both - devstral & gpt-oss models. If i try to generate /init it also fails in similar way. Last message from screenshot is from grok and this agent is working properly. Messages about read-only mode are independent from mode chosen in TUI (plan/build/review).
How can I provide you more verbose information to help?
Tool use with Ollama models. #1068: Tool use with Ollama models - shows tool call executions being aborted with Ollama models, similar behavior to your read-only responses
These issues all describe similar symptoms where Ollama models appear to generate tool calls but they don't execute properly, which could manifest as the "read-only" behavior you're experiencing.
Feel free to ignore if none of these address your specific case.
I tried prompting, I tried fixes from #1068 - it doesn't work. I need a tool that works well with local models. Sincere thanks for the open source tool, but my use case is not really supported.
note: you may need to tweak the context based on your available memory. 8192 is a good starting point and then increment by 1024 until you get something that works (or memory runs out).
Hmm, great! After set up of this variable it started working with gpt-oss.
As I am a Nix user, for those interested, here is my ollama with nvidia GPU declaration.
Activity
github-actions commentedon Sep 1, 2025
This issue might be a duplicate of existing issues. Please check:
These issues all describe similar symptoms where Ollama models appear to generate tool calls but they don't execute properly, which could manifest as the "read-only" behavior you're experiencing.
Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Sep 1, 2025
Hm you may need to set
"tool_call": truein your opencode.json, can you share yours by chance?ex:
WJKPK commentedon Sep 2, 2025
I already added my config. Add tool_call helped, but models now have problems with tool calling.
Should we continue here, or should I create new issue?
rekram1-node commentedon Sep 2, 2025
you may have to prompt for that, most models don't have that issue and you are using a pretty small model there
WJKPK commentedon Sep 2, 2025
I tried prompting, I tried fixes from #1068 - it doesn't work. I need a tool that works well with local models. Sincere thanks for the open source tool, but my use case is not really supported.
rekram1-node commentedon Sep 2, 2025
I have heard people get 20b working so I will try to get back to you on if they did anything special
rekram1-node commentedon Sep 3, 2025
Can you set
OLLAMA_CONTEXT_LENGTH=12288I heard some people say ollama basically doesnt work without it in many casesjohnjelinek commentedon Sep 3, 2025
note: you may need to tweak the context based on your available memory.
8192is a good starting point and then increment by1024until you get something that works (or memory runs out).rekram1-node commentedon Sep 3, 2025
thank you @johnjelinek for jumping in!
WJKPK commentedon Sep 3, 2025
Hmm, great! After set up of this variable it started working with gpt-oss.
As I am a Nix user, for those interested, here is my ollama with nvidia GPU declaration.
rekram1-node commentedon Sep 3, 2025
thank you both of you I will try to point people here if they encounter
ollama issueslocal inference issuesjohnjelinek commentedon Sep 3, 2025
I think this mustn't be unique to
ollama. I'd be surprised if you didn't have to set the context window likewise inllama-serverMarvAmBass commentedon Oct 31, 2025
thanks so much
OLLAMA_CONTEXT_LENGTH=12288fixed the issue on my machinethdxr commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.