Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

307 plugins found

K

dsh-kolmopdf

komoai2026/dsh-kolmopdf

Official KolmoPDF plugin for DeepSeek Harness: six tools for PDF-to-Markdown/OCR with formulas and tables, layout-preserving PDF translation, Markdown export to DOCX/PDF/HTML/LaTeX, cost estimation, and a Settings → KolmoPDF key and live-credits panel. PDFs and Markdown you process are uploaded to the KolmoPDF cloud service (www.kolmopdf.com) with your API key, and conversions use your KolmoPDF credits.

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

318 days agoMemoryMIT
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.

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

34 days agoModels & ProvidersMIT
Y

dsh-usage-wallet

yeoksin/dsh-usage-wallet

Unofficial fork of dougen/dsh-deepseek-usage (baseline v0.16.0): sidebar balance and quota card for the active model provider, covering DeepSeek, Moonshot, Z.ai, OpenRouter, Kimi, MiniMax and OpenCode, plus Alibaba Cloud voucher balance for qwen-token-plan (BSS OpenAPI with AccessKey) and Xiaomi MiMo console balance with token-plan usage (console cookie). Ships a provider query-status page and per-token unit prices. Do not install it alongside upstream dsh-deepseek-usage: both render the same sidebar card.

320 days agoUsage & Billing
L

dsh-pet-chat

lintwosix-beep/dsh-pet-chat

Desktop pet with a chat panel: QQ-style history, favorites, and branch threads that merge back into the log as a forward card; the panel docks beside the pet and resizes from its edges and corners. Modified from PC2005-cloud/dsh-pet (MIT); do not install together with the original.

323 days agoJust for Fun
C

dsh-skin

changan0617/dsh-skin

Homepage-style chat background skin for DeepSeek Harness, ported line by line from deepseek.com/harness: WebGL fluid background (5-colour noise field, flow-field brush, light, bloom, vignette, grain), white 90px dot-line grid with mouse perturbation and spring return, and a digital point-cloud whale that assembles from particles, breathes, swims, is pushed radially by the cursor and brightened by a light beam. Dark theme only; disabled automatically under reduced-motion.

3last monthThemes & AppearanceMIT
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.

3yesterdaySessions & MessagesMIT
D

dsh-service-portal

dingminhua/dsh-service-portal

Exposes any local service on a LAN address and a public cloudflared quick-tunnel domain behind one password login, with per-route open/block gates managed from the plugin settings page. Requires Python 3 and cloudflared on the machine, and reports either of them being missing or misconfigured in the settings page before you start; LAN and local access are passwordless by default, while the public tunnel requires the passcode.

37 days agoIntegrations & RemoteMIT
Z

dsh-radeon-cloud-patcher

zhz8888/dsh-radeon-cloud-patcher

Adds AMD Radeon Cloud as a model provider in DeepSeek Harness, with reasoning-effort levels declared per model. The provider definition ships in the plugin's own patch layer rather than in your profile.

312 days agoModels & ProvidersMIT
X

dsh-prompt-lab

xueccci/dsh-prompt-lab

Agent-structured prompt optimizer for DeepSeek Harness: rewrites composer drafts into role/task/context/constraint/format with normal, slim, and expand modes, a confirm modal with score, continue-optimize, and local, hybrid, DSH, or cloud-API engines.

3last monthUsage & BillingMIT
B

dsh-voice-call

biliye/dsh-voice-call

Voice call assistant for the DSH desktop app and the Web GUI (the same plugin, only the profile name differs): a draggable floating call ball, browser-side VAD that sends each utterance after a pause, speech recognition through the local SenseVoice model already downloaded by the official voice-input plugin (no second model), FunASR HTTP or streaming, or a cloud-compatible API, MiniMax / MiMo-V2.5-TTS (director mode and voice clone) / OpenAI-compatible TTS replies, an optional wake-word mode with auto-sleep, and task dispatch to separate sessions with progress, stop, and spoken completion reports.

32 months agoVision, Voice & MultimodalMIT
R

dsh-remote-tunnel-easy

