Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

1011 plugins found

I

dsh-agent-team-room

ishuowang/dsh-agent-team-room

Coordinate independent DSH Sessions and provider-backed members without merging their histories, using persistent native Rooms with identity-bound leading `@` mentions, direct delivery, broadcasts, and leader-scoped controls.

43 months agoWorkflow & AutomationMIT
M

dsh-win-notify

muziisabel/dsh-win-notify

DSH 插件:代理任务完成时弹出带声音的 Windows Toast 通知,点击通知即可直接切回并前台显示 DSH 标签页

43 months agoIntegrations & RemoteMIT
J

dsh-stream-rules

jiesou/dsh-stream-rules

Inject rules when needed, without wasting context. DSH port of opencode-stream-rules.

43 months agoWorkflow & AutomationMIT
0

dsh-verification-receipt

030611/dsh-verification-receipt

Writes local JSONL summaries of per-turn tool counts and coarse verification signals without storing prompts, tool arguments, or result text.

421 days agoSecurity & PermissionsMIT
S

dsh-dungeon-master

superchipper/dsh-dungeon-master

QQ Bot channel and D&D 5e Dungeon Master plugin for DeepSeek Harness (fork of @tencent-connect/dsh-qqbot; do not enable alongside upstream): /dnd runs turn-based campaigns with 19 `dnd_*` tools for dice, checks, grid positioning, fog and battle maps, story chronicles, snapshot rollbacks and an optional dedicated combat subagent, plus /persona per-chat switching with handoffs, shared Markdown notes, sticker collection, read-only Bilibili tools and per-chat tool-access gating. Direct and group chats default to open in cordis.patch.yml while non-allowlisted QQ chats are blocked from shell and subagents; requires QQBOT_APPID/QQBOT_SECRET or in-app QR binding, with optional sharp for rendered maps and ffmpeg for audio/video. Shared notes are visible to every session, so private-chat content may be recalled in groups.

33 days agoIntegrations & RemoteMIT
L

dsh-market-watching

leni-more/dsh-market-watching

A market card pinned to the DSH sidebar: live price and 24-hour change for crypto pairs, A-share / Hong Kong / US stocks and world indices, FX majors and London spot gold and silver. An optional long or short cost basis plus a position size turn the change column into a P&L percentage and a cash amount; symbols, order and refresh interval are chosen in DSH settings. No login and no API key. Quotes come from public endpoints of Gate.io, Eastmoney and Sina, and the symbols you choose are sent to them on every refresh.

39 days agoUI EnhancementsMIT
S

dsh-theme-animal-island-ui

shirolin/dsh-theme-animal-island-ui

Animal Island theme with boarding-pass masthead, cream notebook paper, 118 ThemeRuntime tokens, in-app appearance presets, and starry night mode.

33 days agoThemes & AppearanceMIT
B

dsh-mcp-center (dsh-plugin)

bai-2008/dsh-mcp-center

Browse, install, inspect, update, and remove MCP server connections inside DeepSeek Harness, with an online catalog and native Streamable HTTP/stdio support.

322 hours agoDev & Plugin ToolsMIT
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.

33 days agoModels & ProvidersMIT
R

dsh-obsidian-notes

revive123456/dsh-obsidian-notes

Obsidian-style notes panel in the DSH right sidebar: a tree over a local folder, Markdown preview with line numbers, edit and save, Obsidian callouts, tables and wikilinks, screenshot paste into the vault, one-click insert of a note path into the chat input, and batch archive or delete for sessions and workspaces.

38 days agoUI EnhancementsMIT
D

dsh-memory-palace

dafantong01/dsh-memory-palace

Local long-term memory for DSH sessions: archives older turns under context pressure, with a turn-summary index for faster turn lists, statistics, window probing and archive planning (rebuilt automatically when unavailable, with a manual full verification), four tiered hot-memory boards, project documents with enabled/disabled/archived filters and optional owner-controlled family sharing, project hot memory, dual user/assistant turn previews, memory families with editable names and root transfer, root-abdication recovery, orphan-family takeover, summary keyword locator with segment-level candidates and paging, manual injection, 20K segmented reads, and tag-related retrieval. Includes staged recall cues, automatic compatibility with older memory layouts, and post-install version verification. Off in each new session until you turn it on with `/palace on` or the Memory Palace tab. All data stays in the workspace.

33 days agoMemoryMIT
R

companion-memory

root-7-khx/companion-memory

Roleplay companion memory for DeepSeek Harness: per-conversation editable persona documents (1-100 weight per entry, AI may refine them in small story-driven steps), per-speaker favorability and bond in multi-person chats, active memories with AI-scored vectors, a nine-emotion table updated every turn, an AI self-evolution ledger, recent 48-hour transcript search, companion-style conversation compression, sleep-time compute that pre-guesses the next topics while a conversation is idle, per-conversation tone cards learned from its own past replies, a habit-hint small-model bridge that writes the user habits it extracts into this conversation memory, a date-archived local knowledge base with auto-packing by turns or tokens, and a unified integrations page that lists curated plugins and downloads their GitHub releases. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.

34 days agoMemoryMIT
C

dsh-lane-bridge (dsh-lane-bridge)

cnranger1124/dsh-lane-bridge

