From dsh web to one turn/end
Connect profiles, bundles, Cordis, ReactLoopAgent, SessionEvent, and Web/ACP into one route before opening the six deeper boundaries.
Read the chapter →Source notes · Seven-part route
DeepSeek Harness: who owns the agent's runtime semantics?
DeepSeek Harness places model adapters, tools, the session log, the agent loop, interfaces, and persistence in one Cordis plugin tree. These seven chapters follow commit ddefc45 from dsh web to event projection, governed side effects, delegation, and persistent plugin extension.
Reading order.For a first encounter with DSH, follow 01–07. The order reflects runtime dependencies, not a feature catalog: establish the end-to-end turn first, then open Cordis composition and the deeper state boundaries.
How Everything is a Plugin becomes concrete
Follow patches, Context, Service, isolation, Fiber, and HMR through deterministic composition, dependency activation, and structured teardown.
Read the chapter →Model-visible means logged
Follow four message types, stream settlement, and plugin projections through model and human views before validating v3 restoration seeds.
Read the chapter →When is a side effect safe to dispatch?
Follow tool/call, flush checkpoints, approval, sandboxing, JSONL, and crash repair to decide when an external action may run and when its outcome remains unknown.
Read the chapter →Shrink model surface without deleting history
Follow request pressure, text pruning, image offload, and summary replacement to reconstruct requests from system messages and headers.
Read the chapter →Delegation and orchestration over one provider seam
Follow SubagentRuntime, spawn/fork, continuable children, workflow, Ralph, and experimental Team through context, ownership, and coordination.
Read the chapter →When an agent can extend its runtime
Follow read-only Inspect into persistent Bundles, separating profile writes, Host activation, browser verification, and cross-session permissions.
Read the chapter →