Description
This is a follow-up to the closed issue #15357.
In #15357, the issue where [config-context] getConfigContext() called before initConfigContext() overlaps the TUI was supposedly resolved by updating the oh-my-opencode plugin from v3.8.5 to v3.9.0.
However, the issue still persists because the plugin fails to automatically upgrade itself (e.g., from v3.9.0 to v3.10.0).
When opencode starts, the plugin manager (bun) fails to resolve the latest version and falls back to the cached buggy version, leaving users stuck with the [config-context] warning spam on every single startup.
Steps to Reproduce
- Have an older version of
oh-my-opencode (e.g., v3.9.0) cached locally.
- Run
opencode in any directory.
- Observe that
opencode fails to upgrade the plugin and throws the [config-context] warning before TUI renders.
Expected Behavior
- The plugin manager should successfully resolve the latest version of
oh-my-opencode and automatically upgrade it.
- Users shouldn't be permanently stuck on a cached version that breaks the TUI experience.
Actual Behavior
The upgrade process fails silently in the background, and the cached version continues to throw the warning.
Looking at the opencode logs, the following warning is caught during the upgrade attempt:
WARN 2026-03-02T08:05:10 +225ms service=bun pkg=oh-my-opencode cachedVersion=3.9.0 Failed to resolve latest version, using cached
Environment
- opencode version: v1.2.15
- oh-my-opencode version:
3.9.0 (stuck, failing to upgrade to 3.10.0 or later)
- Package Manager:
bun
Related Issues
Description
This is a follow-up to the closed issue #15357.
In #15357, the issue where
[config-context] getConfigContext() called before initConfigContext()overlaps the TUI was supposedly resolved by updating theoh-my-opencodeplugin fromv3.8.5tov3.9.0.However, the issue still persists because the plugin fails to automatically upgrade itself (e.g., from
v3.9.0tov3.10.0).When
opencodestarts, the plugin manager (bun) fails to resolve the latest version and falls back to the cached buggy version, leaving users stuck with the[config-context]warning spam on every single startup.Steps to Reproduce
oh-my-opencode(e.g.,v3.9.0) cached locally.opencodein any directory.opencodefails to upgrade the plugin and throws the[config-context]warning before TUI renders.Expected Behavior
oh-my-opencodeand automatically upgrade it.Actual Behavior
The upgrade process fails silently in the background, and the cached version continues to throw the warning.
Looking at the
opencodelogs, the following warning is caught during the upgrade attempt:Environment
3.9.0(stuck, failing to upgrade to3.10.0or later)bunRelated Issues