DSH

Providing small models with too many prompt tokens (tens of thousands to hundreds of thousands of specifications and tools) disperses their limited attention, and lightweight frameworks such as DSH are more small-model-friendly.

Everything described in the article is based on single-source empirical testing by community users; stability is uncertain, and it is recommended to use official paid APIs in production environments.

DSH-type projects share API quotas through aggregation or forwarding.

Each time the DSH image starts, it checks a remote source for a new version; if a new version is detected, it is automatically downloaded and launched, otherwise the current version continues to run.

The new version of DSH introduces an automatic update mechanism for container images that automatically checks for new versions each time it starts.

DSH's automatic update changes were introduced by Bilibili UP host "云镜之端," with the goal of reducing the cost of manual maintenance for users.

The DSH automatic update version is best suited for individual developers and technology enthusiasts who are accustomed to deploying self-hosted services with Docker, want to reduce manual maintenance overhead, and are willing to accept the trade-off of always running the latest version.

After the DSH project was open-sourced, users can view the source code, understand the automatic update implementation logic, and perform secondary development or submit improvements.

DSH's Bundle resolution order is to first look for built-in Bundles from the DSH installation location, then look in the Profile's own node_modules.

DeepSeek Harness (DSH) has no independent configuration language, and an Agent's capabilities depend solely on which plugin rows are combined.

DSH is essentially a Coreless (kernel-free) application where all capabilities are built upon the same empty root, composed by layering three levels: Profile, Bundle, and Patch.

The Coreless.iml file in DSH's Profile directory contains only an empty array (a pair of square brackets), which is an intentional empty-root design.

DSH adopts a layered configuration approach of empty root plus layered overrides, similar to Docker image layered file systems or CSS cascade rules, with the core advantage being change isolation.

DSH's complete Patch stacking order is: each Bundle's Patch, the Profile-level Coreless.patch.iml, Home-level Patch, and command-line Patch overrides, with the rule being that later entries override earlier ones.

DSH's Patch is not a deep merge but a wholesale replacement; modifying a capability means modifying the entire row rather than a single field.

DSH's row-level Patch uses wholesale atomic replacement, contrasting with field-level merging approaches such as JSON Merge Patch (RFC 7396), with the trade-off being that fine-tuning a single parameter requires copying the entire row in full.

DSH plugins are not loaded in the order they are written in the file; row order carries no loading semantics, and Coreless activation is driven by service availability (lazy activation).

In DSH, any row that publishes a service must be wrapped in a domain called Isolate; otherwise, services hanging at the process global level will cause same-name service collisions.

DSH's official annotation recommends treating the Coreless Preset session as Shell permissions.

DSH's UI remains consistent across devices, allowing users to see a consistent context state when initiating operations from any device.