Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

1806 plugins found

H

dsh-plugins-sidebar-manager

hightoward/dsh-plugins-sidebar-manager

Sorts the entries of the DSH sidebar panel list into one or two levels of categories, draws a titled collapsible header for each group, and shows or hides each entry, all edited from a Plugin Sidebar page in Settings and mirrored to $DSH_HOME/plugins-sidebar-manager.json.

27 days agoUI EnhancementsMIT
H

dsh-PEC

huajikano/dsh-pec

Control a DeepSeek Harness session from an Android phone: pair over Wi-Fi or Tailscale, follow the live transcript, send prompts, switch model, mode and permission, browse workspace files, run a terminal and change settings.

24 days agoIntegrations & RemoteMIT
E

dsh-breeze-tts

eslaykey/dsh-breeze-tts

Breeze Blue text-to-speech for DeepSeek Harness: agent tools, reply playback, voice design and a settings page.

220 days agoVision, Voice & MultimodalMIT
B

dsh-siyuan-sender

baby7/dsh-siyuan-sender

Sends a Markdown file from the conversation into a self-hosted SiYuan notebook: a button on every delivered-file card and on the document-preview toolbar, or just ask the agent to send it, all through the SiYuan kernel HTTP API. Existing notes are never overwritten — a repeated title gets a timestamp suffix — and the API token stays in the host credential store rather than in settings files or the browser.

29 days agoTools & CapabilitiesMIT
J

dsh-linked-workspace

jiahui-huang1/dsh-linked-workspace

SSH-backed remote directories and linked local⇄remote workspaces: read-only remote browsing, an editable linked workbench, bidirectional SFTP transfer, mirroring and a linked_workspace tool. Sidebar pages require the dsh-better-sidebar plugin (v0.24+); without it only the Settings pages load.

22 days agoIntegrations & RemoteMIT
K

dsh-eni (armor-break)

konshinhaoshin/dsh-eni

Per-model jailbreak armor: a Settings table arms model patterns with spells (25 spells: 20 across 11 model families, plus a model-agnostic armor, an upstream preferences file and three stackable persona layers), previews the exact injected block, and writes it into the armed model's system prompt only, leaving every other model untouched.

216 days agoIntegrations & RemoteMIT
L

dsh-whalepaper

leriuslei/dsh-whalepaper

Animated ASCII orca-ocean wallpaper for DeepSeek Harness that follows local time, with native plugin settings for brightness, saturation and composition.

214 days agoThemes & AppearanceMIT
C

dsh-search-proxy

chaos-paradox/dsh-search-proxy

SearXNG web search with a managed local runtime, external instance support, Web settings, and an optional DSH process proxy.

221 days agoTools & CapabilitiesMIT
S

dsh-tri-model

starry-sky-blip/dsh-tri-model

Multi-model layered pipeline for DeepSeek Harness: a strong model plans, a fast one drafts, a third reviews, and a failed review is reworked automatically — endpoints, protocols, models and gates all configured from the DSH settings panel.

215 days agoModels & ProvidersMIT
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
Z

dsh-tide-theme

zdt3476/dsh-tide-theme

Deep-sea tidal-blue theme for the DeepSeek Harness Web client with a single accent color and matte (non-glass) surfaces in light and dark modes. Same-token UI additions: a single-line dock HUD reading real session projections (context usage vs. window, TPS, cache-hit rate, elapsed time), per-turn subagent delegation cards showing token usage and an optional cost estimate from OpenRouter public prices, sidebar pagination with pinned sections and type-to-filter, and model / reasoning-effort / permission controls under the composer. Each addition can be toggled in the plugin settings.

215 days agoThemes & AppearanceMIT
L

dsh-harness-autostart

lolitakawayi/dsh-harness-autostart

Adds one row to Settings → General with a switch that writes or removes a Windows logon startup entry for the DeepSeek Harness desktop app, and registers a dsh_autostart tool exposing the same status, enable and disable operations. Defaults to a single HKCU Run value, no admin rights; the startup-folder launcher mode adds an optional delay and launch arguments.

219 days agoDev & Plugin ToolsMIT
L

dsh-adapt-packs

lugabeeee/dsh-adapt-packs

Adaptation packs for third-party DSH plugin panels on phones — 44px touch floor, width reclaim, shell hit targets and floating-widget clearance — loaded by the dsh-mobile plugin from its extensions directory (dsh-mobile must be installed for them to take effect), with a settings page that installs them and a per-plugin compatibility list.

22 days agoUI EnhancementsMIT
N

dsh-agy-gemini-quota

nursatechstudio/dsh-agy-gemini-quota

