cli: opencode run hangs indefinitely with local Ollama model

オープン
#65,367 コメント 6 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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分
マージ済み PR(30日)
484

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

anomalyco/opencode のほかの issue

anomalyco/opencode の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。