v2 config: child repositories cannot combine global and shared workspace configuration #36539

Summary

In OpenCode v2, a running background service does not load the shared workspace configuration referenced by OPENCODE_CONFIG_DIR when OpenCode is opened inside a child git repository. The shell has the correct environment variable, but the resulting session only has the configuration associated with the context where the background service was started.

Environment

• opencode version: v0.0.0-next-15361
• OS: Linux 7.0.0-27-generic (Ubuntu, x86_64)
• Terminal: TERM_PROGRAM=ghostty, TERM=xterm-ghostty, COLORTERM=truecolor
• Shell: /usr/bin/zsh
• Install/channel: next (preview)

Reproduction

$HOME/
├── .envrc                        # global environment
├── .config/
│   └── opencode/                 # global OpenCode config
└── workspace/
    ├── .envrc                    # exports OPENCODE_CONFIG_DIR
    ├── .opencode/
    │   ├── opencode.json         # shared workspace MCP/config
    │   ├── skills/
    │   └── agents/
    ├── project/                  # git repo; OpenCode is opened here
    │   └── ...
    ├── project2/                 # git repo; should inherit both configs
    │   └── ...
    └── project3/                 # git repo; should inherit both configs
        └── ...

1. Create workspace/.envrc:

   export OPENCODE_CONFIG_DIR=$(pwd)/.opencode

2. Put configuration shared by all repositories in workspace/.opencode/, including an opencode.json with an enabled MCP server and workspace-specific skills.

3. Start the OpenCode v2 background service from $HOME, where the global OpenCode configuration is available.

4. Enter a child repository and verify that direnv sets the workspace variable:

   cd workspace/project
   echo $OPENCODE_CONFIG_DIR
   # /absolute/path/to/workspace/.opencode

5. Open opencode2 inside workspace/project. The client connects to the background service that was already started from $HOME.

6. Inside the resulting OpenCode session, inspect the variable:

   echo $OPENCODE_CONFIG_DIR
   # Empty

7. Run opencode2 mcp list. The workspace MCP server is not listed, and the workspace skills are not available in the session.

8. Restarting the background service from inside workspace/project reverses the problem: the workspace MCP server and skills become available, but the global configuration is lost.

Expected Behavior

Opening OpenCode v2 inside workspace/project, workspace/project2, or workspace/project3 should combine:

• The global OpenCode configuration.
• The shared configuration from workspace/.opencode/, referenced by the OPENCODE_CONFIG_DIR value loaded through workspace/.envrc.
• Any project-specific configuration, if present.

Each child git repository should inherit the common configuration from its parent workspace without losing the global configuration.

Actual Behavior

The loaded configuration depends on the directory context from which the background service was started, rather than the directory where the OpenCode client is opened:

• Service started from $HOME: global configuration is available, but workspace/.opencode/ is not loaded in child projects.
• Service restarted from the workspace: workspace configuration is available, but global configuration is lost.

The shell used to open OpenCode inside the child repository has the expected OPENCODE_CONFIG_DIR, while a shell command executed inside the resulting OpenCode session shows it as empty. Consequently, the workspace MCP server is absent from opencode2 mcp list and workspace skills are unavailable.

Additional Context

Restarting the service from the workspace is not a viable workaround because it trades the global configuration for the workspace configuration. OpenCode v2 should merge the global and shared workspace configuration according to the active client location instead of requiring the service to be restarted from one configuration scope or the other.