Opencode hangs after model selection with opencode-go/minimax-m3

[zlzhangn]

Description

I subscribed to Opencode, but in my environment the app hangs when sending a request to the model. The local installation appears to start normally, and the provider credentials are available, but once the model is selected the request never returns a response.

Environment:
OS: Linux
Shell: bash
opencode version: 1.18.18
Provider: opencode-go
Model: minimax-m3

Plugins

oh-my-opencode-slim

OpenCode version

1.18.18

Steps to reproduce

Run opencode providers list
Confirm that credentials are present
Run:
opencode --print-logs --log-level DEBUG -m opencode-go/minimax-m3 run "hello"
Observe that the process reaches the model selection stage and then stalls without returning any result

Expected behavior:
The model should respond normally to the prompt.

Actual behavior:
The request hangs after llm runtime selected and stream providerID=opencode-go modelID=minimax-m3
The process must be manually interrupted
Exit code is 130

Screenshot and/or share link

timestamp=2026-08-13T12:25:56.269Z level=INFO run=a05ce97c message="creating instance" directory=/home/zlzhangn/projects/‌alphaquant
timestamp=2026-08-13T12:25:56.270Z level=INFO run=a05ce97c message=fromDirectory directory=/home/zlzhangn/projects/‌alphaquant
timestamp=2026-08-13T12:25:56.282Z level=INFO run=a05ce97c message=bootstrapping directory=/home/zlzhangn/projects/‌alphaquant
timestamp=2026-08-13T12:25:56.286Z level=INFO run=a05ce97c message=loading path=/home/zlzhangn/.config/opencode/config.json
timestamp=2026-08-13T12:25:56.287Z level=INFO run=a05ce97c message=loading path=/home/zlzhangn/.config/opencode/opencode.json
timestamp=2026-08-13T12:25:56.291Z level=INFO run=a05ce97c message=loading path=/home/zlzhangn/.config/opencode/opencode.jsonc
...
timestamp=2026-08-13T12:25:57.171Z level=INFO run=a05ce97c message=stream providerID=opencode-go modelID=minimax-m3 session.id=ses_004e9e886ffeLm52lnnnJmwVSn small=true agent=title mode=primary
timestamp=2026-08-13T12:25:57.185Z level=INFO run=a05ce97c message="llm runtime selected" llm.runtime=ai-sdk llm.provider=opencode-go llm.model=minimax-m3
timestamp=2026-08-13T12:26:00.576Z level=INFO run=a05ce97c message=process session.id=ses_004e9e886ffeLm52lnnnJmwVSn messageID=msg_ffb161892001zWeIGHL9kXu82k
timestamp=2026-08-13T12:26:00.577Z level=INFO run=a05ce97c message=stream providerID=opencode-go modelID=minimax-m3 session.id=ses_004e9e886ffeLm52lnnnJmwVSn small=false agent=orchestrator mode=primary
timestamp=2026-08-13T12:26:00.578Z level=INFO run=a05ce97c message="llm runtime selected" llm.runtime=ai-sdk llm.provider=opencode-go llm.model=minimax-m3

Operating System

WSL:Ubuntu

Terminal

No response

[github-actions]

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

• [Bug] opencode-go provider silently returns empty response / hangs on machines with broken IPv6 connectivity #40095: opencode-go provider silently returns empty response / hangs on machines with broken IPv6 connectivity (same provider, same hang symptom)
• opencode run hangs indefinitely when the usage quota is exhausted, instead of reporting the error it already has #40747: opencode run hangs indefinitely when usage quota is exhausted, instead of reporting the error
• Desktop v1.18.11 freezes completely when streaming from opencode-go provider #40205: Desktop v1.18.11 freezes completely when streaming from opencode-go provider

If none of these match your situation, please let us know and we'll continue investigating.

[MilkyWay008]

Seconding the #40095 lead — opencode-go hangs when outbound connectivity stalls, and WSL's default NAT setup has flaky IPv6/DNS that produces exactly this "stream starts, never returns" pattern. Test with a plain curl -v --max-time 10 to the gateway endpoint from inside WSL, and try disabling IPv6 on the interface (sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1) or pinning a DNS server. If the curl stalls too, it's the WSL network layer, not the provider.