Skip to content

Commit 7133eee

Browse files
jpheinclaude
andauthored
fix(opencode): empty .opencode/opencode.json — repo config keeps overriding user wrapper (#110)
The previous `enabled: false` approach (PR #108) didn't work in practice. opencode appears to merge the repo-level and user-level MCP entries by name; the repo entry's `command` overrides the user-level one even when `enabled` is set to false. Symptom: the user-level wrapper at `~/.config/opencode/opencode.jsonc` points at the daemon-routed `mempalace-mcp-wrapper.sh`. The repo-level entry pointed at `.venv/bin/python -m mempalace.mcp_server`. Opencode's log on session start shows the local palace getting opened with 'mempalace-mcp: routing → local palace @ /home/jp/.mempalace/palace' and the HNSW capacity divergence warning — meaning the repo's local-spawn command won despite enabled=false. Strip the `mcp` block from the repo config entirely. The user-level wrapper handles daemon routing. Contributors who don't have a daemon can add their own user-level config or re-add the entry under `.opencode/opencode.local.json` (gitignored). Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 637bb01 commit 7133eee

1 file changed

Lines changed: 1 addition & 8 deletions

File tree

.opencode/opencode.json

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,3 @@
11
{
2-
"$schema": "https://opencode.ai/config.json",
3-
"mcp": {
4-
"mempalace": {
5-
"type": "local",
6-
"command": [".venv/bin/python", "-m", "mempalace.mcp_server"],
7-
"enabled": false
8-
}
9-
}
2+
"$schema": "https://opencode.ai/config.json"
103
}

0 commit comments

Comments
 (0)