OpenCode recommends upgrading to 1.18.21 when Ox Alpha produces network errors; the release automatically retries unknown stops, improving client resilience but not repairing provider outages or rate limits.
Suitable tasks: Recovering from interrupted requests and unknown stops in OpenCode.
Unsuitable tasks: Using retry behavior as evidence of model correctness, throughput, or service stability.
Applicable model version: Ox Alpha stealth preview; the announcement gives no weight version.
Applicable clients, agents, or APIs: OpenCode 1.18.21.
Recommended reasoning levels and parameters: Not disclosed; fix the prompt, task, and concurrency before and after the upgrade.
The official post does not publish a configuration-file snippet. Reproduce the client difference in this order:
1. Record the current OpenCode version, model identifier, exact error, request duration, and retry count.
2. Upgrade to OpenCode 1.18.21.
3. Run the same repository, prompt, permissions, and task at least 10 times.
4. Report automatic recovery, final completion, repeated tokens, total duration, and remaining upstream errors separately.
5. Separate client retry success from model task success.The official post only says that unknown stops will be retried automatically and “should make things more usable.” It gives no recovery rate, retry limit, or backoff policy. Replies during the same period still report endpoint-unavailable errors, slow responses, and mid-run stops.
Ox Alpha