xuender/dsh-history
Recall and re-run the current session's command history with ↑/↓ keys in the DSH
DSH Web command history plugin: with the composer input focused, press ↑ / ↓ to step through previously sent commands in the current session, edit them, and press Enter to re-send. Records every message (plain and /xxx slash commands) automatically, isolated per session. ↑ steps back (first press saves the draft you were editing); ↓ steps forward and returns to the saved draft from the newest entry. Safe fallbacks: while a / or @ trigger menu is open, during IME composition, when the composer is busy/locked, or when input is not focused, ↑/↓ keep native behavior and never interfere.
Install
ln -s + dsh web --patch /absolute/path/to/dsh-history/cordis.ymlSource install per README (English): the entry name must be the bare package name dsh-history, resolvable from both resolution trees, so two symlinks are required — ln -s /absolute/path/to/dsh-history ~/.dsh/profiles/node_modules/dsh-history and ln -s /absolute/path/to/dsh-history <dsh-install>/node_modules/dsh-history. Then launch with dsh web --patch /absolute/path/to/dsh-history/cordis.yml, or merge the insert stanza into $DSH_HOME/profiles/web/cordis.patch.yml permanently. No npm package — source checkout required.
Compatibility
DeepSeek Harness web GUI (standard DSH static plugin). History derived from the session log (user/command nodes) — rebuilt automatically after reload, no extra storage.
Details
- Repo: xuender/dsh-history
- Category: Memory Enhancement
- Stars: 3
- Version: GitHub source (no npm package)
- Last push: 2026-08-14
- First seen: 2026-08-14
Recent updates
per-session command history; ↑/↓ recall + edit + re-send; draft save/restore; IME/menu/busy-composer safe fallbacks; log-derived rebuild.
FAQ
- Is history persisted?
- It is derived from the session log (user/command nodes), so it rebuilds automatically after a page reload — no extra storage.
- Does it ever break my input?
- No — during IME composition, trigger menus, busy composers, or unfocused input, ↑/↓ keep native behavior.
- Is it per session?
- Yes — history is recorded and isolated per session.
Alternatives
PerryLink/dsh-composer-history · PerryLink/dsh-mcp-panel · R3alloc/dsh-session-deeplink