Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

392 plugins found

X

dsh-instance-manager

xswt442-cmd/dsh-instance-manager

Instance manager for DSH Web: a Mini Utility Dock panel that lists every local dsh web instance the machine can see (port, PID, uptime, live session count, resident memory, version), starts a new instance on an automatically picked free port in 3080-3129 or on a port you name, opens a row in a new tab, and stops one or all of them through that instance’s own graceful shutdown (appExit). Rows also show what each instance is serving, and read-only instance logs and session summaries are one click away. Where a peer is configured, the same panel lists and queries instances on other machines over a bearer-authenticated link. Every route is loopback-guarded, and a browser-facing action must additionally pass the host’s own browser authentication.

44 days agoDev & Plugin ToolsMIT
W

dsh-remote-ssh-ops

weisiren000/dsh-remote-ssh-ops

SSH remote ops for DSH: pair servers over SSH or a one-time-code remote-hostd, then run commands, manage background jobs, and read or write remote files with reviewable changes (host_pair/host_bash/host_jobs/host_read_file/host_write_file/host_review_changes).

43 months agoTools & Capabilities
T

dsh-model-visibility

tzyceng/dsh-model-visibility

Manage which models appear in the composer model menu. A settings page lists every provider's models with a per-model switch, provider-level show/hide, collapsible groups and filters by kind; switched-off models leave the menu while the model in use in the current session stays. The list can be searched by name or ID and filtered by capability (multimodal, reasoning) and by minimum context window (128K / 256K / 512K / 1M). Rows show the model kind, and chat models also show reasoning support with the adapter's effort levels, their context window and input modalities. Labels merge manual overrides, the settings document, the adapter, the relay's GET /models response, a built-in pi-ai / models.dev catalog, name inference and vendor corrections in that priority order, with the source named on hover and dashed borders marking inferred values. Any model can be edited by hand (kind, context window, modalities, effort levels); those edits are stored outside the profile and can be written back into the model provider's settings. A hard re-fetch drops every cache and asks the adapter and all relays again. A switch, on by default, lets relay routes whose models declare text-only input accept images in memory, without editing configuration files. The hidden list is stored in the profile patch and mirrored to $DSH_HOME.

3yesterdayUI EnhancementsMIT
3

dsh-cookie-guard

3150481853/dsh-cookie-guard

Windows-only. Counts the dsh-auth-* login cookies the DSH desktop shell has accumulated, shows how much of the 16 KiB request-header budget they eat and how many launches are left before the shell stops opening with "desktop welcome: Web authentication failed". The web UI gets a draggable floating card that re-checks every 10 minutes, keeps one snapshot per local date and can refresh on demand; a standalone Windows checker ships in desktop/.

321 days agoUsage & BillingMIT
R

dsh-plugins (dsh-drafts)

romany-saad/dsh-plugins

Get back what you typed and walked away from: a new Web conversation you leave before sending never appears in the sidebar, so its draft is out of reach. This plugin lists those drafts above the composer of the next new conversation, newest first, with their workspace and time; Open takes you back with the text and chips in place, and Discard drops one, with Undo.

322 hours agoUI EnhancementsMIT
0

DeptAI-UI-DSH

01men/deptai-ui-dsh

A collaboration front-office for AI agents and humans — department boards, tickets, approvals and industry calculations run inside the DSH conversation and panel, so agents do the work in chat while humans stay accountable in the panel. It calls the 01men/ybkkasi governance base over existing contracts (asset ledger, IAM, OIDC SSO, RBAC and scene-level authorization) instead of re-implementing governance. Ships as a Cordis bundle and mounts at /gate01; the selftest suite is green on every push. Do not install this and 01men/ybkkasi as dsh bundles in the same profile: both register the ops-platform-core / ops-iam / ops-authn rows. Requires DSH >=0.1.0-rc.7 <0.2.0.

315 days agoUI EnhancementsMIT
A

dsh-protect-generated-files

acus9345/dsh-protect-generated-files

DeepSeek Harness plugin that stops hand edits to generated files (lockfiles, protobuf/codegen output, files marked @generated or DO NOT EDIT) and tells the model which source to edit and what to run instead.

