DSH Toolbox

dsh-session-superagent

A session-level supervisor that watches a GitHub issue and keeps working.

Version 0.10.12 of dsh-session-superagent, last published 2026-11-09; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-session-superagent writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add dsh-session-superagent

Compatibility

engines.dsh in dsh-session-superagent declares >=0.2.1-rc.5 <0.2.2-0 || >=0.2.2-rc.1 <0.3.0-0; run dsh --version and compare it, because outside that range the CLI skips the plugin at boot and prints the requirement instead of booting.

If two plugins fight

Its range is >=0.2.1-rc.5 <0.2.2-0 || >=0.2.2-rc.1 <0.3.0-0. On a 0.2.1-rc.2 CLI it is skipped at boot with the incompatibility message, so a "nothing happened after install" report is the range, not the plugin.

Who made it

Author: MYCF711. Repository: https://github.com/MYCF711/dsh-session-superagent. Package page: https://www.npmjs.com/package/dsh-session-superagent.

After install

It declares @deepseek-ai/cordis as a peer and renders archive, restore, favorite and delete actions in each row of the session list; after dsh plugin add dsh-session-superagent, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

No storage peer appears in the manifest of dsh-session-superagent, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.

Removing it

Removing dsh-session-superagent is the mirror command, dsh plugin --profile web remove dsh-session-superagent. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.

Common questions

Does it collide with @michengai/dsh-archive-manager?

For dsh-session-superagent the recommendation is @michengai/dsh-archive-manager: It peers 16 official packages including dsh-session-projection-cache and dsh-storage-domain; the supervisor peers one and needs a narrow dsh range.

Which dsh versions load it, and what happens outside that window?

On >=0.2.1-rc.5 <0.2.2-0 || >=0.2.2-rc.1 <0.3.0-0 the CLI loads dsh-session-superagent; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-session-superagent is the per-package override if you accept the risk.