dsh-lens-lite

In DeepSeek Harness, dsh-lsp provides semantic navigation—goto definition, find references, hover—yet nobody tells the model "this file has a type error" right after an edit. The model writes code, then discovers the error only a few turns later, almost by accident. dsh-lens-lite closes that gap: after any successful file-mutating tool call, it runs the type-checkers or linters you have configured and attaches their output to the same tool result, so the very next model request already carries the diagnostics.

The plugin ships zero built-in commands. Every checker is yours to declare in config—which executable to run, which file extensions it claims, how long it may take, and how much output to keep. Arguments support placeholders like {file} and {dir} for precise, single-file invocations. All matching checkers run concurrently, and their combined output arrives as a compact, collapsible notice in the transcript rather than a wall of compiler text flooding the context window. The plugin never vetoes or rewrites a tool call; it simply folds diagnostic context onto whatever decision came back from the downstream waterfall.

If you use DeepSeek Harness for day-to-day code editing and want the model to catch mistakes on the very first turn after a write—instead of discovering them three turns later—dsh-lens-lite is a lightweight, zero-intrusion fit. It only requires that your toolchain has a command you can invoke per file (tsc, ruff, golangci-lint, or any equivalent). For large repositories, prefer single-file invocation patterns to keep per-edit latency low, and raise timeoutMs only for checkers that genuinely need it.