326 days agoSecurity & PermissionsMIT
S

dsh-cherry-bridge

saxem1997/dsh-cherry-bridge

Bridge DeepSeek Harness sessions to Cherry Studio desktops over the LAN - QR pairing, 15 cherry_* tools for agents, sessions, history and interactions (including uploading local files as attachments and reading desktop-uploaded images back as image blocks), a settings page for devices and per-workspace tool scope, and an experimental subagent that delegates the way DSH's own subagent does (Claude Code / Codex style) with the child running on a Cherry Studio agent.

3yesterdayIntegrations & RemoteMIT
D

dsh-im-union

drscrewdriver/dsh-im-union

Union IM bridge for DSH — an independent implementation uniting the capability sets of community peer plugins (xmanrui/dsh-im, MichengAI/dsh-im-connect). Drive your agent session from 15 channel adapters across 12 platforms (including email; WeCom/DingTalk/QQ each contribute two: bot + self-built app or notify tier) — WeChat (official iLink QR bind), Feishu/Lark (long-connection + streaming cards; the voice tier requires system ffmpeg), Telegram, Discord, WeCom intelligent bot & self-built app (signed callback), DingTalk (stream + AI Card and custom-robot notify), QQ official bot (plus notify tier), Slack (Socket Mode), WhatsApp (Baileys QR pairing; the dependency ships as an optionalDependency of the plugin package), Matrix, iMessage (macOS only), Email (IMAP/SMTP thread routing). The cross-version narrow waist auto-adapts settings gen1/gen2/gen3 across hosts 0.1.2-rc.1→0.2.1-rc.2 (12-tag enum; rc.2 verified by a real desktop-profile install with double read-back) using capability probing only, never version branches. In chat: a 25-command panel, tool-approval and question loops answered in the originating chat (deny-by-default, initiator-only, 5-min expiry), image/file input gated on host model metadata, deliverable file return, a delivery log with bounded retry (uncertain is never re-sent), proactive delivery and fragment composition. It also splits the native sidebar into self-owned Tasks / Channels tabs (standing down entirely when another plugin already owns the slot), registers an `im-concise` agent preset plus reply sanitisation that keeps GenUI fences and raw HTML out of text-only chats, renders `svg` fences to PNG images, guards model choice with an allowlist, and mirrors each turn's final answer to notify channels via `/relay` (addressed by account ID or alias, never guessed on ambiguity). Secrets are one-way into the vault and never echoed back. npm: `dsh-im-union`.

35 days agoIntegrations & Remote
A

dsh-plugin-memfuse

a1141171521/dsh-plugin-memfuse

Long-term memory for DSH stored as plain Markdown. Real user/assistant exchanges are captured into daily session files without a model call; an LLM pass then distils them into memories that are injected into the system prompt each turn. Retrieval is local (CJK bigram + BM25) in three levels — index, summary, full text — so the model only pays for the detail it asks for. Memories carry priorities; P0 and user-written entries are never changed automatically, and forgetting marks an entry stale instead of deleting it, so the whole chain stays auditable in status.md. Six tools cover recall, write, status, extract, feedback and the skill library; when a cluster of memories is ready to become a skill, a card appears at the end of the turn, writes the SKILL.md on click, and installs it only after you approve. Learning is on by default and follows the conversation model; turning the master switch off stops the LLM entirely while capture keeps working. Failures are surfaced in the prompt and in status.md instead of being swallowed. Pure JavaScript, no third-party runtime dependencies beyond the harness packages.

319 days agoMemoryMIT
X

dsh-user-memory

xinzeqing/dsh-user-memory

White-box memory in two parts: four user-authored long-term tiers (must-follow rules, behavior settings, user profile, optional rules) injected as one system-prompt section, plus a separate temporary working set (cross-session handoffs, stage goals, waiting items) with its own 1200-character budget that stops being injected once an entry is done. The long-term tiers are plain Markdown files the user can read and edit; the agent can only propose them, and nothing is written until the user accepts in the Chinese panel. Temporary entries are written only when the user explicitly asks, and live in <DSH_HOME>/temp-memory.json (created on first write), not in the memory directory. No auto-capture, no background writes, no network.

