GPL-3.0 JavaScript plugin that turns DeepSeek Harness into a driver for Huawei eNSP — 50 scenario blueprints, command-by-command config push, assertion-based verification and Word lab reports, on Windows with administrator rights.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-15
License
GPL-3.0
01What can it help you accomplish?
Build a Huawei eNSP lab from a DeepSeek Harness session: generate the `.topo`, boot the devices, push each device's config and check every command
A `.topo` file eNSP opens and renders, devices confirmed ready and then minimized, and a config run reported as `{ ok, failedAt }` down to the failing line
Network engineers, trainers and students running Huawei eNSP on Windows who want the lab driven from a DSH conversation instead of manual clicking
Turn a finished lab into a submittable Word document instead of writing it by hand
A `.docx` with the six fixed chapters, the config read back from the devices themselves, the full output of every check command and a pass / not-passed / unverified verdict
Instructors and learners who must hand in lab reports, and anyone who needs evidence of what the devices were actually configured with
Locate the failing item when startup fails or a click does nothing — before touching the topology
A seven-item verdict in a fixed order (client binary, VirtualBox, images, console ports, input injection, memory, anchors), each failing item paired with a concrete fix
People on freshly set up or just-upgraded Windows machines, and anyone working from a service, scheduled task or SSH session where input injection is unavailable
02How to install into DeepSeek Harness
Prerequisites
- Windows only — eNSP has a Windows version only, so the plugin declares `win32`
- Huawei eNSP installed and able to run (the repo bundles neither eNSP nor any Huawei software)
- Node.js 18 or newer
- DSH from 0.2.0 up to but not including 0.3.0 — `engines.dsh` decides compatibility
- Run the tool and eNSP as administrator, both at the same privilege level
Installation steps
- 01
Search `dsh-ensp` in the plugin marketplace and install it, or run `dsh plugin --profile desktop add dsh-ensp`
$ dsh plugin --profile desktop add dsh-ensp
- 02
Without DSH: `npm install -g dsh-ensp`, then `ensp status`
$ npm install -g dsh-ensp
- 03
For MCP clients (the README names Claude Desktop and Cursor): register `{"command": "npx", "args": ["-y", "dsh-ensp", "mcp"]}`
- 04
Install paths normally need no configuration: the tool probes `--exe` / `--vbox`, then `DSH_ENSP_EXE` / `DSH_VBOX`, then the registry, then common install roots and `PATH`
Verify the integration
- Run `ensp doctor --topology lab.topo`: seven checks are judged in a fixed order, a failing item gets an executable fix, and eNSP is never started
- The CLI install block runs `ensp status` immediately after `npm install -g dsh-ensp`
- Then follow the documented order — `doctor` judges the environment, `up` the devices, `verify` the config result
03DSH integration and capability boundaries
DSH plugin — used in-session as model tools (17 `ensp_*` tools) over the same core as the CLI and the MCP server, installed with `dsh plugin --profile desktop add dsh-ensp`
Topology generation
a built-in scenario blueprint, or devices and links you assemble with `buildTopology`→a `.topo` file eNSP opens and renders correctly, with interface groups matching the model
writes the `.topo` file to the path you hand to `writeTopology`Device start and stop
a `.topo` file→toolbar anchors located automatically, each device confirmed ready, then the window minimized
the eNSP window stays minimized while starting and pushing config, so it does not steal the foreground`ensp show` only restores and raises the window; topology and device state are left untouched`ensp stop` closes every deviceCommand-by-command config push
one script per device (console port + command text)→`{ ok, failedAt }` with line, command and raw device output; "already exists" answers are recorded as skipped, any other error aborts the run
reconfigures the devices running in eNSPProtocol convergence waits
console port plus a neighbour id, a prefix, or a command with a regex→`{ ok, converged, output, attempts, waitedMs }` from polling instead of a fixed sleep
50 scenario presets
a scenario name, or a keyword via `--search`→the objects to create, the config order and the check commands; `--topo` writes the blueprint topology and `--config` emits per-device address configs
Verification and Word lab report
a scenario name plus `--topology <file>`→a pass / fail verdict judged from output content (about 48 scenarios carry targeted assertions), and a six-chapter `.docx` report
runs the scenario's check commands against the devicesruns `display current-configuration` on every device when building the report
04Who is it for? When not to use it?
Good for
- Network engineers, trainers and students running Huawei eNSP on Windows who want the lab driven from a DSH conversation instead of manual clicking
- Instructors and learners who must hand in lab reports, and anyone who needs evidence of what the devices were actually configured with
- People on freshly set up or just-upgraded Windows machines, and anyone working from a service, scheduled task or SSH session where input injection is unavailable
Not for
- Windows only. eNSP ships a Windows build only, so the plugin declares `win32` — there is no macOS or Linux path.
- The tool must run as administrator and eNSP must sit at the same privilege level: Windows UIPI drops input messages from a lower-integrity process, so `SendInput` returns success while the click does nothing.
- The plugin cannot raise the eNSP window — only the process holding foreground rights may switch the foreground window — so eNSP must be brought to the front and kept on top before a run; otherwise a covering window receives the synthetic clicks and the tool stops before clicking.
- Compatibility is pinned to DSH 0.2.0 up to but not including 0.3.0, decided by `engines.dsh`.
- Services, scheduled tasks and SSH sessions cannot inject input at all, and elevation does not change that; `ensp doctor`'s `input-injection` item decides whether the current session can drive eNSP.
05Compatibility, maintenance and safety notes
- Windows only. eNSP ships a Windows build only, so the plugin declares `win32` — there is no macOS or Linux path.
- The tool must run as administrator and eNSP must sit at the same privilege level: Windows UIPI drops input messages from a lower-integrity process, so `SendInput` returns success while the click does nothing.
- The plugin cannot raise the eNSP window — only the process holding foreground rights may switch the foreground window — so eNSP must be brought to the front and kept on top before a run; otherwise a covering window receives the synthetic clicks and the tool stops before clicking.
- Compatibility is pinned to DSH 0.2.0 up to but not including 0.3.0, decided by `engines.dsh`.
- Services, scheduled tasks and SSH sessions cannot inject input at all, and elevation does not change that; `ensp doctor`'s `input-injection` item decides whether the current session can drive eNSP.
- The project is an automation shell: no eNSP, no Huawei software and no device images are bundled, images are never downloaded automatically, and you are responsible for installing eNSP and honouring Huawei's licence.
- eNSP allows only one instance; a crashed run can leave a zombie process holding the single-instance lock, which makes the next start show a blank window — the tool detects and cleans up such a process before launching.
GPL-3.0 · latest release v0.8.0 (2026-11-14T09:40:23Z)
06Frequently asked questions
How do I install dsh-ensp into DeepSeek Harness?
Search `dsh-ensp` in the plugin marketplace and install it, or run `dsh plugin --profile desktop add dsh-ensp`. The README also documents a standalone CLI (`npm install -g dsh-ensp`) and an MCP server (`npx -y dsh-ensp mcp`); all three share the same core.
Which DSH version does it support?
DSH 0.2.0 up to but not including 0.3.0 — compatibility is decided by `engines.dsh`. Node.js 18 or newer is required as well.
Do I need administrator rights when driving it from DeepSeek Harness?
Yes. The README requires the tool to run as administrator with eNSP at the same privilege level: Windows UIPI discards input messages from a lower-integrity process, so a normal-privilege `SendInput` returns success but the input queue does not change and the click is a no-op. Services, scheduled tasks and SSH sessions cannot inject input even when elevated — the `input-injection` item of `ensp doctor` says whether the current session qualifies.
What do the 17 DSH tools cover?
The README lists `ensp_status`, `ensp_build_topology`, `ensp_open`, `ensp_start`, `ensp_stop`, `ensp_apply`, `ensp_apply_dir`, `ensp_query`, `ensp_probe`, `ensp_show`, `ensp_images`, `ensp_doctor`, `ensp_verify`, `ensp_report`, `ensp_scenarios`, `ensp_scenario` and `ensp_preset_config`, and the recommended order for a whole lab is `doctor`, `up`, `verify`.
Does it ship eNSP or the device images?
No. The README calls the project an automation shell that contains neither eNSP nor any Huawei software or image; you install eNSP yourself and follow Huawei's licence. Images are never downloaded automatically — `ensp images` only reports where each model expects its image and can install a file you already have.
07Related DSH workflows
dsh-agent-teams
by nanmicoder
AgentTeams 多智能体团队协作插件:自然语言驱动建团队、拉成员、拆任务声明依赖、成员间消息直达,Web 右上角活动面板
dsh-blender-plugin
by sixtysevenlf
Adds tools for Blender scene editing, viewport capture, render profiling, headless work, and verification.
dsh-free-search
by dddmuc
DSH 免费搜索插件,执行联网检索。
dsh-bili-scroll
by c1overzz
Schedules Bilibili discovery, reads subtitles, writes daily reports, and optionally posts a comment tagging you.
08Data and sources
- DeepSeek Harness 插件:以模型工具的形式在会话内使用
提供 17 个工具:`ensp_status`、`ensp_build_topology`、`ensp_open`、`ensp_start`、`ensp_stop`、`ensp_apply`、`ensp_apply_dir`、`ensp_q…
dsh plugin --profile desktop add dsh-ensp
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-15. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
