Ollama context stuck at 0% #21736

Activity

1. nshiab

   added

   bugSomething isn't workingSomething isn't working

   on Apr 9, 2026
2. github-actions

   assigned

   rekram1-node

   on Apr 9, 2026
3. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on Apr 9, 2026
4. github-actions commented on Apr 9, 2026

   

   github-actionsBot

   on Apr 9, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Ollama Cloud doesn't display context size #9189: Ollama Cloud doesn't display context size (same symptom: 0 tokens/0% context shown when using Ollama)
   • Context usage count is always 0 for some local openai-compatible providers #423: Context usage count is always 0 for some local OpenAI-compatible providers (same underlying issue with local models including Ollama)

   Both are closed — it's possible this is a regression or a related but distinct case. Feel free to reference those issues for additional context.
5. RemeJuan commented on Apr 10, 2026

   

   RemeJuan

   on Apr 10, 2026

   More actions

   I’m seeing the same thing on macOS with OpenCode 1.4.3 and Ollama. The session reaches service=llm providerID=ollama modelID=gemma4:e4b ... stream and then stalls with no completion/error.

   Direct calls to Ollama’s OpenAI-compatible endpoint work fine (/v1/chat/completions with gemma4:e4b, including tool calls), so this looks like an OpenCode streaming regression rather than an Ollama/model issue.

   I also confirmed the same behavior in --pure mode, so it doesn’t seem plugin-related.

   👍React with 👍1Reacted by Alessandro Cimarelli
6. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on May 3, 2026
7. thdxr

   assigned

   jlongster

   and unassigned

   rekram1-node

   on May 3, 2026
8. github-actions commented on Jul 3, 2026

   

   github-actionsBot

   on Jul 3, 2026 – with GitHub Actions

   Contributor

   More actions

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

   closed this as not plannedon Jul 3, 2026
10. dercodeKoenig commented on Sep 14, 2026

    

    dercodeKoenig

    on Sep 14, 2026

    More actions

    still broken