AI Agent Hub
Back to plugins
🖥️

dsh-provider-badge

Client Updated 2026.08.19

Run the following command in DeepSeek Harness:

dsh plugin install marshfolx/dsh-provider-badge

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

Run dsh plugin install marshfolx/dsh-provider-badge to add the plugin (repo: https://github.com/marshfolx/dsh-provider-badge) to your DeepSeek Harness profile, then restart DSH to activate it.

About this plugin

When you juggle multiple model providers in DSH, switching models often means squinting at the selector text to figure out who is actually serving the request. dsh-provider-badge tackles exactly this: it renders a brand-recognisable visual mark right beside the composer model selector so you can confirm the active provider at a glance.

Matching is precise. DeepSeek gets a whale SVG, OpenCode Go renders a bold GO wordmark, OpenCode Zen a ZEN wordmark, and every other provider falls back to blocky initials. The badge subscribes to the model-selection plugin per-session store, so it repaints the instant the model changes. It also tracks the tool-row height, meaning DPI scaling and window resizing never leave the icon misaligned. Icon scale, vertical offset, and colour (including rgba half-transparency and CSS color-mix) are tunable permanently via TUNING_DEFAULTS or temporarily through the browser console; a hard refresh is all that is needed. The whole plugin is zero-build, zero-dependency, living in a single client.js file.

It is built for DSH power users who switch between DeepSeek, OpenCode, and several other providers daily, or for teams that want a single visual cue in the editor UI to eliminate the small-but-annoying friction of misidentifying the active provider.

Use Cases

  • Confirming the active provider at a glance when switching between DeepSeek and OpenCode
  • Sharing a DSH profile across a team with consistent brand cues to reduce mis-clicks
  • Keeping the badge aligned with the tool row after DPI zoom or window resizing

Best For

  • DSH power users juggling multiple model providers daily
  • Developers who want to minimise mis-clicks when switching models
  • Teams that value editor UI consistency and visual clarity