Skip to content

Commit 637bb01

Browse files
jpheinclaude
andauthored
fix(opencode): drop $comment key — opencode schema rejects unknown root fields (#109)
The $comment field I added in commit 47018e5 to explain why the repo-level MCP entry defaults to enabled=false isn't part of opencode's config schema. Opencode's bootstrap validator throws ConfigInvalidError and refuses to start the TUI entirely: Error: 4 of 5 requests failed: Unexpected server error. Affected startup requests: config.providers, provider.list, app.agents, config.get JSON parses fine, but opencode rejects unknown top-level keys. Move the explanation to a code comment if needed; for now just remove the field so opencode starts. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 47018e5 commit 637bb01

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

.opencode/opencode.json

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
{
22
"$schema": "https://opencode.ai/config.json",
3-
"$comment": "Repo-level MCP entry disabled by default to avoid spawning a second mempalace-mcp against the legacy local palace when a user-level (daemon-routed) entry is also configured. Contributors without a daemon can flip enabled=true; their python with mempalace installed will be picked up from .venv/bin/python.",
43
"mcp": {
54
"mempalace": {
65
"type": "local",

0 commit comments

Comments
 (0)