OpenCode 1.18: native jev-lsp path empty diagnostics (client path; not YAML) #21

Activity

1. makefunstuff commented on Sep 21, 2026

   

   makefunstuff

   on Sep 21, 2026

   OwnerAuthor

   More actions

   Fixed by the official bridge path: #22 (editors/opencode/).

   Root cause, confirmed on 1.18. Three client-side behaviours, none of them a rules/YAML
   regression:

   1. It advertises workspace.diagnostics.refreshSupport: false and answers the
      workspace/diagnostic/refresh jev-lsp sends anyway with an empty OK, so the re-pull the
      server asks for never happens.
   2. It pulls textDocument/diagnostic once when a document opens, before the ambient pass has
      cached anything, and keeps that empty report for the session.
   3. The Diagnostic.report() it hands the agent after a write keeps severity === 1 only, and
      every rule finding is a Warning.

   jev-lsp's finding path is pull (PROTOCOL §3.4/§9), which is what VS Code and Neovim implement.
   Pushing ambient findings from the server would break §9, so the translation is on the client side
   and PROTOCOL.md is unchanged.

   What shipped. editors/opencode/jev-lsp-opencode-bridge.py proxies stdio JSON-RPC to a
   jev-lsp --stdio child and: answers initialize with diagnosticProvider removed (puts OpenCode
   on its push path), advertises refreshSupport: true to the server, answers each refresh and pushes
   the pull as textDocument/publishDiagnostics, remaps Warning → Error with a [jev warning] prefix
   (Error is the only severity OpenCode's transcript shows), and synthesizes the didSave OpenCode
   never sends, without which the save-triggered rules pass never runs. editors/opencode/README.md
   has the config, and the top-level README's OpenCode section no longer recommends bare
   jev-lsp --stdio.

   Evidence — bash editors/opencode/verify-bridge.sh, 0 failures, four stages, no key and no
   network (stub decide tier with its decision call stalled so the native pull lands before the
   finding exists):

   	native jev-lsp --stdio	bridge
   opencode debug lsp diagnostics handler.rs	[] for a file the rule flags	the finding, severity: 1, [jev warning]
   OpenCode-shaped probe client	pulls: 1, first_pull_items: 0, refresh_requests_acked: 2, pushes: 0	provider_advertised: false, pulls: 0, pushes: 2

   Falsified deliberately: with the bridge replaced by a plain exec of the server, the bridge
   stages report 3 failure(s) and exit 1 while the native reproduction stays green. The row is now
   opencode_bridge in verify/run-suite.sh (ok in a full-table run here), and
   docs/VERIFICATION.md §1.2 records it.

   Native without the bridge remains broken by OpenCode 1.18's design and stays unsupported until
   OpenCode implements workspace/diagnostic/refresh or shows warnings to its agent; at that point
   lsp.jev.command can point straight at jev-lsp --stdio and the bridge can be deleted.
2. makefunstuff

   added a commit that references this issue on Sep 21, 2026

   editors/opencode: lead with Warning→Error distortion (#21)

   ...

   943c4d8
3. makefunstuff commented on Sep 21, 2026

   

   makefunstuff

   on Sep 21, 2026

   OwnerAuthor

   More actions

   Follow-up from QA (OpenCode ambient TUI bar)

   After #22 @ 0e03685, QA re-checked ambient coding-session UX on OpenCode 1.18.31 with the official editors/opencode/ bridge:

   • Coding-only edit/save → green LSP · jev
   • No readable [jev warning] / diagnostic chrome in the TUI (no review prompt, no debug dump)
   • Earlier “PASS” shots were on-demand / debug lsp diagnostics JSON, not ambient file-view UX

   Evidence: /workspace/jev-lsp-pr22-qa/opencode-ambient-before.png, opencode-ambient-violation.png

   Scope split

   • editors/opencode: the bridge is the supported OpenCode client path (#21) #22 remains: supported workaround for refreshSupport / Warning filter (push/probe path)
   • This issue stays open for native problems and for ambient TUI visibility in a normal coding session (even behind the bridge)

   Not a YAML / rules regression.
4. makefunstuff

   added 7 commits that reference this issue on Sep 21, 2026

   site: OpenCode one-liner — push/probe only, ambient still #21

   a8cd0dc

   docs: OpenCode Pages note — push/probe only, ambient #21

   f0083b4

   docs(opencode): match Pages — push/probe only, ambient still #21

   7bce1fb

   docs(readme): OpenCode bridge is push/probe; ambient still #21

   c7fcdcd

   docs: drop OpenCode bridge pitch — unsupported until #21

   5bb8d6e

   site: drop OpenCode bridge pitch — unsupported until #21

   0bdc70f

   docs(readme): mark OpenCode 1.18 unsupported until #21

   63cff9e
5. makefunstuff commented on Sep 21, 2026

   

   makefunstuff

   on Sep 21, 2026

   OwnerAuthor

   More actions

   Upstream evidence (OpenCode client, not jev-lsp):

   • [FEATURE]: Configure minimum LSP diagnostic severity level (show Warnings, not just Errors) anomalyco/opencode#17869 — Error-only filter; Warnings never reach agent/TUI
   • ESLint LSP fails to load anomalyco/opencode#23911 / Kotlin LSP not working (timeouts, no pull-diagnostics, etc.) anomalyco/opencode#23873 — green LSP, empty diagnostics (no pull/refresh)

   Matches QA ambient FAIL + nvim/VS Code proving the server. Also cited on docs PR #23.
6. makefunstuff commented on Sep 21, 2026

   

   makefunstuff

   on Sep 21, 2026

   OwnerAuthor

   More actions

   Status after #24 merge (b619e9b):

   • Ambient for good clients (nvim / VS Code / omp after decide) is fixed via background publishDiagnostics + jev.checking pending.
   • This issue stays open: OpenCode 1.18 still does not surface Warning ambient (upstream Error-only filter, e.g. [FEATURE]: Configure minimum LSP diagnostic severity level (show Warnings, not just Errors) anomalyco/opencode#17869). PR editors/opencode: the bridge is the supported OpenCode client path (#21) #22 bridge closed as costume.
   • Docs will keep OpenCode marked unsupported with links here + upstream until real ambient Warning works.
7. makefunstuff

   added 2 commits that reference this issue on Sep 21, 2026

   docs(readme): ambient publish + pending cue; OpenCode unsupported (#21)

   35bd3ac

   docs(site): ambient honesty + OpenCode #21/#17869

   6bff511