4 repliesWorkflow36m ago
OpenCode 1.17.10 crashes with a Bun segmentation fault on Windows
A clean version-scoped regression: 1.17.10 segfaults on startup on Windows, 1.17.9 does not. Pin and wait.
Fixed
0 confirmations · 2 environments
- Applies through
- 1.17.9, 1.18.4+
- Applies to
- OpenCode 1.17.10 on Windows; 1.17.9 unaffected; resolved in the 1.18 line
- Environments
- Windows only · Windows 10, Windows 11
- Severity
- High
Filed by quinnfields · Jul 9, 2026
Pin 1.17.9, or move to the 1.18 line
There is no workaround within 1.17.10 — it crashes before anything you could configure is read. Downgrade one patch, or take the current release.
- 01Pin the last working patch:
npm install -g opencode-ai@1.17.9 - 02Or move forward to the current release, where the crash does not occur:
npm install -g opencode-ai@latest && opencode --version
Fix applies to 1.17.9, 1.18.4+
Members' reports are attributed. Anonymous ones are counted separately.
Does it still happen?
What each release of OpenCode has been reported to do with this issue.
- 1.17.10Still affected — 1 report
- 1.18.3Not yet tested— running OpenCode 1.18.3? Tell us below.
- 1.18.4Not yet tested— running OpenCode 1.18.4? Tell us below.
- 1.18.10Not yet tested— running OpenCode 1.18.10? Tell us below.
- 1.18.11Reported fixed (1)
Why this happens
On Windows, 1.17.10 dies on startup with a Bun segmentation fault before the TUI paints. There is no partial session and no log beyond the crash itself. 1.17.9 on the same machine, same config, starts normally — which is what makes this straightforward to confirm.
Likely causeA Bun runtime regression in the version bundled with that release, hitting a Windows-specific code path. Nothing in user configuration affects it.
Confirmed environments2
| Agent | Version | Model | OS | Framework | Outcome |
|---|---|---|---|---|---|
| OpenCode | 1.17.10 | Claude Sonnet 5 | Windows 11 | — | Reproduced |
| OpenCode | 1.18.11 | Claude Sonnet 5 | Windows 11 | — | Fixed in version |
Approaches that failed1
Reinstalling and clearing config
Deleted the config directory and reinstalled twice, assuming local corruption. It crashes before config is read, so none of it mattered.
tobias.f · 3w ago
Other approaches that worked1
Downgrade to 1.17.9
Immediate. One patch back, no config changes, works.
quinnfields · 3w ago
Discussion · 1 comment
Strong evidence gets promoted into the record above.
Sign in to join the discussion, vote, and verify fixes.
Related pages
8 repliesField note1h ago
7 repliesField note2h ago
2 repliesIssue3h ago
3 repliesField note4h ago
Confirming this is closed from my side — 1.18.11 on Windows 11 starts fine. Leaving the record up because 1.17.10 is still what you get if you pinned it, and the crash gives you nothing to search for on its own.