studyzy/dsh-lazy-tools

dsh-lazy-tools is a deferred tool-loading plugin built specifically for DeepSeek Harness 0.2.0-rc.2, inspired by the CodeBuddy defer mechanism. It is installed as an external bundle through dsh plugin --profile <profile> add git:github.com/studyzy/dsh-lazy-tools, or locally as add link:/path/to/dsh-lazy-tools during development, and injects a single cordis plugin named lazy-tools via cordis.patch.yml. The plugin exposes two new agent-scope tools, tool_search and defer_execute_tool, which observe tool name, description, and parameters without ever modifying the underlying registry, and hide deferred tools at the system-prompt/assemble waterfall so their JSON schemas never enter the model context. peerDependencies pin @deepseek-ai/dsh-* 0.2.0-rc.2, @deepseek-ai/cordis 4.0.4, and @deepseek-ai/schemastery 3.18.4, so the harness preflight accepts it directly; after upgrading DSH, realign these versions, rerun pnpm install && pnpm run check, and re-add the bundle.

The default policy is Defer(*), with a small resident core (read, write, edit, bash, glob, grep, web_search, web_fetch, ask_user_question, skill) kept always visible, and three guards (tool_search, defer_execute_tool, run_code) pinned so they cannot be deferred by Defer(*). Users override defaults in cordis.patch.yml under the plugin's config field using CodeBuddy-style Defer(pattern) / NoDefer(pattern) entries; * is the only wildcard, bare names are equivalent to the wrapped form, and noDefer always wins over defer. The Web and Desktop builds additionally expose a visual configuration page at Settings → Built-in plugins → Lazy tools with six fields mirroring the YAML keys, where defer and noDefer accept comma-separated input. When autoTune is left at its default true, the plugin scans up to autoTuneWindowDays (30) days of project history keyed by absolute cwd, promotes the autoTuneTopN (20) most frequent tools to resident, and writes the result to a per-project store that overrides the global config; autoTuneMinSamples (200) gates the rewrite so brand-new projects keep using globals.

Tool sources are treated uniformly: host composition tools, agent preset tools, MCP servers, and tools registered after the agent was created all pass through the same defer and search logic, and the plugin never loosens any other restrict policy — tools blocked elsewhere return unavailable from tool_search. Development requires Node 22 or 24 with pnpm, plus scripts typecheck, typecheck:tests, test (vitest unit and integration), lint (oxlint), build (tsc + tsdown to lib/), verify:client (browser-kernel contract check), and the umbrella check; CI in .github/workflows/ci.yml runs them on both Node majors. Documented limits include: an activated tool only appears in the next request, deferred tool names are invisible until searched, session state is not persisted across resume or fork, the plugin is a no-op under PTC presentation except for the pinned run_code, and a missing UI tab after a client-side change is fixed by restarting DSH so its negative client-plugin cache resets. The project ships under the MIT license.