cli: opencode run hangs indefinitely with local Ollama model
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 38/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- nodejs, ollama, typescript
- Área
- cli
Línea de trabajo
Start by reproducing with opencode debug config to confirm the resolved default model, then run opencode run "Reply with exactly: LOCAL_OK" with a short timeout and check whether the request ever reaches http://127.0.0.1:11434/v1. The report leaves two suspects: the @ai-sdk/openai-compatible provider path and the sandbox block, since Docker Desktop's engine was not running during the hang while the remote-model control succeeded. Done means opencode run either prints the reply or exits with a clear timeout/connection error, ideally covered by a test that exercises a non-streaming local endpoint.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
opencode run with the default local Ollama model produces no output and never exits. The same CLI completes normally with an HTTP-compatible remote model, and Ollama's own API answers the same prompt in seconds.
Environment
- opencode version: 1.18.31 (
opencode --version; executable resolved through%APPDATA%\npm\opencode.ps1). OpenCode Desktop 2.3.2 is also installed but its CLI is not the one onPATH. - OS: Microsoft Windows NT 10.0.26300.0 (Windows 11 x64).
veris unavailable in PowerShell, so[Environment]::OSVersion.VersionStringwas used. - Terminal:
TERM=xterm-256color;TERM_PROGRAM,COLORTERM, andWT_SESSIONunset. Command was launched from the OpenCode shell tool (non-interactive). - Shell:
%COMSPEC%=C:\WINDOWS\system32\cmd.exe; OpenCode config sets"shell": "powershell"for its own shell tool. - Install/channel: npm global install, release channel (
C:\Users\<user>\AppData\Roaming\npm\opencode.ps1). - Active plugins: None found. No
pluginskey in~/.config/opencode/opencode.jsonoropencode.jsonc; no.opencode/plugin,.opencode/plugins,plugin, orpluginsdirectories under the global config directory.
Reproduction
- Install Ollama 0.40.16 and pull
qwen2.5-coder:7b(4.7 GB). Runollama servewithOLLAMA_HOST=127.0.0.1:11434; confirmGET http://127.0.0.1:11434/api/tagsreturns 200. - In the global config, the resolved default model is
ollama/qwen2.5-coder:7b(opencode debug configconfirms this). - Run
opencode run "Reply with exactly: LOCAL_OK"from any directory. - Wait several minutes. No output is produced and the prompt never returns.
- Control A: direct
POST http://127.0.0.1:11434/api/generatewith{"model":"qwen2.5-coder:7b","prompt":"Say OK","stream":false,"options":{"num_predict":8}}returns HTTP 200, body{"response":"OK"}, in about 19 seconds. - Control B:
opencode run -m freellmapi/nemotron-3-ultra-550b "Reply with exactly: SAFE_OK"printsSAFE_OKand exits normally.
Expected Behavior
opencode run should print the model's reply and exit, or surface a clear timeout/connection error if the model cannot be reached.
Actual Behavior
The process stayed alive for about 8 minutes with no stdout and no error. Get-Process showed the opencode.exe process alive with Responding = True and roughly 22 seconds of cumulative CPU time. The parent shell also stayed alive with no output because the pipeline buffers until the child exits. Both were terminated manually; the shell reported exit code 4294967295.
Additional Context
- Frequency: observed once; not re-run after restarting Ollama.
- Ollama was listening only on
127.0.0.1:11434with an inbound firewall block, so this is not a network reachability problem. - Relevant global config (no credentials shown):
"model": "ollama/qwen2.5-coder:7b",
"provider": {
"ollama": {
"npm": "@ai-sdk/openai-compatible",
"options": { "baseURL": "http://127.0.0.1:11434/v1" },
"models": {
"qwen2.5-coder:7b": { "name": "Qwen2.5 Coder 7B" }
}
}
},
"sandbox": {
"enabled": true,
"image": "langchain/langgraph-sandbox:latest",
"resources": { "cpu": 2, "memory": "4GiB" }
}
- Docker Desktop's engine was not running during the failing test (it was started afterwards for an unrelated container audit). If sandbox startup is involved in this hang, that is worth checking; the remote-model control succeeded under the same condition.
- No custom plugins or provider overrides affect this model beyond the config above.
- Lenguaje dominante
- TypeScript
- Estrellas
- 227k
- Forks
- 30.7k
- Merge medio
- 3 h 57 min
- PR fusionados (30 d)
- 484
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de anomalyco/opencode
-
[Site] Active section detection should respect scroll-margin-topPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea/web reproduced type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
anomalyco/opencode#65384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/cli type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#65379 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Shell tool: no upper bound on the timeout a model can ask for, so one call can hold a turn for hoursAbiertoarea/core platform/linux type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
anomalyco/opencode#65254 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
inference/go type/feature
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
anomalyco/opencode#65148 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/providers type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#64845 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de anomalyco/opencode
Issues similares
-
[Provider] antigravity-acp catalog omits gemini-4-hydrogen and gemini-4-neon that agy acp offersPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertocatalog provider provider-compatibility
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
lidge-jun/opencodex#9037 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Project submission: xmcp DocsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
slavakurilyak/awesome-ai-agents#1005 ·
-
kind/bug triage/unresolved
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
Los mantenedores suelen responder en 1 día
-
effort:S P3 refactor
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nightscout/nocturne#3735 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
wpilibsuite/systemcore-blocks-interface#641 ·
Los mantenedores suelen responder en 2 días