raiyan007-gb/dsh-remote-tunnel-easy

Scan a QR code in Settings to open the DeepSeek Harness web UI on your phone inside the active session via a cloudflared quick tunnel.

33 months agoIntegrations & RemoteMIT
A

dsh-cos

annexwu/dsh-cos

Adds COS storage browsing and transfers, workspace artifact uploads, temporary links, and conversation attachments that retain local copies with cloud object identity, plus Agent tools for Tencent Cloud COS, CI, and MetaInsight.

3last monthTools & Capabilities
Y

dsh-homepage-skin

yushi-xxh/dsh-homepage-skin

Adds the DeepSeek Harness homepage background to dsh web: WebGL fluid light, dot-line grid and a digital point-cloud whale, with dark and light palettes.

33 months agoJust for FunMIT
P

dsh-plugin

picgo/dsh-plugin

Upload local images and files to your image host through PicGo's existing configuration (PicGo Cloud, GitHub, S3, COS, Qiniu, or any installed uploader plugin), via a `picgo_upload` tool and a `/picgo` command.

326 days agoTools & Capabilities
0

dsh-amdkey

0xdaj/dsh-amdkey

Rotates multiple AMD Radeon Cloud API keys behind a local proxy, reads real daily credit from the usage endpoint, and applies model selection without a restart.

2yesterdayModels & Providers
P

dsh-sound-atelier

puffdog-git/dsh-sound-atelier

Reads assistant replies aloud using Edge, cloud and local speech engines, with per-persona voices, Chinese/Japanese dubbing, cloud voice management, RVC voice conversion and a speech API other plugins can call.

24 days agoVision, Voice & MultimodalMIT
Z

dsh-excalidraw-canvas

zhiyaunhe-ops/dsh-excalidraw-canvas

Excalidraw workspaces for local DSH Desktop or a separately deployed cloud server, with automatic saving and document-scoped assistant sessions. Requires workspace setup.

25 days agoTools & CapabilitiesMIT
M

dsh-pocket

moranyue/dsh-pocket

Fork of shaobeichen/dsh-pocket for remote phone access to the DSH Web UI: QR-code access over LAN or a cloudflared tunnel with live sync; mobile layout is left to DSH itself, the plugin adds safe-area and touch chrome, soft-keyboard Enter inserts a newline while hardware keyboards send on Enter, and install/update is left to the plugin manager. The command-line mode listens on 0.0.0.0 by default so a phone on the same Wi-Fi can scan the QR code; it generates an access password (embedded in the QR code) unless you pass --no-auth, and a cloudflared tunnel exposes the Web UI beyond your LAN.

23 days agoIntegrations & RemoteGPL-2.0
W

DSH-PaperReading

wuke-luke/dsh-paperreading

Paper-reading workspace for DeepSeek Harness — page-by-page bilingual PDF translation, select-to-translate, paper-aware chat with page citations, notes, diagrams and cloud sync.

215 days agoTools & Capabilities
X

dsh-brain-hub

xxwjxx-1210/dsh-brain-hub

A second brain for DeepSeek Harness where Markdown is the database and git is the sync, with zero runtime dependencies. Core memory is injected into every system prompt, one file per note with weighted search; cards produced in the sidebar web chat land in an inbox first and are approved one by one as cloud notes or local-only notes (private/ is permanently gitignored and never pushed); web-chat progress is saved to progress.md with the last 20 drafts archived. A four-step flow lives behind one header icon: open web chat, extract cards, review them, back up to the cloud. The extraction prompt is editable in the panel and applies immediately.

212 days agoMemoryMIT
K

agentkit-personal-assistant

kingsoftcloud/agentkit-personal-assistant

Standalone personal assistant DSH plugin with multi-Bot profiles and an explicit Cloud Computer Broker boundary.

219 days agoTools & CapabilitiesApache-2.0
Z

dsh-netease-daily

zxcvbnmlxy/dsh-netease-daily

DeepSeek Harness 每日听歌插件:设置页配置、静默播放、按描述推荐与 AI 评价

224 days agoWorkflow & AutomationMIT