opencode2 failed on open after updating from 2.0.4 -> 2.0.7 and failed to open with unknown error

Description

Description : opencode2 failed to update and open after updating to the latest version (2.0.7), I used to run into this failed update issue every time, but I had a workaround: running Opencode2, which would reapply the failed updates and then successfully update. That’s how I always managed to update it before, but this time, when I tried the same method, I got an unknown error.

Issue :

PS D:\myfolder> opencode2 update -m bun
┌  Upgrade
│
●  Using method: bun
│
●  From 2.0.4 → 2.0.7
│
■  Upgrade failed
│
■  Failed to update with bun
│
└  Failed


PS D:\myfolder> opencode2
Starting background server...
[10:55:56.198] ERROR (#1): UnknownError: An error occurred in Effect.tryPromise
    at <anonymous> (B:/~BUN/root/chunk-vy88shnm.js:24:5598)
    at ~effect/Utils/internal (B:/~BUN/root/chunk-vy88shnm.js:8:1540)
    at s (B:/~BUN/root/chunk-vy88shnm.js:24:5696)
    at processTicksAndRejections (native:7:39)
    at Tui.run (B:/~BUN/root/chunk-72reczrb.js:98:247)
    at Tui.run (definition) (B:/~BUN/root/chunk-72reczrb.js:93:17047) {
  [cause]: ClientError: Transport
      at <anonymous> (B:/~BUN/root/chunk-mqc14m21.js:2:817)
      at async <anonymous> (B:/~BUN/root/chunk-mqc14m21.js:2:1038)
      at processTicksAndRejections (native:7:39) {
    [cause]: TypeError: Unable to connect. Is the computer able to access the url?
        at async <anonymous> (B:/~BUN/root/chunk-mqc14m21.js:2:781)
        at async <anonymous> (B:/~BUN/root/chunk-mqc14m21.js:2:1038)
  }
}
PS D:\myfolder> opencode2 update -m bun
┌  Upgrade
│
●  Using method: bun
│
▲  OpenCode upgrade skipped: 2.0.7 is already installed
│
└  Done

Plugins

No response

OpenCode version

2.0.7

Steps to reproduce

1. update opencode2 from old version (2.0.4) -> to 2.0.7 using bun as method
2. wait for the update to fail
3. open opencode2 from the cli
4. opencode2 attempts to apply the failed updates and displays this error.

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

Windows PowerShell

Start by reproducing the failed 2.0.4 to 2.0.7 update with the bun method on Windows PowerShell, then launch the CLI and capture the background-server error. Trace the update retry and startup network request associated with the reported Effect.tryPromise and Transport errors. Done means the update path no longer reports success while leaving startup unable to connect, or the failure is reported with an actionable cause.