37 days agoMemoryMIT
K

dsh-plugin-stardeck

kaiji-z/dsh-plugin-stardeck

An RTS-style orchestration dashboard where commands replace chats: a resident commander agent decomposes each order into task briefs with acceptance criteria, typed subagent troops (recon/engineer/medic/scribe) execute them across isolated workspaces, and every session is indexed by the order that started it.

37 days agoWorkflow & AutomationMIT
F

dsh-stool-plugin

fufengyuan/dsh-stool-plugin

Nine consolidated tools that give agents full access to the stool ops CLI: server management, database query/redis, log search/tail, CI/CD deploy and history, MFA codes, git operations, notes, todos, and misc utilities (accounting, weekly reports, audit, project listing, nginx presets).

32 months agoTools & CapabilitiesMIT
S

dsh-docker

stardustlc666/dsh-docker

Docker tools for agents: ps/images/logs/inspect/exec/manage/health with JSON output, env-configurable CLI path, approval-gated exec and zero runtime dependencies.

3yesterdayTools & CapabilitiesMIT
S

dsh-dingtalk

stardustlc666/dsh-dingtalk

DingTalk group-robot notifications (notify/text/health; webhook + HMAC signing, zero runtime dependencies).

32 days agoIntegrations & RemoteMIT
S

dsh-slack

stardustlc666/dsh-slack

Two-way Slack messaging (notify/channels/inbox/reply/health) over Socket Mode, no public callback needed.

32 days agoIntegrations & RemoteMIT
L

dsh-ops-kit

lesliewylie/dsh-ops-kit

Evidence-first operating kit: six read-only tools (capability catalog, staged workflow plans, packaged skill reader, bounded local memory search, repository release audit, release checklist) and five packaged skills - plans and audits, never remote writes.

33 months agoWorkflow & AutomationMIT
C

dsh-connect-doubao-plus

chsw-cc/dsh-connect-doubao-plus

Fork of Wahwayhale/dsh-connect-doubao that connects a Doubao account to DeepSeek Harness as a model provider after one browser QR sign-in. Keeps the upstream menu-driven model discovery, composer billing multipliers, per-model thinking ladders, task-mode models on paid quota, chain-of-thought passthrough, Seedream image generation and read-only quota panel, and adds a daily check-in that can claim the reward and re-claim it on a timer, monthly and incentive quota windows instead of the fixed five-hour and weekly ones, a model picker that offers exactly the models ticked in the settings card, Windows / macOS / Linux session sealing, and stream hardening: a rejected conversation is never reused, the same-turn fallback opens a fresh one, three consecutive upstream failures trip a local circuit valve, and an interrupted stream stops the server-side generation.

215 hours agoModels & ProvidersMIT
A

dsh-rea-pro

acuteszw/dsh-rea-pro

Mounts REA's reverse-engineering MCP toolset in DeepSeek Harness behind a composer chip; it starts off after install, and switching it on registers the server while switching it off withdraws the tools and stops the MCP child process so idle sessions pay no context for them.

23 days agoTools & CapabilitiesMIT
Z

dsh-plugins (dsh-opencode2api)

zhiqiangme/dsh-plugins

Runs the standalone opencode2api backend (jasonxu114514/opencode2api, Windows x64/ARM64, no Docker or OpenCode CLI) with DSH and on exit stops only the process it launched; its settings card installs, updates or rolls back the backend from checksum-verified GitHub releases, copies the initial admin password and syncs /v1/models into an opencode2api provider with context, vision and reasoning efforts, re-syncing every 10 minutes. Frozen archive: 26.10.31 is the last version, and the author points to dsh-magpie as the replacement.

218 hours agoModels & ProvidersMIT
S

dsh-windows-computer-use

shinji00222/dsh-windows-computer-use

Windows computer use for DSH built on a native C# engine: text-only DeepSeek models can read UI Automation controls and fill forms in verified batches without screenshots, stale control refs can be re-found by unique identity, CAPTCHAs and verification codes are refused and handed back to you through the DSH approval prompt, and Esc stops the turn at any time. A derived project based on Yu-tao-Li/dsh-computer-use-win; do not install it together with that upstream plugin, since both drive the same desktop.

