Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

471 plugins found

M

dsh-hu-tao-skin

mistyrain-field/dsh-hu-tao-skin

A Genshin Impact Hu Tao (Wangsheng Funeral Parlor) skin for the dsh web GUI - a 14-token ink-black, crimson and amber palette, falling plum petals and spirit butterflies, a plum-blossom brand mark, and a floating petal toggle that tracks the sidebar.

32 months agoThemes & AppearanceMIT
C

dsh-router-ext-rtk

carvin94/dsh-router-ext-rtk

RTK (Rust Token Killer) extension for dsh-router: rewrites each bash tool call through `rtk rewrite` so the agent reads compressed command output, and falls back to the original command when rtk is missing or has no equivalent.

319 days agoTools & CapabilitiesMIT
R

dsh-plugin-opencode-omo

royenheart/dsh-plugin-opencode-omo

dsh plugin + agent preset that replicates opencode + oh-my-openagent (omo): opencode's toolchain and system prompt, omo's multi-role subagent orchestration, and browser-side omo role selection + per-role model/fallback settings.

32 months agoWorkflow & Automation
Y

dsh-loop-continue

yunxiyang/dsh-loop-continue

Resumes an agent turn that ended after narrating its next action without calling a tool: the guard replays the turn log on agent/turn-stopping, asks a judge model one true/false question, and steers the same turn to run one more step.

32 months agoMemoryMIT
H

deepseek-whale-wallpaper

heshen-1/deepseek-whale-wallpaper

Live dot-matrix whale wallpaper for the DSH Web UI: ~1,750 breathing WebGL2 particles with pointer liquid vortices, light/dark themes, and a Canvas2D fallback.

32 months agoThemes & AppearanceMIT
C

dsh-web-search-aggregation

chendefine/dsh-web-search-aggregation

Aggregated web-search provider for the built-in web_search tool: one prioritized queue over nine providers (AnySearch, TinyFish, Tavily, Brave, Exa, Firecrawl, Jina, SerpApi, Serper), with multi-key rotation per provider, ordered fallback on failed attempts, and a live settings card.

32 months agoTools & CapabilitiesMIT
L

dsh-plugin-heartbeat

littleblacktong/dsh-plugin-heartbeat

Autonomic heartbeat for each root agent: silent pulses diff the session's todos, Agent Team board and goal against what the last pulse saw, and speak only on a signal — L1 report, L2 ask (ask_user_question), L4 escalate — never starting work. Each message carries a why-now line, an optional one-line physiology signature (time since your last message and how many times it has reached out today) and a compact task snapshot (800-char cap); a dedupe window, quiet hours, a daily budget, refractory/restart cooldowns and persisted vitals keep it quiet, while busy-safe followup injection never stacks. It shares one advisory speech floor with dsh-plugin-memory (~/.dsh/proactive-cooldown.json, 180 s) so the two never talk over each other, stays silent while a child subagent or teammate is still working, and surfaces a "subagents working · N" pill in the conversation header (polling pauses while the tab is hidden). v0.8 adds a diagnostics panel that explains recent quiet pulses and names the current speech-floor holder, plus panel controls for the arbitration window, presence suppression and the physiology line; its settings section carries a stroked heart mark (16×16, stroke 1.3, same spec as dsh-plugin-memory). v0.8.1 makes the plugin compatible with DSH 0.2.2-rc.2: the agent registry is read with agents.roots() when available and falls back to agents.list() on rc.2, and every agent/created listener is exception-guarded — on rc.2 an unguarded throw there rejects agent registration and no session can be created, so rc.2 users must upgrade to 0.8.1 or newer.

35 days agoWorkflow & AutomationMIT
C

dsh-deepseek-chat

coldcgh/dsh-deepseek-chat

Web chat entry for DeepSeek Harness: a sidebar button opening chat.deepseek.com in a dedicated desktop window under dsh-desktop, with in-webview fallback for plain web environments.

33 months agoUI EnhancementsMIT
S

dsh-yolo-mode

severuszh/dsh-yolo-mode

LLM auto-approval for sandbox escalation requests, with presets and a fail-closed fallback.

328 days agoSecurity & PermissionsMIT
J

dsh-polyglot

jesse-njx/dsh-polyglot

The model switch for DSH: point it at any OpenAI-compatible endpoint, with curated free/cheap DeepSeek provider presets and automatic fallback when a free tier rate-limits you.

33 months agoModels & ProvidersMIT
H

dsh-gatekeeper

huajikano/dsh-gatekeeper

Inspects the model's streamed reply before it is committed and either discards it or holds it for review when it reads as a refusal, so that text does not stay in the session context. Detection combines built-in phrase rules (an opening refusal, a capability denial, policy wording, first-person intent, refusals quoted in reasoning) with a plain-text word list and optional regular expressions. Interception can sit at the llm/stream waterfall, at the HTTP fetch layer before encryption (not TLS decryption, and it cannot tell which session a call belongs to), at both, or in a preview mode that shows a transient preview while the original chunks stay in memory until the whole reply has been checked. The same plugin also guards tool calls on tools/pre-execute: a command that deletes a drive, filesystem or user-profile root, formats or repartitions a volume, empties the Recycle Bin, fetches and executes a remote script, or writes to a raw device is denied, and a recursive delete outside build directories is recorded by default. Each tier can be set to deny, ask, record, or off, and the disk guard has its own switch. Both halves are heuristics: they can miss phrasings, the disk guard sees the arguments of a call rather than what a running script does, and they fail open.

