anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #7141] fix: config precedence now correctly allows local config to override remote #12270

New Issue
Closed
opened 2026-02-16 18:17:11 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:17:11 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/7141

State: closed
Merged: Yes

Fixes an issue where remote config from .well-known/opencode overrides local config instead of the other way around.

problem: Remote config was loaded last in the config precedence chain, meaning organizational defaults (like enabled: false on MCP servers) couldn't be overridden by users in their local config.

example: we ship MCP servers configured (for discovery!) but disabled (to avoid context bloat) as below. The current config merging prevents a user from having mcp: { "jira": { "enabled": true } } in their local config to enable JIRA (and retain all other settings).

    "mcp": {
      "jira": {
        "type": "remote",
        "url": "https://jira.mcp.example.org/mcp",
        "enabled": false,
        "oauth": {

        }
      },
      "wiki": {
        "type": "remote",
        "url": "https://wiki.mcp.example.org/mcp",
        "enabled": false,
        "oauth": {

        }
      },
      "gitlab": {
        "type": "remote",
        "url": "https://gitlab.mcp.example.org/mcp",
        "enabled": false,
        "oauth": {

        }
      },

solution: Reorder config loading so remote config loads first as the base layer:

  1. Remote config (.well-known/opencode) — organizational defaults
  2. Global config (~/.config/opencode/) — user preferences
  3. Project config (opencode.json) — project-specific overrides

Users can now enable MCP servers that organizations disable by default:

{ "mcp": { "jira": { "enabled": true } } }

Remote config fetch failures still hard-fail (as before) but now with a clearer error message showing the URL and HTTP status.

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/7141 **State:** closed **Merged:** Yes --- Fixes an issue where remote config from `.well-known/opencode` overrides local config instead of the other way around. **problem**: Remote config was loaded last in the config precedence chain, meaning organizational defaults (like `enabled: false` on MCP servers) couldn't be overridden by users in their local config. **example**: we ship MCP servers configured (for discovery!) but disabled (to avoid context bloat) as below. The current config merging prevents a user from having `mcp: { "jira": { "enabled": true } }` in their local config to enable JIRA (and retain all other settings). ``` "mcp": { "jira": { "type": "remote", "url": "https://jira.mcp.example.org/mcp", "enabled": false, "oauth": { } }, "wiki": { "type": "remote", "url": "https://wiki.mcp.example.org/mcp", "enabled": false, "oauth": { } }, "gitlab": { "type": "remote", "url": "https://gitlab.mcp.example.org/mcp", "enabled": false, "oauth": { } }, ``` **solution**: Reorder config loading so remote config loads first as the base layer: 1. Remote config (`.well-known/opencode`) — organizational defaults 2. Global config (`~/.config/opencode/`) — user preferences 3. Project config (`opencode.json`) — project-specific overrides Users can now enable MCP servers that organizations disable by default: ```json { "mcp": { "jira": { "enabled": true } } } ``` Remote config fetch failures still hard-fail (as before) but now with a clearer error message showing the URL and HTTP status.
yindo added the pull-request label 2026-02-16 18:17:11 -05:00
yindo closed this issue 2026-02-16 18:17:11 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#12270
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?