Why DeepSeek Harness Plugins the Runtime, Not Just the Tools

Overview

DeepSeek Harness (DSH) treats the entire Agent runtime—model adapters, system prompts, tool catalog, sessions, storage, sandbox, Agent loop, Web UI, headless runner, and various presets—as a unified plugin system.

From Configuration to Runtime Graph

When DSH starts it reads a Profile and a set of Bundle s, applies user Patch es, and the Cordis Loader mounts each configuration line as a plugin instance.

Bundle : distributes a group of Cordis configurations and the corresponding plugin code.

Profile : selects which bundles to stack; built‑in templates include web and headless.

Patch : replaces or inserts configuration lines for user overrides or CLI flags.

The Loader produces a running plugin tree rather than a static object. Each line defines plugin name, hierarchy, parameters, activation conditions, and service isolation domain. Changing the configuration can reconfigure, unload, or mount plugin instances, which distinguishes DSH from ordinary “register a batch of plugins”.

Cordis Runtime: Context, Service, Fiber, Effect

Context : a singleton‑like object (e.g., ctx.tools, ctx.llm, ctx.sessions) that also defines service boundaries. Child contexts inherit services; isolate() creates an isolated realm for a service.

Service : abstracts capability interfaces so consumers depend on stable names rather than concrete implementations (e.g., a filesystem fs provider can be swapped for a sandboxed version).

Fiber : a concrete plugin mounting. The same plugin definition can produce multiple fibers under different contexts, each tracking configuration, dependencies, lifecycle state, and cleanup function.

Effect : records side‑effects such as listeners, handles, or processes. When a fiber unloads, Cordis knows which resources to dispose.

This design makes Cordis a mutable dependency graph that refreshes when providers change, allowing dynamic re‑binding and unloading.

React Analogy (but not React Fiber)

Cordis borrows the React effect model: effects are attached to lifecycle nodes and cleaned up by the runtime. Unlike React Fiber, which manages UI rendering, Cordis Fiber manages plugin dependencies, lifecycles, and resource reclamation. Dependency changes trigger service‑level refreshes rather than a full re‑render.

Event System and Loader Extensibility

Four event mechanisms drive extensibility: emit, parallel, serial, bail for observation and flow control. waterfall whose next() can wrap remaining steps, enabling hooks at agent/pre-step, agent/request, llm/stream, and tool execution points without altering the core Agent loop.

The Loader parses configuration entries, creates fibers via a Registry, and updates or disposes them when entries change.

Append‑Only Session Event Stream

While the plugin graph describes current capabilities, the Session maintains an immutable log of events: turn, step, user/message, assistant/message, tool/call, and tool/result. Recovery, branching, UI replay, and analytics derive from this log.

Only the surface needed for the next model request is projected via deriveMessages(); raw chunks, turn boundaries, and statistical events are not re‑sent, preserving auditability while allowing selective compaction.

Agent Presets

DSH ships four presets— standard, code, minimal, cordis —that share the same Agent loop and host services. Differences are expressed by configuration lines within the session scope, not by separate executables, enabling a single Web process to host sessions of different presets simultaneously.

Comparison with Other Harnesses

Pi focuses on a tight inner loop with direct model calls; OpenClaw emphasizes gateway integration; Hermes‑Agent organizes capabilities around AIAgent with cost‑aware design; Codex defines execution semantics (Thread, Turn, Item) for typed app‑server protocols. DSH’s distinguishing feature is that the composition relationship itself becomes a runtime system, allowing providers, tools, sessions, sandbox, UI, and loop to be recombined dynamically.

Dynamic Plugins and Cache Efficiency

Although Cordis permits runtime plugin loading/unloading, DSH does not regenerate the entire prompt each step. As long as the system prompt, tool schema, model routing, and historic prefix remain unchanged, the same prefix can be reused. Cache invalidation only occurs when visible inputs change (tool set, prompt sections, model switch, or compaction replacement).

When DSH Is a Good Fit

If an organization’s complexity resides in a fixed Agent loop, few stable tools, and a single host, a lighter framework like Pi may be easier. DSH shines when complexity stems from multiple hosts, providers, session‑level isolation, hot‑swapping, third‑party plugin ecosystems, and varied Agent modes. npx @deepseek-ai/dsh web DSH is currently in developer preview; APIs, plugin contracts, and target models are not guaranteed stable.

Boundaries of “Everything Is a Plugin”

The phrase describes the organization of application capabilities, not a literal recursive plugin tree. Cordis creates the root Context, Fiber, Registry, Events, and Logger services at construction time; Session objects, boot code, and UI cannot be interpreted before the plugin graph exists.

Benefits and Costs

Unified composition: tools, providers, UI, and presets share Context, Service, Event, Effect, and Fiber.

Lifecycle as a first‑class concern: configuration, dependencies, and disposers are tied to a single Fiber.

Late binding and positional replacement of dependencies.

Modes are composable, not separate program branches.

Runtime observability of entries, fibers, services, and effects.

Costs include:

Static code no longer reflects the actual system topology; the real topology depends on Profile, Bundle, Patch, Preset, conditions, and realms.

Dynamic dependencies can cascade, causing many fibers to unload/reload on a single provider change.

Effect cleanup is not a full transaction; external side‑effects need separate idempotency and compensation.

Plugin isolation does not prevent direct Node API usage; inject only restricts Context‑based access.

The meta‑framework and local forks become new core maintenance points.

FAQ

Is the core innovation the Agent loop? No. The minimal Agent loop is common; DSH’s value lies in how Cordis’s plugin graph and session event stream jointly manage compositional complexity.

Can Cordis effects guarantee rollback of external actions? No. Effects only manage resources declared by plugins (listeners, handles, processes). External actions such as network calls or file writes need independent idempotency mechanisms.

Is the minimal preset safer? Not necessarily; it narrows the model‑visible tool surface but does not remove host‑level permissions, approvals, or sandbox services.

Is DSH ready for production? It is better suited for architectural research, internal prototypes, and harness experiments. Production use requires validation of configuration recomposition, reliable fiber unloading, and consistent session projection after compression or branching.