23 days agoSessions & Messages
C

dsh-bilibili-radio

cestbonn/dsh-bilibili-radio

Sidebar radio that plays Bilibili audio with search, playlists, scrolling lyrics (looked up on music.163.com, kugeci.com and lrclib.net), and chat-driven song picks. Runs a local audio proxy on 127.0.0.1:13210 and, when the system resolver fails, DNS lookups in the whole DSH host process fall back to public DoH servers (1.12.12.12, 223.5.5.5).

29 days agoVision, Voice & MultimodalMIT
G

aurabot-qq-mac

geng-zy/aurabot-qq-mac

macOS (Apple silicon) fork of aureth-labs/dsh-aurabot-qq: the same QQ persona bot (chat, voice notes, stickers, memory, song covers, modules) with the Windows-only code removed. It connects to a OneBot v11 gateway such as SnowLuma running in OrbStack or Docker, falls back to the macOS `say` voice, sends files over 30 MB to a containerised gateway through a loopback-only temporary download link, and installs the song-cover environment (Applio, audio-separator, uv, Rubber Band, separation models) at pinned versions. It keeps the upstream package name and plugin id (dsh-aurabot-qq), so it replaces upstream and cannot be installed alongside it; use upstream on Windows.

215 hours agoIntegrations & RemoteMIT
C

dsh-big-fish-speak

chaowei08/dsh-big-fish-speak

Makes the dsh-pet desktop pet read model replies aloud in its own configured voice. Newer dsh-pet gets the whole text in one request (up to its 500-char cap); older versions automatically fall back to 60-char chunks. Each piece is verified against the pet log to confirm it actually played.

24 days agoVision, Voice & MultimodalMIT
G

dsh-github-radar

goodboys155/dsh-github-radar

Right-sidebar GitHub panel with four rising-repository lists — created within 2 days, 7 days, 30 days, and 20k+ stars still pushed — where the first three are ranked by star velocity (stars per day) rather than total stars, so repositories that gained traction fast surface above older ones with more stars. Each row shows the repository name, its own description, language, the stars-per-day rate and up to two topics, and links to the repository. A keyword search box queries the GitHub Search API directly, debounced and IME-aware so a Chinese or Japanese composition costs one request instead of one per keystroke. Reads the public GitHub Search API anonymously: no token, no login, no account, nothing else contacted. Lists cache for 30 minutes and search results for 5; outbound requests go direct first and fall back to a listening local proxy port only if direct fails.

29 days agoUI EnhancementsMIT
W

lit-report-ppt

wld12314/lit-report-ppt

Turns one journal paper PDF into a Chinese group-meeting literature report deck (.pptx) in the Nanyang Normal University physics template, plus a matching Word speaker script. Requires Python 3 with python-pptx, python-docx, Pillow and pymupdf (pypdf fallback); install them with pip install -r requirements.txt.

28 days agoSkillsMIT
L

dsh-intent-recognition

lilixinsniper/dsh-intent-recognition

Five-layer intent recognition pipeline (rules, pgvector retrieval, Jev scoring, fine-tuned arbitration, LLM fallback) with scenario management UI, PostgreSQL storage and distributable API services.

213 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.

216 days agoModels & ProvidersMIT
F

dsh-poke

fssama/dsh-poke

DSH 插件:agent 提问时自动把 DSH App 顶到前台,失败则发通知兜底。Focused foreground + notification fallback for DeepSeek Harness.

22 months agoIntegrations & RemoteMIT
C

dsh-plugins (dsh-next-git)

caozeal/dsh-plugins

Git tab in the DSH web UI right sidebar for the current session repository — switches branches from a dropdown of local and remote branches (with ahead/behind counts), stages files in staged/unstaged/untracked/conflicted groups, commits, fetches, pulls and pushes with automatic upstream setup, drafts a Conventional Commits message from the staged diff with the default model and falls back to a plain chore message when none is available, and renders git log --graph with per-branch colors plus a word-level highlighted diff.

218 days agoGit & Code ReviewMIT
S

dsh-everything

s1n7t/dsh-everything

Whole-disk file search tool backed by the local Everything (voidtools) index: millisecond path queries for the agent over a loopback-only HTTP fast channel with es.exe fallback, plus verified auto-install of the latest stable Everything + ES CLI backend (signature-checked, proxy-aware). Windows only.

220 days agoTools & CapabilitiesMIT
Z

dsh-notes-plugin

zxy0902/dsh-notes-plugin

Notes and folder reader in the main panel: a file tree with pinned files, closeable tabs, Markdown split edit/preview with synced scrolling, plain-text editing, manual save, and drag-to-move. Deleting a file moves it to the system trash where one exists (macOS, Linux), falling back to an in-folder dsh-notes-trash directory; Windows has no delete entry.

211 days agoTools & CapabilitiesMIT
S

dsh-plugin-deepsearch

seaviod/dsh-plugin-deepsearch

Switch DSH's built-in web_search between the DeepSeek Search API (/v1/tools/search) and the default account search, with automatic fallback, a settings page and a sidebar switch.

2last monthTools & CapabilitiesMIT