Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

1447 plugins found

O

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.

311 hours agoIntegrations & RemoteMIT
D

dsh-novel-voice

drizzlegig/dsh-novel-voice

Want AI to write in the style of novels you love, or to develop a voice that is uniquely yours? Creative Style imports novels you like and your own original work, distils their writing patterns into a personal style profile, and lets you blend several sources into one voice. Before you write it compiles a short brief; afterwards it points out clichés, repetition and off-style sentences, and can rewrite specific spans. Off by default, no scores, no model training.

34 days agoTools & CapabilitiesMIT
Q

dsh-rugu (dsh)

qiuyedx/dsh-rugu

Persona memory for DeepSeek Harness: one memory shared by every entry point (DSH desktop, and QQ through the dsh-qq bridge) that records what the agent itself experienced. Raw messages are kept, five recall routes (vector, keyword, people and events, time, who is present) run before each reply, and a per-context check decides whether a remembered thing may be said. Adds memory_recall, memory_note, memory_fix and memory_look tools and a Settings page; embeddings are optional (local Ollama or an OpenAI-compatible endpoint).

36 days agoMemoryMIT
C

voice-call

crease123/voice-call

Start with the author tutorial: https://www.bilibili.com/video/BV1t9sJ6NErV/ . Talk to your current DSH Agent without switching presets: automatic speech transcription and sending, streamed spoken replies, voice interruption, and a five-bar microphone meter. Choose DeepSeek or Doubao independently for ASR and TTS, configure your own credentials, and edit instructions applied only during calls. Includes a Bilibili usage tutorial, phone-button screenshots, and a Restore defaults action for call instructions.

32 days agoVision, Voice & MultimodalMIT
J

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.

317 hours agoDev & Plugin ToolsMIT
K

dsh-hoi4-modding

kiant98/dsh-hoi4-modding

Hearts of Iron IV modding bundle for DeepSeek Harness: registers 15 skills covering focus trees, events, decisions, ideas, characters, technologies, localisation, GUI and error.log triage, and mounts 20 local MCP tools (a Python stdio server) to scaffold content, statically validate mods, build a SQLite FTS5 knowledge base from the vanilla game, and preview focus trees offline. Ships a 163-document reference library; requires DSH >=0.2.0 <0.3.0 and Python 3.9+ on PATH (standard library only, no game assets).

38 days agoMCP & Connectors
M

dsh-prism-plugin

mantonlove/dsh-prism-plugin

DSH Background adds custom photo or GIF wallpapers to the DSH Web interface, lets you choose which images join the carousel and drag to reorder them, and tunes glass, typography, accent colors, aurora, six presets, and portable themes. Needs DSH 0.2.2-rc.1 or later.

33 days agoThemes & AppearanceMIT
R

pi-better-edit

rianico/pi-better-edit

Hash-anchored read/apply_patch tools for DeepSeek Harness (dsh). Every line gets a unique 3- or 4-char hash (A-Za-z0-9, configurable) that stays stable across edits; apply_patch is the only file-mutation entry point and commits one patch batch per transac

313 days agoTools & CapabilitiesMIT
C

dsh-watch

cyuni1996/dsh-watch

Continue DeepSeek Harness conversations on an Android watch and install the watch app with a desktop wizard.

314 days agoIntegrations & RemoteMIT
N

dsh-physics-lab

novick1212/dsh-physics-lab

Interactive physics lab in the DSH sidebar — 24 parameter-driven animations (mechanics, electromagnetism, optics, thermodynamics) grouped by grade, each with a knowledge-point lesson whose steps follow the animation, a quiz with answer checking, and a draggable 3D view for four field models. Pure client side: analytic solutions computed locally, no LLM calls, no network, no telemetry.

317 days agoJust for FunMIT
L

dsh-dafeiyu-emotion

lidu-china/dsh-dafeiyu-emotion

Adds a fish-ear microphone to DSH that transcribes speech locally, estimates tone and emotion, and lets BigFish reply with an emotion-aware prompt.

314 days agoVision, Voice & MultimodalMIT
A

dsh-her

aicivilization/dsh-her

A desktop companion for DSH: she lives on your real desktop, in the wallpaper or in dsh's own page, talks by voice, speaks first and remembers you. Several characters, each with her own look and scene rules.

32 days agoVision, Voice & MultimodalMIT
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.

316 days agoIntegrations & RemoteMIT
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
L

dsh-phone-mirror

liyuhan7/dsh-phone-mirror

Mirrors an Android phone or tablet into the DSH right sidebar over adb with mouse and keyboard control, keeping videos, clips and chats next to the desktop instead of in your hand; Opus audio needs Android 11+, Windows only.

32 days agoIntegrations & RemoteMIT
V

dsh-minimax-connect

vicqiufeeng/dsh-minimax-connect

Turns the MiniMax Code (Mavis) subscription already signed in on this machine into a DSH model provider, renewing the OAuth token itself so the desktop client can stay closed, with points, check-in and subscription-quota panels.

316 days agoModels & ProvidersMIT
C

dsh-cngtn-pond

cngtn/dsh-cngtn-pond

Paper-and-ink theme with warm surfaces, hairline strokes, near-square corners and a living ASCII koi pond behind the shell; the theme sets no font family, so the shell's own stacks (or your Settings choice) apply.

313 days agoThemes & Appearance
0

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.

316 days agoUI EnhancementsMIT
K

DSH-PDR-Plugin

kipozannaki/dsh-pdr-plugin

Runtime plugin firewall for sessions started through its launcher (the DSH Desktop app cannot be injected and is not covered): filesystem, network and subprocess calls plugins make are attributed to the plugin that made them and judged against what that plugin declares, so a plugin doing its declared job stays silent and leaving it is recorded. Attribution is best-effort, not a guarantee - uncovered calls fall back to host, never to another plugin. Also adds a pre-install health card (capability surface, red-line combinations, PASS/WARN/BLOCK), boundary judging, opt-in pre-execution blocking with a credential-exfil rule, update diff with a trial install in an isolated child process, SARIF/CSV audit export, and multi-source aggregation. Local-only storage, no telemetry; the optional webhook is off by default.

37 days agoSecurity & PermissionsMIT
A

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.

311 days agoMemoryMIT
Y

dsh-sidebar-entry-manager

yanli-nyan/dsh-sidebar-entry-manager

Per-row display switches for the DeepSeek Harness sidebar's panel entries: a hidden row is still reachable from the More menu, and the choice is kept in localStorage across reloads and restarts.

326 days agoUI EnhancementsMIT
H

dsh-mobile-shell

htao-uu/dsh-mobile-shell

DeepSeek App-style mobile shell for the DSH Web UI with drawer navigation, app-like composer and settings; best paired with the dsh-android app, which supplies the native Android back key (standalone use works but is not recommended).

36 days agoIntegrations & RemoteMIT
P

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.

328 days agoTools & CapabilitiesMIT