cli: opencode run hangs indefinitely with local Ollama model

未關閉
#65,367 6 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
38/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
nodejs, ollama, typescript
領域
cli

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

area/cli platform/windows type/bug version/v2

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 on PATH.
  • OS: Microsoft Windows NT 10.0.26300.0 (Windows 11 x64). ver is unavailable in PowerShell, so [Environment]::OSVersion.VersionString was used.
  • Terminal: TERM=xterm-256color; TERM_PROGRAM, COLORTERM, and WT_SESSION unset. 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 plugins key in ~/.config/opencode/opencode.json or opencode.jsonc; no .opencode/plugin, .opencode/plugins, plugin, or plugins directories under the global config directory.

Reproduction

  1. Install Ollama 0.40.16 and pull qwen2.5-coder:7b (4.7 GB). Run ollama serve with OLLAMA_HOST=127.0.0.1:11434; confirm GET http://127.0.0.1:11434/api/tags returns 200.
  2. In the global config, the resolved default model is ollama/qwen2.5-coder:7b (opencode debug config confirms this).
  3. Run opencode run "Reply with exactly: LOCAL_OK" from any directory.
  4. Wait several minutes. No output is produced and the prompt never returns.
  5. Control A: direct POST http://127.0.0.1:11434/api/generate with {"model":"qwen2.5-coder:7b","prompt":"Say OK","stream":false,"options":{"num_predict":8}} returns HTTP 200, body {"response":"OK"}, in about 19 seconds.
  6. Control B: opencode run -m freellmapi/nemotron-3-ultra-550b "Reply with exactly: SAFE_OK" prints SAFE_OK and 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:11434 with 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.
主要語言
TypeScript
星號
227k
分支
30.7k
平均合併
3 小時 57 分鐘
30 天內合併 PR
484

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

anomalyco/opencode 的其他 Issue

查看 anomalyco/opencode 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。