DSH Plugin Hub settings: updates, npm mirror and proxy

Many people treat the DSH Plugin Hub settings page as a master switch for plugins, then hunt for a plugin's model, permissions or hotkeys and find nothing — because this page only governs how the market itself behaves. The left side has five fixed groups: Update Settings, Security Trust, System Diagnostics, System Logs and Restore Defaults (2.2.5 index). This article reads them by the question each group answers rather than reciting the UI top to bottom. The entry sits on the Settings tab of DSH Plugin Hub.

What the DSH Plugin Hub settings page does and does not control

This page controls market-level behavior — where versions are checked, where packages come from, whether requests use a proxy and which install channels are allowed — and it controls nothing about how an installed plugin runs. Keeping that boundary straight prevents most wasted clicking.

1. Open Settings → Plugin Market → Settings and read the five group names before changing anything.
2. Decide which question you are answering: network, trust, health, history or reset.
3. If the question is about one plugin's model, permissions or shortcuts, leave this page; those live in the plugin's own settings.
4. Note the current values of the three Update Settings fields so you have a baseline.

A settings page is only useful if you know which layer it owns. Everything below stays inside the market layer.

Update settings in dsh plugin market: startup check, mirror and proxy

Update settings answer one question only: where the market looks for new versions, where it fetches packages and whether requests leave through a proxy. Each field covers a different link in the chain, and each one fails with a distinct symptom.

1. Open Settings → Plugin Market → Settings and read the current values of the three fields.
2. Decide on the startup check by habit: enable it if you update often, disable it for faster startup and check manually.
3. Choose an npm mirror that is stable on your network; when ERR_PNPM_FETCH_404 appears, switch back to the official registry briefly before touching the package name.
4. Keep the proxy address consistent with http_proxy and https_proxy in your terminal, so the browser working does not leave the market unable to fetch.
5. Save without closing the page; the next step is to prove the change with a real request.

Mirror and proxy are different links: the mirror decides which repository packages come from, the proxy decides how requests leave the network. If both are wrong, fix the proxy first, otherwise you cannot tell whether a 404 is mirror lag or no connection at all.

Still timing out with both configured? Check these three combinations

1. Browser works but the market cannot fetch: the proxy only applies to the browser layer and the host process did not inherit it — set the proxy on the settings page instead.
2. The list loads but installs return 404: the mirror is lagging; switch back to the official registry to confirm rather than renaming the package.
3. Both look fine yet timeouts are intermittent: note the timestamp and compare it with system logs to see which registry that request used.

Three combinations, three fixes. Do not reach for Restore Defaults, which would also wipe the values that are already correct.

Security trust: deciding the three DSH Plugin Hub channel switches

The Security Trust group decides which custom-install methods are allowed, not which plugins may run. It maps to the NPM, GitHub and DSH channels, and disabling one disables the corresponding custom-install card (Hub repository).

1. Ask whether you will use custom install at all in the near term; if not, all three channels can be off.
2. If you only use prebuilt npm packages, keep NPM and disable GitHub source and DSH command.
3. If you follow source or documentation commands, enable only the one you need instead of turning everything on.
4. After disabling, open Custom Install and confirm the card is disabled and offers a link back to settings.

The value of this group is a smaller source surface, but it does not replace pre-install checks. An enabled channel only means the input format is allowed, not that a given package is trustworthy; permissions, dependencies and build scripts still need review. See how to install plugins safely.

Diagnostics and system logs: two separate dsh plugin market evidence paths

System diagnostics answer whether the market is healthy now, while system logs answer what just happened; only together do they locate a problem. Many people dig through hundreds of log lines without first reading the diagnostic conclusion.

1. Open System Diagnostics and check whether overall market status is healthy; the exact checks follow the current interface.
2. Switch to System Logs and filter by category: install, uninstall, settings change or diagnostics.
3. Filter by error or warning level and find the entry matching your reproduction time.
4. Use Copy Full Text or Export Logs to take the evidence away before deciding whether to change configuration or retry.
5. For long-term retention, change the log location to your own working directory and save.

The log page also offers Open Log Viewer and Open File: the first reads in the interface, the second locates the file in Finder. Both show the same records, only in different reading modes. The full triage order is in how to read notifications when a plugin install fails.

Restore Defaults: when to reset DeepSeek Harness plugin market settings

Restore Defaults is a group-level reset, not a single-field undo; it suits "the configuration is scrambled and I cannot say what changed" rather than "one field is wrong". In the second case, editing that field is faster and leaves a correct mirror and proxy intact.

1. Before touching it, copy or screenshot the three update settings and the three security trust switches.
2. Confirm that the problem is overall configuration chaos, not one specific error.
3. Run Restore Defaults and restart DeepSeek Harness.
4. Reopen the market and confirm the list loads; then re-enter the mirror and proxy values you still need.
5. If the problem disappears after the reset, one original value was the root cause; add values back one at a time to find it.

Restore Defaults does not clear caches and does not reinstall Hub. If the problem is a version mismatch or a front-end asset 404, resetting settings will not help; see Hub blank but CLI works.

Verifying the change: three steps for a DSH plugin settings update

Saving is not the same as taking effect; only a real request proves it. The order is fixed: restart, load the list, install a known plugin.

# 1. Record the current CLI version for later comparison
dsh --version
# 2. Check which market configuration the current profile sees (read-only)
dsh --profile web --dump-config | grep -in -E 'registry|proxy|mirror'
# 3. After restarting, load the market list and watch for timeouts or 404s

1. Restart DeepSeek Harness after saving so the new configuration is loaded.
2. Load the market list once and confirm cards appear; if the list is blank, check the proxy first.
3. Install a small, known plugin and watch whether a mirror 404 or timeout still occurs.
4. Check system logs to confirm the request used the registry you configured rather than the old one.
5. Once all three pass, record these values in your own environment notes.

Change one variable at a time during verification: adjust the mirror, verify it, then adjust the proxy and verify again. Change both together and a failure tells you nothing about which one caused it. The interface descriptions also line up with the Hub 2.2.5 release tour.