Repository navigation
[bug] [config-context] getConfigContext() called before initConfigContext() warning appears on every startup and obscures TUI #15357
Description
Description
Description
Every time opencode starts, the following warning is printed to stderr before
the TUI initializes, visually obscuring the input area:
[config-context] getConfigContext() called before initConfigContext(); defaulting to CLI paths.
This message appears consistently on every launch and cannot be suppressed without
redirecting stderr externally (e.g. opencode 2>/dev/null).
Steps to Reproduce
- Install opencode v1.2.15 with oh-my-opencode plugin
- Run
opencodein any directory - Observe the warning printed before TUI renders
Expected Behavior
Either:
initConfigContext()is called before any code that depends on it, or- The warning is suppressed / demoted to debug-level logging only
Actual Behavior
Warning is printed to stderr on every startup, overlapping with the TUI interface
and forcing users to scroll or wait for it to clear.
Environment
- opencode version: v1.2.15
- oh-my-opencode version: latest
- OS: Debian (WSL2 on Windows)
- Shell: bash
Workaround
alias opencode='opencode 2>/tmp/opencode-stderr.log'This hides the warning but also swallows legitimate errors, which is not ideal.
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Activity
khhan0423 commentedon Feb 27, 2026
Resolved. Root cause was outdated oh-my-opencode plugin (v3.8.5).
Updating to v3.9.0 fixed the issue.
DEAN-Cherry commentedon Mar 2, 2026
Still happening (from v3.9.0 -> 3.10.0), why can't the oh-my-opencode upgrade itself?
DEAN-Cherry commentedon Mar 2, 2026
opencode logs:
WARN 2026-03-02T08:05:10 +225ms service=bun pkg=oh-my-opencode cachedVersion=3.9.0 Failed to resolve latest version, using cached