AI Agent Hub
Back to plugins
🖥️

dsh-md-view

Client Updated 2026.09.01

Run the following command in DeepSeek Harness:

dsh plugin install joao-paulo-santos/dsh-md-view

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

Run dsh plugin install joao-paulo-santos/dsh-md-view within DeepSeek Harness to install this plugin (source: https://github.com/joao-paulo-santos/dsh-md-view), then restart the harness to start using the mdView service.

About this plugin

Client plugins in the DeepSeek Harness ecosystem often need to render Markdown across README displays, compaction journals, and quick-note pads, yet there was no single rendering entry point. Each plugin either hand-rolled its own parser or silently fell back to plain text. dsh-md-view closes that gap by injecting a mdView client service into the host so every plugin that needs Markdown rendering reuses one shared pipeline, with zero per-plugin styling or parsing maintenance.

Rendering runs through the Harness built-in MarkdownText pipeline, giving you GFM syntax, math formulas, footnotes, and Shiki-highlighted code blocks with copy buttons right out of the box. For document-specific needs the plugin additionally resolves raw tags into real images and rewrites relative link and image targets against the GitHub raw-content host. Fenced code blocks and inline code spans are left untouched to avoid conflicting with upstream highlighting. On the safety front, rendered output consists solely of React plain-text nodes; any raw HTML in the source is preserved as visible text, eliminating injection risks.

If you are building a DSH client plugin that needs formatted Markdown in READMEs, journals, or pads and want zero extra dependencies, no standalone UI, and no self-managed CSS, simply inject the mdView service. Existing plugins such as dsh-workspace-history and dsh-wo-github already use it as an optional renderer, gracefully degrading to plain text when it is not installed.

Use Cases

  • Unifying Markdown rendering across READMEs, journals, and pads in client plugins
  • Resolving raw tags and relative links to real GitHub resource URLs
  • Safely displaying GFM, math, footnotes, and highlighted code blocks with copy buttons

Best For

  • Developers adding Markdown display capabilities to DSH client plugins
  • Plugin teams wanting to reuse a shared rendering pipeline instead of hand-rolling parsers
  • Plugin authors who prefer zero extra dependencies and no self-managed Markdown CSS