Adds /D and /G slash commands to DSH Web: discuss and write a plan first, then start a fresh implementation session from that plan.
Install
# from npm (prebuilt)
dsh plugin --profile web add dsh-workflow-shortcuts
# from a prebuilt release tarball
dsh plugin --profile web add "https://github.com/person-clouds/dsh-workflow-shortcuts/releases/latest/download/dsh-workflow-shortcuts.tgz"
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:person-clouds/dsh-workflow-shortcuts
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
Slash commands for DSH Web that support a "discuss first, write a plan, then implement in a fresh session" workflow.
/D [task]: enter discussion mode in the current session without modifying files; after the requirements settle, write the agreed solution to aPLAN-*.mddocument./G <plan path>: create a new implementation session from that plan document and send it the plan path plus implementation requirements.
The goal is to separate requirement discussion from code implementation so the implementation session does not carry the whole discussion history, reducing long-context usage.
Commands
| Command | Description |
|---|---|
/D [task] |
Enter discussion mode in the current session. No files are modified; after discussion converges, write the solution to PLAN-*.md. |
/G <plan path> |
Create a new session in the current workspace titled 实施:<plan file name>, then send it the plan path to start implementation. |
The plan path for /G may be absolute or relative to the current session working directory.
Installation
Install from npm:
dsh plugin --profile web add dsh-workflow-shortcuts
Or install the prebuilt tarball from GitHub Releases:
dsh plugin --profile web add https://github.com/person-clouds/dsh-workflow-shortcuts/releases/latest/download/dsh-workflow-shortcuts.tgz
For local development, install from a linked source directory:
dsh plugin --profile web add link:/path/to/dsh-workflow-shortcuts
Restart dsh-web.service and refresh the page. This plugin contains client-side code only, so a page refresh is usually enough.
If the current AI sandbox has read-only access to ~/.dsh, run the installer on the host:
bash task/dsh-workflow-shortcuts/scripts/apply-profile.sh web
The script creates a local symlink, registers the package.json dependency, backs up and updates cordis.patch.yml, and restarts dsh-web.service when present.
Usage
- Type
/Din the current session, choose "discuss", enter a task description, and press Enter. - The agent enters discussion mode. Once requirements converge, it writes a plan document and returns its absolute path.
- Start a new session or type
/G <plan path>. The plugin creates a new session, renames it, and sends the implementation prompt.
/G uses the current session working directory as the new session workspace and registers that workspace automatically when needed.
Security boundaries
- Registers only a client-side
/input source. It adds no public port and no host API. /Donly sends a discussion prompt; it does not modify files directly. Writing the plan document is performed by the agent following the prompt./Gparses the path but does not verify that the file exists; a missing path is reported by the implementation agent in the new session.- It does not read credentials, access network resources, or inject HTML.
Limitations
/Dand/Gwork only in the DSH Web client. Terminal/API sessions still use normal prompts or host commands./Greuses the current session workspace and registers it automatically when needed.- The plugin depends on the DSH client services
inputTriggers,sessions,workspaces, anduiWorkspace; DSH upgrades that change these interfaces require an adapter update.
Development and tests
npm test
node -e "new (require('vm').Script)(require('fs').readFileSync('client.js','utf8'))"
npm pack --dry-run
Tests use Node's built-in node:test and vm; they require neither a browser nor external services.
Publishing
See PUBLISHING.md. The marketplace entry draft is at market/person-clouds__dsh-workflow-shortcuts.yml.
License
Links
More in this category
loopx-project/loopx#dsh-loopx-plugin★ 6694
LoopX, a provider-neutral, local-first state kernel and control plane for long-horizon agents: keeps Goal, Todo, gate, evidence, quota, recovery, and handoff state above DeepSeek Harness, while the plugin bootstraps the CLI and skills, admits bounded same-session continuation, and adds a loopback GoalBar for the exact bound loop.
Q00/ouroboros#integrations/dsh-plugin★ 6373
Config-only bundle that mounts Ouroboros through the DSH MCP client, exposing 36 interview, Seed, execution, evaluation, and evolution workflow tools in DSH.
chuspeeism/dashi-taskboard#deepseek-harness★ 3495
Embeds the active installed Codex Taskboard runtime in the DeepSeek Harness sidebar, using its launcher runtime descriptor instead of a fixed port.
NanmiCoder/dsh-agent-teams★ 2978
AgentTeams multi-agent teams.
EthanYoQ/AI-Novel-Writer#dsh-ai-novel-writer★ 2670
Installs a dedicated AI novel-writing preset and workbench: revisioned local project assets, a compact side drawer, and native approval-gated single-file changes.
shanliuling/dsh-image-gen★ 1576
Native conversational image generation for DeepSeek Harness: ask the agent to create an image, and it handles generation and keeps the result directly in the conversation.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.