214 days agoTools & CapabilitiesMIT
L

dsh-local-trim

leonlee114514/dsh-local-trim

One-step local model onboarding plus a light harness for DSH. On load it probes loopback and private-network inference endpoints (llama.cpp, Ollama, vLLM, LM Studio), reads each model's context window and output budget from the backend, and registers the provider through settings, so a local model becomes selectable without hand-writing config. It then trims only that provider: masks the tool list through tools.restrict, drops named system-prompt sections and memory contexts, swaps the injected instruction block for a short one while preserving its first 80 and last 96 characters, and truncates tool-schema descriptions without touching structure or required fields. Cloud providers are returned as the same assembly object, untouched. The injected block is re-read from disk on every assembly, so editing the file takes effect on the next request with no reload. The panel in the plugin detail page is a live operations view: it shows whether the takeover is active and by which hook, how many characters the last assembly was trimmed from and to, and which providers are online (probed concurrently, with a real one-shot completion reporting latency and reply text per provider). If a local backend is not running, the panel offers a one-click launch: it probes the port first (never starting a duplicate), then starts the matching server (ollama serve, or a custom command you supply) detached and polls until the endpoint answers, clamping the wait to 3-600 seconds, reaping the child it just spawned if it never answers, and naming the paths it searched when it cannot find the binary. A stop button kills backends this plugin started (SIGTERM, then SIGKILL) and refuses to touch a server somebody else launched. When a model has just been downloaded and no backend exists yet, the panel can also scan the machine for .gguf files with hard caps (300 models, 20000 directory entries, Downloads only one level deep), start llama-server on the chosen one (skipping the .mmproj. vision projection and reusing a server that already answers), register the provider under the model id the backend reports, and run one real completion to prove it works. Before spawning anything it does a fit check that counts only the part of the file the GPU cannot hold: hostBytes = fileSize - VRAM, compared against max(total RAM - 2GB, free RAM). A file far larger than RAM is refused outright; a heavy host-side remainder is refused unless you confirm; the same remainder under mmap is only a warning, because the weights land in reclaimable page cache. A load-mode selector (auto / mmap / none / mlock / mmap+mlock) maps to llama.cpp --load-mode, and the default is whatever the engine picks. From 0.4.2 everything above is derived from the platform instead of assumed: home and data directories come from os.homedir() and the OS conventions (LOCALAPPDATA on Windows, ~/Library/Application Support on macOS, XDG_DATA_HOME elsewhere); backend binaries are looked up in the official install locations of each OS and can be pinned with OLLAMA_BIN, LLAMA_SERVER_BIN, VLLM_BIN or LMSTUDIO_BIN; model discovery walks DSH_LOCAL_MODELS_DIR, ~/models, ~/llama.cpp/models, ~/.cache/llama.cpp and the LM Studio data directory, with the WorkBuddy layout demoted to one candidate among them. VRAM is asked from nvidia-smi, then rocm-smi, then sysctl hw.memsize on Apple Silicon (flagged unified, so the same bytes are not charged twice), and any flip to a unified-memory budget is handled explicitly. Before building a command line the plugin runs llama-server --help once and keeps only the flags that build actually has, so older engines get --n-gpu-layers 99 and no KV quantization while newer ones get auto plus q8_0; anything it cannot probe is passed through rather than dropped. LM Studio is started with lms server start --port N rather than being lumped in with the engines that need a model argument, and vLLM gets its own --model example instead of llama.cpp syntax. Windows, macOS and Linux are all exercised in CI, including a windows-latest and a macos-latest job, because a cross-platform claim that has only ever run on one OS is not a claim. Two of those suites exist specifically to catch this machine's blind spots: one replays the whole suite with process.platform rewritten to each OS, and one deletes every advantage this development box has — no nvidia-smi, no rocm-smi, no sysctl, an empty PATH, a home directory with no models — and requires graceful degradation rather than a crash. That last one caught a real class of bug: several assertions hardcoded 'lms.exe', which cannot pass where the executable has no suffix. Measured on the reference machine: a 16.9GB 27.2B MoE with 14.5GB of VRAM holds a 285-691MB working set and sustains 76 tok/s after a 1000-2000 token warm-up, so file size alone is not a fit signal. From 0.4.3 the scanned models are shown as a table rather than a dropdown (one row per gguf, with its size and any fit warning), so you can see what is on disk before choosing. From 0.4.4 the delete button on the provider table removes the provider entry, not the weights file on disk. That distinction matters: what people actually want to clear out is the dead entry - one pointing at a port that never answered, one registered twice for the same port, one whose model file was deleted long ago - not a 15.8GB gguf. Deleting a config is undone by importing again; deleting a gguf is not. The removal goes through settings.mutate with an unset op on \['providers', id], because update merges layers: writing null there leaves a null provider key that the loader reads as a broken config rather than an absent entry, and only mutate/unset is implemented as Reflect.deleteProperty. The result is read back afterwards, because unset on a key that comes from a lower layer (the profile cordis.patch.yml or a home patch) does not delete it - it restores the inherited value, so the call succeeds while the entry stays. When the entry is still there the panel says so and points at the file to edit instead of reporting success, and a DSH whose settings service predates mutate() is told plainly rather than silently ignored. Deleting takes two clicks and clearing the confirmation is as easy as clicking another row; on success the online and baseURL caches are cleared and the tool surface is recomputed, since the provider list changed. The gguf itself is never touched by this plugin - the scanned-model table is display and selection only.VRAM reporting is driver-dependent. From 0.4.5 model discovery also reads Ollama's own storage: its blobs are named sha256-… with no extension, so extension matching could never list them. Weights are now accepted by extension OR by GGUF magic header (only dot-free files of at least 8MB, capped at 600 header reads per scan; obviously-not-weights extensions like .json/.md/.safetensors/.part are never opened). Ollama models are resolved from their manifests: the model layer is picked by mediaType application/vnd.ollama.image.model (never adapter/mmproj layers), the human-readable name is restored from the manifest path (…/qwen3/8b becomes qwen3:8b, …/latest stays bare), tags sharing one blob merge into a single row, and the metadata kv supplies name, quantization and context length. Adopting an Ollama model does not start a duplicate llama-server over the same weights: it confirms ollama serve answers on 11434 (launching it if not) and registers the provider under the tag the endpoint itself reports — the blob's sha256 name would never match anything, since 11434 lists qwen3:14b, not sha256-a8cc…. Two real-machine-only traps fixed on the way: existsSync('<file>/') returns true on Windows, so manifest-vs-directory branching now goes by parseable content instead of trailing-slash semantics; and the quantization label table had been copied from a stale ggml enum generation, labelling ggml_type 15 as Q5_K_S while ollama show reports Q4_K_M. Same-blob dedup is by (dev,ino), keeping whichever entry has a name. Verified on the reference machine: the scan goes from 1 row to 4 — qwen3:14b (8.64G) and qwen3:8b (4.87G) now appear with Q4_K_M badges — in 4ms; npm run verify exits 0 (launcher 57, portable 35, panel-host green including the linux/darwin simulated-platform runs); the new panel-host suite builds a real miniature Ollama store in tmpdir and points OLLAMA_MODELS at it, so results no longer depend on whether the test machine happens to have Ollama installed. From 0.4.6 the panel shows each model its real name instead of its file name, because some download tooling stores every weight under one generic file name, leaving the real name only inside the GGUF header. The scan now reads each file GGUF KV section - not a fixed-size head buffer, because tokenizer.ggml.tokens (hundreds of thousands of strings on a large MoE model) and the chat template push general.file_type past any window; and GGUF string arrays are interleaved (u64 length plus payload per element), so treating them as a length table walks the cursor off the rails and produces astronomically large reads. Reading and skipping are accounted separately: key names and types are always read, string values over 256KB and string arrays are only walked past without copying, non-string arrays over 64 elements are skipped outright, and a cursor past the file size stops the read, because an out-of-range position means the cursor is wrong rather than that a limit should be raised. The displayed name goes Ollama tag, then general.basename plus size_label, then general.name, then the file name, with the full string kept for the hover text since it usually carries internal build numbers; mmproj files are now identified by general.type as well as by name. A short read (truncated file) no longer feeds half a value into the parser. On the reference machine, reading one file header parses 44 keys in about 16ms, and a whole scan takes about 31ms. From 0.4.7 the smoke test no longer fails the first time and passes the second. The old code gave both request attempts one shared AbortController and one shared 30-second timer, so the total budget covered both rounds: a cold load of a large model burned it in round one, the abort left the signal permanently aborted, and the second round (the Ollama-style reasoning_effort: none retry) could not even be sent - which is exactly why the first click returned This operation was aborted and the second succeeded. Now each attempt gets its own controller and timer, a timeout retries once automatically (retryOnTimeout, on by default) because a first-request timeout almost always means the weights are still being read from disk, and non-timeout errors (refused connection, HTTP error) are not retried at all. Timeouts report themselves: the message says the wait exceeded smokeTimeout, whether a retry already happened, and points at the new smokeTimeout setting (seconds, default 60, clamped to 5-600) - port responding is not the same as tokens coming out, so it is a separate knob from launchTimeout. Unrelated: an example naming one specific model was dropped from the panel copy, since not every machine has that model downloaded, and the explanation now describes the mechanism instead. From 0.4.8 adopting a plain .gguf no longer registers an unrelated Ollama model. The port field used to follow the last click rather than the file: selecting an Ollama entry moved it to 11434, selecting a plain .gguf did not move it back, so a 11434 left over from an earlier click stayed. The server accepted it as given, probed the port, found Ollama answering and borrowed it (the skipped-launch log line about the port already answering is this path), and then the model id - derived from the file name - could not be matched against Ollama's /v1/models, where the fallback was to grab the first entry in the list. Embedding models tend to sort first, so the adopt registered a model the user never selected. Now the port follows the file: a plain .gguf landing on another engine's port (ollama 11434, vLLM 8000, LM Studio 1234) is moved to 8090 and the panel says so. Only ports belonging to a known engine are overridden - a hand-typed 9999 aimed at your own llama-server is left alone. The model-id fallback no longer guesses either: it takes the only entry when there is exactly one (a single-model backend may legitimately report a different id than the file name) and otherwise reports an error listing the ids it did see, rather than registering a wrong provider. From 0.4.9 the panel can no longer vanish. It used to be possible for the whole section to disappear from the plugin detail page while the host stayed up, the HTTP bridge kept answering, and no crash log appeared. The cause was a scope error: a helper was declared inside one component and referenced from another, which is valid JavaScript and passes a syntax check, so it only threw at render time - when the user pressed the scan button and React ran the state updater. The host wraps every slot entry in an error boundary whose fallback is an empty anchor, so the throw was contained silently: the panel was not uninstalled or crashed, it was replaced by an empty div. The helpers now live in the module scope both components share. The client half also gained its own test - a minimal React stand-in loads the real panel module, really calls the components, really runs the state updater at render time, and presses the scan button, so this class of error can no longer reach a release.

