PerryLink/dsh-lsp-actions
dsh-lsp-actions completes the LSP action surface for DeepSeek Harness. The official DSH ctx.lsp seam covers navigation (go-to-definition, references, hover); this plugin adds the feedback loop: eight lsp_* tools (diagnostics, formatting, completion, code actions, symbols, signature help, inlay hints, rename), all served by real language servers. Also exposes a stable editor-action protocol (lsp.actions.list / lsp.actions.run / lsp.events) so VS Code or other editors can consume agent-generated actions directly.
Install
dsh plugin --profile web add dsh-lsp-actionsnpm package dsh-lsp-actions 0.3.4 (registry-verified 2026-08-24). Requires the language servers you want to use installed on your PATH (e.g. npm i -g typescript-language-server for TypeScript). Compatible with DeepSeek Harness 0.1.1-rc.2 (peers >=0.1.0-rc.8 <0.2.0), Node.js ^22.19.0 || >=24.0.0. Gitee mirror at gitee.com/perrylink/dsh-lsp-actions.
Compatibility
DeepSeek Harness 0.1.1-rc.2 (peers >=0.1.0-rc.8 <0.2.0); Node.js ^22.19.0 || >=24.0.0. Pure host plugin (subprocess + filesystem, no network). Works with any language server on PATH. CI-tested on Node 22/24 across Linux, Windows, and macOS using a real typescript-language-server.
Details
- Repo: PerryLink/dsh-lsp-actions
- Category: Coding & Development
- Stars: 6
- Version: npm dsh-lsp-actions 0.3.4 (registry-verified 2026-08-24)
- Last push: 2026-09-21
- First seen: 2026-08-13
Recent updates
0.3.4: eight lsp_* tools; editor-action protocol v1 (lsp.actions.*); real typescript-language-server in CI; Node 22/24 CI matrix across Linux/Windows/macOS; pure host mount (inject: [tools, fs, subprocess]).
FAQ
- Do I need to install language servers separately?
- Yes — dsh-lsp-actions launches the language server process itself, but the server binary must already be on your PATH. For TypeScript/JavaScript, run npm i -g typescript-language-server typescript. For other languages, install the relevant LSP server (rust-analyzer, pylsp, clangd, etc.).
- What is the editor-action protocol and why does it matter?
- The editor-action protocol (lsp.actions.list / lsp.actions.run / lsp.events) is a stable JSON-RPC surface that lets editors like VS Code consume the same agent-generated LSP actions directly — so the agent writes code, requests a diagnostic, and the editor reflects the fix without copy-pasting. VS Code integration is the first supported consumer.
- How is this different from the official ctx.lsp seam?
- The official DSH ctx.lsp covers navigation (go-to-definition, find-references, implementation, hover). dsh-lsp-actions adds the action half — diagnostics, formatting, completion, code actions, rename, symbols, signature help, and inlay hints — which is what the agent needs to write and fix code in a loop.
Alternatives
PerryLink/dsh-composer-history · PerryLink/dsh-background-agents · omdsh-dev/dsh-open-in-vscode