Environment
- T3 Code v0.0.23 (winget) on Windows 11
- opencode 1.14.48 (
npm i -g opencode-ai)
- Ollama 0.23.1, cloud-stub models
~/.config/opencode/opencode.json configures the ollama provider via @ai-sdk/openai-compatible against http://localhost:11434/v1
Repro
- Open the OpenCode tab
- Select any ollama model (verified with
qwen3-coder:480b-cloud and gpt-oss:120b-cloud)
- Send any prompt (e.g.
test)
- Assistant completes — opencode logs show
step-finish and finish: "stop"
Expected: assistant response renders in the chat view.
Actual: chat view stays blank after the user message. No assistant content ever appears.
Evidence the response is there in opencode
$ opencode export <session-id>
returns the full assistant message. For qwen3-coder:480b-cloud it was:
"Hello! I'm here to help with software engineering tasks. What would you like me to assist you with?"
Present in opencode.db, absent from the UI. step-finish reason is stop, cost: 0, finished cleanly.
opencode CLI works fine
opencode run -m ollama/qwen3-coder:480b-cloud "list the files in the current directory using the glob tool"
runs the full multi-step agent loop, calls glob + read, returns clean output in the terminal. So the opencode ↔ ollama path is healthy; the bug is t3code's OpenCode-tab renderer.
Possibly related
#2426 — Cursor provider responses disappearing after assistant message id collision. Same shape (saved but vanished). May be the same underlying renderer bug across providers.
Environment
npm i -g opencode-ai)~/.config/opencode/opencode.jsonconfigures theollamaprovider via@ai-sdk/openai-compatibleagainsthttp://localhost:11434/v1Repro
qwen3-coder:480b-cloudandgpt-oss:120b-cloud)test)step-finishandfinish: "stop"Expected: assistant response renders in the chat view.
Actual: chat view stays blank after the user message. No assistant content ever appears.
Evidence the response is there in opencode
returns the full assistant message. For
qwen3-coder:480b-cloudit was:Present in
opencode.db, absent from the UI.step-finishreason isstop,cost: 0, finished cleanly.opencode CLI works fine
runs the full multi-step agent loop, calls
glob+read, returns clean output in the terminal. So the opencode ↔ ollama path is healthy; the bug is t3code's OpenCode-tab renderer.Possibly related
#2426 — Cursor provider responses disappearing after assistant message id collision. Same shape (saved but vanished). May be the same underlying renderer bug across providers.