dsh-prompt-predict

dsh-prompt-predict is a DeepSeek Harness plugin: after every assistant turn it predicts the message you are most likely to type next and floats it into the composer as gray ghost text. The suggestion never enters the editor — only pressing Tab inserts it, and even then it stays undoable — so a wrong prediction costs you nothing.

📑 Table of Contents

• ✨ Features
• 🚀 Installation
• ⌨️ Usage
• ⚙️ Settings
• 🔌 HTTP API
• 🧩 How it works
• 🛠️ Development
• 🔐 Security and cost
• ⚠️ Known limitations
• 📄 License

✨ Features

• A suggestion the moment a reply ends — gray ghost text rendered at the composer's first character, matching the editor's caret position, font size and line height
• Four interactions — Tab to accept, Alt+→ to accept piece by piece, ↻ for a different suggestion, Esc to dismiss; typing hides it, and clearing the draft brings it back
• Lightweight context — only the most recent user/assistant text; tool results, attachments and system prompts never leave your machine
• Follows the current session model by default — nothing is hard-coded to a provider, the prediction call reuses whatever model the session itself uses; you can also pin a cheaper model
• No repeats, no dead ends — a repeat of the previous suggestion triggers an automatic "give me a different one"; a reasoning level the real model doesn't support falls back automatically, so you never hit "settings look fine but no suggestion ever appears"
• Everything is adjustable — on/off, provider / model, response timeout, context size and budget, output cap, reasoning effort; changes apply immediately, no DSH restart
• The UI follows your language — switch Settings → Language to 中文 and the whole plugin UI changes at once, including the ghost hint above the composer and the validation errors inside Settings (those are produced by the host, which answers in the language the client sends); no reload needed, and it falls back to Chinese when no locale service is present
• Zero runtime dependencies — plain ESM on both the host and client side

🚀 Installation

The plugin is published on npm. Options are ordered by convenience.

Install inside DSH (recommended)

GUI: open the plugins page → Add plugin → enter the package name dsh-prompt-predict → install.

Or the dsh CLI — pin any published version with pnpm's @version syntax:

dsh plugin --profile desktop add dsh-prompt-predict@0.2.4

Replace --profile with your own profile (usually desktop on the desktop app, web for the web build), then restart DSH.

⚠️ The CLI only installs the package. DSH loads a plugin only when it is also listed in dsh.profile.bundles inside ~/.dsh/profiles/<profile>/package.json. Verified: with the package installed but not in that list, the plugin's routes answer 404 and nothing loads. The GUI route above handles it for you; with the CLI add "dsh-prompt-predict" to that array yourself, or just run scripts/install.sh below, which does both steps.

You'll find the switch and all parameters under Settings → Prompt Suggestions.

Install from a release tarball

Every release carries the exact tarball that is on npm (shasum matches the registry), which is handy for offline machines or for pinning an artifact you can verify:

gh release download v0.2.4 --repo ferrisching/dsh-prompt-predict --pattern '*.tgz'
dsh plugin --profile desktop add ./dsh-prompt-predict-0.2.4.tgz

Same caveat as the CLI route above: add "dsh-prompt-predict" to dsh.profile.bundles yourself, or run scripts/install.sh instead.

Install from source

git clone https://github.com/ferrisching/dsh-prompt-predict.git
cd dsh-prompt-predict
bash scripts/install.sh

The script packs this repo on the fly, installs it into the profile's node_modules, and adds dsh-prompt-predict to dsh.profile.bundles. The default target is ~/.dsh/profiles/desktop; for another profile:

bash scripts/install.sh ~/.dsh/profiles/web

Restart DSH afterwards, then look under Settings → Prompt Suggestions.

Manual install

cd ~/.dsh/profiles/desktop
pnpm add dsh-prompt-predict              # from npm
# or link local source (symlink — handy while developing):
pnpm add /path/to/dsh-prompt-predict

Then open that profile's package.json and add "dsh-prompt-predict" to the dsh.profile.bundles array, and restart DSH.

Requirements

• Verified on DSH 0.2.1-rc.2 (web build; the desktop app runs the same host and client code)
• node / pnpm: the install script prefers DSH's own runtime under ~/.dsh/dsh-runtimes/*/dependencies and only falls back to PATH
• macOS / Linux; Windows untested

⌨️ Usage

1. Chat normally, wait for the assistant to finish its turn, and leave the composer empty
2. About 350 ms later a gray suggestion appears, with Tab / ↻ / Esc on its right
3. Pick what you need:

Action	Effect
Tab	Accept the whole thing (only now is it inserted, and it stays undoable)
Alt+→	Accept piece by piece — a couple of characters at a time in CJK, one word in Latin; the rest keeps floating, stop whenever you like
↻ (button on the right)	Reroll — ask the model for a different suggestion
Esc	Dismiss this one
Just start typing	It disappears; clearing the draft brings it back (only Esc is a permanent dismissal)

Suggestions only appear when the composer is empty and the session isn't running. Switching sessions or interrupting a reply clears any pending suggestion.

⚙️ Settings

Settings → Prompt Suggestions:

