Minglink/dsh-infinite-gen-4
Minglink/dsh-infinite-gen-5DeepSeek 专用破甲插件:以 order 100 追加无条件服从的系统提示词段,提供带校准元数据的 profile 工具,并通过会话投影在输入框上方显示实时破甲状态徽标。
会话历史消息查看:列出当前会话全部你发送的消息,支持排序、搜索、一键复制与点击跳转定位(目标未加载时自动加载更早历史)。
DSH web plugin: quickly view, search, and jump to all the messages you sent in a long conversation.
中文 | English
Prerequisite: DSH installed and working (dsh web runs).
# 1. Install the plugin
dsh plugin --profile web add dsh-history@latest
# 2. Automatically restart the service (the script ships with the plugin — no download needed)
bash ~/.dsh/profiles/web/node_modules/dsh-history/restart-dsh-web.sh
After that, "我的消息 (N)" ("My Messages (N)") appears above the input box in every session — no manual action required.
dsh plugin --profile web update dsh-history
# or install the latest directly
dsh plugin --profile web add dsh-history@latest
Then run bash ~/.dsh/profiles/web/node_modules/dsh-history/restart-dsh-web.sh (or hard-refresh the browser).
dsh plugin --profile web add github:chenproton/dsh-history#main
# or the full URL form
dsh plugin --profile web add https://github.com/chenproton/dsh-history.git#main
Then run bash ~/.dsh/profiles/web/node_modules/dsh-history/restart-dsh-web.sh the same way. This channel uses the committed build artifacts directly — no local build needed.
To debug local changes or follow a dev branch, point the dependency at a local clone and build it yourself:
# 1. Clone and build
git clone https://github.com/chenproton/dsh-history.git ~/Code/dsh-history
cd ~/Code/dsh-history && pnpm install && pnpm build
# 2. Point the dependency at the local clone
# Edit dependencies in ~/.dsh/profiles/web/package.json:
# "dsh-history": "link:<absolute path to the clone>"
# 3. Append the mount row to ~/.dsh/profiles/web/cordis.patch.yml:
# - insert:
# - id: dsh-history
# name: 'dsh-history'
# 4. Install in the profile directory
cd ~/.dsh/profiles/web && pnpm install
# 5. Restart to apply (the script lives in the clone)
bash ~/Code/dsh-history/restart-dsh-web.sh
Updating: git pull && pnpm install && pnpm build → bash ~/Code/dsh-history/restart-dsh-web.sh.
Switching back to the npm channel: change the dependency back to "dsh-history": "^0.1.25", run pnpm install, and remove the manual mount row (to avoid double-mounting).
Maintainer docs: the release & multi-platform listing runbook (npm / GitHub / awesome-dsh-plugin / dsh-market) lives in docs/publishing.md.
Prerequisite: DSH with plugin-registry integrated (the
dsh registrycommand exists). Enabling both channels at once double-mounts (two Node halves, two panels).
git clone https://github.com/chenproton/dsh-history.git && cd dsh-history
pnpm install && pnpm build
node scripts/package-registry.mjs # assemble registry/ staging (manifest + artifacts + README, not committed)
dsh registry install ./registry # install (disabled by default)
dsh registry enable dsh-external/dsh-history
bash restart-dsh-web.sh # automatically restart to apply
Updating: git pull && pnpm install && pnpm build → node scripts/package-registry.mjs → dsh registry uninstall/install/enable → bash restart-dsh-web.sh. Remove the other channel's mount before switching.
It is a one-click restart script shipped with the plugin: it detects the deployment method and restarts DSH Web so the plugin takes effect —
dsh-web.service) → runs systemctl restart (clean, single instance);dsh web process and restarts it with its original arguments (nohup);dsh web if no process is found.No such file or directory means the script is not in your current shell directory — use the full path, or copy it first:
# Use the script inside the installed package directly (full path, works from any directory)
bash ~/.dsh/profiles/web/node_modules/dsh-history/restart-dsh-web.sh
# Or copy it to your current directory
cp ~/.dsh/profiles/web/node_modules/dsh-history/restart-dsh-web.sh ~/restart-dsh-web.sh
bash ~/restart-dsh-web.sh
# Or download from the repo when the package is not installed
curl -O https://raw.githubusercontent.com/chenproton/dsh-history/main/restart-dsh-web.sh
bash restart-dsh-web.sh
Options: -n previews the commands to run (dry-run), -p PID targets a specific process, -l FILE sets the log file.
Safe to ignore. DSH provides @deepseek-ai/* and react at runtime through its own module table — no need to reinstall them in the profile (official plugins show the same warnings).
restart-dsh-web.sh) or hard-refreshed the browser (Cmd/Ctrl+Shift+R);dsh.profile.bundles in ~/.dsh/profiles/web/package.json should contain dsh-history;dsh plugin --profile web list in an issue.⧉ copy button on each row copies the full text (turns into ✓ for 1.4s, then restores).conversation.input.dock's session is now a SessionSnapshot (no chat), and Chat nodes moved behind the standard useChat selector hook — fixes the list rendering while message locate/jump silently failed.session.snapshotEvents() instead of the removed session.events (old getter kept as fallback), restoring the in-memory fast path.src/client/util.ts, slimmed the component file and unified repeated logic — no behavior change (internal refactor).scrollIntoView; it now positions the conversation scrollport directly (getBoundingClientRect-centered), scrolling synchronously and reliably regardless of panel state.dsh web and stops them), then verifies with an HTTP health check; non-dsh processes are never mis-killed.is-active, which reports active the instant the process forks but can still crash right after).systemctl status + journal logs on failure.restart-dsh-web.sh companion script: one-command service restart after install/update. Auto-detects the deployment (systemd service / bare process restart / fresh start), with -n dry-run, -p PID, -l LOG.scripts/package-registry.mjs and a registry-specific client bundle).HH:mm).Esc closes the panel; keyboard-accessible rows (Enter/Space) and aria-labels.MIT