dsh-enhanced-plugins

English | 中文

dsh-enhanced-plugins is an all-in-one enhancement bundle for the DeepSeek Harness (DSH) Web profile. One installation adds native desktop alerts and a DeepSeek pet, a plugin community, MCP server management, model request-type declarations, workspace file references, last-message editing, and Claude Code / Codex subagent switches.

The package uses only public DSH plugin extension points and does not modify DSH core. Each of the seven features owns its applicable Host, Client, Settings, and runtime lifecycle, so an unavailable optional dependency does not prevent unrelated features from loading.

Features at a glance

Requirements

• Node.js 22.19 or newer.
• A DSH Web profile. This repository is currently verified against the DSH 0.1.0-rc.5 public ABI, using local baseline commit 47f943859bef60e4160492346772ded9b24f765a.
• Windows 10 or newer with Windows PowerShell 5.1 for the native sound and desktop-pet feature. The other bundle features remain portable.
• Official DSH packages are supplied by Harness; this plugin neither copies nor patches DSH core.

DSH is still a developer preview. After upgrading DSH, check this project's supported ABI before upgrading the plugin if compatibility errors appear.

Installation

The installer handles dependency installation, package build, web profile installation, and load verification. Run the following commands from the dsh-enhanced-plugins repository root.

Plugin and DSH source under the same parent directory

Use this directory layout:

<workspace>/
├── deepseek-harness/
└── dsh-enhanced-plugins/

The installer discovers the sibling deepseek-harness checkout automatically:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1

Plugin and DSH source in different directories

Pass the DSH source checkout explicitly with -DshCheckout:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1 -DshCheckout "E:\projects\deepseek-harness"

Restart DSH once after installation if it is already running.

Usage

The screenshots below use the Simplified Chinese locale; DSH translates labels according to the selected application language.

Desktop alerts & pet

Location: Settings → Desktop pet. This is an independent entry in the left Settings navigation, not a card under Plugins.

1. Choose Off, either built-in default sound, or Custom WAV independently for task-completion and confirmation sounds. Uploading a WAV selects it immediately; files are limited to 2 MiB and stored inside the current DSH profile.
2. Turn on Enable desktop pet to show the DeepSeek fish in a native always-on-top window outside the browser.
3. Choose its size and starting corner. You can drag the pet anywhere after it appears.

The pet has three live states across all sessions: Idle gently floats and breathes, Working swims with bubbles and a rotating activity ring, and Needs attention hops, shakes, pulses, and displays an alert badge while an approval, plan review, or ask_user_question answer is pending. Needs-attention state has priority when other sessions are still running. Completion sounds fire only for top-level tasks, so completed subagents do not create duplicate chimes.

Settings apply live. Pet motion uses native WPF animations so the window remains responsive; hovering keeps the arrow cursor and dragging temporarily uses the move cursor. Turning the pet off closes and joins its managed PowerShell/WPF process; with the pet disabled, sound notifications use a short-lived process and leave no resident helper. The child receives only a fixed script path plus JSON control messages over stdin, and DSH's subprocess service owns tree cleanup.

Plugin Community

Location: Settings → Plugin Community.

1. The first visit reads the bundled catalog snapshot. Select Sync channel when you want fresh community data.
2. Search by repository, package name, description, or topic.
3. Open the GitHub repository and verify its source before selecting Install.
4. Use the Installed tab to inspect or remove plugins installed through this page.
5. Restart the current Web profile after an install or removal, as prompted by the page.

The bundled snapshot works without a GitHub token. If synchronization hits GitHub API limits, open Configure and store a read-only, short-lived fine-grained token. It is sent only to the local DSH Host and kept by the credentials service.

MCP server manager

Location: Settings → Plugins → Plugin configuration → MCP servers.

1. Select Add server, enter a unique name, and choose a transport.
2. For stdio, provide the command, arguments, working directory, and environment variables. For Streamable HTTP, provide an HTTP(S) URL and request headers.
3. Alternatively, select Import Claude Code and Codex. The Host reads supported local configuration, skips duplicate names or definitions, and explains entries that cannot be converted safely.
4. Review the format audit at the top of the card, then select Save. The Host starts, updates, or disposes each server connection independently after a successful commit.

When the browser reads an existing server, environment-variable and header values are masked. Unchanged secrets are not reconstructed or overwritten from the redacted view.

pi-ai model request types

Location: Settings → Plugins → Plugin configuration → pi-ai model request types.

1. Add pi-ai model overrides on DSH's Models page or in settings.yaml first.
2. Expand the pi-ai model request types card.
3. For each model, select Provider default, Text only, or Text and images. The choice is saved immediately.

The card appears only while the official llm-pi-ai settings namespace is available. These are capability declarations, not endpoint probes. Confirm that the provider really accepts image requests before declaring Text and images.

Workspace file references

Location: the session composer after selecting a workspace.

1. Type #, then continue with part of a file name or path to narrow the results.
2. Use ↑ / ↓ and Enter, or click a result, to insert the reference.
3. Finish the prompt and send it. At submission, the Host resolves the path again, checks workspace containment, and adds a UTF-8 text snapshot to that model request.

Defaults allow up to 8 files, 128 KiB per file, and 512 KiB total. Binary, invalid UTF-8, oversized, non-regular, and outside-workspace files are rejected.

Edit last message

Location: beside Copy on the latest editable user-message bubble.

1. Wait for the current session to finish, or stop it manually.
2. Select Edit last message and revise the text inline.
3. Select Resend or press Ctrl/⌘ + Enter. Press Esc or select Cancel to leave edit mode.

Resending stays in the current session. The plugin replaces the active model context from the edited user message onward and regenerates through the same AgentLoop. The underlying DSH Session log remains append-only audit history, and external side effects from tools that already ran are not rolled back. Messages containing images or other non-text blocks do not expose Edit, preventing silent content loss.

Product subagents

Location: Settings → Subagents.

1. Turn on Claude Code or Codex.
2. The change applies immediately to Agent presets that load this controller, including running sessions; the profile does not need a restart.
3. Turning a product off removes its tool live. The corresponding local product and official DSH provider must still be available.

Both switches default to off. Each update writes only its Boolean path under settings revision fencing, avoiding accidental overwrite of newer edits from another page or external writer.

Advanced configuration

The default composition is in cordis.patch.yml. A later profile patch replaces an entire Loader row's config; when overriding one, repeat every field that must be preserved.

To expose product-subagent tools only to selected Agent presets, disable or remove the root subagent-product-toggle-tools row and mount dsh-enhanced-plugins/sub-agent/preset only inside those preset compositions. Do not mount both layouts in the same scope.

Development and verification

Repository rules use this read-only sibling checkout as the DSH API, type, and real Web assembly baseline:

D:\work\workspace\github\deepseek-harness

Run the standard checks with the package manager selected by the repository lockfile:

npm install
npm run typecheck
npm test
npm run build
npm pack --dry-run
git diff --check

The browser bundle uses CSS Modules and only DSH --dsw-alias-* semantic theme tokens, so it follows light, dark, and system appearance automatically.

License

MIT