Files
deepseek-harness/packages
Dudu-0223 ff563d07e0 feat(subagent): name subagents in their creator catalog
Models coordinate subagents through send_message, interrupt_agent, list_agents,
and Team task owners, but every one of those addressed a member by a
36-character Session id. Each new child now has a name, unique among its
creator's children, recorded as a field of the subagent/catalog entry the
creator already appends (payload version 3).

The Session id stays the only execution identity for routing, authorization,
persistence, task ownership, and navigation. A name is a model-facing
reference: 1-32 lower-case letters, digits, or hyphens starting with a letter,
never `lead`, so a UUID never parses as one. Omission selects the first free
`agent-N`; an explicit duplicate or invalid name fails before startup. The
creator reserves the name synchronously at admission and releases it when the
catalog entry commits or startup fails, so no second write, rollback protocol,
or optional naming service exists.

The root is `lead`, and a descendant's full name is its path from the root
without a `lead/` prefix, such as `reviewer/checker`. Sibling-unique segments
make full names tree-unique without a root registry, and cold resume rebuilds
a member's path from the catalogs along its creation chain. A member below an
unnamed historical creator keeps its Session id as its name. resolveName()
reads only the catalogs along the path and grants no authority.

Tools, runtime-authored text, and the Web client consume names: delegation
takes an optional name and returns { kind, subagentId, name }; send_message and
interrupt_agent take `agent`; list_agents rows carry name, status, and
description; Team task results report the owner's name while storage keeps
ownerId; identity runtime context, message framing, and settlement notices use
full names. Recorded sessions, CLI and Web expectations, the Python runtime
snapshots, bilingual docs, an upgrade guide, and an Agent Note follow.
2026-11-02 14:58:32 +08:00
..
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-31 10:40:31 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-28 02:03:15 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
2026-10-29 20:42:48 +08:00
…
…

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 service with owner-scoped sessions and a local shell backend
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
team/ Team coordination: shared task boards and model-facing task tools
jobs/ Generic background-job runtime and model-facing job control tools
experimental/ Capabilities under evaluation; status and support policy
workflow/ Workflow seam, PTC process engine, and the model-facing workflow tool
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
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 utilities and data-only package lists shared across groups (Branded<B>, home/path helpers, timeout, retention, official bundle lists)

Release expectations

Product groups have maintained product roles, while their public APIs remain pre-stable. Experimental status is independent of publication, installation, and optional delivery. Nonexperimental runtime packages must have product use or an explicit package classification; SDK, build, test, and declaration infrastructure have separate classifications.


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.