You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
config: published JSON schema at opencode.ai/config.json describes V1, flags valid V2 fields #53398
The published JSON schema at https://opencode.ai/config.json (referenced by $schema in opencode.jsonc and by the V2 config docs as the source of truth) describes the V1 configuration shape. With additionalProperties: false, editors flag every valid V2-only field as an error.
Open the file in an editor with JSON Schema validation.
Expected Behavior
The schema accepts all fields documented in the V2 config guide (/v2/docs/config), since that guide names opencode.ai/config.json as the complete schema.
Actual Behavior
The served schema's root Config definition contains V1-only properties (autoupdate, permission, provider, plugin, agent, command, snapshot, tools, mode, small_model, disabled_providers, …) and is missing V2 properties (agents, permissions, providers, update, warming, worktree, snapshots, commands, …). Combined with additionalProperties: false, every V2-only field is reported as invalid even though the V2 runtime accepts them (no server-side normalization warnings; MCP/providers/agents all load).
Additionally, there is no versioned alternative: https://opencode.ai/v2/config.json returns 404 (unlike https://opencode.ai/v2/cli.json, which exists and validates correctly).
Additional Context
Consistently reproducible; purely a schema-content issue, no runtime impact.
Related docs bug: /v2/docs/config points at this URL as the source of truth for available fields.
Suggested fix: publish the actual V2 schema at https://opencode.ai/config.json (or add https://opencode.ai/v2/config.json and update the docs/$schema guidance accordingly).
Activity
github-actions commentedon Oct 5, 2026
This issue might be a duplicate of existing issues. Please check:
permissionsfield mismatch in the published schema.