A native DSH runtime injector that loads local plugin packages into a running web on the fly (junction + loader.create), with hot reload, staging, and uninstall — no restart, no bundle edits.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-08-24
License
Not specified by the author
01What can it help you accomplish?
Inject any local plugin package into a running DSH web at runtime without a process restart
A fully active plugin (host tool + client UI) injected via junction + loader.create, with hot reload, staging, and uninstall tooling
DSH (dsh) developers and modders who want to load local plugin packages at runtime, bypassing the official bundle-assembly entry
Run a local plugin package without rebuilding, via the cloud self-bootstrap path
Downloaded release copy assembled and run from the cloud copy, with self-check (8/8) and process recovery in ~6 seconds after failure
DSH developers who want a no-build, runtime inject path for local plugin packages
02How to install into DeepSeek Harness
Prerequisites
- A running DSH web environment with the injector resident (required for the runtime-inject dev path)
- For the git-assembly path, network access to pull tsdown on first build (local cache afterwards)
Installation steps
- 01
Release path (recommended, no build): download `dsh-external-dsh-super-injector-0.0.1.tgz` from Releases, unzip, then run `dsh plugin --profile web add <unzipped dir>`
$ dsh plugin --profile web add <unzipped dir>
- 02
$ git assembly: run `dsh plugin --profile web add github:yjh051108/dsh-super-injector`
- 03
Bootstrap assembly (source, once): add the `dsh-super-injector` insert block to `~/.dsh/profiles/web/cordis.patch.yml`
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
BepInEx-style runtime mod injector: injects local plugin packages into a running DSH web at runtime (junction + loader.create), without touching patch / package.json / bundles and without a process restart
Runtime injection (junction + loader.create)
a local plugin package directory→a fully active DSH plugin (host tool + client UI) in a running web without restart
modifies the running process's plugin state via junction + loader.create (does not touch patch / package.json / bundles)Hot reload / staging / uninstall tooling
an injected local plugin→hot reload, staging, and uninstall operations for injected plugins
reboot uses entry._dispose (official _disposing exemption) with automatic rollback on failureOfficial REPLACE-structure self reload
DSH 0.1.0-rc.6 source semantics (docs/SPEC.md)→a refactored self-reload that only schedules and never self-terminates; behavior backed by source
behaviors derived from DSH source semantics rather than empirical patches
04Who is it for? When not to use it?
Good for
- DSH (dsh) developers and modders who want to load local plugin packages at runtime, bypassing the official bundle-assembly entry
- DSH developers who want a no-build, runtime inject path for local plugin packages
Not for
- The bootstrap (method C) self-registers a `dsh-super-injector` bundle layer that collides with the manual insert entry id; after assembly via method A/B do NOT add the manual insert block, or you get a `duplicate loader entry id` error.
05Compatibility, maintenance and safety notes
- The bootstrap (method C) self-registers a `dsh-super-injector` bundle layer that collides with the manual insert entry id; after assembly via method A/B do NOT add the manual insert block, or you get a `duplicate loader entry id` error.
- The git-assembly path pulls the source repo (no prebuilt `lib/`); the `prepare` hook builds a self-contained `lib/` with tsdown on first install, which needs network to fetch tsdown. If the build fails, use the prebuilt Release tgz instead.
TypeScript · active, latest release v0.3.3 (2026-08-15); main branch
06Frequently asked questions
How is this different from the official bundle-assembly entry?
The official assembly mechanism (profile bundle / repository-plugin) is the only official entry, like a game launcher. This injector breaks that: the bootstrap goes through the official entry once, after which anything can be injected at runtime.
Which install path should I use?
The Release tgz (download `dsh-external-dsh-super-injector-0.0.1.tgz`, unzip, `dsh plugin --profile web add <dir>`) is recommended and needs no build. git assembly pulls source and builds `lib/` with tsdown on first install (network needed). Method C bootstrap is a one-time source insert.
What happens if I mix install methods?
If you assemble via method A/B and then also add the manual `insert` block from method C, the bundle layer collides with the manual loader entry id and you get a `duplicate loader entry id` error. Pick one path.
Is it compatible with the released DSH version?
The README states v0.3.0 runs unchanged on DSH 0.1.0-rc.6 (peerDeps are declared as ranges, proven by the peerDeps range declaration), and it does not hard-code a DSH version.
07Related DSH workflows
dsh-routing-suite
by yjh051108
dsh-routing-suite — injector + router-standard kit: install the runtime injector first, then the task-aware reasoning-mode router preset (measured P1-P23).
brooks-lint
by hyhmrright
AI code reviews grounded in 12 classic engineering books — decay risk diagnostics with book citations, severity labels, and 6 analysis modes including full-sweep auto-fix
dsh-plugin-shop
by livxue
The most comprehensive DeepSeek Harness plugin market — refreshed daily, sourced across the Internet, reviewed before publishing.
anolisa
by agentic-os-org
ANOLISA (Agentic Nexus Operating Layer & Interface System Architecture) | Agentic OS with runtime, security, observability, and Tokenless response compression for lower token usage and cost.
08Data and sources
DSH 生态的 **BepInEx 式模组注入入口**：运行时把任意本地插件包注入运行中的 web
不碰 patch / package.json / bundles 列表、不重启进程。**注入即完整生效
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-08-24. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.