Feature request: Up/Down arrow input history in the Web composer

[surya9815]

In the Web composer, ↑ / ↓ should navigate previously sent prompts, similar to terminal history.

• ↑ on an empty draft / start of text recalls the latest prompt.
• Repeated ↑ / ↓ navigates session-local history.
• Preserve existing multiline, IME, menu, and modifier behavior.
• Recalled prompts only fill the draft - Enter still submits.

[surya9815]

I’ve implemented this in my fork in case anyone wants to try it out or reuse the implementation:

👉 https://github.com/surya9815/deepseek-harness/tree/feature/web-composer-input-history

If you have any suggestions @tianyicui tianyicui, improvements, or run into issues, feel free to open an issue on the repo. Feedback is welcome!

[liyangbing]

这个功能适合定义成“Session-local draft history”，而不是直接复用 durable Session history：已发送 prompt、当前 draft、被撤回/失败的 draft 和 attachments 的生命周期不同，混用会造成隐私泄露或误重发。

我维护的独立 DeepSeek Harness 社区手册中，Web IME composition 与 prompt admission durability 建议按以下矩阵验收：

• 空 draft / 光标在开头 / 光标在中间 / multiline draft 分别测试 ↑ 和 ↓；
• history 只保存明确提交且属于当前 Session 的文本，不保存未发送 draft、密码式输入或附件 bytes；
• recalled text 只填充 draft，不自动触发 Enter、steer、queue 或重复的 user/message；
• IME composing 时不拦截箭头，Shift+Enter、命令菜单、attachments、直接发送和 modifier 组合保持原语义；
• Session 切换、reload、reconnect 和两 tab 场景明确选择 local persistence 还是清空，并测试不会把 A Session 的 prompt 填入 B Session；
• 发送失败时区分 draft history 与 durable user/message：有 durable event 就不要重复提交，没有才恢复 draft。

实现若采用 browser-local storage，也应记录作用域、清理/导出策略和敏感内容排除规则。手册是独立社区资料，不代表官方 DeepSeek AI 项目。

[gengwg]

this might be helpful: #4135

[gengwg]

dsh-composer-history covers this and works on 0.1.1-rc.2.

Installed dsh-composer-history@0.6.2 (npm, Apache-2.0) with dsh plugin --profile web add dsh-composer-history on dsh 0.1.1-rc.2, Linux, Node 24.19. Working after a Host restart.

Two things that made it look broken first:

• A running dsh web Host will not pick it up. The plugin tree is composed at boot, and this plugin declares dsh.client.platform: web and injects into the @deepseek-ai/dsh-client-ui-* packages, so the browser bundle gets rebuilt too. Restart the Host, then do a cache-bypassed reload. A plain page reload is not enough.
• The store only holds messages sent after install, so the first ↑ on a fresh install correctly does nothing. Send a few prompts before concluding it is dead.

Worth verifying from the shell rather than the UI, since "installed but inert" and "not installed" look identical there: dsh --profile web --dump-config should list id: composer-history, and the served page should carry a /plugins/dsh-composer-history/client.js?rev=... script tag that returns 200.

On the design points raised above: recall is edge-first, bare ↑/↓ move the caret and recall only triggers when the caret is already on the first/last line, and the first recall stashes {draft, caret} and restores both exactly on bottom-out or Esc. That covers the multiline and draft-loss cases. Note the scope difference though: this history is browser-local and persists across reloads and sessions, not session-local, so read the plugin's data section if prompt retention matters for your setup.

One rough edge from its own known limitations: each recall is a setDraft transaction in the input machine's undo log, so Ctrl+Z steps back through recalls rather than through your typing.

One platform, one user report, not a security or compatibility endorsement.