@michengai/dsh-archive-manager

Q: Does it collide with dsh-session-superagent?

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

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

On >=0.2.0-rc.1 <0.3.0-0 the CLI loads @michengai/dsh-archive-manager; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version @michengai/dsh-archive-manager is the per-package override if you accept the risk.

Archive, restore, favorite and permanently delete sessions, plus damaged-log diagnosis.

Version 1.3.5 of @michengai/dsh-archive-manager, last published 2026-11-13; the install command and the range come from its own manifest.

Install

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

dsh plugin --profile web add @michengai/dsh-archive-manager

Compatibility

engines.dsh in @michengai/dsh-archive-manager declares >=0.2.0-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

Sixteen peers, including @deepseek-ai/dsh-session-projection-cache and @deepseek-ai/dsh-storage-domain: it writes session state, not just views. Running it beside dsh-session-superagent means two plugins mutating the same session lifecycle — archive first, then check the workspace list before trusting either.

Who made it

Author: MichengAI. Repository: https://github.com/MichengAI/dsh-archive-manager. Package page: https://www.npmjs.com/package/@michengai/dsh-archive-manager.

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 @michengai/dsh-archive-manager, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

@michengai/dsh-archive-manager routes whatever it persists through @deepseek-ai/dsh-storage-domain under $DSH_HOME, and its own dependency line sits in $DSH_HOME/profiles/<name>/package.json.

Removing it

Removing @michengai/dsh-archive-manager is the mirror command, dsh plugin --profile web remove @michengai/dsh-archive-manager; the surface goes with it, and whatever it stored under $DSH_HOME stays until you delete it.

Common questions

Does it collide with dsh-session-superagent?

@michengai/dsh-archive-manager is the one to keep here: 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.0-rc.1 <0.3.0-0 the CLI loads @michengai/dsh-archive-manager; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version @michengai/dsh-archive-manager is the per-package override if you accept the risk.