Setting	Description	Default
Enable predictions	Master switch	On
Provider / model	Model used for the prediction call; pick "Follow current session model" to reuse the session's own model	Follow current session model
Response timeout (advanced)	1–60 seconds	12 seconds
Context size (advanced)	Small 3 / Standard 8 / Large 12 messages	Standard 8
Context budget (advanced)	Character cap sent to the helper call, 1000–20000	6000
Output cap (advanced)	Token cap per suggestion, 16–512	64
Reasoning effort (advanced)	Options are generated from the model actually in use (the session's model when following it); unsupported levels never appear	Off (fastest, cheapest)

The bottom of the settings page shows a last prediction line: time, model, latency, whether the reasoning level was auto-downgraded or a reroll happened, and the reason when it failed — no more guessing why nothing appeared.

• Changes take effect immediately — no DSH restart
• Settings are stored at ~/.dsh/dsh-prompt-predict/config.json (mode 600)
• Precedence: user-saved settings > cordis patch deploy defaults > built-in defaults

🔌 HTTP API

The plugin registers a same-origin prefix route /dsh-prompt-predict on DSH's web server; both the settings page and the composer suggestion go through it. Every endpoint is authenticated with DSH's browser cookie (connection.requestRejection) — off-machine callers get 401/403.

Method	Path	Description
GET	/dsh-prompt-predict/status	Current session model, effective settings, saved overrides, deploy defaults
GET	/dsh-prompt-predict/catalog	All providers and models (for the dropdowns)
GET	/dsh-prompt-predict/efforts?provider=&model=	The reasoning levels that model actually supports
POST	/dsh-prompt-predict/settings	Save settings; { "reset": true } restores defaults
POST	/dsh-prompt-predict/suggest	{ sessionId } → one suggestion

Every endpoint accepts an optional x-dsh-locale header (zh / en, default Chinese) deciding which language validation errors and prediction failures come back in. The client sends the active UI language automatically.

🧩 How it works

Host side (lib/)

1. lib/index.js is the plugin entry point and registers the same-origin HTTP route
2. On suggest, lib/predict.mjs trims the session down to the most recent user/assistant plain text — walking backwards under both a message-count limit and a character budget
3. That trimmed history is framed as a single request-only user input before it reaches the helper model: DSH assistant messages must carry a full stream / replayState, so a trimmed fragment cannot masquerade as one (same approach session-title uses)
4. The streamed reply is normalized (code fences, Suggestion: prefixes and wrapping quotes stripped, newlines collapsed) and returned to the client

For model selection, provider / model set to auto means "follow the session": no route is hard-coded onto the helper call, and predictNextPrompt inherits whatever the session itself selected.

Client side (client/)

• Injects into the conversation.composer.dock (lifecycle mount point next to the composer) and settings.section slots
• The ghost text is an overlay — it is never written into the Lexical editor; only accepting goes through inputActions.insertText

🛠️ Development

git clone https://github.com/ferrisching/dsh-prompt-predict.git
cd dsh-prompt-predict
npm test        # 71 cases: 51 host-side + 20 client render smoke tests

.
├── lib/                 Host side (plain ESM, no build step)
│   ├── index.js         Plugin entry point, registers the HTTP route
│   ├── host-route.mjs   Same-origin API: status / catalog / efforts / settings / suggest
│   ├── predict.mjs      Session trimming, helper-model call, suggestion normalization
│   ├── messages.mjs     User-facing host copy (Chinese + English)
│   └── config.mjs       User settings persistence
├── client/
│   └── client.js        Client: composer ghost-text overlay + settings page
├── test/
│   ├── predict.mjs      51 cases: trimming, cleanup, route inheritance, settings validation, degrade-retry, dedup, bilingual errors, HTTP end-to-end
│   └── client-render.mjs  20 cases: renders the ghost overlay and settings page through a tiny React stand-in, incl. both locales and dictionary self-checks
├── scripts/
│   └── install.sh       One-shot install / upgrade
├── cordis.patch.yml     Plugin mount patch
└── package.json

test/client-render.mjs is the only automated safety net for the client side: no browser needed — a tiny React stand-in expands the components into a plain object tree so the test can assert that the ghost shows up and that Tab / ↻ / Esc are all there. It exists because of a real incident: the overlay referenced a variable it never read from props, the render threw, React's error boundary swallowed it, and the symptom was "the API returns a suggestion but nothing ever appears" — while every host-side test was green.

The tests need no DSH runtime: a fake ctx plus a local HTTP server cover route registration, settings validation, route inheritance and end-to-end calls.

🔐 Security and cost

• One small helper call per assistant turn by default (maxTokens: 64); an extra attempt only happens when the reasoning level needs downgrading or a suggestion needs rerolling — three calls is the hard ceiling, and they share a single timeout budget
• Suggestions are not written to the session log; only after you accept with Tab and send does the text become a real message
• Only trimmed user/assistant plain text is sent — tool results, attachments and system prompts never leave the machine
• Both the settings page and the suggestion endpoint sit behind DSH's own browser-cookie authentication

⚠️ Known limitations

• Verified only on DSH 0.2.1-rc.2; other versions untested
• Depends on the host's conversation.composer.dock and settings.section slot names — a major DSH update may require adapting
• Predictions consume quota on the selected model; pinning a fast small model is cheaper than following a reasoning model

📄 License

MIT © ferrisching

Free to use, modify and distribute, including in closed-source commercial projects — just keep the copyright notice and license text.

See CHANGELOG.md for the change history (中文).