ollama integration no results returned

Having tried a number of different Ollama models all result in no output and an eventual time out.

I have this issue only in opencode all the models work and respond almost immediately either in the terminal or the Ollama UI.

Same short prompt: what is in this directory?

Answer s/b: the directory is empty. as it is a new project.

Result is: timeout

opencode.json is:{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "ollama": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "Ollama (local)",
      "options": {
        "baseURL": "http://localhost:11434/v1"
      },
      "models": {
        "llama3.1:8b": {
          "name": "llama3.1"
        },
        "llama3.2:3b": {
          "name": "llama3.2"
        },
        "qwen2.5-coder:7b": {
          "name": "qwen coder"
        },
        "mistral:7b-instruct": {
          "name": "mistral"
        }
      }
    }
  }
}

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

Timeout then tool errors with Devstral-Medium #2865: Timeout then tool errors with Devstral-Medium - Similar timeout issues with Ollama models, specifically mentions "Timeout error" with editing operations
Bash tool does not show time out to model or user, model might set time out incorrectly #2985: Bash tool does not show time out to model or user, model might set time out incorrectly - Discusses timeout behavior and how timeouts are not properly communicated to the model
bash tool often times out #1721: bash tool often times out - Reports frequent timeout issues with bash tool operations
[Bug] Timeout not working for Local LLM with MLX Models #2974: Timeout not working for Local LLM with MLX Models - Specifically about timeout settings being ignored for local LLM providers
Message generation interrupted, stuck at Generating #2137: Message generation interrupted, stuck at Generating - Similar behavior with responses getting stuck or interrupted with local models
Opencode in linux cannot access tools or create files #729: Opencode in linux cannot access tools or create files - Reports similar "no access to files" issues with local models like Devstral/Ollama

The core issue appears to be timeout-related problems with Ollama integration where models work fine outside opencode but fail to return responses when used through opencode.

Feel free to ignore if none of these address your specific case.

issue #2137 is similar to what I am experiencing. It is not exactly the same but similar.

I have this issue only in opencode all the models work and respond almost immediately either in the terminal or the Ollama UI.

so like if you curl you get a response instantly?

Maybe you can do:

opencode run hello --print-logs

Thank you for looking into this I have run several tests today. Attached are txt based log files for opencode and ollama server outputs of the tests. In each case I first run "ollama serve > ollama.out.logs 2>&1", then in a separate terminal "ollama ps" to verify no model is loaded, the "ollama run qwen2.5-coder:7b" prompt with hello or sup bro get a response of hello how can I help, then "ollama ps" again to verify the model is running, then "opencode run hello > opencode.logs.out 2>1&" to capture opencode logs. I tried this both with and without starting ollama run qwen2.5-coder:7b, each time with fresh runs of "ollama serve" from cold starts.

all results ended with very limited or not calls to the /v1 api in ollama serve logs and opencode logs end in timeout.

I admit to being in relative noob status so if I am overlooking something totally obvious please let me know.

ollama.logs.out.2.txt

opencode.logs.out.2.txt

@delphijc

@delphijc the only thing I can think of is increasing your timeout?

You can set a custom timeout like so (this is a 10 minute one):

{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "ollama": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "Ollama (local)",
      "options": {
        "baseURL": "http://localhost:11434/v1",
        "timeout": 600000
      },
      "models": {
        "llama3.1:8b": {
          "name": "llama3.1"
        },
        "llama3.2:3b": {
          "name": "llama3.2"
        },
        "qwen2.5-coder:7b": {
          "name": "qwen coder"
        },
        "mistral:7b-instruct": {
          "name": "mistral"
        }
      }
    }
  }
}

you need to change the context size.

To test:

pkill ollama
OLLAMA_CONTEXT_LENGTH=32000 ollama serve

permanent solution is to add the variable to your plist, or modify the model (with modelfile) to use a bigger context

Thank you adding the timeout and a OLLAMA_CONTEXT_LENGTH has this working with qwen2.5-coder:7b on my MacBook. I will try it again on my Mac mini with this same configuration to clear the issue if it also works there. Same amount of unified memory in each but Mac mini is Intel based maybe just too slow.

…

On Oct 19, 2025, at 5:28 PM, Aiden Cline ***@***.***> wrote: rekram1-node left a comment (anomalyco/opencode#3265) <#3265 (comment)> @delphijc <https://github.com/delphijc> the only thing I can think of is increasing your timeout? You can set a custom timeout like so (this is a 10 minute one): { "$schema": "https://opencode.ai/config.json", "provider": { "ollama": { "npm": ***@***.***/openai-compatible", "name": "Ollama (local)", "options": { "baseURL": "http://localhost:11434/v1", "timeout": 600000 }, "models": { "llama3.1:8b": { "name": "llama3.1" }, "llama3.2:3b": { "name": "llama3.2" }, "qwen2.5-coder:7b": { "name": "qwen coder" }, "mistral:7b-instruct": { "name": "mistral" } } } } } — Reply to this email directly, view it on GitHub <#3265 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOK52WGTDA3DPHEWZVDKAL33YP66TAVCNFSM6AAAAACJSC4NYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMJZHE3TCNZVGM>. You are receiving this because you were mentioned.

I have the same issue. when I select a local ollama model I either get an immediate error "AI_APICallError: Forbidden" or "AI_APICallError: registry.ollama.ai/library/deepseek-coder-v2:16b does not support tools" (same for startcoder of all versions), but if I use llama or QWEN it just animates the "Generating" and does nothing - I know because ollama ps shows nothing is using it.

I assume that means OpenCode is just not really ready for Ollama yet.

A few things may help:

Make sure the model you want to use has a "tools" tag or it won't work.
In your opencode.json add a "timeout": 600000 tonthe options section after "baseurl": url,
increase the context size to at least 32000. export OLLAMA_CONTEXT_LENGTH=32000, and then start ollama serve.

These got me to the point where I was receiving results. I have not gotten to the point where I am being productive yet. Maybe after $dayjob this evening. Good luck! #noobsunite

lmk if yall run into any issues and if there is anytbung we should change / document better

Navigation Menu

Repository navigation

ollama integration no results returned #3265

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

ollama integration no results returned #3265

Description

Activity

github-actions commented on Oct 18, 2025

delphijc commented on Oct 18, 2025

rekram1-node commented on Oct 19, 2025

delphijc commented on Oct 19, 2025

rekram1-node commented on Oct 19, 2025

sylvain-billie commented on Oct 20, 2025

delphijc commented on Oct 21, 2025

seefood commented on Oct 21, 2025

delphijc commented on Oct 21, 2025

rekram1-node commented on Oct 21, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions