Architecture · Launch wave B

DeepSeek Harness Architecture: Cordis, Profiles & Plugins

DeepSeek Harness composes an empty Cordis root from ordered bundle patches, the profile patch, a home-level patch and command-line overlays. Later layers win by row, and a patch replaces a targeted row’s complete config rather than deep-merging arbitrary keys. This page separates verified behavior from community reports and marks the release-candidate context so you can act without mistaking an observation for a permanent guarantee.

Verified Aug 14, 2026Developer previewIndependent guide
Evidence status: Official architecture/reference docs. Re-check the linked first-party source after a new release candidate.

What is verified now

DeepSeek Harness composes an empty Cordis root from ordered bundle patches, the profile patch, a home-level patch and command-line overlays. Later layers win by row, and a patch replaces a targeted row’s complete config rather than deep-merging arbitrary keys.

Evidence basis: Official architecture/reference docs. The status was checked on 14 August 2026; re-check the linked source after any dsh release.

Safe workflow

Use the smallest reversible workflow first. Do not add community plugins or paste credentials while validating the base behavior.

  1. Inspect the default bundle layers.
  2. Dump the composed configuration before boot.
  3. Add one patch overlay and verify which complete config row wins.

Verify before moving on

A successful result should be observable: a version string, reachable local URL, valid provider response, loaded configuration, or disappearance of the exact error. If the result differs, stop and capture sanitized evidence rather than stacking unrelated fixes.

  1. Record the exact dsh, Node or Python version.
  2. State the operating system and installation method.
  3. Link the first-party source and include only sanitized logs.

First-party sources

Open the original source before acting on a changed version or unresolved community report.

Continue by layer