DeepSeek Harness plugin for Antigravity Gemini quota monitoring in settings submenu agy-quota

228 days agoUsage & BillingMIT
Z

dsh-plugins (dsh-presets-zh)

zhiqiangme/dsh-plugins

Four Chinese agent presets in one plugin, Standard, PTC, Minimal and Creation (standard-zh, ptc-zh, minimal-zh, cordis-zh), each keeping the matching built-in tool set; Standard, PTC and Creation translate known host instructions into Chinese while tool IDs, schemas and SDK declarations stay unchanged; a settings page enables each mode and edits its name, description and system prompt.

213 hours agoWorkflow & AutomationMIT
1

dsh-video-skills

1368546410qq/dsh-video-skills

Browses the awesome-claude-video-skills catalog (373 entries) inside DSH settings and installs a chosen skill into ~/.claude/skills and/or ~/.dsh/skills: it downloads the GitHub archive of that repository and copies the skill directory, and executes no code from the repository. Installs run as background jobs with live progress (bytes downloaded, files copied) and can be cancelled; skills installed by the plugin can be uninstalled, while directories without its marker are left untouched. Rows show an approximate repository size reported by GitHub. The same actions are exposed to the agent as the video_skill_search, video_skill_install and video_skill_uninstall tools.

27 days agoSkillsMIT
M

dsh-ai-session-title

maouxy/dsh-ai-session-title

Generates a session title from the conversation with the session's own model, either from the /ai-title command or from a button in the rename dialog. Four title shapes (subject, action, subject + outcome, custom prompt) and an optional MM-DD prefix, all editable on the plugin's settings page.

220 days agoSessions & MessagesMIT
J

dsh-window-size

jue5hen/dsh-window-size

Set the startup window size of DeepSeek Harness Desktop from a settings page, with 4:3, 16:9 and 16:10 presets and up to 12 custom presets.

214 days agoUI EnhancementsMIT
S

dsh-insight

suguyun/dsh-insight

Chrome/Edge companion extension: select text on a page and click the badge to get a Markdown answer from dsh in the side panel or a floating card, with native multi-turn follow-ups; host-side tools let the agent read the current page, capture HTTP traffic and drive the browser. Fork of stuarthu/dsh-chrome (MIT): upstream supplied the bridge, browser tools and page injector, and this fork adds select-to-interpret, native multi-turn follow-up, in-panel settings and appearance options. It registers the same browser_* tool names as the upstream, so the two cannot be installed together.

216 hours agoTools & CapabilitiesMIT
Z

dsh-scribe

zcd0818/dsh-scribe

Cross-session memory and a per-workspace knowledge base in one plugin. Memories are plain JSONL under ~/.dsh/memory by default; each session starts with the relevant ones already in the system prompt and writes one back when it ends. A read-only kb/ folder per workspace plus one global folder is searched with results cited down to file lines. Eleven tools under a scribe_ prefix (seven scribe_memory_*, four scribe_kb_*), a /scribe slash command, and a settings page with overview, memory, knowledge base and migration tabs. Cloud backends (Bailian memory library, ChromaDB, cloud-primary with local mirror) are opt-in; moving data between them requires an explicit approval and is logged so it can be rolled back.

222 days agoMemoryMIT
J

dsh-prompt-library

jianhangly/dsh-prompt-library

Composer-side prompt library: a button next to the input opens a picker with group chips and word-split AND search over saved snippets, inserting one into the draft or appending it, filling {{variables}} before insertion, with 13 built-in templates. Snippets live in one local JSON file behind a rev lock, a per-save backup, and whole-library JSON import/export; a settings page handles editing, grouping, pinning and a 6-second delete undo.

222 days agoUI EnhancementsMIT
Z

dsh-rea-powerpack

zhishulo/dsh-rea-powerpack

Installs and verifies the reverse-engineering engines REA needs on Windows (Ghidra, JADX, apktool, adb, WABT, frida and more), pins the rea-agents MCP server version, and reports capability gaps in a settings card.

29 days agoTools & CapabilitiesMIT
T

dsh-subagent-route-pin

tkaiz0406/dsh-subagent-route-pin

Registers a wrapper provider that gives delegated subagents their own LLM route — one-off spawns through provider.start, Agent Teams members through a hook on startActivation — while the main agent keeps its model. Ships a Settings section for picking that route, a per-expert override file, a capability flag reporting which seams the hook caught, and a readiness record written at mount.

26 days agoModels & ProvidersMIT
K

academic-agent (academic-dsh-ui)

kw78/academic-agent

DSH sidebar and panel for courses, tasks, plans, connections, course materials, automation and settings.

221 days agoUI EnhancementsApache-2.0