dsh-creator-mode-plus

中文

Plugin-only boundary: official DSH source and artifacts are read-only, including copies and worktrees. Use public extension points; missing APIs never authorize a Host patch. Takeover, approval and --force cannot override CORE_SOURCE_IMMUTABLE.

Pick Creator Mode+ in a normal DeepSeek Harness Web session. Ten fixed tools scaffold, check, mount, and uninstall a file-backed plugin in a safe order.

This source is paired with Harness dsh-v0.2.0-rc.2 (SHA 639ed015397290b3745d163aafe02ffee4aa3f84). The plugin peer range is >=0.2.0-rc.1 <0.2.1. It accepts 0.2.0-rc.2 and stable 0.2.0, rejects 0.2.0 alphas, and rejects 0.1.7-rc.2. The bridge compatibility range stays DSHX >=0.9.1 <0.10.0; 0.9.2 fits, and 0.9.0 and 0.7.9 are rejected. The desk pin, peer range, and human-confirmed takeover capability are checked before use. Session recovery listens on agent/created. The ten fixed tools are unchanged.

Use it in a conversation

Select a workspace and Creator Mode+, then state the feature and delivery target:

Create a page counter plugin and install it in this DSH. Then add a server tool to it.

The Agent creates source, builds, checks, selects activation and continues. Server changes use same-process hot reload; a new client entry needs a page refresh. Correct build failures before retrying. A missing browser adapter blocks its UI check only. An explicit installation request carries through these steps.

Install

DSH Studio desktop app (recommended)

Open Settings → Plugins → Add plugin and enter this in “Package name or address”:

github:aa2246740/dsh-creator-mode-plus#v0.3.10

The desktop plugin manager owns the Desktop profile and bundled package manager. This release includes built artifacts; normal use needs no clone, build, or DSHX installation. Follow the app if it asks you to reload or reopen after installation. Then choose Creator Mode+ in a new session.

Web CLI

dsh plugin --profile web add github:aa2246740/dsh-creator-mode-plus#v0.3.10

This official CLI command writes only the web profile; it cannot modify the Desktop App profile. For an already-running Web Host, reopen that Host once and reload the page.

Creator Mode+ uses DSHX inside a conversation to develop, check, and activate the user's own plugins. That capability is not a prerequisite to install Creator Mode+, and it never permits modifying official DSH source.

Source-development install

Only when editing this repository, use a local link and installer in a separate Harness checkout:

cd /path/to/deepseek-harness
git clone https://github.com/aa2246740/dsh-creator-mode-plus.git tools/dsh-creator-mode-plus
pnpm dsh plugin --profile web add link:./tools/dsh-creator-mode-plus
node tools/dsh-creator-mode-plus/scripts/install.mjs --harness "$PWD"

The installer derives a user preset from the shipped Standard patch, writes profiles/web/creator-mode-plus/agent.cordis.yml, and includes that file from the Web profile cordis.patch.yml. It leaves the shipped Standard and Creator presets alone and does not write .agent-presets. Open the official WebUI, confirm Creator Mode+ is in the mode list, and try it in a new session. Adding a profile dependency is not by itself a reason to restart the Host.

Contracts: Bridge v2 and DSHX v0.7 alignment.

The ten tools

Whole-plugin removal goes through dshx_remove_plugin only. Running the installer again on an existing install does not overwrite.

Harness inventory is read-only through update plan. DSHX disables prepare, verify, apply and rollback for every caller, including the external supervisor.

Source-development upgrade

cd /path/to/deepseek-harness/tools/dsh-creator-mode-plus
git pull --ff-only
node scripts/install.mjs --harness /path/to/deepseek-harness --upgrade
npm run verify:dshx -- --harness /path/to/deepseek-harness

Develop

npm test
npm run check
DSHX_HARNESS=/absolute/path/to/deepseek-harness npm run test:native
npm run verify:dshx -- --harness /absolute/path/to/deepseek-harness
npm run verify:harness-install -- --harness /absolute/path/to/deepseek-harness

License

MIT.

dshx_request_takeover({name}) asks through the current conversation’s user-question UI, then drains old work and atomically transfers ownership. This requires the human-confirmed-creator-takeover capability in addition to the version range.