mektpoy
a64d6406f5
parseRelayFrame parsed the wire text for the lifecycle snapshot and again for the envelope, and unsupportedFrameRefusal repeated both parses. One JSON.parse now feeds the snapshot check, the envelope, and the refusal branch, so the hot path decodes each frame exactly once.
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 |
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.