Bridges the LiuHe MCP code toolkit (44 tools) into dsh web: repo_map, symbol search, edit_batch with tolerant matching, transactional edits with undo journal, and deterministic quality gates — backed by a crash-isolated Rust tree-sitter parse daemon and SQLite index.
Install
# from npm (prebuilt)
dsh plugin --profile web add @jieai/dsh-malong-bridge
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:wulun811/LiuHe#path:/malong/dsh/bundle
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
Official DSH (DeepSeek Harness) plugin for LiuHe / malong. One command puts the
Six-He line (13 malong__* MCP tools) into dsh web, and malong's workspace
automatically follows the current conversation's workspace — no need to pass a path
manually.
(Since 0.5.22 the bridge defaults to graph + state layer = 13 tools — the recommended
daily entry. The classic full catalog (44) and the diagnostic tier (18) are still one
env away: export MALONG_INTERFACE=classic|diagnostic on the dsh host.)
0.6.2 upgrade notes: lifecycle cleanup now uses cordis 4
ctx.effect(no orphanmcp-server.jsafter disable/uninstall);better-sqlite3is optional with a^11.10.0floor; the 512 MB heap and GC behavior are documented under Memory and lifecycle.0.6.3 additive switches:
MALONG_NO_GIT_EXCLUDE=1keeps real git worktrees byte-identical (no.git/info/exclude, journals/transactions under$MALONG_STATE_DIR/workspace-artifacts/);MALONG_READONLY=1rejects workspace/git/command writes withreadonly_mode. Both are off by default; seeRESPONSE-CONTRACT.md§2.5 for the exact allow/deny list.
dsh plugin --profile web add @jieai/dsh-malong-bridge
pkill -f "dsh web"
dsh web --port 3456 --host 127.0.0.1
--host must be one concrete local address. dsh rejects wildcard addresses
(0.0.0.0, ::); the default is loopback. For remote access, bind an explicit
interface and put authentication/firewall in front yourself: this UI grants
file read/write and shell execution to anyone who can reach the port, and the
token in the printed URL is not a substitute for network controls.
better-sqlite3 is optional since 0.6.2 and is declared as
^11.10.0(the first 11.x release verified on Node 24). If pnpm skips its build script (Ignored build scripts: better-sqlite3) or the native build fails, installation still succeeds and the server automatically falls back to the vendored sql.js WASM backend (server/vendor/, zero native deps). The startup log shows which backend is active; both use SQLite with compatible data files. The native backend is faster on large indexes, but the fallback is functional. To opt into the native backend:pnpm approve-builds # check better-sqlite3 # or add better-sqlite3 under onlyBuiltDependencies in the profile's # pnpm-workspace.yaml, then: pnpm rebuild better-sqlite3
Uninstall
dsh plugin --profile web remove @jieai/dsh-malong-bridge
pkill -f "dsh web"
dsh web --port 3456 --host 127.0.0.1
Configuration (optional, zero-config by default)
| Env var | Default | Description |
|---|---|---|
MALONG_SERVER_PATH |
bundled server/mcp-server.js |
Override the mcp-server entry (e.g. point at your own LiuHe dev copy) |
MALONG_STATE_DIR |
~/.local/state/malong-dsh |
Index/state storage dir (all workspaces isolated under it by hash) |
MALONG_TOOL_TIMEOUT_MS |
300000 |
Per tool call timeout |
You can also write a config: override on the malong-dsh-bridge entry in the
profile's cordis.patch.yml (user layer, applied later).
How It Works
DSH Agent → malong__read_symbol(...) (no workspace_dir)
→ dsh-bridge injects workspace_dir = current session workspace
→ malong mcp-server (spawned subprocess) → per-path-hash isolated indexes
- Dynamic workspace follow: every tool invocation carries the session
workspace (
exec.agent.session.header.cwd); the bridge injects it automatically; explicit paths from the model are respected (cross-workspace management). - State isolation: indexes are hash-isolated by workspace path under
MALONG_STATE_DIR, unrelated to any project directory. - Zero intrusion: does not touch dsh's node_modules; dsh upgrades are safe.
Memory and lifecycle
- The bridge starts
mcp-serverwith--max-old-space-size=512before the script path, so V8 actually enforces a 512 MB old-space cap. This is a heap cap, not an RSS cap; native buffers and the parser daemon are outside it. - If a very large workspace exhausts the heap, the child exits and the bridge rejects in-flight calls with a retryable error, then restarts with exponential backoff (1s → 30s). Indexes are on disk, so retry after the restart.
- Periodic GC is only enabled when the child is started with
--expose-gc. The bridge does not add it by default;periodic GC disabled, memory monitoring still onin the log is expected. The watchdog still reports memory warnings withoutglobal.gc. - On DSH fiber unload (disable, remove, hot reload), the bridge registers a
cordis
ctx.effectdisposer: it stops restart scheduling, rejects pending calls, sendsSIGTERM, and escalates toSIGKILLafter 2s. It never restarts after disposal. (0.6.1 used the cordis v3ctx.on("dispose")event, which cordis 4 no longer emits; if you still see orphanmcp-server.jsprocesses, you are running an older bundle.)
Platform / runtime support: verified on Linux x86-64 with Node 22.19+ (the bundle's
enginesfloor; DSH 0.2.2 itself requires a newer Node). Windows and macOS are not verified for this release — see Parser setup below before assuming they work.
Parser setup (malong-parse)
This tarball contains the bridge and the MCP server, not the Rust parser.
npm install alone does not give you working parsing. Two separate things must
hold:
- The binary must exist. Resolution order (
parse-bin.js):MALONG_PARSE_BIN→MALONG_PARSE_BIN_ALT→ an installed@jieai/malong-parse-<platform>-<arch>package (none is published yet) →server/bin/malong-parse(legacy layout, absent here) →~/.local/bin/malong-parse→ a sibling../malong-parse/target/{release,debug}dev build. The last entry is why a dev checkout works without any env var — do not rely on that for an installed setup. - A daemon must be reachable. The MCP server connects to a shared Unix
socket at
/tmp/malong-parse-<uid>.sock(MALONG_SOCKEToverrides it) and spawns a daemon if none is running. The daemon is per-user, shared by all sessions — which is why an unrelated running daemon can make a wrongMALONG_PARSE_BINlook like it works (you get aDRIFTwarning inhealthinstead of a failure).
Recommended install:
# Linux x86-64 asset shipped alongside this release
install -Dm755 malong-parse-linux-x64-0.3.39 ~/.local/bin/malong-parse
malong-parse --version # confirm it runs at all
Then, in the dsh host environment:
export MALONG_PARSE_BIN="$HOME/.local/bin/malong-parse" # optional but explicit
Verify it, don't assume it. invoke_capability(name='health') reports a
Parse Service line; check three things: connected=true, the daemon's
size/exe matches the binary you installed, and drift.detected is false.
When it is genuinely missing, parse-dependent calls fail with an explicit message naming every searched location:
malong-parse binary not found. Searched: <candidates...>.
Set MALONG_PARSE_BIN (Windows: point at the .exe) or install it (~/.local/bin/malong-parse).
Degradation is partial, and it is not a clean fallback. Indexing,
outline/symbols and symbol search need the parser. code_read, code_status
and plain text editing keep working off the static index and the filesystem, so
a missing parser shows up as empty or absent symbol results rather than as a
hard stop. Treat "tools respond" as not evidence that parsing works —
check health.
glibc: the shipped Linux binary is dynamically linked against GLIBC_2.34 (highest versioned symbol). Older distros (e.g. CentOS 7, Ubuntu 20.04) will fail at load time with
GLIBC_2.34 not found; build from source there or use a newer base image. It is not "any Linux x64".
On Windows, replacing an existing source file uses the inbox Windows PowerShell
and .NET File.Replace with a hidden process to preserve the target's ACL.
Edits, undo and rollback use this path; new files inherit their directory's
permissions. If Windows PowerShell is blocked or replacement is denied, the
write fails explicitly instead of falling back to a rename that resets the ACL.
This adds Windows-only process startup overhead to existing-file writes.
Differences vs. the official dsh-mcp-client
The official dsh-mcp-client bridges a single MCP server; this plugin's bridge
adds dynamic workspace injection (fills workspace_dir per invocation from
the session workspace, so the model never needs to know the path) — a
capability unique to LiuHe.
Troubleshooting
| Symptom | Fix |
|---|---|
Log shows mcp tools/list timeout |
Verify the install is complete (dsh plugin reports no node_modules errors); restart dsh |
No malong__* tools in the conversation |
Confirm the bundle layer is attached (dsh web --dump-config | grep malong); hard-refresh the browser |
Call fails with missing_parameter: workspace_dir |
The conversation has no workspace (no cwd) to inject; pass a path in the prompt |
malong-parse binary not found. Searched: ... |
Install the parser (see Parser setup) or set MALONG_PARSE_BIN |
Tools respond but outline/symbol search is empty |
Parser unreachable or wrong binary. Check health → Parse Service (connected, size/exe, drift.detected). Tools responding is not proof parsing works |
health shows DRIFT: daemon binary ... differs |
A stale per-user daemon is running an older build. Stop it (pkill -x malong-parse) and let the next call respawn from the resolved binary |
FILE_NOT_INDEXED after a crash |
Run invoke_capability(name='reindex', args={workspace_dir, blocking:true}). reindex is asynchronous by default |
| Plugin stops working after a dsh upgrade | The plugin lives at the profile layer, upgrades do not affect it; if the cordis interface changes, reinstall the plugin |
Index Rules (Transparency)
- Default ignored:
node_modules,.git,dist,build,target,coverage,__pycache__,.venv,.malong,.ai-transactions,vendor, etc. - md/json not indexed: only code files are indexed; use a read tool for documents
.malongignorecustomization: a.malongignorefile at the project root excludes directories allowlist-style (one per line;*wildcards supported; max 100 entries)
License
MIT
Links
More in this category
Tencent/WeKnora#dsh-weknora★ 37546
Four read-only tools over a WeKnora knowledge base: list knowledge bases, hybrid passage search, reassemble one document's chunks in order, and WeKnora's own cited RAG or ReAct-agent answer with a resumable session id.
DayuanJiang/next-ai-draw-io#dsh-plugin★ 36997
Draws draw.io diagrams in DeepSeek Harness through the next-ai-drawio MCP server: the link in the reply opens a live preview in the right sidebar, you can edit the diagram by hand, and each AI change is a version you can restore. Node.js 18+; npx downloads the MCP server on first use.
superdesigndev/treg★ 8164
Tool catalog for agents: search ~2,600 external endpoints (SEO and SERP, backlinks, social, people and company enrichment, ad libraries, scraping) by the task you want done, read each one's parameters and per-call price, then call it with the credential injected server-side. Ships the skill plus an MCP row that stays disabled until TREG_TOKEN is set.
T-Auto/dsh-ops★ 5864
Provides bash, PowerShell 7, and high-performance Rust tools for DSH on Windows to reduce token usage.
sixtysevenlf/dsh-blender-plugin★ 2147
Lets a DSH agent drive a local Blender over a direct TCP channel with 15 tools: viewport frames, custom-angle renders, Python execution, headless and job offload, transaction rollback, and a planning layer of 228 ops across 34 families.
helloHub1212/dsh-windows-mcp★ 1456
Bridges the CursorTouch/Windows-MCP desktop automation server into DSH through the official MCP client bridge, registering its screenshot, UI tree snapshot, mouse and keyboard input, clipboard, process and registry tools as mcp__windows__* tools for the model, and adds a windows_mcp_doctor diagnostic tool. Computer Use is off by default and is switched on from the plugin panel.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.