1321928757/dsh-prompt-polish

dsh-prompt-polish

English | 中文

A composer-side prompt optimizer for DeepSeek Harness (DSH). Click Optimize to send the current draft through the model provider configured in DSH and review a clearer, more specific version before deciding whether to use it.

Data boundary: This plugin does not add a separate API endpoint. Optimization uses the provider and model selected by DSH. When context is enabled, the request may include recent messages, the current goal and todo list, a compaction summary, and optional tool-result summaries. The draft and enabled context are therefore visible to that model provider; review its privacy and retention policy before using the feature with sensitive conversations.

At a glance

Features

• Six prompt-rewriting modes: Default, Concise, Structured, Creative, Translate and optimize, and Code request.
• Three language choices: Follow draft, Chinese, or English. An explicit language choice is applied after optional custom preferences; in Translate and optimize mode, Follow draft means optimize without translating.
• Optional context injection from the current session: goal, todo list, compaction summary, recent messages, and—when both context switches are enabled—short tool-result summaries.
• A result popover with the original draft, optimized draft, Adopt optimized result, Keep draft, and Later actions. Results are never automatically adopted.
• Stop while a model stream is running; when the DSH conversation-block API is available, clear the composer block immediately and ignore late results from the cancelled run.
• Failure results stay visible with the original draft and a Retry action.
• A current-component, in-memory history of the last five optimization attempts. Successful entries can be reviewed or explicitly refilled into the composer; failed entries are retained as failure records.
• Settings are saved locally and best-effort synchronized to a workspace file.
• The browser UI uses DSH theme tokens and supports light/dark themes, keyboard focus, Escape/outside-click dismissal, reduced motion, and high-contrast borders. The composer controls stay quiet at rest: Optimize is transparent when idle and gains a host interactive surface only on hover, focus, or press, with lighter label text matching adjacent DSH controls.

Modes and language behavior

The Follow draft language choice preserves the draft language. Chinese and English lock the final requested language. Custom instructions are limited to 500 characters and can influence optional behavior, but the optimizer's prompt places them below the output contract, draft/context boundaries, and explicit language lock.

The optimizer instructs the model to output one user-facing request rather than an answer, plan, explanation, or code fence. This is a model instruction, not a deterministic output filter: review the generated text before adopting it.

Runtime behavior and limits

This plugin is a browser composer extension, not a standalone shell command or a model tool exposed to the agent. The browser calls the Host promptPolish service through Typert RPC; the Host then streams a request through DSH's configured LLM service.

Requirements and compatibility

• DeepSeek Harness with a compatible Web profile that provides the plugin's Host and browser dependencies.
• DSH 0.2.0-rc.2 or newer, below 0.3.0. Version 0.4.1 keeps the DSH 0.2 Typert migration and fixes the full settings modal surface; version 0.4.0 first migrated both Host and Client Typert strict codecs to the DSH 0.2 create() factory contract. It no longer supports DSH 0.1.x; use plugin 0.3.2 there.
• The package targets @deepseek-ai/cordis ~4.0.4, the DSH 0.2.0-rc.2 service packages listed in package.json, and React ^18.2.0; it directly depends on zod ^4.4.3. The package declares Node.js >=20.
• A configured DSH model provider is required for optimization. Provider availability, model limits, network access, and provider policy remain outside this package.

Install, update, or remove

Install the pinned GitHub release

The primary path installs the currently documented tag into the web profile:

dsh plugin --profile web add github:1321928757/dsh-prompt-polish#v0.4.1

Restart the existing DSH Web process after installation. Then verify the profile composition:

dsh --profile web --dump-config | findstr dsh-prompt-polish

After the restart, the Optimize button and gear should appear on the left side of the composer. If the button is missing, see Troubleshooting.

Update to a newer pinned tag

The repository's installer aligns an existing installation by running dsh plugin ... add again. You can use the same approach manually with the release tag you want:

dsh plugin --profile web add github:1321928757/dsh-prompt-polish#v0.4.1

Replace v0.4.1 with a newer published tag, then restart that profile's DSH Web process and repeat the --dump-config check.

Install from npm

Use this only after the package has been published and is available in your registry:

dsh plugin --profile web add dsh-prompt-polish

PowerShell installer

The repository contains a pinned installer:

irm https://raw.githubusercontent.com/1321928757/dsh-prompt-polish/v0.4.1/scripts/install.ps1 | iex

Review the script before executing a remote irm | iex command. It checks for dsh, ensures pnpm is available, pins pnpm 11.21.0, prefers Git when available, falls back to the GitHub tag archive when Git is unavailable, and installs the pinned release into the web profile by default. It may activate pnpm through Corepack or install it globally through npm. The script accepts -Profile <name> when run from a downloaded file; when using another profile, use that profile in your own restart, verification, and removal commands.

To inspect it before running:

$path = Join-Path $PWD install.ps1
Invoke-WebRequest https://raw.githubusercontent.com/1321928757/dsh-prompt-polish/v0.4.1/scripts/install.ps1 -OutFile $path
Get-Content $path
powershell -NoProfile -ExecutionPolicy Bypass -File $path -Profile web

