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
I can confirm this bug. I have multiple projects and each needs to use a different model, but I can't get this to work because the global opencode.json takes precedence. ConfigPaths.directories returns dirs in an order that only makes sense for first-wins consumers, but its main consumers (commands/agents/plugins config merge) are later-wins — so ~/.opencode silently overrides project .opencode, contradicting the docs ("project configs can override global defaults") and OpenCode's own file precedence (ConfigPaths.files does .toReversed() so nearest wins). Skills and themes each do their own, mutually inconsistent, thing.
Activity
github-actions commentedon May 18, 2026
This issue might be a duplicate of existing issues. Please check:
.opencode/config precedence is inverted in nested directories #21307:.opencode/config precedence is inverted in nested directories — related config precedence inversion bugIf your issue is distinct from those (e.g. specific to MCP
enabledfield merging), please clarify the difference.nielsgron commentedon Jul 10, 2026
I can confirm this bug. I have multiple projects and each needs to use a different model, but I can't get this to work because the global opencode.json takes precedence. ConfigPaths.directories returns dirs in an order that only makes sense for first-wins consumers, but its main consumers (commands/agents/plugins config merge) are later-wins — so ~/.opencode silently overrides project .opencode, contradicting the docs ("project configs can override global defaults") and OpenCode's own file precedence (ConfigPaths.files does .toReversed() so nearest wins). Skills and themes each do their own, mutually inconsistent, thing.
github-actions commentedon Sep 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.