`.opencode/` config precedence is inverted in nested directories

[zckman]

Description

When .opencode/opencode.json (or .jsonc) exists in multiple nested directories, the parent directory wins instead of the child.
This is the opposite of how plain opencode.json files behave and opposite of the documented "local overrides global" precedence model.

Root cause:
ConfigPaths.directories uses Filesystem.up, which yields directories child-first.
The merge loop in loadInstanceState applies mergeDeep(result, next) where the later-processed entry wins.
So the last parent always overrides the child.

Plain opencode.json files (not in .opencode/) don't have this problem:
Filesystem.findUp is called with { rootFirst: true }, which reverses the list before merging.

Plugins

MCP context7, no plugins

OpenCode version

1.3.7

Steps to reproduce

1. Create configs in .opencode/ for parent and child.
2. Verify the resulting config values

For example:

mkdir -p /tmp/oc-bug/.opencode /tmp/oc-bug/child/.opencode

echo '{ "$schema": "https://opencode.ai/config.json", "username": "parent-wins" }' \
  > /tmp/oc-bug/.opencode/opencode.json

echo '{ "$schema": "https://opencode.ai/config.json", "username": "child-should-win" }' \
  > /tmp/oc-bug/child/.opencode/opencode.json

cd /tmp/oc-bug/child && opencode debug config | grep username

# Expected: "username": "child-should-win"
# Actual:   "username": "parent-wins"

---

Check without .opencode/ directories (correct behavior):

mkdir -p /tmp/oc-bug2/child

echo '{ "$schema": "https://opencode.ai/config.json", "username": "parent" }' \
  > /tmp/oc-bug2/opencode.json

echo '{ "$schema": "https://opencode.ai/config.json", "username": "child-wins" }' \
  > /tmp/oc-bug2/child/opencode.json

cd /tmp/oc-bug2/child && opencode debug config | grep username
# Correct output: "username": "child-wins"

Screenshot and/or share link

No response

Operating System

Ubuntu 24

Terminal

Konsole

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Global configuration supersedes local configuration #19296: Global configuration supersedes local configuration — describes the same config precedence inversion where global/parent config overrides project/child config, likely sharing the same root cause in the merge logic
• opencode will use default values instead of user config values when a project level config exists #16897: opencode will use default values instead of user config values when a project level config exists — related config hierarchy issue with .opencode/ directories

[QuantumEdu]

Comment for Issue #21307 (.opencode/ config precedence inverted)

This is a significant bug that affects monorepo workflows where different subdirectories need different configurations. The current behavior breaks the expected "local overrides global" model.

Additional Impact Areas

Beyond the reported issue, this bug affects:

1. Monorepo subprojects:

   /monorepo/
     .opencode/opencode.json    # Base config (monorepo-wide)
     services/
       .opencode/opencode.json  # Service-specific overrides
       web/
         .opencode/opencode.json # Web-specific overrides
   

2. Feature-specific overrides:

   /project/
     .opencode/opencode.json    # Project defaults
     features/
       auth/.opencode/opencode.json  # Auth feature config
       billing/.opencode/opencode.json  # Billing feature config
   

3. Environment-specific configs (if using directory-based env separation):

   /project/
     dev/.opencode/opencode.json
     prod/.opencode/opencode.json
   

Suggested Testing

Add regression tests for:

• Nested directory precedence (child > parent > grandparent)
• Mixed .opencode/ and root-level configs
• Config merge behavior with conflicting keys
• .jsonc vs .json file handling

Temporary Workaround

Until fixed, users can work around this by:

• Using root-level opencode.json instead of .opencode/opencode.json
• Avoiding nested .opencode/ directories
• Manually merging configs before use

The fix is critical for projects that rely on hierarchical configuration for different parts of the codebase.