Tianyi Cui
6f0174b5a2
A structured local activation now accepts continuation messages, but its terminal predicate checked only delegated children. A correction accepted during the model request could therefore remain in either Inbox queue while the earlier response committed structured_output. The loop later consumed the correction, but the terminal tool guard prevented revising the captured value, so callers could receive the obsolete answer as completed work. Require both Inbox queues to be empty as well as all owned children to be released before staging a structured result. Keep input admission closed from that synchronous staging point through authoritative result policy, including the enclosing PTC result. Derive this admission state from the existing staged, pending, and captured records instead of introducing a second lifecycle controller. Failed results delete their stage and reopen input; successful capture keeps the existing terminal behavior. Caller-owned delivery, complete final text, descendant ownership, and cold resume remain unchanged. Add deterministic barriers for accepted steering and queued input, and for Native/PTC post-execute acceptance and rejection. All six new cases failed against the unchanged runtime for stale results or incorrectly accepted late input, then passed with the fix. Extend the authored headless structured scenario to reject answer 41, consume a parent correction, and commit 42. Its two own schema sidecars also need the current master bash/edit/write definitions: retaining their previous definitions fails verifyHeaders on this pinned base. Update the owning bilingual result-admission documentation. Validation: - pnpm run build:native-system - pnpm exec vitest run packages/subagent/subagent/tests/structured.spec.ts packages/subagent/subagent/tests/continuation.spec.ts packages/subagent/subagent/tests/external-activation.spec.ts (214 passed) - pnpm run test:snapshot:refresh snapshots/session/headless.snapshot.ts -t subagent-structured-parent - pnpm run test:snapshot snapshots/session/headless.snapshot.ts -t subagent-structured-parent (1 selected scenario passed) - pnpm run test:docs (21 gates passed) - pnpm run doc-sync (42 gates passed) - pnpm run lint completed its host build; after correcting test deferred generic types, pnpm run lint:contracts-ready passed - git diff --check
description, kind
| description | kind |
|---|---|
| The DeepSeek Harness package workspace: how the npm packages under packages/ are grouped, what each group owns, and the conventions that bind them. | package-group |
Packages
English | 中文
Summary
The harness is assembled from npm packages under packages/, grouped by capability family: sessions and the agent loop, model-facing tools, shell and filesystem execution, web access, subagents, and the rest. Use this page as the top-level map: find the owning group, then open its README for the package list. Every package is scoped @deepseek-ai/dsh-* and lives in exactly one group; each group README is the authoritative package map for its family.
Table of Contents
Package groups
Every package lives in exactly one group; new packages join existing groups, and a new group updates its own README and this table.
| Group | Role |
|---|---|
core/ |
Product API spine: sessions, prompts, tools, agent services, and the concrete loop |
api/ |
Remote BFF assembly and Typert RPC gateway |
typert/ |
Type graph generation, artifact loading, and runtime registry |
goal/ |
Same-session goal persistence and lifecycle |
schedule/ |
Host-owned scheduled follow-ups |
feedback/ |
Human feedback capture and command |
telemetry/ |
Shared Cordis OTel reporting channels |
identity/ |
Shared anonymous identity |
llm/ |
LLM capability family: abstract service + provider adapters |
subprocess/ |
Subprocess capability family: Service Definition + local process-tree provider |
ssh/ |
POSIX remote connection with paired filesystem, subprocess and sandbox providers |
shell/ |
Bash capability family: executor seam, local impl, model-facing tools |
terminal/ |
Persistent PTY capability family: owner-scoped sessions, local implementation, model-facing tools |
ptc-runtime/ |
PTC execution capability family: Service Definition + sandboxed Node provider + PTC mode Consumer |
computer-use/ |
Exclusive named desktop-provider registration |
browser-use/ |
Exclusive named browser-provider registration |
sandbox/ |
Process-confinement seam; bwrap/Landlock/Seatbelt backends |
deliverables/ |
Turn deliverables: explicit file delivery and recorded workspace changes |
fs/ |
Filesystem capability family: seam, local impl, model-facing file tools, discovery tools |
lsp/ |
LSP capability family: seam, generic stdio provider, and the lsp tool |
skill/ |
Skill capability family: provider registry, local provider, model-facing catalog/loader |
compaction/ |
Compaction capability family: Service Definition + basic provider + command Consumer |
context/ |
Model-visible request context: workspace instructions, time context, references |
subagent/ |
Subagent capability family: provider-registry contract and model-facing delegation tools |
jobs/ |
Generic background-job runtime and model-facing job control tools |
experimental/ |
Pre-stable prototypes with explicit private exceptions |
workflow/ |
Workflow seam, PTC process engine, and model-facing workflow/ralph tools |
webhook/ |
Verified external events, trusted rules, and fire-and-forget Workspace Sessions |
web/ |
Web capability family: seam, search/fetch providers, model-facing web tools |
document/ |
Shared Host Office-to-PDF conversion |
attachment/ |
Durable attachment identity, validation, local content-addressed storage |
spill/ |
Spill capability family: storage seam, local impl, tool-result spill policy |
todo/ |
The model-facing todo_write tool |
plan/ |
Plan collaboration state with a direct entry command and reviewed exit |
preset/ |
Per-session agent composition from preset cordis.yml files |
guard/ |
Loop-hygiene guards: advisory repeat-call reminders + the tools/execute deadline enforcer |
bundle/ |
Installable dsh --profile patch layers |
extensions/ |
Agent runtime self-modification: live plugin/service inspection and model-written mount/unmount |
mcp/ |
External Model Context Protocol servers exposed as native tools |
hooks/ |
Hook bridges + the shared Claude Code / Codex wire-protocol library |
session/ |
Durable session data plane: persistence seam + backends, projection seam, log-backed titles, session reporting |
session-query/ |
Session retrieval family: logical corpus, bounded reads, lineage, semantic filtering, SQLite full-text search |
settings/ |
User-settings seam + file-backed provider |
credentials/ |
Credential-reference and credential-record seam + env-over-.env provider + authorization flows that ask a human |
storage/ |
Non-session storage hub + backends + domain form |
workspace/ |
Workspace entity |
sdk/ |
Out-of-process SDK: JSON-RPC protocol and TypeScript client/server |
acp/ |
Automation-only Agent Client Protocol server |
interaction/ |
Human-collaboration plane: approval/interaction seams, permission preset, commands, ask-user tool |
boot/ |
Shared app-bin boot glue |
host/ |
Web GUI host services, directory picking, application launch, plugin inventory, and product telemetry |
client/ |
Web-GUI browser half: shell, wire, object services, slots, ui-* plugins |
test-support/ |
Test infrastructure (testkits, replay, Loader smokes) |
util/ |
Low-level zero-dependency utilities shared across groups (Branded<B>, home/path helpers, timeout, retention) |
Release expectations
Most groups are product — stable API. The exceptions: experimental/ publishes without stability or support promises, and test-support/ and util/ are support with lower compatibility expectations.
Dependencies
The dependency graph is generated: docs/module-graph.md (pnpm run gen-module-graph, freshness-gated in CI).
Extension plugins depend on Service Definitions, never concrete providers. dsh-agent-loop is swappable; UI, hook, and tool plugins use dsh-agent. Composition bundles may depend on spine plugins. Capabilities separate Service Definition / Service Provider / Consumer roles when they evolve independently; see capability seams.
Package README contracts
Every package README covers purpose, configuration, extension points, and Model Experience unless the model-agnostic omission allowlist exempts it. It also carries ## Known Limitations and Deferred Work or uses its allowlist. Package conventions — exports, service access, tests — live in packages/AGENTS.md.
Dev Note
Working context for maintainers — click to expand
None.