Files
deepseek-harness/packages/lsp
Tianyi Cui 43d81b67ce fix(subprocess): consumers with one mixed env map split DSH_* onto the managed channel
Codex review of the acp-only fix found lsp-local carries the identical
defect: its server config's unrestricted env merges into the connection's
ordinary spawn channel, so a configured DSH_* fact crashed the spawn with
the reserved-namespace rejection. The partition now lives on the seam as
splitEnvChannels() beside the scrub it complements; the ACP run and the
LSP connection both use it, and each proves child delivery end-to-end
(MOCK_ECHO_ENV / LSP_FAKE_ECHO_ENV fixture knobs). Seam + consumer README
rows updated (en+zh, re-recorded). bash-local is already two-channel;
mcp/pty/sdk bypass the seam and only share the scrub.
2026-07-27 01:21:32 +08:00
..
2026-07-26 05:06:39 +08:00
2026-07-26 05:06:39 +08:00
2026-07-26 05:06:39 +08:00

lsp/ - LSP capability family

English | 中文

The language-server capability seam: an abstract LSP interface, a generic stdio provider, and the model-facing lsp tool. All product packages.

Package Role ctx key
lsp/ Abstract LSP seam (provider registry by branded id + extension mapping, per-query selection, vocabulary, LspError) ctx.lsp
lsp-local/ Generic multi-server local backend (spawn, JSON-RPC, transient-open queries) (registers providers on ctx.lsp)
tool-lsp/ Model-facing lsp tool (four operations, one-based UTF-16 cursor coordinates) (registers on ctx.tools)

The interface lives at lsp/lsp/. The seam exposes exactly four semantic operations — goToDefinition, findReferences, goToImplementation, hover — and no generic JSON-RPC escape hatch, so a provider swap does not change how the model asks for navigation and no protocol payload or unreviewed mutation reaches the model contract. Providers register capabilities, not tools; tool-lsp is the only owner of the model-facing name, schema, prompt guidance, and presentation.

See the LSP capability seam Agent Note for the design rationale, including why documents open transiently per query, why the local host reads through Node APIs rather than ctx.fs, and why extension ownership is exclusive within one runtime.