How do I uninstall a DSH plugin?

Run dsh plugin --profile web remove . The command forwards to pnpm, which removes the dependency; restart dsh web and the plugin stops loading.

How do I fully remove an npx-installed DSH?

npx leaves no global install, so deleting the ~/.dsh data directory completes the uninstall. Optionally run npm cache clean.

How do I remove a source-built DSH?

Delete the cloned deepseek-harness repo, run pnpm store prune to clean the cache, then delete ~/.dsh.

Can I restore a DSH plugin I removed by mistake?

Yes. Every plugin's install command is recorded on its dsh-plugin.org detail page — reinstall with dsh plugin --profile web add.

How to uninstall DSH plugins and clean up DSH data

Q: Does uninstalling a DSH plugin delete my sessions?

No. Sessions live in ~/.dsh/sessions; removing a plugin only changes profile dependencies, not your session data.

Remove a DSH plugin with dsh plugin --profile web remove <package>; to fully uninstall DSH itself, delete the ~/.dsh data directory.

Removing a single DSH plugin

remove mirrors add — one command drops the plugin dependency. In your terminal, run:

bash

dsh plugin --profile web remove <package-name>

The command forwards to pnpm inside the profile directory, which runs pnpm remove and removes the plugin from dependencies (source). After restarting dsh web, the plugin's capabilities stop loading. Removal only touches the profile you name — here only web, so anything installed in the headless profile is unaffected. Not sure of the package name? Run dsh plugin --profile web why <package> to inspect dependencies, or check the plugin's detail page on dsh-plugin.org. Removing a plugin never cascades to DSH itself or other plugins, so it's safe to run.

Cleaning up profiles after removing DSH plugins

Removing a plugin doesn't touch the profile directory; to clean fully, delete the profile. Each profile maps to a directory under ~/.dsh/profiles/<name> — for example, the web profile lives at ~/.dsh/profiles/web. The profile directory holds the plugins' dependency declarations (package.json) plus the profile's own manifest (dsh.profile, which records bundles in order), so deleting the whole directory clears every plugin and all configuration in that profile at once. If you no longer want a profile, just delete its directory; DSH recreates the built-in web and headless profiles on next launch (source). For a plugin you only temporarily stop using, prefer removing it over deleting the profile — restoring is then a single add away.

Uninstalling DSH entirely

Uninstalling DSH depends on how you installed it; the core step is clearing the data directory. Two cases:

npx install: npx only fetches packages temporarily and leaves no global install — deleting ~/.dsh completes the uninstall.
Source build: delete the cloned deepseek-harness repo, run pnpm store prune to clean the pnpm cache, then delete ~/.dsh.

Note that DSH is in developer preview, so the file layout (including the ~/.dsh default for $DSH_HOME) may shift — verify against the official docs before a clean removal. Before deleting ~/.dsh, be clear about what you're losing: it holds both profile configuration and every session record — once deleted, they're gone.

Before you uninstall DSH plugins

Uninstalling doesn't touch session data, but back it up first anyway. Sessions live in ~/.dsh/sessions; removing a plugin only changes profile dependencies. Deleting ~/.dsh, however, removes sessions with it — copy the folder if you want to keep them. Accidentally removed a plugin? Reinstall it with the add command from How to install a DSH plugin. If other things stop working after the removal, that plugin was probably depended on by others — run dsh plugin --profile web why <package> to inspect the dependency tree before deciding what to do next.

Source: dsh CLI README, official Quickstart