opencode.ai/config.json schema uses top-level $ref/$defs, which breaks autocomplete/validation in the standard JSON LSP (neovim jsonls / VS Code) #41014

Activity

1. github-actions

   assigned

   kitlangton

   on Aug 7, 2026
2. Bearmancer commented on Sep 13, 2026

   

   Bearmancer

   on Sep 13, 2026

   More actions

   Fresh Windows repro on 1.18.30: the published opencode.ai/config.json produces zero diagnostics in the standard JSON language server, even when explicitly enabling validation — so unknown keys in opencode.jsonc/omo.jsonc are never caught (no VS-Code-style squiggles).

   Environment

   opencode 1.18.30 (Windows 11)
   plugins: oh-my-openagent 4.19.4, @cortexkit/opencode-antigravity-auth 2.2.1
   lsp (in ~/.config/opencode/opencode.jsonc):
     "global-json-schema": {
       "command": ["cmd", "/c", "vscode-json-language-server", "--stdio"],
       "extensions": [".json", ".jsonc"],
       "initialization": { "json": { "validate": { "enable": true } } }
     }
   server binary: vscode-json-language-server (vscode-langservers-extracted@4.10.0)
   

   Repro

   1. Create a directory with no repo markers (no lockfile/biome.json).
   2. probe.json:

      {"$schema":"https://opencode.ai/config.json","bogusKey":1}

   3. Write it through opencode and read the write tool result's <diagnostics>.

   Expected vs actual

   Expected: a schema violation for bogusKey (Additional properties are not allowed ('bogusKey' was unexpected)), i.e. the same squiggle VS Code shows.

   Actual: no diagnostics block for probe.json at all. Verified twice (two separate writes, server warm). The same directory does produce diagnostics for other servers, so the LSP pipeline itself works:

   # control — same bare dir, same session:
   <diagnostics file="...\global-lsp-probe\probe2.py">
   ERROR [1:6] "(" was not closed
   ...
   

   # probe.json → nothing
   

   Mechanism

   The published schema's root is a $ref into top-level $defs:

   { "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$ref": "#/$defs/Config",
     "$defs": { "Config": { ... }, ... } }

   vscode-json-language-server (and neovim jsonls) resolve a document's schema from its $schema URI but do not dereference a bare top-level $ref + $defs the way ajv/opencode's own validator does, so the document ends up with no effective schema and no diagnostics. That matches the report in this issue; the fresh part here is that it also fails with json.validate.enable: true and the exact VS Code server, not just neovim.

   Suggested fix direction: publish the schema with $defs inlined (or wrap it as {"type":"object","properties":{...}} with no top-level $ref), or serve a JSON-LS-compatible variant at a documented secondary URL.

   ---

   Note (separate, already tracked elsewhere): .jsonc additionally never reaches the server with the right languageId because .jsonc is missing from LANGUAGE_EXTENSIONS (packages/opencode/src/lsp/language.ts:53 has ".json": "json", no .jsonc; client.ts:560 falls back to "plaintext"). Cross-ref: #15859 (comment added).

   Verified 2026-09-13.
3. Bearmancer commented on Sep 13, 2026

   

   Bearmancer

   on Sep 13, 2026

   More actions

   ---

   Environment (software)

   item	value
   OS	Microsoft Windows 10 Pro — 10.0.19045 (Build 19045), 64-bit
   Shell	PowerShell 7.6.6 (+ Windows Terminal)
   opencode	1.18.30
   plugins	oh-my-openagent 4.19.4 · @cortexkit/opencode-antigravity-auth 2.2.1
   runtimes	Node v24.19.0 · npm 11.17.0 · Bun 1.4.2
   LSP binaries	biome 2.5.13 · basedpyright 1.40.1 · roslyn-language-server 5.12.0-1.26426.8 · bash-language-server 5.6.0 · shellcheck 0.11.0 · vscode-langservers-extracted 4.10.0 · PowerShellEditorServices 4.7.0 · PSScriptAnalyzer 1.25.0
   logs	~/.local/share/opencode/log/opencode.log · ~/.omo/agent/OmO-debug.log · ~/.omo/agent/logs/config-reload.log

   OS facts collected with:

   Get-CimInstance Win32_OperatingSystem | Select-Object Caption,Version,BuildNumber,OSArchitecture

   No hardware, hostname, username, or credentials included.
4. rekram1-node

   closed this as completedin #55524on Oct 14, 2026