Plugins
Browse, filter, and install DeepSeek-Harness plugins.
1586 plugins found
dsh-chapter-whale
thus-zhou/dsh-chapter-whale
Windows x64 DSH workbench for scheduled, unattended novel writing and Fanqie publishing, with configurable tasks and optional free-quota model channels. First start downloads a pinned Python and browser runtime (about 280 MB) from GitHub into %LOCALAPPDATA%\ChapterWhale; publishing signs in to your Fanqie writer account.
dsh-FocusCapture
janehk416-alt/dsh-focuscapture
Windows screenshot and annotation plugin with configurable global hotkeys, always-on-top pinned images, and capture delivery to the current DSH chat draft; requires a compatible Python runtime. Ships a prebuilt Windows executable (native/DualCtrlSnip.exe) and a Python helper that polls only the state of the selected hotkeys.
tmem
kentzjh-cmd/tmem
Project-scoped deterministic execution trace memory and zero-token session digest plugin for DSH, compiling session histories into guarded playbooks and behavior summaries with inline session_id lineage. Registers the /tmem slash command, recalls memories only on explicit file-path or error anchors in agent/pre-step (skipping unchanged repeated steps), and intercepts tools/post-execute errors and code edits with same-origin L2 fixes, failure-loop warnings, and statistical L1 co-change partner hints (skipping routine read calls when idle). Needs Python 3 on PATH (or TMEM_PYTHON) and spawns python3 -m tmem.cli with a 5-second timeout; stores all data inside each project's .tmem/ directory (no ~/.tmem/ global store) and makes no network requests. It needs Python 3 on PATH (or TMEM_PYTHON) and runs python3 -m tmem.cli synchronously, with a 5-second timeout, on every agent step and tool result; traces are stored in .tmem/ inside each project and in ~/.tmem/ shared across projects. It makes no network requests.
dsh-llm-adapters
k1-h2/dsh-llm-adapters
DeepSeek Harness adapters for Loomy, SenseTime Raccoon and Trae. Sign in through the provider’s own web page (WeChat QR for Loomy and Raccoon, a dedicated browser window for Trae), or reuse a signed-in local Trae client for the mainland check-in, then use
dsh-agentrix
991206772-debug/dsh-agentrix
DSH Agentrix supports coordinator-led direct or delegated work, configured worker models, dispatch-time coordinator models for independent review, progress and request usage tracking, registered requirements linked to verification evidence, and a read-only acceptance view that distinguishes plan completion from request coverage. Verified only on Windows with PowerShell 7 (pwsh) and Git; other systems are untested.
dsh-go-plugin-adb
jminn0/dsh-go-plugin-adb
Gives a DSH agent a real adb shell on the phone itself over loopback, with no root and no PC. Needs DSH Go with android-tools-adb installed in its Ubuntu environment and a one-time Wireless debugging pairing; adb has to be switched to TCP port 5555, which then also accepts connections from the local network (still key-authenticated).
dsh-textbook-parser
teanuky/dsh-textbook-parser
Breaks a STEM textbook into a four-level card map (book, chapter, section, knowledge point) in a sidebar panel, where each point names the defect of the previous approach it fixes and each chapter keeps its remaining gap as the motive for the next; marks key points with a star, shows theorems as cards with statement, conditions and symbol table, folds step-by-step derivations, and exports the same map as a self-contained offline HTML file, Word or PDF. Ships a textbook-parser skill and a textbook_archive tool (save_book / save_chapter / list_books / get_book / delete_book) plus a bundled 12-chapter Signals and Systems sample with 116 sections, 263 points and 601 worked examples. No runtime dependencies and no network access.
dsh-wsl-suite
stallenlu/dsh-wsl-suite
WSL workspaces for DeepSeek Harness. A sidebar W button lists installed distros and registers a Linux folder as a host workspace addressed by a UNC path, and the sidebar terminal opens a real Linux pty inside the distribution for WSL sessions. A persistent zero-dependency agent running in the distro answers file, shell and search requests over a JSON-lines pipe, so no polling timers touch the distribution while it is idle and /mnt drives stay reachable from tools and the terminal (registering one as a workspace is refused, because the host realpaths workspace paths and Windows cannot resolve drvfs); grep and glob run the distro's own ripgrep. WSL preset twins such as wsl-standard swap in the WSL shell and fs tools. A rebuild of 6Mikao9/dsh-wsl-workspace — do not install both: they mount the same W entry in the Workspaces header, publish the same wsl-<mode> presets, and each wrap the host's single-slot terminal provider.
dsh-explorer-open
ame-code/dsh-explorer-open
Adds a right-click command "通过 dsh 打开" (open with dsh) to the Windows Explorer right-click menu for a folder, a folder's empty background and any file: it launches DeepSeek Harness on that folder, creates a new session every time, and puts the clicked file into the new draft as an @ reference. Ships a packaged-COM menu for the Windows 11 modern menu plus a registry entry for the classic menu; first install asks once for a certificate trust (native/trust-cert.bat).
dsh-ontology-viewer
a158070653-hash/dsh-ontology-viewer
Renders .ttl, .owl, .rdf, .jsonld, .nt, .n3, .nq and .trig ontology files as an interactive graph in the DSH sidebar preview, with local Turtle, N-Triples, RDF/XML and JSON-LD parsing and no runtime dependencies.
dsh-siyuan-sender
baby7/dsh-siyuan-sender
Sends a Markdown file from the conversation into a self-hosted SiYuan notebook: a button on every delivered-file card and on the document-preview toolbar, or just ask the agent to send it, all through the SiYuan kernel HTTP API. Existing notes are never overwritten — a repeated title gets a timestamp suffix — and the API token stays in the host credential store rather than in settings files or the browser.
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.
dsh-session-timeline
columforge/dsh-session-timeline
Right-sidebar session timeline: fishbone layout of every workspace session with native fork/handoff lineage, manual drag links, branch fan-outs, archived-session display and per-turn detail browsing.
dsh-windows-computer-use
shinji00222/dsh-windows-computer-use
Windows computer use for DSH built on a native C# engine: text-only DeepSeek models can read UI Automation controls and fill forms in verified batches without screenshots, stale control refs can be re-found by unique identity, CAPTCHAs and verification codes are refused and handed back to you through the DSH approval prompt, and Esc stops the turn at any time. A derived project based on Yu-tao-Li/dsh-computer-use-win; do not install it together with that upstream plugin, since both drive the same desktop.
dsh-whalepaper
leriuslei/dsh-whalepaper
Animated ASCII orca-ocean wallpaper for DeepSeek Harness that follows local time, with native plugin settings for brightness, saturation and composition.
dsh-visible-action-row
bobnemimimmi/dsh-visible-action-row
Pins each message's action row — copy/like/dislike/branch controls, timestamp, and third-party additions — so it stays visible without hovering.
dsh-tokenlens
senyingxidi/dsh-tokenlens
dsh-TokenLens (词元透镜) — provider-aware plan capacity plus local token statistics (today/7d/30d/all-time, by harness/provider/model/workspace) for DSH.
dsh-ssh-mac
skyzzq/dsh-ssh-mac
Fork of @linxin666/dsh-ssh (the two cannot be enabled at the same time): resolves an SSH host by its NIC MAC address before dialing, so DHCP address changes stop breaking saved hosts.
dsh-search-proxy
chaos-paradox/dsh-search-proxy
SearXNG web search with a managed local runtime, external instance support, Web settings, and an optional DSH process proxy.
dsh-soul-evolve
xiachuyoufeng/dsh-soul-evolve
Persona state and slow evolution for DSH: five state dimensions (valence, arousal, energy, intimacy, focus) move after each turn and decay toward baseline over time; four scene types (work, tech, support, chat) modulate reply length and warmth without changing the state itself; the Soul panel keeps a persona card plus weighted evolution entries and injects them into the system prompt persona-first under a 4000-character budget. Ships a browser panel with a persona card editor and a live state view (the five metrics plus the last six events), appends a JSONL trace to disk, and seeds a usable default persona on first install.
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-autocad-bridge (bundle-autocad-ui)
cmm00100/dsh-autocad-bridge
Drives the installed AutoCAD over COM and exposes it to the agent as 18 mcp__autocad__ tools: connect and status, cancel the current command, list registered ProgIDs, list or create documents, save, create and list layers, draw lines, circles, rectangles, polylines, arcs and text, list entities, zoom to extents, and pass any native command through. A sidebar panel owns the Python bridge process — start, stop, restart, dependency bootstrap, live logs and crash recovery — and resolves every path at runtime, so the same bundle serves both the web app and the desktop app. Windows only, Python 3.10-3.12, AutoCAD 2022-2024 documented (2024 is the default; other versions require setting CAD_PROG_ID to the matching ProgID).
dsh-weekly-report
l956615272-hub/dsh-weekly-report
Report generator that follows your own style: pick DSH sessions by time window and slice each one to the turns inside it, optionally merge Git commits from several repositories filtered by author, then a new session reads the evidence with read-only collector scripts and writes a daily, weekly or monthly Markdown report matching a pasted sample; finished reports stay in a local library.
CatDogTrace (dsh-plugin)
xiebaiyuan/catdogtrace
DogCatTrace attribution parody as a right-sidebar tab: draw three integer challenges, paste each model reply into one box at a time, read the 24-breed dog and cat ranking.