22 days agoModels & ProvidersMIT
G

dsh-auto-rerun

good-saltfish/dsh-auto-rerun

Automatically retries model failures (drops, timeouts, rate limits, 5xx) in-turn. Retry count, delays, backoff, fallback and more are configurable. Rate-limit backoff is capped and jittered, server retry hints are honored, and optional retry-until-success keeps going within a time ceiling. Every option is editable from the plugin config or the sidebar panel: retry count, initial and max delay, backoff factor and jitter, rate-limit delay window, retry-until-success ceiling, fallback trigger and switch cap, dead-route blacklist TTL, log file. When a route keeps failing it can switch to a pinned, allowlist-filtered, or catalog-picked alternate model route, with a 30-minute dead-route blacklist (auth failure, subscription expired, billing) and a stale-assembly guard that keeps retried requests on the switched route. Ships a right-sidebar panel with live retry state, route labels and incident counters, Chinese and English locale, and memory-only logging by default.

219 days agoModels & ProvidersMIT
X

dsh-kon-fee-widget

xiao2236/dsh-kon-fee-widget

K-ON! themed tea-table widget: click it to see the DeepSeek balance, today's spend and peak-hour state; each finished turn pops a cost bubble; double-click shows zh/ja character lines.

29 days agoUsage & BillingMIT