dsh-local-plugins

dsh-local-plugins

Customize any dsh plugin — even a built-in one — without losing your changes when things update, break or get reinstalled.

What you can do with it

And when something goes wrong, it tells you whether your setup is still safe and what to do next — it does not just say "failed".

Install (2 minutes)

1. In a terminal (replace web with your profile name if you use another):

   dsh plugin --profile web add github:ishanshmalviya5/dsh-local-plugins
   

2. Restart dsh web.
3. Open Settings → Local Plugins.

You need git, npm and Node 26 or newer, on macOS or Linux (details).

Your first customization

1. + Add → Migrate and pick a plugin you already use. Anything you had already changed by hand is kept as your starting point.
2. Make your change — edit the files in ~/.dsh/local-plugins/<plugin>, or press Work on it to have an AI agent do it with you.
3. Commit, then Apply, then restart dsh web.

That's the whole loop. Nothing changes in dsh until you click Apply, and if the new version can't be built or doesn't pass the checks, the old one simply keeps running.

More stories

The author released a new version

Press Check now (it also checks shortly after dsh starts). A plugin with news shows Update available; click Update. Your changes and the new release are combined for you. If you and the author changed the same lines, the card lists those files and you choose: fix them (or press Fix with agent) and Finish update, or Abort to forget the attempt. Your running plugin is untouched throughout; you decide when to Apply.

A change made things worse

Click Deploy older commit… and pick the version that worked. If dsh itself starts misbehaving right after you applied something, it notices, puts the last working version back, and shows a message — your edits are saved for you to fix with Work on it.

If dsh won't start at all, run this in a terminal to put every original plugin back: node ~/.dsh/local-plugins/.deployed/dsh-local-plugins/scripts/undo.mjs --all

I'm customizing a built-in plugin and want out

Unlink (restore original) gives dsh the original, untouched plugin again. Your version stays listed (as Not applied), so you can switch it back on with Apply whenever you like.

I want to remove a plugin from the list

Unlink it first, then Delete… and type its name. Your work is moved to ~/.dsh/local-plugins/.trash/, not erased. Move the folder back and press Repair installation to bring it back.

I don't know what state things are in

Press Repair installation. It looks for anything that doesn't add up (for example after a crash or a dsh upgrade), fixes what is safe, tells you about the rest, and never deletes your work. Recent operations shows what ran, how long it took, and the log; Disk usage shows space per plugin and lets you clean up old versions with a preview first.

Using an exact version

For npm plugins: name, name@1.2.3 or name@beta. For plugins from git: a web address, github:owner/repo or git@host:owner/repo, optionally ending in #v1.2.0 (a release), #branch, or #commit. A pinned release or commit never moves by itself.

What the labels mean

You stay in control

• Scripts need your OK. Some plugins want to run install or build scripts with your full access. That is off by default; you choose Allow this time or Always allow for this plugin, and it asks again if the publisher changes.
• Your work is never silently lost. Unlink, Delete, rollbacks and crash recovery all keep your edits somewhere you can get them back.
• Only a finished, checked version is ever switched on — never a half-done edit.
• It only talks to the sources you track (the plugin's git or npm origin).

How this is guaranteed: Security · Recovery · How it works.

Compatibility — dsh-local-plugins 0.3.0

Built and tested against dsh 0.2.0-rc.2. Upgrading from version 0.1 needs nothing from you: your plugins stay exactly as they are (details in the CHANGELOG).

Good to know

• If a plugin crashes dsh before this one loads, it can't repair that itself — use the undo.mjs command above.
• The check before going live confirms the files are complete and readable; it does not run the plugin first.
• Built-in plugins follow the version that ships with your dsh, not newer npm releases.
• It does one thing at a time; if you click while it is busy, it asks you to wait.

For developers

HTTP API · Status rules · Troubleshooting · Performance · Release checklist · Developing

Contributions are welcome, including AI-assisted ones: read CONTRIBUTING.md first (and AGENTS.md for coding agents).

License

MIT — see LICENSE.