On this page
On October 28, 2026, OpenCode published v1.19.5 as a formal GitHub Release—not a draft or prerelease. The cut is a bugfix only: the Release body lists Bugfixes and does not add new features. Related OpenCode reading: OpenCode Users on Windows Should Update to 1.18.33, Security Firm Says.
What the patch changes
Under Core → Bugfixes, the Release states that failed TUI worker requests now return an error instead of leaving the caller hanging, credited to @Nowaker. The matching community pull request is #54936 (fix(opencode): answer a failed TUI worker request instead of hanging). When a TUI worker handler throws, the caller now gets an error path that can settle, instead of waiting forever on a hung call.
A failed request can surface a visible error so the TUI can exit cleanly—for example when a chosen --port is already in use—rather than leaving a blank terminal stuck. The Release does not frame this cut as a CVE-style security advisory; it is a hang-to-error reliability fix for the TUI worker path. Same brand, different topic: OpenCode Says a Security Incident Hit About 1.4% of Console Users.
How the build ships
npm package opencode-ai lists latest = 1.19.5, matching the GitHub tag. A common path is npm i -g opencode-ai@latest. For that package, 1.19.5 is the current latest line carrying this hang→error fix. For another short CLI version brief on this site, see Claude Code 2.1.312 Adds OIDC user_id_claim and Safer Large-File Writes.
Scope of this cut
This tag does not introduce a new product surface or feature list in the Release notes. No pricing or plan change is tied to v1.19.5 in the Release or the linked PR. Details such as exact error strings, RPC wiring, and edge cases follow the GitHub Release for v1.19.5 and PR #54936—for reference only.