How to use dsh-market: install, browse and manage plugins

Install dsh-market

On regular dsh web, run the install command from the README, then restart dsh web. If your host uses a different profile name, replace web with that name.

If you use DSH Desktop, the README recommends installing through the app instead: open Settings, go to Plugins, search for dshmarket, and install it with the app's plugin manager. The command line can report success while installing into a profile the Desktop app does not use, so the README advises against it on a machine with Desktop.

• Regular dsh web: run the command below, then restart dsh web.
• Custom profile: use dsh plugin --profile <profile> add dshmarket and follow your host's restart instructions.
• DSH Desktop: install from Settings, then Plugins, with no command line.
• Requires a DSH web build that the README says is current enough. On an older host the market disables itself and logs a message in the browser console, so if the Plugin Market entry never appears, check your host version first.

Open the Plugin Market tab

On newer DSH hosts, open the Plugins page and select the Plugin Market tab next to Installed. This works on plain dsh web without the desktop app.

On older hosts, open Settings and then Plugin Market. The market can also add its own Plugin Market row to the sidebar, which you turn on from the market's card under Plugins.

Browse, search and install plugins and themes

The market shows the community catalog with category filters, top and new sorting, and descriptions that follow your UI language. Each card shows the DSH requirement the plugin declares, and the compatibility filter hides only plugins that are confirmed to mismatch your running host. Plugins with an unknown or missing requirement stay visible.

To install, pick a plugin, confirm its source, and watch the live progress. Most plugins start working after a page refresh, with no restart. Themes have their own tab: install one and it becomes active immediately, and you can switch between themes with one click. Uninstall a theme to go back to the default.

• Filter by category and sort by top or new.
• Bookmark plugins and themes as favorites and find them later in the Favorites tab.
• Screenshots appear on the card when the author supplied them, and otherwise load when you open the install dialog.
• Uninstall uses a two-step confirm. Plugins installed in the current session are removed live.

Organise your installed plugins

Groups let you put installed plugins into named groups, rename or delete them, and search within a group. A plugin belongs to one group, and ungrouped is the default. A group has a switch that turns all its members on, turns them off, or shows the mixed state they are actually in, so you can switch a working set as one unit.

Notes let you write your own one-line description for any installed plugin. Your note replaces the author's description on that row. Notes, groups and favorites are stored locally in the profile's state.json file and are not sent anywhere.

• Enable or disable a plugin with its toggle. The choice is written to cordis.patch.yml in the profile and re-applied on every boot.
• Hand-edited patch rows appear as badges, and host-infrastructure plugins cannot be toggled.
• A group can hold at most one theme.

Back up and restore your plugin setup

Backup exports your profile's plugin list and configuration as readable JSON. You can import that file on another machine, store it on WebDAV with daily auto-backup, or sync it through a private GitHub Gist.

Restore merges the backup into your current setup. Plugins you installed after the backup was made are kept. The market validates the file before writing and rolls back if the restore fails.

Keep plugins updated and understand network use

The market checks each installed plugin for updates, using the npm version or pinned commit compared with the latest. You can update one plugin, or update everything at once. Each row with a pending update has a What changed link to the release notes or commits. A plugin installed from an archive link is only updated from its own source, so a catalog entry with the same name is never offered as its replacement.

Comments open a plugin's GitHub Discussions thread in place. Opening that thread contacts giscus.app and GitHub. If you do not want that, do not open the comments panel.

• Updates: per plugin, all at once, or from the market itself.
• In the China download region, GitHub routes have fallbacks, and you can set one custom HTTPS prefix under Settings, then Plugins, then Plugin configuration, then GitHub acceleration.