dsh-composer-input-history
DSH 撰写器的 Shell 风格输入历史：按向上箭头可调出已发送的消息，按向下箭头可向前浏览并恢复草稿。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:liumorrisclaw/dsh-composer-input-history#f4cdfaef8f63ebba3d51077bed5bd85e02dbfa72Composer Input History 以 dsh-composer-input-history 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Shell-style input history for the DeepSeek Harness Web composer — the behaviour you know from opencode and other terminal agents.
Press ↑ in the composer to pull back a message you already sent in this Session. Press ↓ to walk forward again; past the newest message your original draft comes back.
| Gesture | Behaviour |
|---|---|
| ↑ with an empty draft | recalls the newest sent message |
| ↑ again | walks one message older each time |
| ↑ on the first line of a single-line draft | recalls; the draft you were writing is remembered |
| ↑ inside a multi-line draft, below the first line | left to the editor, so the caret still moves |
| ↓ while browsing | walks one message newer |
| ↓ past the newest message | restores the draft you were writing before browsing |
| typing anything while browsing | leaves browse mode; the recalled text becomes your draft |
History is what you sent in this Session, oldest to newest, read from the Chat node store the view itself renders (snapshot.nodes, ordered by anchor sequence): ordinary user messages, steering messages, and the message that woke a turn. Skipped: hidden nodes (compacted or interrupted), attachment-only messages, and everything the Harness authors on your behalf — goal rounds, skill catalogs, runtime snapshots, job notices, model notices, approval answers, and compaction checkpoints.
The Harness composer deliberately leaves ↑/↓ to its shell-owned Lexical editor, so no slot or command seam owns them. This plugin therefore:
conversation.composer.dock;useChat hook (snapshot.nodes) and the draft through the standard useInput hook;inputActions.setDraft API, so the edit stays part of the composer's own draft history;keydown listener and the shortcuts service's observeFixedInput seam. The document listener runs after the composer's own keymap, so a slash menu or an IME that already handled the key still wins; the fixed-input seam covers compositions where a native Desktop adapter owns the DOM feed. Exactly one path acts, because the first one to act cancels the event.A key is declined when the slash/reference menu already consumed it, when an IME is composing, when a modifier is held, when the event is outside the composer editor, or when the composer is submitting/adjudicating. The plugin imports no Harness Client package and styles nothing.
From this repository (available now):
dsh plugin --profile web add https://github.com/liumorrisclaw/dsh-composer-input-history
Once the package is on npm, the short form is:
dsh plugin --profile web add dsh-composer-input-history
Or add it in the Web UI's Plugins page, or list the package directory with the plugin manager. The bundle ships off until the profile selects it.
For a local checkout, install by path:
dsh plugin --profile web add /absolute/path/to/dsh-composer-input-history
The npm name dsh-input-history is already taken by a different community plugin that also recalls prompts with ↑/↓. The two differ in mechanism and behaviour:
| dsh-composer-input-history (this plugin) | dsh-input-history | |
|---|---|---|
| History source | the Session transcript the Chat view already loads | a separate local store of submitted prompts |
| Non-empty draft | recalls and remembers the draft, restoring it below the newest message | recalls only from an empty composer |
| Attachments | not part of the recalled text | persists and re-attaches them |
| Menu/IME | yields the key to an open slash/reference menu and to IME composition | — |
Pick this one if you want recall driven by the conversation you can see, including from a draft you are already typing.
Developed and verified against @deepseek-ai/dsh 0.2.0-rc.2. The plugin uses only documented seams: ctx.slots, the Session standard props (useChat, useInput, inputActions), and ctx.shortcuts.observeFixedInput. It declares dsh.client.inject on dsh-client-ui-conversation, dsh-client-ui-chat, and dsh-client-shortcuts so activation order is deterministic.
npm test), run on every push by .github/workflows/ci.yml on Node 20 and 22.dsh --profile <name> --dump-config).immediately: true, and the web host serves the bundle body byte-for-byte.Not yet verified by automated browser control: the in-page interaction itself. Pressing ↑ in a running composer is the acceptance check.
MIT