fix: ensure checkUpgrade sets init:

[code-yeongyu]

Problem

In TUI mode, a race condition occurs in environments where initialization involves significant latency (e.g., SSH, WSL2, remote VSCode).

The checkUpgrade function is scheduled to execute after 1 second. If the TUI initialization phase takes longer than 1 second, checkUpgrade executes first. Previously, checkUpgrade called Instance.provide() without passing the init (InstanceBootstrap) object.

Found this and fixed this using my personal plugin oh-my-opencode, but i thought there is no ai slop for this and found the real cause and fixed so I made this PR.

Root Cause

The Instance.provide() method follows a singleton pattern with caching.

1. checkUpgrade executes and calls Instance.provide() (without init).
2. An Instance is created using default settings without executing configuration or event hooks, and this uninitialized instance is cached.
3. When the main TUI logic eventually calls Instance.provide(init), the system detects the cached instance.
4. It returns the existing (poisoned) instance, effectively ignoring the provided init object.

Impact:

• Config hooks are skipped -> Custom agents defined on plugin are not registered.
• Event hooks are skipped -> Plugins do not receive events.

Solution

Updated checkUpgrade in packages/opencode/src/cli/cmd/tui/worker.ts to accept and pass the init: InstanceBootstrap object.

Now, regardless of whether checkUpgrade or the main TUI loop wins the race to create the Instance, the singleton is guaranteed to be initialized with the correct configuration and hooks.

Reproduction

1. Run OpenCode TUI in a constrained environment (or inject artificial delay in TUI startup > 1s).
2. Observe that checkUpgrade runs.
3. Verify that custom agents defined in config are missing or event handlers are not triggering.

Related

Closes #4846

[rekram1-node]

@code-yeongyu is the issue actually w/ plugin init? Or is the issue with how check upgrade is working? Because it kinda sounds like the later but maybe I misunderstand the issue

[code-yeongyu]

You're right. I initially misunderstood the flow and tried to make Plugin.init() idempotent. But as you said, the issue was actually in how checkUpgrade works. I've updated the code to pass init: InstanceBootstrap to checkUpgrade now.

[rekram1-node]

good find, thanks!