You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] Plugin 'oh-my-opencode' fails to auto-update via bun, causing persistent '[config-context]' warnings #15673
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)
Activity
github-actions commentedon Mar 2, 2026
This issue might be a duplicate of existing issues. Please check:
@dev) never auto-update due to bun lockfile caching #12712: Plugins never auto-update due to bun lockfile caching — likely the same root cause as the upgrade failure described hereIf you believe your issue is distinct, please clarify what differentiates it from these.