magian1127/deepseek-harness-zhipu_plan_tools

Zhipu MCP suite · DeepSeek Harness plugin

中文 · English

Brings three Zhipu GLM Coding Plan MCP services into DSH as native providers and tools: it replaces the built-in web_search and web_fetch backends, and optionally adds three github_* repository tools. A bilingual settings card applies changes live.

Features and settings order

Open the Zhipu Tools configuration form on the sidebar → Plugins → deepseek-harness-zhipu_plan_tools page (DSH 0.1.6+). The rows below follow the form from top to bottom:

Setting	Plugin default	Summary
Enable Zhipu tools	on	Master switch; off enters search/reader compatibility fallbacks and unregisters repo tools and related guidance while keeping the card
Web search (takes over web_search)	on	Routes search through Zhipu web_search_prime and replaces the model-visible built-in search guidance
Web reader (takes over web_fetch)	on	Routes reads through Zhipu webReader; since DSH v0.1.2 the Web agent presets ship web_fetch by default, so it takes effect right after install
Repository tools	off	Adds github_search_doc, github_get_repo_structure, and github_read_file
Chinese prompts	off	Switches plugin-injected guidance, tool descriptions and github_* error messages from the default English to Chinese; tool names stay unchanged
Credential reference	ZAI_CODING_CN_API_KEY	Stores only the credential reference name, never the API key

The card starts collapsed and ends with Restore defaults / Discard changes / Save. Search and reader are provider swaps, so model-facing web tool names stay unchanged; repository tools are registered natively and disappear from the model catalog when disabled. The web_search shadow is never registered under the minimal preset (the "persistent shell + str_replace_editor" two-tool composition), preserving that preset's promise. See the behavior contract for query guidance, data boundaries, and errors.

Requirements

• DeepSeek Harness ≥ 0.1.7-alpha.2; Web uses web, Open Design stdio uses open-design, and DSH one-shot tasks may use headless
• Node.js ^22.19.0 || >=24.0.0
• A Zhipu GLM Coding Plan API key referenced by ZAI_CODING_CN_API_KEY by default

Install

Published package:

# Web GUI
dsh plugin --profile web add deepseek-harness-zhipu_plan_tools

# Open Design's actual stdio profile
dsh plugin --profile open-design add deepseek-harness-zhipu_plan_tools

# Optional: DSH's built-in headless profile
dsh plugin --profile headless add deepseek-harness-zhipu_plan_tools

# Hot-install only into a running Web GUI
npx -y deepseek-harness-zhipu_plan_tools install --profile web

Bundles are profile-scoped. Open Design actually runs dsh --profile open-design --stdio, not headless; both non-Web profiles load on their next short-lived process. Because open-design reserves stdout for strict JSONL, this plugin routes informational startup logs to stderr there.

DSH Desktop (the Electron app): supported (desktop Host port 19387); the desktop profile (~/.dsh/profiles/desktop) is owned exclusively by the app, and both the dsh plugin CLI and this plugin's CLI reject --profile desktop by name. For a link dev install (while the app is not running), edit ~/.dsh/profiles/desktop/package.json:

"dependencies": { "deepseek-harness-zhipu_plan_tools": "link:<absolute path to this repo>" },
"dsh": { "profile": { "bundles": [ /* keep official bundles, append */ "deepseek-harness-zhipu_plan_tools" ] } }

then pnpm install inside the profile directory; start the app to mount, npm run build + restart after source changes, remove both entries + pnpm install to uninstall. Search/reader credentials live under $DSH_HOME and are shared between Web and Desktop.

Local source development:

npm install
node bin/dsh-zhipu.mjs install --profile web --link <project-path>
dsh plugin --profile open-design add "link:<project-path>"
dsh plugin --profile headless add "link:<project-path>"

The patch includes web.config; bridge/temporary rows are only for Web hot installation. Use the official persistent channel elsewhere and verify independently:

npx -y deepseek-harness-zhipu_plan_tools status --profile web
dsh plugin --profile open-design list
dsh --profile open-design --dump-default-config
dsh plugin --profile headless list

First use: add zai-coding-cn

Before calling the tools:

1. Open DSH Settings → Models.
2. Add the China-region provider zai-coding-cn, not the overseas zai.
3. Ensure ZAI_CODING_CN_API_KEY exists in the environment or ${DSH_HOME:-~/.dsh}/.credentials.yaml.

The provider and this plugin then use the same credential reference. If your key uses a different environment-variable name, set that name as credentialRef in the plugin card. Resolution order and security guarantees are defined in Credentials and data boundaries.

Open Design and stock headless have no settings page, but profiles under the same ${DSH_HOME:-~/.dsh} share settings.yaml and credentials. Configure Web once; open-design / headless read the same dsh-zhipu namespace.

web_fetch availability

Since DSH v0.1.2, the Web agent presets (standard / ptc / codex) include web_fetch in the model tool catalog by default. This plugin swaps only the backend provider and never touches that switch: once installed, web_fetch routes through the Zhipu webReader with no extra step.

Only older DSH builds (whose Web composition did not ship web_fetch) need the profile-patch enablement:

- id: tool-web
  config:
    fetch: true

Data boundary: with the reader on, fetching happens on Zhipu's cloud (the local process never connects to the target; the URL is submitted to the Zhipu MCP). With the reader off, it falls back to the local bounded HTTP(S) fetch. See the authoritative enablement boundary.

Settings and data

The six fields shown above are stored in that same order in the dsh-zhipu namespace of DSH settings.yaml and apply live; the API key itself is never stored there. Switching search/reader off enters compatibility fallbacks at runtime (the DSH DeepSeek request shape via DEEPSEEK_API_KEY; a bounded HTTP(S) text fetch), without restarting DSH. The HTTP fallback validates URLs, follows same-origin redirects only, and caps transfer and decoded output; its exact limits and residual DNS-rebinding boundary are documented in the behavior contract, together with credential lookup, failure codes, and telemetry boundaries.

Uninstall

dsh plugin --profile web remove deepseek-harness-zhipu_plan_tools
dsh plugin --profile open-design remove deepseek-harness-zhipu_plan_tools
dsh plugin --profile headless remove deepseek-harness-zhipu_plan_tools
# A running Web GUI can also use:
npx -y deepseek-harness-zhipu_plan_tools remove --profile web

Removal is profile-scoped; short-lived profiles stop loading it on the next invocation. Existing dsh-zhipu settings may remain.

Development

Use Development for repository structure, hot paths, invariants, and test strategy. Use Release for the complete pre-publish checklist. The common local checks are:

npm run typecheck
npm run build
npm test
npm run verify

Do not restart DSH merely for development. The client half hot-swaps in-page through dsh-client-hmr; the host half currently has no working partial-reload channel (its self-watch depends on the removed registerConfig/partialReload), so a rebuilt lib/ needs one process restart — refresh the page only as a fallback.

Documentation index

• Behavior contract — defaults, settings, credentials, boundaries, errors
• Architecture — runtime structure, module contracts, decisions, research, roadmap
• Development — repository layout, hot paths, invariants, tests
• Troubleshooting — symptom-driven diagnosis and runtime observation
• Release — validation, version notes, npm publishing

Roadmap

The technical roadmap is maintained in Architecture; release state belongs in Release.

License

MIT