Under DSH’s plugin-based architecture, UI elements are often rendered by the host or multiple plugins. When you need to identify which module a UI control belongs to, or when you want to hide distracting interface elements, manually inspecting the DOM structure is both tedious and error-prone. The dsh-element-inspector plugin identifies element ownership using local algorithms and provides export and hiding features.

Plugin Overview

This is an unofficial community project for identifying the ownership of page elements in DeepSeek Harness, distinguishing them between the host interface and installed plugins, and supporting export (screenshot, HTML, Markdown) and persistent hiding.

Core Features

  • Evidence-based ownership identification: Uses DOM markers, ancestor distance, and source code matching to distinguish DSH UI from plugins, rather than relying solely on names.
  • Source discovery and quick navigation: Displays all matched owners, versions, and source files, and supports opening plugin directories or repositories.
  • Element export: Supports local screenshots (PNG), copying outerHTML, or converting to GitHub Flavored Markdown.
  • Persistent hiding: Allows hiding selected elements, with support for restoring individual elements or clearing rules.
  • Configurable shortcuts: The default shortcut is F1, and it can be modified in the plugin configuration.

Installation and Enablement

Install the prebuilt package to the web profile:

dsh plugin --profile web add dsh-element-inspector

After installation, restart the corresponding DSH Web or Desktop instance. If you need to install from GitHub source code, you can use:

dsh plugin --profile web add github:muyuanjin/dsh-element-inspector#v0.7.0

Typical Usage

  1. Press the configured shortcut key (default F1) to enter selection mode.
  2. Move the mouse to preview elements, then click to inspect them.
  3. View the ownership result and expand it to see the evidence (such as React owner, package name, etc.).
  4. Perform actions: take a screenshot, copy HTML/Markdown, open the source location, or hide the element.
  5. Press the shortcut key again, modify the shortcut through settings, or manage hiding rules in the plugin configuration.

Applicable Scenarios and Notes

  • Applicable scenarios: Development and debugging scenarios where you need to quickly confirm the source of UI elements or hide interference from specific plugins or the host interface.
  • Limitations: This plugin runs with the permissions of the current DSH process. Ownership identification is based on a local evidence-scoring algorithm, not code signing or official auditing, so a confirmed result does not imply that a plugin is absolutely trustworthy. It does not support inspecting iframes, closed shadow roots, canvas-drawn content, or CSS pseudo-elements.
  • Version requirements: DeepSeek Harness >= 0.1.0-rc.8 < 0.2.0-0.

Summary

This tool uses local algorithms to solve the UI provenance problem under DSH’s plugin-based architecture, making it suitable for users who need fine-grained control over the interface during development and debugging.