Plugins
Browse, filter, and install DeepSeek-Harness plugins.
765 plugins found
dsh-creative-studio
ylight-cpu/dsh-creative-studio
Image and video production toolkit for DeepSeek Harness - background removal with quality tiers, local inpainting retouch, headline and logo compositing, batch platform-size exports and image QA reports; for video, AI subject matting with background replacement (RVM ONNX, plus a chroma-key path), animated titles with fade/slide/typewriter/karaoke presets, 53 transitions with stylized variants, and light-effect and grading presets with LUT support, alongside footage inventory, accurate cutting, subtitle burn-in, music mixing and platform-spec exports; it provisions its own local Python runtime through a bundled bootstrap script.
dsh-lit-search
flan246/dsh-lit-search
Academic literature search and citation tools for DeepSeek Harness: paper search via Crossref and OpenAlex with no API key, related-works discovery, and citation formatting in GB/T 7714, APA and BibTeX.
dsh-formatforge
tianbuyu-wwx/dsh-formatforge
FormatForge for DeepSeek Harness: forge any file format (pdf/docx/xlsx/pptx/eml/toml/...) into AI-readable structured data. Thin bundle that spawns the local Python CLI (python -m formatforge) and returns protocol JSON; enhancement is delegated to the cur
dsh-attachment-formats
linkingoscar/dsh-attachment-formats
DeepSeek Harness Web plugin — PDF text-layer and scanned-PDF OCR, Office docx/xlsx/pptx to Markdown, TIFF/epub and long-document index cards.
dsh-at-any
hatsuyuki0103/dsh-at-any
Codex-style `@file` mentions for the web GUI: search and reference workspace files of every format (.java, .vue, PDF, images, extension-less, hidden) with no index truncation. Replaces dsh-at-file.
dsh-character-profiler
mlittlefriend/dsh-character-profiler
Character consistency toolkit: personality profile cards, appearance-weight stats, and behavioral-drift detection for long-form fiction.
dsh-deepseek-quota-bar
jiangli07/dsh-deepseek-quota-bar
Draggable transparent balance card with a blood-bar of remaining balance vs month-opening, today/month spend (official when the platform token is configured), and session cost.
pocketagents
oscarka/pocketagents
PocketAgents (formerly deepseekharness-remotecontrol): self-hosted mobile Web PWA and Feishu remote control hub for DeepSeek Harness plus local adapters for Antigravity IDE, Codex, Claude Code, WorkBuddy and Doubao, with swipe-triage approvals, multiple-choice popup replies, hold-to-talk voice steering, TTS reply playback, HLS/WebRTC media preview, multi-host pinning, Web Push notifications, and 5-second terminal QR pairing.
dsh-doubao
ralsei1337/dsh-doubao
Rewrites DSH model output as "Doubao-speak": a barrage of superlatives, a long list of negations, healing diagnoses, verbatim repeats and a service-style closing question. Five strength levels (off / light / standard / heavy / max) instead of a dial, two independent channels (system-prompt style bible and llm/stream post-processor), three transform modes, and every length knob adjustable live in a settings page with a preview.
dsh-remedy (plugin)
jjjjjjjjnnjnn/dsh-remedy
A patch set for DeepSeek Harness that repairs fused tool-call argument text at the llm/stream seam and re-throws whatever it cannot prove: a call is dispatched only when every fragment parses to a plain object, the first call keeps its id and synthesized ones are marked, and a stream that cannot be split keeps its original error instead of a success. It also listens on agent/request-error to name the deterministic refusals it will not retry, answers per failure class which patch covers it and whether that patch is switched on in the profile you point it at, and reads multi-frame zstd session logs offline to count every turn ending and every error code. Everything it claims is registered with the seam it touches and the limits it does not cross; the resolver never invents a value and never downgrades a configured setting.
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.
DSH_Eplan
shangyunqiang1/dsh_eplan
EPLAN Electric P8 automation for DeepSeek Harness (Windows): a bundled eplan-mcp server drives the running P8 2025 instance through the EPLAN Remote Client interface, a settings page sets the EPLAN install root, and five skills cover connection and safety, C# scripting, documentation lookup, EEC Pro development and setup. Five offline SQLite documentation indexes (P8 2025 API reference, P8 2025 platform help, P8 2026, P8 2027, EEC Pro 2026) answer questions without network access, but they are not shipped in the repository: download the release zip or build them with the included scripts; the P8 2026 and P8 2027 rows ship disabled. Requires EPLAN P8 2025 with Remote Client access enabled and Python 3.12+ with mcp and pythonnet (run scripts\setup.ps1 once). A version panel records releases and applies a newer one from the repository.
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.
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.
dsh-memory-plugin
2132774831/dsh-memory-plugin
Fully local long-term memory for dsh: cross-conversation and cross-project, stored as a single JSON file on your machine with no network calls, no model calls and no API key. Ships memory_save, memory_search, memory_list, memory_forget and memory_review tools, keyword-and-tag recall injected before each turn with adjustable ranking weights, Markdown import (including Kun and Hermes Agent formats) and export (native and Hermes Agent formats), and a settings page to browse and edit memories.
DeptAI-UI-DSH
01men/deptai-ui-dsh
A collaboration front-office for AI agents and humans — department boards, tickets, approvals and industry calculations run inside the DSH conversation and panel, so agents do the work in chat while humans stay accountable in the panel. It calls the 01men/ybkkasi governance base over existing contracts (asset ledger, IAM, OIDC SSO, RBAC and scene-level authorization) instead of re-implementing governance. Ships as a Cordis bundle and mounts at /gate01; the selftest suite is green on every push. Do not install this and 01men/ybkkasi as dsh bundles in the same profile: both register the ops-platform-core / ops-iam / ops-authn rows. Requires DSH >=0.1.0-rc.7 <0.2.0.
dsh-vidlens
cctv2333/dsh-vidlens
Samples a video the way a person does instead of downloading it: metadata and chapters first, then timestamped frames as images, subtitle-first transcripts (local ASR only when the platform carries no subtitles), AudioSet 527-class sound tags and top comments — 21 tools sharing one on-disk cache behind a cross-process lock. Needs Python 3.10+, ffmpeg and the vidlens package (pip install vidlens-mcp); a missing install comes back with the two ways to fix it instead of a bare ImportError.
dsh-flymemory
aujurd22/dsh-flymemory
Structural long-term memory for DSH: supersede, decay and entity-state tracking across 15 MCP tools, automatic recall and capture hooks, and a bounded pointer index published per request instead of filling the window. Requires Python 3.10+ with torch and sentence-transformers; the first run downloads a ~470 MB embedding model.
office-ppt
pawpress/office-ppt
Builds presentations by driving the LibreOffice installed on the machine over UNO instead of writing OOXML in JavaScript: `lo_build` opens a real Impress document from structured slides and lets LibreOffice export editable PPTX/ODP plus PDF and per-slide PNG, `lo_render` re-renders an existing PPTX/PPT/ODP, `lo_convert` converts between Office formats, `lo_probe` reports the detected soffice path, version and UNO bridge, and `lo_config` edits the stored settings. Needs a local LibreOffice (verified on 26.8.1.1); it uses the bundled Python, so no system Python is needed, and it keeps one warm soffice process between calls. Fully verified on Windows only; on Linux it falls back to the system python3, which needs python3-uno.
dsh-scroll-boost
twfu-wcy/dsh-scroll-boost
Skips offscreen chat and trajectory rows so long sessions scroll smoothly; measured row heights keep the scrollbar steady, visible content unchanged.
dsh-chat-perf-css
light-ei/dsh-chat-perf-css
A long conversation that renders many LaTeX formulas at once can become laggy, because the browser keeps styling, laying out and painting content that is off screen. This plugin applies content-visibility: auto to the off-screen message bodies, so that work is skipped and the lag is reduced.
dsh-im-union
drscrewdriver/dsh-im-union
Union IM bridge for DSH — an independent implementation uniting the capability sets of community peer plugins (xmanrui/dsh-im, MichengAI/dsh-im-connect). Drive your agent session from 15 channel adapters across 12 platforms (including email; WeCom/DingTalk/QQ each contribute two: bot + self-built app or notify tier) — WeChat (official iLink QR bind), Feishu/Lark (long-connection + streaming cards; the voice tier requires system ffmpeg), Telegram, Discord, WeCom intelligent bot & self-built app (signed callback), DingTalk (stream + AI Card and custom-robot notify), QQ official bot (plus notify tier), Slack (Socket Mode), WhatsApp (Baileys QR pairing; the dependency ships as an optionalDependency of the plugin package), Matrix, iMessage (macOS only), Email (IMAP/SMTP thread routing). The cross-version narrow waist auto-adapts settings gen1/gen2/gen3 across hosts 0.1.2-rc.1→0.2.1-rc.2 (12-tag enum; rc.2 verified by a real desktop-profile install with double read-back) using capability probing only, never version branches. In chat: a 25-command panel, tool-approval and question loops answered in the originating chat (deny-by-default, initiator-only, 5-min expiry), image/file input gated on host model metadata, deliverable file return, a delivery log with bounded retry (uncertain is never re-sent), proactive delivery and fragment composition. It also splits the native sidebar into self-owned Tasks / Channels tabs (standing down entirely when another plugin already owns the slot), registers an `im-concise` agent preset plus reply sanitisation that keeps GenUI fences and raw HTML out of text-only chats, renders `svg` fences to PNG images, guards model choice with an allowlist, and mirrors each turn's final answer to notify channels via `/relay` (addressed by account ID or alias, never guessed on ambiguity). Secrets are one-way into the vault and never echoed back. npm: `dsh-im-union`.
human-writing-skills
whh110112/human-writing-skills
Multilingual writing, chunked long-form collaboration and continuity review, with on-demand DSH delegation discovery. Requires Python 3.9+ on PATH.
dsh-scholar-suite
docsor1212/dsh-scholar-suite
Eight academic skills bundled for one-command install — publication-ready academic figures designed from real data with visual review, AI-text humanization, paper polishing and rewriting, PubMed citation verification (DOI/PMID reconciliation), Chinese citation and medical-book reference checks, and WeChat medical article structuring. Three skills run fully local, five call external services only when used (NCBI E-utilities, DOI resolvers, publishing platforms), declared per skill. Zero telemetry, no install-time scripts. Skills run local Python 3.8+; the academic-figures skill also needs its pip dependencies installed.