dsh-molbio-tools 0.20.0 → 0.21.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +111 -0
- package/README.md +31 -12
- package/benchmark/README.md +1 -0
- package/benchmark/_freeze-trace.mjs +92 -18
- package/benchmark/tasks/06-analysis.json +2 -1
- package/build/release-preflight.mjs +1 -1
- package/docs/history.md +32 -0
- package/docs/maintainer.md +1 -1
- package/docs/roadmap.md +7 -2
- package/docs/workflow.md +6 -4
- package/icon.svg +8 -0
- package/package.json +4 -2
- package/preset/molbio-lab/agent.cordis.yml +31 -157
- package/preset/molbio-lab/preset.patch.yml +14 -144
- package/test/contract.mjs +55 -10
- package/test/drift-probe.mjs +14 -5
- package/test/fixtures/benchmark-traces.json +20 -9
- package/test/preset-health.mjs +1 -1
|
@@ -41,16 +41,24 @@
|
|
|
41
41
|
#
|
|
42
42
|
# ── How this file is maintained ─────────────────────────────────────────────
|
|
43
43
|
#
|
|
44
|
-
# This row list is a COPY of the DSH-shipped `standard` preset with
|
|
45
|
-
# intentional
|
|
46
|
-
#
|
|
47
|
-
# config
|
|
48
|
-
#
|
|
49
|
-
#
|
|
44
|
+
# This row list is a COPY of the DSH-shipped `standard` preset with ONE
|
|
45
|
+
# intentional difference: the trailing `tool-molbio` row. Everything else —
|
|
46
|
+
# every row, every config key, in upstream's ORDER — is upstream's
|
|
47
|
+
# `config.plugins:` block, de-indented by ten spaces. This release's upstream
|
|
48
|
+
# list carries no comments of its own, so none appear below; provenance and the
|
|
49
|
+
# upgrade rules live in this header.
|
|
50
|
+
#
|
|
51
|
+
# Baseline: the `standard` preset of dsh 0.2.1-rc.2 (harness root
|
|
50
52
|
# `%APPDATA%\npm\node_modules\@deepseek-ai\dsh`, file
|
|
51
53
|
# `node_modules/@deepseek-ai/dsh-web-app/presets/standard.patch.yml`, whose
|
|
52
|
-
# rows live under the `preset-standard` row's `config.plugins:`).
|
|
53
|
-
#
|
|
54
|
+
# rows live under the `preset-standard` row's `config.plugins:`).
|
|
55
|
+
#
|
|
56
|
+
# 0.2.1-rc.2 is the first bump since 0.1.7-alpha.1 that changed the row list: it
|
|
57
|
+
# added `time-context`, `tool-schedule` and `tool-plugin-market`; dropped the two
|
|
58
|
+
# disabled optional subagent providers (`tool-subagent-codex`,
|
|
59
|
+
# `tool-subagent-claude-code`) and `tool-ralph`; dropped the persona `suffix` and
|
|
60
|
+
# both `backgroundMode: continuable` settings; and reworded the plan-mode
|
|
61
|
+
# section. Absorb such a bump verbatim — see workflow.md §4.
|
|
54
62
|
#
|
|
55
63
|
# Keeping the text verbatim is not cosmetic: a preset mounts DSH's OWN
|
|
56
64
|
# packages, so upstream drift here kills the whole preset at mount (the failure
|
|
@@ -66,98 +74,47 @@
|
|
|
66
74
|
# for the right reason;
|
|
67
75
|
# 2. re-run `node build/preset-patch.mjs`, then `node test/preset-health.mjs`,
|
|
68
76
|
# which validates every row's config against the INSTALLED package's own
|
|
69
|
-
# schema and reports drift; only the allowed
|
|
77
|
+
# schema and reports drift; only the allowed difference above may remain;
|
|
70
78
|
# 3. `node test/drift-probe.mjs` must still catch its mutations — a guard
|
|
71
79
|
# nobody has seen fail is not a guard.
|
|
72
80
|
#
|
|
73
81
|
# Do NOT "fix" `present` (or any other row) by hand to suit the toolset: if the
|
|
74
82
|
# upstream row is wrong for this preset, fix it upstream, not here.
|
|
75
83
|
|
|
76
|
-
# ── identity ────────────────────────────────────────────────────────────────
|
|
77
|
-
|
|
78
|
-
# The preset's own persona, shadowing the deployment default for this agent.
|
|
79
|
-
# `{{model}}` and `{{cwd}}` resolve from the agent's own route and workspace.
|
|
80
84
|
- id: persona
|
|
81
85
|
name: '@deepseek-ai/dsh-persona'
|
|
82
86
|
config:
|
|
83
|
-
|
|
84
|
-
prefix: >-
|
|
85
|
-
You are a coding agent powered by the {{model}} model.
|
|
86
|
-
|
|
87
|
+
prefix: You are a coding agent powered by the {{model}} model.
|
|
87
88
|
- id: agent-instructions
|
|
88
89
|
name: '@deepseek-ai/dsh-agent-instructions'
|
|
89
90
|
config:
|
|
90
91
|
maxBytes: 65536
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
# `shell-env` stays in the HOST composition: `apps/cli/src/web.ts` injects it to
|
|
95
|
-
# publish `DSH_WEB_URL`/`DSH_WEB_MODE`, and a host row that injects a service is
|
|
96
|
-
# the criterion for host-plane ownership — injection resolves before any session
|
|
97
|
-
# exists, so there is no agent to key by. Behind a preset realm those variables
|
|
98
|
-
# never reached the model's shell at all. Both shell tools consume the host
|
|
99
|
-
# registry from here; their executors (`bash-sandbox`/`pwsh-sandbox`) are
|
|
100
|
-
# host-plane too.
|
|
92
|
+
- id: time-context
|
|
93
|
+
name: '@deepseek-ai/dsh-time-context'
|
|
101
94
|
- id: tool-bash
|
|
102
95
|
name: '@deepseek-ai/dsh-tool-bash'
|
|
103
96
|
disabled: !!js process.platform === 'win32'
|
|
104
|
-
|
|
105
97
|
- id: tool-pwsh
|
|
106
98
|
name: '@deepseek-ai/dsh-tool-pwsh'
|
|
107
99
|
disabled: !!js process.platform !== 'win32'
|
|
108
|
-
|
|
109
|
-
# ── filesystem ──────────────────────────────────────────────────────────────
|
|
110
|
-
|
|
111
|
-
# Both register into the host `tools` registry and provide nothing, so
|
|
112
|
-
# they need no realm. The `fs` service and its policy stay in the host.
|
|
113
100
|
- id: tool-fs
|
|
114
101
|
name: '@deepseek-ai/dsh-tool-fs'
|
|
115
|
-
|
|
116
102
|
- id: tool-fs-search
|
|
117
103
|
name: '@deepseek-ai/dsh-tool-fs-search'
|
|
118
104
|
config:
|
|
119
105
|
sampleOverCapGlobResults: false
|
|
120
|
-
|
|
121
|
-
# ── background jobs ────────────────────────────────────────────────────────
|
|
122
|
-
|
|
123
|
-
# Only the model-facing controls. The task REGISTRY stays on the host plane:
|
|
124
|
-
# its producers sit outside any realm this file could put it in — `tool-bash`
|
|
125
|
-
# above resolves it with `ctx.get`, and an entry-local realm here is invisible
|
|
126
|
-
# to every sibling row, so `run_in_background` would answer "background jobs
|
|
127
|
-
# unavailable" while these controls sat in the catalog. The registry is keyed by
|
|
128
|
-
# owning agent anyway, so one host instance serves every session. What a preset
|
|
129
|
-
# chooses is whether its agent can collect and stop background work at all.
|
|
130
106
|
- id: tool-jobs
|
|
131
107
|
name: '@deepseek-ai/dsh-tool-jobs'
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
# The skill REGISTRY lives in the host composition and is layered per scope:
|
|
136
|
-
# these rows register into THIS preset's layer of it, so they need no realm.
|
|
137
|
-
# `skill-filesystem` contributes local-root discovery for agents on this preset, and
|
|
138
|
-
# `tool-skill` gives them the catalog and loader; the merged catalog also
|
|
139
|
-
# carries whatever the deployment registered globally (repository plugins).
|
|
108
|
+
- id: tool-schedule
|
|
109
|
+
name: '@deepseek-ai/dsh-tool-schedule'
|
|
140
110
|
- id: skill-filesystem
|
|
141
111
|
name: '@deepseek-ai/dsh-skill-filesystem'
|
|
142
|
-
|
|
143
112
|
- id: tool-skill
|
|
144
113
|
name: '@deepseek-ai/dsh-tool-skill'
|
|
145
|
-
|
|
146
|
-
# ── goals ───────────────────────────────────────────────────────────────────
|
|
147
|
-
|
|
148
|
-
# The goal service and session driver stay on the host plane, where the Gateway
|
|
149
|
-
# can resolve them. The human command and model-facing tool register into this
|
|
150
|
-
# preset's scoped layers.
|
|
151
114
|
- id: command-goal
|
|
152
115
|
name: '@deepseek-ai/dsh-command-goal'
|
|
153
|
-
|
|
154
116
|
- id: tool-goal
|
|
155
117
|
name: '@deepseek-ai/dsh-tool-goal'
|
|
156
|
-
|
|
157
|
-
# ── plan mode ───────────────────────────────────────────────────────────────
|
|
158
|
-
|
|
159
|
-
# Plan state is per-agent by nature, so an entry-local realm is not a
|
|
160
|
-
# workaround here — it is the correct lifetime.
|
|
161
118
|
- id: planning
|
|
162
119
|
name: cordis:group
|
|
163
120
|
group: true
|
|
@@ -168,29 +125,17 @@
|
|
|
168
125
|
name: '@deepseek-ai/dsh-plan-mode'
|
|
169
126
|
config:
|
|
170
127
|
section: |
|
|
171
|
-
|
|
172
|
-
|
|
173
|
-
Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
|
|
128
|
+
You are in plan mode. Stay in plan mode until the user approves your plan through exit_plan_mode or switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
|
|
174
129
|
|
|
175
|
-
|
|
130
|
+
Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
|
|
176
131
|
|
|
177
|
-
|
|
132
|
+
The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
|
|
178
133
|
|
|
179
|
-
|
|
134
|
+
Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
|
|
180
135
|
|
|
181
|
-
|
|
136
|
+
Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
|
|
182
137
|
|
|
183
|
-
#
|
|
184
|
-
|
|
185
|
-
# `compaction-basic` reads `toolResultPrune` through `ctx.get`, so the pruner must
|
|
186
|
-
# share this realm rather than sit outside it.
|
|
187
|
-
#
|
|
188
|
-
# `tokenMeter` is deliberately NOT in this realm: the meter stays on the HOST
|
|
189
|
-
# plane, and the rows here resolve that one instance. It takes no configuration,
|
|
190
|
-
# keys every fold by Session, and owns the context-meter projection units the
|
|
191
|
-
# browser reads for every session — behind a realm those units would come and go
|
|
192
|
-
# with whichever presets happen to be mounted. What a preset chooses is whether
|
|
193
|
-
# its agent compacts at all, which is `compaction-basic` below.
|
|
138
|
+
When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
|
|
194
139
|
- id: compaction
|
|
195
140
|
name: cordis:group
|
|
196
141
|
group: true
|
|
@@ -200,28 +145,14 @@
|
|
|
200
145
|
config:
|
|
201
146
|
- id: compaction-basic
|
|
202
147
|
name: '@deepseek-ai/dsh-compaction-basic'
|
|
203
|
-
|
|
204
148
|
- id: command-compact
|
|
205
149
|
name: '@deepseek-ai/dsh-command-compact'
|
|
206
|
-
|
|
207
150
|
- id: tool-result-pruner
|
|
208
151
|
name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
|
|
209
152
|
config:
|
|
210
153
|
thresholdChars: 8192
|
|
211
154
|
headChars: 4096
|
|
212
155
|
tailChars: 1024
|
|
213
|
-
|
|
214
|
-
# ── delegation and workflows ────────────────────────────────────────────────
|
|
215
|
-
|
|
216
|
-
# The `subagents` registry and its spawn/fork backends live in the HOST
|
|
217
|
-
# composition: the registry is a process singleton whose cross-session queries
|
|
218
|
-
# the api-proxy serves to the browser, and a provider name may only be
|
|
219
|
-
# registered once. This preset contributes the delegation TOOLS, which resolve
|
|
220
|
-
# that host registry.
|
|
221
|
-
#
|
|
222
|
-
# `workflows` is different — nothing outside an agent reads it — so every row
|
|
223
|
-
# that reaches it shares one entry-local realm here, and a consumer left
|
|
224
|
-
# outside would resolve a host registry this preset does not populate.
|
|
225
156
|
- id: delegation
|
|
226
157
|
name: cordis:group
|
|
227
158
|
group: true
|
|
@@ -230,101 +161,44 @@
|
|
|
230
161
|
config:
|
|
231
162
|
- id: tool-subagent-control
|
|
232
163
|
name: '@deepseek-ai/dsh-tool-subagent-control'
|
|
233
|
-
|
|
234
164
|
- id: tool-subagent-list-agents
|
|
235
165
|
name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
|
|
236
|
-
|
|
237
166
|
- id: tool-subagent
|
|
238
167
|
name: '@deepseek-ai/dsh-tool-subagent'
|
|
239
168
|
config:
|
|
240
169
|
provider: spawn
|
|
241
170
|
toolName: subagent
|
|
242
171
|
modelSelectionSettings: true
|
|
243
|
-
backgroundMode: continuable
|
|
244
|
-
|
|
245
|
-
# Fork omits model selection so provider/model stay equal to the parent and
|
|
246
|
-
# the inherited history remains eligible for KV Cache reuse. This preset
|
|
247
|
-
# keeps fork continuable; parent and child inherit the same messaging tool,
|
|
248
|
-
# while the parent id and return guidance follow the inherited history.
|
|
249
172
|
- id: tool-subagent-fork
|
|
250
173
|
name: '@deepseek-ai/dsh-tool-subagent'
|
|
251
174
|
config:
|
|
252
175
|
provider: fork
|
|
253
176
|
toolName: subagent_fork
|
|
254
|
-
backgroundMode: continuable
|
|
255
|
-
|
|
256
|
-
# Production dsh does not install these optional providers. Install the
|
|
257
|
-
# matching Bundle in this Profile and restart the Host, then copy this
|
|
258
|
-
# preset and remove `disabled` from the matching tool row. Host availability
|
|
259
|
-
# alone grants no tool.
|
|
260
|
-
- id: tool-subagent-codex
|
|
261
|
-
name: '@deepseek-ai/dsh-tool-subagent'
|
|
262
|
-
disabled: true
|
|
263
|
-
config:
|
|
264
|
-
provider: codex
|
|
265
|
-
toolName: subagent_codex
|
|
266
|
-
backgroundMode: one-shot
|
|
267
|
-
maxDepth: provider-managed
|
|
268
|
-
|
|
269
|
-
- id: tool-subagent-claude-code
|
|
270
|
-
name: '@deepseek-ai/dsh-tool-subagent'
|
|
271
|
-
disabled: true
|
|
272
|
-
config:
|
|
273
|
-
provider: claude-code
|
|
274
|
-
toolName: subagent_claude_code
|
|
275
|
-
backgroundMode: one-shot
|
|
276
|
-
maxDepth: provider-managed
|
|
277
|
-
|
|
278
177
|
- id: workflow-ptc
|
|
279
178
|
name: '@deepseek-ai/dsh-workflow-ptc'
|
|
280
179
|
config:
|
|
281
180
|
provider: spawn
|
|
282
|
-
|
|
283
181
|
- id: tool-workflow
|
|
284
182
|
name: '@deepseek-ai/dsh-tool-workflow'
|
|
285
|
-
|
|
286
|
-
# Off by default with the base row it mirrors: the tool description
|
|
287
|
-
# restricts `ralph` to runs the human explicitly asked for, and completion
|
|
288
|
-
# is a worker self-report, not an independent evaluation. Preset files take
|
|
289
|
-
# no patches, so a session that wants it duplicates this preset under a new
|
|
290
|
-
# id and drops `disabled`; the shipped root shadows a copy that reuses this
|
|
291
|
-
# id.
|
|
292
|
-
- id: tool-ralph
|
|
293
|
-
name: '@deepseek-ai/dsh-tool-ralph'
|
|
294
|
-
disabled: true
|
|
295
|
-
config:
|
|
296
|
-
subagentProvider: spawn
|
|
297
|
-
maxRounds: 64
|
|
298
|
-
|
|
299
|
-
# ── remaining model-facing rows ─────────────────────────────────────────────
|
|
300
|
-
|
|
301
183
|
- id: tool-ask-user
|
|
302
184
|
name: '@deepseek-ai/dsh-tool-ask-user'
|
|
303
|
-
|
|
304
185
|
- id: tool-todo
|
|
305
186
|
name: '@deepseek-ai/dsh-tool-todo'
|
|
306
187
|
config:
|
|
307
188
|
allowParallelInProgress: true
|
|
308
|
-
|
|
309
|
-
# The `web` service and its search provider stay in the host composition; only
|
|
310
|
-
# the model-facing tool is per-session.
|
|
311
189
|
- id: tool-web
|
|
312
190
|
name: '@deepseek-ai/dsh-tool-web'
|
|
313
191
|
config:
|
|
314
192
|
fetch: true
|
|
315
193
|
searchTimeoutMs: 60000
|
|
316
|
-
|
|
317
|
-
# Explicit workspace file delivery. Carried by every shipped preset that is not
|
|
318
|
-
# the fixed two-tool `minimal` training configuration, so this preset keeps the
|
|
319
|
-
# row: without it the agent cannot declare its generated maps/plots/gels as
|
|
320
|
-
# deliverables, which is most of what this toolset produces. It consumes only
|
|
321
|
-
# host-plane services (fs/session/tools) and publishes none.
|
|
322
194
|
- id: present
|
|
323
195
|
name: '@deepseek-ai/dsh-tool-present'
|
|
324
|
-
|
|
325
196
|
- id: tool-plugin-manager
|
|
326
197
|
name: '@deepseek-ai/dsh-plugin-manager/tools'
|
|
327
198
|
disabled: true
|
|
199
|
+
- id: tool-plugin-market
|
|
200
|
+
name: '@deepseek-ai/dsh-plugin-market/tools'
|
|
201
|
+
disabled: true
|
|
328
202
|
|
|
329
203
|
# dsh-molbio-tools: molecular-biology toolset (60 tools across sequence
|
|
330
204
|
# analysis, primers (incl. TaqMan probes and multiplex compatibility),
|
|
@@ -26,84 +26,37 @@
|
|
|
26
26
|
- id: persona
|
|
27
27
|
name: '@deepseek-ai/dsh-persona'
|
|
28
28
|
config:
|
|
29
|
-
|
|
30
|
-
prefix: >-
|
|
31
|
-
You are a coding agent powered by the {{model}} model.
|
|
32
|
-
|
|
29
|
+
prefix: You are a coding agent powered by the {{model}} model.
|
|
33
30
|
- id: agent-instructions
|
|
34
31
|
name: '@deepseek-ai/dsh-agent-instructions'
|
|
35
32
|
config:
|
|
36
33
|
maxBytes: 65536
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
# `shell-env` stays in the HOST composition: `apps/cli/src/web.ts` injects it to
|
|
41
|
-
# publish `DSH_WEB_URL`/`DSH_WEB_MODE`, and a host row that injects a service is
|
|
42
|
-
# the criterion for host-plane ownership — injection resolves before any session
|
|
43
|
-
# exists, so there is no agent to key by. Behind a preset realm those variables
|
|
44
|
-
# never reached the model's shell at all. Both shell tools consume the host
|
|
45
|
-
# registry from here; their executors (`bash-sandbox`/`pwsh-sandbox`) are
|
|
46
|
-
# host-plane too.
|
|
34
|
+
- id: time-context
|
|
35
|
+
name: '@deepseek-ai/dsh-time-context'
|
|
47
36
|
- id: tool-bash
|
|
48
37
|
name: '@deepseek-ai/dsh-tool-bash'
|
|
49
38
|
disabled: !!js process.platform === 'win32'
|
|
50
|
-
|
|
51
39
|
- id: tool-pwsh
|
|
52
40
|
name: '@deepseek-ai/dsh-tool-pwsh'
|
|
53
41
|
disabled: !!js process.platform !== 'win32'
|
|
54
|
-
|
|
55
|
-
# ── filesystem ──────────────────────────────────────────────────────────────
|
|
56
|
-
|
|
57
|
-
# Both register into the host `tools` registry and provide nothing, so
|
|
58
|
-
# they need no realm. The `fs` service and its policy stay in the host.
|
|
59
42
|
- id: tool-fs
|
|
60
43
|
name: '@deepseek-ai/dsh-tool-fs'
|
|
61
|
-
|
|
62
44
|
- id: tool-fs-search
|
|
63
45
|
name: '@deepseek-ai/dsh-tool-fs-search'
|
|
64
46
|
config:
|
|
65
47
|
sampleOverCapGlobResults: false
|
|
66
|
-
|
|
67
|
-
# ── background jobs ────────────────────────────────────────────────────────
|
|
68
|
-
|
|
69
|
-
# Only the model-facing controls. The task REGISTRY stays on the host plane:
|
|
70
|
-
# its producers sit outside any realm this file could put it in — `tool-bash`
|
|
71
|
-
# above resolves it with `ctx.get`, and an entry-local realm here is invisible
|
|
72
|
-
# to every sibling row, so `run_in_background` would answer "background jobs
|
|
73
|
-
# unavailable" while these controls sat in the catalog. The registry is keyed by
|
|
74
|
-
# owning agent anyway, so one host instance serves every session. What a preset
|
|
75
|
-
# chooses is whether its agent can collect and stop background work at all.
|
|
76
48
|
- id: tool-jobs
|
|
77
49
|
name: '@deepseek-ai/dsh-tool-jobs'
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
# The skill REGISTRY lives in the host composition and is layered per scope:
|
|
82
|
-
# these rows register into THIS preset's layer of it, so they need no realm.
|
|
83
|
-
# `skill-filesystem` contributes local-root discovery for agents on this preset, and
|
|
84
|
-
# `tool-skill` gives them the catalog and loader; the merged catalog also
|
|
85
|
-
# carries whatever the deployment registered globally (repository plugins).
|
|
50
|
+
- id: tool-schedule
|
|
51
|
+
name: '@deepseek-ai/dsh-tool-schedule'
|
|
86
52
|
- id: skill-filesystem
|
|
87
53
|
name: '@deepseek-ai/dsh-skill-filesystem'
|
|
88
|
-
|
|
89
54
|
- id: tool-skill
|
|
90
55
|
name: '@deepseek-ai/dsh-tool-skill'
|
|
91
|
-
|
|
92
|
-
# ── goals ───────────────────────────────────────────────────────────────────
|
|
93
|
-
|
|
94
|
-
# The goal service and session driver stay on the host plane, where the Gateway
|
|
95
|
-
# can resolve them. The human command and model-facing tool register into this
|
|
96
|
-
# preset's scoped layers.
|
|
97
56
|
- id: command-goal
|
|
98
57
|
name: '@deepseek-ai/dsh-command-goal'
|
|
99
|
-
|
|
100
58
|
- id: tool-goal
|
|
101
59
|
name: '@deepseek-ai/dsh-tool-goal'
|
|
102
|
-
|
|
103
|
-
# ── plan mode ───────────────────────────────────────────────────────────────
|
|
104
|
-
|
|
105
|
-
# Plan state is per-agent by nature, so an entry-local realm is not a
|
|
106
|
-
# workaround here — it is the correct lifetime.
|
|
107
60
|
- id: planning
|
|
108
61
|
name: cordis:group
|
|
109
62
|
group: true
|
|
@@ -114,29 +67,17 @@
|
|
|
114
67
|
name: '@deepseek-ai/dsh-plan-mode'
|
|
115
68
|
config:
|
|
116
69
|
section: |
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
|
|
70
|
+
You are in plan mode. Stay in plan mode until the user approves your plan through exit_plan_mode or switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
|
|
120
71
|
|
|
121
|
-
|
|
72
|
+
Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
|
|
122
73
|
|
|
123
|
-
|
|
74
|
+
The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
|
|
124
75
|
|
|
125
|
-
|
|
76
|
+
Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
|
|
126
77
|
|
|
127
|
-
|
|
78
|
+
Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
|
|
128
79
|
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
# `compaction-basic` reads `toolResultPrune` through `ctx.get`, so the pruner must
|
|
132
|
-
# share this realm rather than sit outside it.
|
|
133
|
-
#
|
|
134
|
-
# `tokenMeter` is deliberately NOT in this realm: the meter stays on the HOST
|
|
135
|
-
# plane, and the rows here resolve that one instance. It takes no configuration,
|
|
136
|
-
# keys every fold by Session, and owns the context-meter projection units the
|
|
137
|
-
# browser reads for every session — behind a realm those units would come and go
|
|
138
|
-
# with whichever presets happen to be mounted. What a preset chooses is whether
|
|
139
|
-
# its agent compacts at all, which is `compaction-basic` below.
|
|
80
|
+
When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
|
|
140
81
|
- id: compaction
|
|
141
82
|
name: cordis:group
|
|
142
83
|
group: true
|
|
@@ -146,28 +87,14 @@
|
|
|
146
87
|
config:
|
|
147
88
|
- id: compaction-basic
|
|
148
89
|
name: '@deepseek-ai/dsh-compaction-basic'
|
|
149
|
-
|
|
150
90
|
- id: command-compact
|
|
151
91
|
name: '@deepseek-ai/dsh-command-compact'
|
|
152
|
-
|
|
153
92
|
- id: tool-result-pruner
|
|
154
93
|
name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
|
|
155
94
|
config:
|
|
156
95
|
thresholdChars: 8192
|
|
157
96
|
headChars: 4096
|
|
158
97
|
tailChars: 1024
|
|
159
|
-
|
|
160
|
-
# ── delegation and workflows ────────────────────────────────────────────────
|
|
161
|
-
|
|
162
|
-
# The `subagents` registry and its spawn/fork backends live in the HOST
|
|
163
|
-
# composition: the registry is a process singleton whose cross-session queries
|
|
164
|
-
# the api-proxy serves to the browser, and a provider name may only be
|
|
165
|
-
# registered once. This preset contributes the delegation TOOLS, which resolve
|
|
166
|
-
# that host registry.
|
|
167
|
-
#
|
|
168
|
-
# `workflows` is different — nothing outside an agent reads it — so every row
|
|
169
|
-
# that reaches it shares one entry-local realm here, and a consumer left
|
|
170
|
-
# outside would resolve a host registry this preset does not populate.
|
|
171
98
|
- id: delegation
|
|
172
99
|
name: cordis:group
|
|
173
100
|
group: true
|
|
@@ -176,101 +103,44 @@
|
|
|
176
103
|
config:
|
|
177
104
|
- id: tool-subagent-control
|
|
178
105
|
name: '@deepseek-ai/dsh-tool-subagent-control'
|
|
179
|
-
|
|
180
106
|
- id: tool-subagent-list-agents
|
|
181
107
|
name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
|
|
182
|
-
|
|
183
108
|
- id: tool-subagent
|
|
184
109
|
name: '@deepseek-ai/dsh-tool-subagent'
|
|
185
110
|
config:
|
|
186
111
|
provider: spawn
|
|
187
112
|
toolName: subagent
|
|
188
113
|
modelSelectionSettings: true
|
|
189
|
-
backgroundMode: continuable
|
|
190
|
-
|
|
191
|
-
# Fork omits model selection so provider/model stay equal to the parent and
|
|
192
|
-
# the inherited history remains eligible for KV Cache reuse. This preset
|
|
193
|
-
# keeps fork continuable; parent and child inherit the same messaging tool,
|
|
194
|
-
# while the parent id and return guidance follow the inherited history.
|
|
195
114
|
- id: tool-subagent-fork
|
|
196
115
|
name: '@deepseek-ai/dsh-tool-subagent'
|
|
197
116
|
config:
|
|
198
117
|
provider: fork
|
|
199
118
|
toolName: subagent_fork
|
|
200
|
-
backgroundMode: continuable
|
|
201
|
-
|
|
202
|
-
# Production dsh does not install these optional providers. Install the
|
|
203
|
-
# matching Bundle in this Profile and restart the Host, then copy this
|
|
204
|
-
# preset and remove `disabled` from the matching tool row. Host availability
|
|
205
|
-
# alone grants no tool.
|
|
206
|
-
- id: tool-subagent-codex
|
|
207
|
-
name: '@deepseek-ai/dsh-tool-subagent'
|
|
208
|
-
disabled: true
|
|
209
|
-
config:
|
|
210
|
-
provider: codex
|
|
211
|
-
toolName: subagent_codex
|
|
212
|
-
backgroundMode: one-shot
|
|
213
|
-
maxDepth: provider-managed
|
|
214
|
-
|
|
215
|
-
- id: tool-subagent-claude-code
|
|
216
|
-
name: '@deepseek-ai/dsh-tool-subagent'
|
|
217
|
-
disabled: true
|
|
218
|
-
config:
|
|
219
|
-
provider: claude-code
|
|
220
|
-
toolName: subagent_claude_code
|
|
221
|
-
backgroundMode: one-shot
|
|
222
|
-
maxDepth: provider-managed
|
|
223
|
-
|
|
224
119
|
- id: workflow-ptc
|
|
225
120
|
name: '@deepseek-ai/dsh-workflow-ptc'
|
|
226
121
|
config:
|
|
227
122
|
provider: spawn
|
|
228
|
-
|
|
229
123
|
- id: tool-workflow
|
|
230
124
|
name: '@deepseek-ai/dsh-tool-workflow'
|
|
231
|
-
|
|
232
|
-
# Off by default with the base row it mirrors: the tool description
|
|
233
|
-
# restricts `ralph` to runs the human explicitly asked for, and completion
|
|
234
|
-
# is a worker self-report, not an independent evaluation. Preset files take
|
|
235
|
-
# no patches, so a session that wants it duplicates this preset under a new
|
|
236
|
-
# id and drops `disabled`; the shipped root shadows a copy that reuses this
|
|
237
|
-
# id.
|
|
238
|
-
- id: tool-ralph
|
|
239
|
-
name: '@deepseek-ai/dsh-tool-ralph'
|
|
240
|
-
disabled: true
|
|
241
|
-
config:
|
|
242
|
-
subagentProvider: spawn
|
|
243
|
-
maxRounds: 64
|
|
244
|
-
|
|
245
|
-
# ── remaining model-facing rows ─────────────────────────────────────────────
|
|
246
|
-
|
|
247
125
|
- id: tool-ask-user
|
|
248
126
|
name: '@deepseek-ai/dsh-tool-ask-user'
|
|
249
|
-
|
|
250
127
|
- id: tool-todo
|
|
251
128
|
name: '@deepseek-ai/dsh-tool-todo'
|
|
252
129
|
config:
|
|
253
130
|
allowParallelInProgress: true
|
|
254
|
-
|
|
255
|
-
# The `web` service and its search provider stay in the host composition; only
|
|
256
|
-
# the model-facing tool is per-session.
|
|
257
131
|
- id: tool-web
|
|
258
132
|
name: '@deepseek-ai/dsh-tool-web'
|
|
259
133
|
config:
|
|
260
134
|
fetch: true
|
|
261
135
|
searchTimeoutMs: 60000
|
|
262
|
-
|
|
263
|
-
# Explicit workspace file delivery. Carried by every shipped preset that is not
|
|
264
|
-
# the fixed two-tool `minimal` training configuration, so this preset keeps the
|
|
265
|
-
# row: without it the agent cannot declare its generated maps/plots/gels as
|
|
266
|
-
# deliverables, which is most of what this toolset produces. It consumes only
|
|
267
|
-
# host-plane services (fs/session/tools) and publishes none.
|
|
268
136
|
- id: present
|
|
269
137
|
name: '@deepseek-ai/dsh-tool-present'
|
|
270
|
-
|
|
271
138
|
- id: tool-plugin-manager
|
|
272
139
|
name: '@deepseek-ai/dsh-plugin-manager/tools'
|
|
273
140
|
disabled: true
|
|
141
|
+
- id: tool-plugin-market
|
|
142
|
+
name: '@deepseek-ai/dsh-plugin-market/tools'
|
|
143
|
+
disabled: true
|
|
274
144
|
|
|
275
145
|
# dsh-molbio-tools: molecular-biology toolset (60 tools across sequence
|
|
276
146
|
# analysis, primers (incl. TaqMan probes and multiplex compatibility),
|