Remove

dsh plugin --profile web remove dsh-prompt-polish

Restart the profile's DSH Web process after removal. The command removes the package from that profile; it does not delete localStorage or an existing workspace settings file.

Local development profile

Keep local development separate from the profile you use daily:

dsh plugin --profile demo add E:\path\to\dsh-prompt-polish
dsh --profile demo --dump-config

Quick start

1. Type a draft into the DSH composer.
2. Optionally open the gear and enable Reference conversation context. Enable Include tool results only if you also want the context request to include short tool summaries.
3. Choose a mode and language. In Translate and optimize, the language selector is the target language.
4. Open Full settings if you need a custom instruction of up to 500 characters, or want to inspect the context preview and recent attempt history.
5. Click Optimize. The composer is blocked while the request is running when the conversation block API is available; the button becomes Stop optimizing.
6. Inspect the original and generated prompt in the result popover.
7. Choose Adopt optimized result, Keep draft, or Later. The latter two only dismiss the result; they do not save a reminder. A changed draft cannot be overwritten by an older result.

The Retry action reuses the original snapshot from the failed attempt. The Refill action in history is an explicit write to the composer and is different from automatic adoption.

Screenshots

The screenshots use published GitHub Raw URLs so they render in GitHub, npm, and external marketplace views after the repository assets are pushed.

Composer entry

The Optimize button and gear are registered in the composer's conversation.input.left slot. In the current UI, the idle trigger is transparent and uses lighter label text; hovering or focusing it reveals the host interactive surface without adding a permanent highlight:

Review before adoption

The result popover shows the original draft and the generated prompt before any composer write occurs:

Quick and full settings

The gear opens quick settings for context, tool summaries, mode, and language. The full dialog adds custom instructions, context statistics, current-component history, and persistence information:

The repository also keeps the three paths in screenshots.json. package.json.files includes both screenshots.json and assets so the metadata and images are present in packed releases.

Settings persistence and history

The plugin has three user-facing settings surfaces, but only two actual storage locations:

1. L1 browser storage: normalized settings are written to localStorage under ptopt.settings.v1 and take effect immediately. If browser storage is unavailable, the current page keeps the settings in memory.
2. L2 Settings surface: DSH Settings → General exposes a linked checkbox for Reference conversation context. This is a UI surface, not a separate database or settings backend; mode, language, tool-result behavior, and custom instructions remain in the composer panel/full dialog.
3. L3 workspace synchronization: settings are shallow-merged into <workspace>/.dsh/prompt-optimizer/settings.json through the Host file service. The write is subject to the DSH sandbox policy. A missing or malformed file is treated as empty settings, and a denied or failed write silently falls back to browser storage.

When a workspace becomes available, the browser makes a best-effort one-time pull and merges keys present in the workspace file. Cross-browser or cross-machine consistency therefore depends on using the same workspace and allowing the Host file operation; it is not a guaranteed cloud sync.

Optimization history is separate from settings. It is a FIFO list of the last five attempts held in the mounted React component, including failures. It is not written to localStorage or the workspace file and can disappear after a page reload, component/session unmount, plugin reload, or profile restart.

Security, privacy, and known limitations

The plugin itself does not collect credentials or create a database. It does store the selected settings in browser storage and, when possible, the workspace JSON file. Installing it runs third-party code in the DSH process; review the source and the provider policy before enabling it for sensitive work.

Troubleshooting

dsh --profile web --dump-config | findstr dsh-prompt-polish

How it works

Composer slots + Settings row
          │ browser UI
          │ Typert remote.promptPolish.*
          ▼
Host promptPolish service
          ├── reads/writes best-effort workspace settings
          ├── assembles mode, language, custom, and optional context rules
          └── streams through DSH's configured LLM provider

• The Host bundle is mounted by cordis.patch.yml and provides getSettings, setSettings, optimizePrompt, and cancelOptimize.
• The browser bundle registers conversation.input.left and settings.general.item.
• Browser-to-Host calls use the Typert contribution declared in lib/typert.host.js; the plugin does not expose another HTTP API.
• On stop, update, or unmount, active streams and browser-side composer blocks are cleaned up where the corresponding DSH service is available.

Development and validation

The repository ships prebuilt JavaScript bundles and does not declare a package build script. From the repository root:

node --test test/shared.test.mjs
Get-ChildItem lib\*.js | ForEach-Object { node --check $_.FullName }
pnpm pack --dry-run
git diff --check

The unit test covers shared strategy assembly, option normalization, history classification, truncation, and finish-reason handling. A local profile can be used for a runtime smoke test:

dsh plugin --profile demo add E:\path\to\dsh-prompt-polish
dsh --profile demo --dump-config

Before publishing a documentation or screenshot change, check that every path in screenshots.json exists and that the packed file list contains assets and screenshots.json. After pushing updated assets, verify the three GitHub Raw URLs used above return HTTP 200.

License and disclaimer

MIT. See NOTICE for project history and attribution. This is an independent, community-maintained plugin and is not affiliated with DeepSeek or the @deepseek-ai/* packages. Installing it executes third-party code on your machine; review the source before installation.