AI Agent Hub
Back to plugins
🖥️

dsh-frontend-inspector

Client Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install lovstudio/dsh-frontend-inspector

Paste the following prompt into your AI chat to install this plugin:

Install the plugin by running dsh plugin install lovstudio/dsh-frontend-inspector in your DeepSeek Harness session; the full open-source repository is available at https://github.com/lovstudio/dsh-frontend-inspector

About this plugin

After DeepSeek Harness builds its Web surface with Vite, the rendered DOM sits behind a layer of compiled artifacts, and figuring out which .tsx file and line produced a particular button or panel usually means guessing with a global search. dsh-frontend-inspector closes that gap with a Lovinsp bridge: hold Shift+Option (Shift+Alt on Windows), sweep the cursor over any rendered element to highlight it, then click once to jump straight to the exact file, line, and column in VS Code or whichever editor you configure. If you prefer a link, the same click copies the GitHub source URL to your clipboard.

The plugin auto-selects between two modes at startup. With a clean DSH checkout on disk, it spins up a persistent Vite process, reads the source tree, applies source maps to every compiled JSX call, and resolves each element to its original .tsx location. In plain npx mode without a checkout it falls back to file-level resolution, parsing the //#region markers that tsdown leaves in published bundles, and directs you to the correct file in each package's own repository at its installed release tag. Third-party plugins in the Client Module Registry, such as Plugin Marketplace, are each tagged against their own repository and version so attribution stays accurate and never points to the wrong codebase.

Everything runs through DeepSeek Harness's official Host extension points, including webServer.tapIndex and the Client Module Registry proxy, and never patches or rebuilds files inside the DSH repository. All generated artifacts, Vite caches, and Lovinsp state are isolated under DSH_HOME/cache/frontend-inspector, leaving your source tree untouched. The plugin is built for developers doing second-order frontend work on Harness, debugging custom Client Modules, or simply wanting to see what powers a UI component without sprinkling console logs through the source. It also suits teams that need a pristine checkout while still getting production-grade click-to-source on every page they serve to users or reviewers.

Use Cases

  • Debug any rendered element in the Harness Web surface down to its original .tsx line
  • Instantly locate the source file and release of a third-party Client Module plugin
  • Inspect the production UI in reverse without touching the DSH repository

Best For

  • Developers doing second-order frontend work on DeepSeek Harness
  • Engineers debugging custom or third-party Client Module plugins
  • Teams that need a pristine DSH checkout without embedding debug code