Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

17421 plugins found

A

dsh-model-logos

altermoe/dsh-model-logos

Model brand marks in the composer model selector; vendor and model marks across Settings → Models (provider rows, model rows, the add-provider dropdown); and a per provider/model icon picker that stores overrides in the DSH user settings document.

33 days agoUI EnhancementsMIT
S

dsh-payload

shengpj/dsh-payload

Adds a { } button under each assistant reply in the DSH Web GUI that opens the exact request sent to the model for that reply: model, call parameters, messages, tools, and provider-reported token usage.

311 days agoDev & Plugin ToolsMIT
L

CodeGraph

longbowzz/codegraph

Turn code flows into source-linked Mermaid diagrams and interactive CodeWalkthrough explainers.

323 days agoTools & CapabilitiesMIT
Q

dsh-squeeze

q8atnight/dsh-squeeze

Adds a squeeze tool: the agent hands a long web page, a batch of pages, a text file or a text PDF (via pdftotext) plus one question to a helper model and gets back only the answer, so the material never enters the chat. A settings page picks up to three helper models from the DSH model list, each with a nickname, a fixed thinking level and a "when to use" note, with optional fallback and size limits taken from each model's context window.

317 days agoTools & CapabilitiesMIT
J

dsh-baidu-netdisk

justinzyc271828-sys/dsh-baidu-netdisk

Connects DeepSeek Harness to Baidu Netdisk's official MCP service for file search, file metadata, and storage quota. Requires Baidu account authorization after installation.

310 days agoTools & CapabilitiesMIT
F

dsh-supermemory

fish9988/dsh-supermemory

Cross-session long-term memory backed by Supermemory: pre-step semantic and chunk recall with per-session deduplication, debounced transcript upload, background LLM fact extraction (add/update/delete) with bigram and semantic deduplication, memory_search / memory_save / memory_forget tools, global or per-workspace container scoping, and a Plugins page UI for API key storage, memory CRUD, recall preview and activity log. Requires a Supermemory API key (a free monthly quota is available), and conversation excerpts are uploaded to Supermemory's cloud.

319 days agoMemoryMIT
P

dsh-qms-capa

perrylink/dsh-qms-capa

QMS NCR, CAPA and 8D tracking with batch and impact assessment.

3yesterdayTools & CapabilitiesApache-2.0
I

deepseek-harness-mobile

imzl-zl/deepseek-harness-mobile

DSH 插件:手机端远程通道的电脑侧桥接

319 days agoIntegrations & RemoteMIT
F

deep-view

fei2411/deep-view

Deep View: interactive views (charts, tables, inputs, answers) in any DeepSeek Harness chat

325 days agoUI EnhancementsApache-2.0
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.

3yesterdayDev & Plugin ToolsMIT
L

dsh-remote-dock

lee-eee-eee/dsh-remote-dock

Use SSH hosts and WSL distributions as remote DSH workspaces, with environment setup, model configuration porting, and the remote interface embedded locally.

321 days agoIntegrations & RemoteMIT
C

dsh-oracle-gate

cresbigb/dsh-oracle-gate

Acceptance gate for DSH: freeze the acceptance criteria into an oracle ledger before work starts, then honor only real execution receipts — files changed after freezing are refused outright, and a failing hard gate overrides any human pass.

318 days agoDev & Plugin ToolsMIT
F

dsh-push-notify

faruzancn/dsh-push-notify

Multi-channel push notification plugin supporting Bark (iOS) and ntfy (Android/iOS/Web/Desktop) for turn completion, approvals, questions, and quota halts.

317 days agoIntegrations & RemoteMIT
P

dsh-legal-clause

perrylink/dsh-legal-clause

Contract clause work: build the clause tree, map it against a 12-key playbook, register the playbook and export the unresolved report — 5 `legal.*` tools.

3yesterdayWorkflow & AutomationApache-2.0
D

dwguard-dsh-hmos

dogwind221/dwguard-dsh-hmos

HarmonyOS delivery orchestration for DSH: freezes a four-dimension acceptance pack whose measurable criteria carry machine-checkable assertions, runs an adversarial pre-review before dispatch, hands the work to DevEco Code in Goal mode, then audits the delivery with independently gathered evidence (screenshots, UI tree, logs, hashed evidence bundle), recomputing assertion verdicts against measured values and filing rework orders; includes a cited rule catalog, a user-confirmation state and a gate calibration ledger.

36 days agoWorkflow & AutomationMIT
L

dsh-copyright-kit

lucky020/dsh-copyright-kit

Turns a repository and a software name into Chinese software copyright registration material - the 60-page source code excerpt (50 lines per page, auto-paginated), the software manual with screenshots, and the derived application-form fields (line count, language, completion date, function summary). Requires Python 3 with python-docx, and Google Chrome for screenshots.

323 days agoTools & CapabilitiesMIT
X

dsh-comfyUI-control

xingxue-ux/dsh-comfyui-control

Adds a Drawing Mode agent preset whose 19 comfyui_* tools drive a local ComfyUI: Anima and Krea2 generation, LoRA search and download, Danbooru character tags, PNG metadata, an upstream repro check, and xiaofanqie de-obfuscation.

319 days agoTools & CapabilitiesMIT
T

dsh-tiaforge

tia-forge/dsh-tiaforge

Bundles five TIA Portal skills (Siemens PLC docs lookup, ladder-logic generation, SimaticML-to-PNG rendering, scan-cycle simulation with PASS/FAIL scenarios, and a TiaLink gateway skill for driving a real TIA Portal project) and wires five MCP endpoints. Requires TiaLink (paid; Windows + TIA Portal V19/V20 + Openness) for real-project work, API keys for the four cloud services (100 free calls each, then paid; rendering is billed per call even on failure), Node 22+, and network access; program snippets are uploaded to tia.hubwiz.com.

35 days agoTools & CapabilitiesMIT
L

dsh-qq-zone

lfelkeea/dsh-qq-zone

Publishes and reads QQ Zone posts through SnowLuma's OneBot qzone_* actions (SnowLuma 2.2+ signed in to QQ), and lets the agent understand images with a local vision model (OpenAI-compatible gateway) or Windows OCR.

322 days agoTools & CapabilitiesMIT
M

dsh-hierarchical-fishmemory

marsstorm/dsh-hierarchical-fishmemory

Layered long-term memory for DeepSeek Harness - a merge of AirPineApplea/feiyu-memory 4.0.2, dsh-soul-md and dsh-shallow-memory (do not install it alongside those plugins): a diary distilled from finished turns, a hand-written feelings diary, a persona card with version history, a hand-note injected in full every turn, and a short-TTL note layer, each capped separately so per-turn injection stays small; ships agent tools and a sidebar panel for recall, editing, compaction, and backup or restore from a local file, WebDAV or a gzip archive.

3yesterdayMemory
H

dsh-per-session-folder

hhuapen/dsh-per-session-folder

Creates an isolated folder for each new default-workspace session and renames it to match the session title.

321 days agoSessions & MessagesMIT
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.

36 days agoModels & ProvidersMIT
I

dsh-shark-bg

iemgnod/dsh-shark-bg

ASCII sharks and schooling fish swim behind the DSH Web interface, with a settings page for veil opacity, shark count, size, fish density, swim speed and grid strength.

320 days agoThemes & Appearance
L

dsh-tokeneconomizer

lksa09871234/dsh-tokeneconomizer

DSH port of TokenEconomizer with cross-session project knowledge, opt-in tool pruning, failure-loop redirection, and token usage records.

322 days agoUsage & BillingApache-2.0