[FEATURE]: New endpoint for v2 configuration only #58495

Activity

1. opencode-agent commented on Oct 23, 2026

   

   opencode-agentBot

   on Oct 23, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the suggestion! As I understand it, you'd like a published JSON schema that describes only the v2 configuration, e.g. at https://opencode.ai/v2/config.json, separate from the current https://opencode.ai/config.json.

   For context: https://opencode.ai/config.json is currently built on purpose to accept both v1 and v2 configs, since v2 reads v1 fields and converts them when it loads the config. v1-only fields are marked as deprecated rather than rejected. A strict v2-only schema would let editors flag leftover v1 keys in a fully migrated config. If that's your use case, or if you have a different one, a short note on what you need it for would help.

   Related:

   • feat(schema): publish V2 config schema and accept V1 and V2 at /config.json #54832: an earlier PR that proposed exactly a strict /v2/config.json; it was closed without being merged, and the combined schema shipped instead
   • fix(schema): publish config schema that accepts V1 and V2 shapes #55524 / config: published JSON schema at opencode.ai/config.json describes V1, flags valid V2 fields #53398: the change that made /config.json accept both v1 and v2
   • [FEATURE]:Allow V1 and V2 to use fully separate configuration roots (and enable strict validation for the V2 root) #46757: a request for separate v1/v2 config roots with strict validation for v2

   The maintainers will consider this request.

   👍React with 👍1Reacted by d3bt3ch