Multi-channel IM bridge for DeepSeek Harness: each QQ (SnowLuma / OneBot v11, official QQ Bot) or Discord group and private chat becomes its own agent session, bound to a role card whose domain carries knowledge bases with draft approval, shared memory, a read-only GitHub reader and group trigger rules; two built-in personas (customer support, group chat), unified push with broadcast, and human hand-off.

324 days agoIntegrations & Remote
C

dsh-codex-history

chameleonn4/dsh-codex-history

Install it by asking DSH in one sentence, then it reads your local Codex CLI/Desktop chat history from ~/.codex/sessions and makes it usable inside DeepSeek Harness: a panel under the composer lists sessions with keyword and date filters and one-click import, the codex_history tool lets an agent list, read, search and summarize past conversations, a session whose working directory matches is injected automatically when a new agent starts, new Codex messages arrive as incremental updates in the running conversation, and a shared folder can mirror both Codex and DSH sessions across machines. Read-only — nothing is written back to Codex.

324 days agoSessions & MessagesMIT
S

dsh-plugin-deepseek-chat

sweet560/dsh-plugin-deepseek-chat

Sidebar panel that embeds chat.deepseek.com full-width in the DSH main area (desktop shell only), restores the last conversation, and keeps a crashed embedded page inside the panel.

33 days agoUI EnhancementsMIT
L

dsh-team-conductor

littlealety/dsh-team-conductor

Control plane for the harness's own Agent Teams: members are ordinary independent sessions created through the same seam the GUI uses, each with its own model, so they open and continue like any other conversation while a sidecar roster and task board coordinate them. Task entries carry a definition of done, a member's completion is submitted and waits for the Lead's review, and availability tells idle apart from awaiting-review or a failed last turn. With delegationEngine=auto it uses independent sessions, continuable subagents, or the kernel roster depending on what the composition provides.

322 days agoMemoryMIT
U

dsh-notify-say

unifilitence/dsh-notify-say

Windows desktop notifications for DSH that speak the turn result by default: Windows TTS needs no download, and 13 VOICEVOX voice packs can be installed from the settings page. A completed alert waits until running subagents and background jobs finish; approval, question and error alerts fire immediately. Voice packs are downloaded from GitHub after a terms confirmation.

326 days agoIntegrations & RemoteMIT
J

dsh-win-notify

jxxxxx729/dsh-win-notify

Windows toast notifications for approval requests, questions, completed or failed runs, and sign-in prompts; clicking a notification reopens the conversation that raised it, and toasts are attributed to the DeepSeek Harness app identity.

329 days agoIntegrations & RemoteMIT
W

dsh-douyin-subagent

wu079/dsh-douyin-subagent

Runs a Douyin subagent that browses videos and reads comments in valley hours and reports back, with dy_* tools for publishing and replying (comments sent from the already-logged-in page with its own request signature, no IM ticket), a daily quota timer, and a settings panel under Settings → Douyin: master switch, auto mode, valley windows, rounds per day and report depth. Windows-oriented; needs the separate douyin-mcp binary (yunsur/douyin-mcp releases, path set via dy_config mcpExe) and an Edge/Chromium login; replying needs a logged-in browser on a CDP port; publishing needs extra credentials most accounts lack.

39 days agoTools & CapabilitiesMIT
W

dsh-ark-wiki

wsk114514/dsh-ark-wiki

Queries PRTS Wiki for Arknights operators, items, stages, story pages and worldbook entries, and predicts unreleased characters, alters and banner schedules from story-cast statistics and banner history.

326 days agoTools & CapabilitiesMIT
W

astro-ph-researcher

wing-tn/astro-ph-researcher

Astronomy research workbench for DSH and Codex: NADC terms, reference library, writing, scoring, author confirmation, recommended books, FITS/XML formats, and analysis guides.

329 days agoTools & CapabilitiesMIT
H

dsh-sessionflow

harryheyu/dsh-sessionflow

Continues work across coding agents inside DeepSeek Harness: six sessionflow_* tools query a local session index built by sessionFlow to find past work, show where the current project left off, and hand the goal, files and open items to the next agent. Requires the separate sessionFlow core, installed from its GitHub repo. Everything stays local — no cloud, no telemetry.

315 hours agoSessions & MessagesMIT
B

dsh-workbuddy-harness

bushizhanghan/dsh-workbuddy-harness

Brings WorkBuddy free/paid models (domestic + international) into DSH without the desktop app, published as @bushizhanghan/dsh-workmate. This package is a maintained fork of Faide-cyber/dsh-workbuddy (whose upstream entry is already listed in this catalogue); do NOT co-install both, as they register the same provider id "workbuddy-ai" and will collide. v1.2.7 relocates over-long system prompts past the domestic gateway channel-risk classifier, rewrites the DSH brand string, and adds a debug dump; supports dsh 0.2.0-rc.2 through 0.2.1 (incl. prereleases).

323 days agoModels & ProvidersMIT
Z

dsh-theme-palette

zuoyunlai/dsh-theme-palette

Five palettes for DeepSeek Harness — mono, warm sand, indigo, moss and a custom three-colour palette — each rebuilt in OKLCH for light and dark, with text and surface contrast solved per palette. Includes config export/import codes and a high-contrast mode.

313 days agoThemes & AppearanceMIT