dsh-progressive-tools
适用于 DeepSeek Harness 的缓存稳定型渐进式工具发现与调度
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:everclear077/dsh-progressive-tools#47e9ea5eaeb73ca2639acdad8f5b76ff5403dd7fProgressive Tools 以 dsh-progressive-tools 发布，当前版本为 0.4.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Cache-stable progressive tool discovery for DeepSeek Harness. The default mode sends a small, fixed tool surface on the first request, keeps the complete catalog in process memory, and executes discovered tools through the ordinary Harness pipeline.
Documentation map · Getting started · Upgrade guide · Troubleshooting
Every visible tool definition consumes input tokens on every request. Changing that definition list later also changes the request prefix and reduces context cache reuse. Progressive disclosure needs both properties at once:
The default stable-proxy mode provides that contract:
complete registry (process memory)
│
├── exact searchable definitions
│
└── fixed request surface
├── tool_search
├── tool_dispatch
└── common direct tools
│
tool_search result ────┴──► append exact matches to conversation history
│
└── tool_dispatch ──► normal DSH execution pipeline
Search changes conversation history, not the top-level tool list. Approval, guards, argument validation, timeout wrappers, result policy, deferred context, and cancellation still run for the selected real tool.
status catalog listing, with an optional
statusGrantsDiscovery grant for trusted deployments.tool_dispatch transport with runtime schema validation through the
original tool definition.dynamic compatibility mode for deployments that require native definitions
after activation.^22.19.0 or >=24.0.00.1.5-rc.1 (exact tested core peer versions)Version 0.4.0 targets runtime 0.1.5-rc.1. Core peer versions are
pinned to that tested release; older runtimes and later prereleases are not
covered. Earlier plugin versions predate this adaptation. The command below
uses the release tag for reproducible deployments.
dsh plugin --profile web add github:everclear077/dsh-progressive-tools#v0.4.0
Source installs run the package prepare script. If pnpm asks for build
authorization, add the exact package key it reports to the profile's
pnpm-workspace.yaml:
allowBuilds:
dsh-progressive-tools: true
Verify the composed layer before starting the profile:
dsh --profile web --dump-config
The dump should contain the progressive-tools row contributed by this bundle.
The default direct surface contains:
tool_search;tool_dispatch;skill, ask_user_question, report, submit_*, and
structured_output* when registered;No special wording is required in an ordinary conversation. A stable system instruction tells the agent to search before declaring a capability unavailable.
Discovery returns exact definitions:
{
"query": "browser navigation",
"max_results": 3
}
The next call uses one returned definition:
{
"name": "browser_open",
"arguments": {
"url": "https://example.com"
}
}
Each match also lists every member tool name of its family, and the whole family becomes dispatchable from that one search — siblings that did not make the top-ranked slice can be dispatched by name or schema-loaded with one exact-name query.
tool_search also accepts {"action":"status"}, which lists every deferred
family with its member tool names alongside catalog and savings estimates. By
default the listing is browse-only: dispatching an unseen name still requires
one exact-name search, and the rejection message says so. Deployments that
prefer immediate access can set statusGrantsDiscovery: true. Search results
are append-only conversation content; they never add native definitions to the
top-level request.
The default configuration is intentionally small:
- id: progressive-tools
config:
mode: stable-proxy
toolName: tool_search
dispatchToolName: tool_dispatch
maxResults: 5
requireDiscovery: true
statusGrantsDiscovery: false
deferToolGuidance: true
alwaysVisible:
- skill
- ask_user_question
- report
- submit_*
- structured_output*
Family rules improve search without changing the stable request surface:
- id: progressive-tools
config:
groups:
- id: browser
description: Browser navigation and page interaction
aliases: [browser, web page, 浏览器]
include: [browser_*]
- id: database
description: Database inspection and queries
aliases: [database, sql, 数据库]
include: [db_*, sql_*]
See configuration for every option, the
plugin-ecosystem onboarding checklist (alwaysVisible for high-frequency
tools, skillBindings for Skill-shipping packages, explicit groups for
unconventional names), and the migration notes for dynamic mode. The
progressive disclosure model maps Skills,
exact tool definitions, execution, and provider capability gaps.
Stable mode filters the authoritative prompt assembly instead of changing the
registry view. A direct call to a deferred name is then denied by a monotonic
tool guard. tool_dispatch creates a nested execution with the original agent,
signal, root call identity, arguments, and real tool name, so normal DSH policy
continues to apply to that real tool.
The guard is a routing invariant, not a replacement for approval or sandbox policy. Security-sensitive deployments should keep their existing controls enabled.
pnpm install
pnpm run check
The test suite includes a real AgentLoop request test that captures the first wire-ready tool array and verifies that discovery leaves both tools and system text unchanged.
The implementation follows the public references for architecture, system prompt assembly, tool execution, skills, and plugin packaging.