Plugins
Browse, filter, and install DeepSeek-Harness plugins.
1024 plugins found
dsh-algorithm-tools
springrinbowcat/dsh-algorithm-tools
Training workbench for competitive programming — syncs Codeforces and AtCoder submissions, profiles weak tags, picks a daily three-band problem set, reviews contests, and keeps a check-in calendar. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
dsh-financial-skills
openfcp/dsh-financial-skills
A Financial Skills entry in the DSH left sidebar that opens a full-page catalog of curated financial-industry skills, built from the openfcp/awesome-financial-skills catalog.json. Search, per-category filters and an installed view; the detail dialog renders the skill's SKILL.md and lists its files, size, license and source coordinates. Install fetches the body from the source declared in the catalog (SkillHub zip, or GitHub raw with API and jsDelivr fallbacks), enforces file-count and size limits, then stages and renames it into the skills directory; uninstall moves the directory into .trash instead of deleting it. Six loopback-only routes serve the page, the client can only pass a skill id, and an unreachable catalog falls back to a bundled snapshot that is labelled as a snapshot.
dsh-remote-connect
winlin926/dsh-remote-connect
Continue the DeepSeek Harness sessions on your computer from a phone browser: scan a QR code, approve the device on the computer, then chat, answer tool approvals and preview workspace files in the host web interface itself, over the same Wi-Fi or a tunnel.
xiaofeiyu-academy
magicsandbag/xiaofeiyu-academy
Undersea learning platform for primary-school kids (grades 1-6): grade-based math/Chinese/English quizzes, a textbook shelf with PDF table-of-contents import, photo mistake collection, variant-question mastery tracking, a feedable fish pet with hunger, coins, outfits and achievements, multi-child profiles and progress reports.
dsh-plugin-whale-butler
cybeshi/dsh-plugin-whale-butler
A local-first ledger for DSH. Record an expense or income from one sentence or a screenshot, with accounts, categories, refunds, installments, loans, debts and offline HTML charts. Data stays in local JSONL files.
dsh-gatekeeper
huajikano/dsh-gatekeeper
Inspects the model's streamed reply before it is committed and either discards it or holds it for review when it reads as a refusal, so that text does not stay in the session context. Detection combines built-in phrase rules (an opening refusal, a capability denial, policy wording, first-person intent, refusals quoted in reasoning) with a plain-text word list and optional regular expressions. Interception can sit at the llm/stream waterfall, at the HTTP fetch layer before encryption (not TLS decryption, and it cannot tell which session a call belongs to), at both, or in a preview mode that shows a transient preview while the original chunks stay in memory until the whole reply has been checked. The same plugin also guards tool calls on tools/pre-execute: a command that deletes a drive, filesystem or user-profile root, formats or repartitions a volume, empties the Recycle Bin, fetches and executes a remote script, or writes to a raw device is denied, and a recursive delete outside build directories is recorded by default. Each tier can be set to deny, ask, record, or off, and the disk guard has its own switch. Both halves are heuristics: they can miss phrasings, the disk guard sees the arguments of a call rather than what a running script does, and they fail open.
dsh-locator
perrylink/dsh-locator
Whole-disk file-name search for DSH with a self-built cross-platform index, agent tools and a Web panel; no Everything required. It indexes your home directory by default; the first content search also builds a local full-text index (SQLite in the platform cache directory) of text and source files there (by extension, up to 1 MB each, 200,000 files) and of your recent DSH session messages; locator_export writes a SQLite copy of the index to any absolute path it is given, replacing an existing file when overwrite is true. The engine is a prebuilt Go binary shipped for six platforms (source in engine/), and the plugin makes no network requests.
dsh-rescue-guard
1250589385/dsh-rescue-guard
Standalone rescue for a broken DeepSeek Harness profile: a CLI that runs without DSH diagnoses the crash logs (six classified causes, from real incidents), pre-flights the profile for command-name collisions and files plugins read at construction time, arms a safe mode that loads only official bundles until a healthy boot restores them, and keeps manifest snapshots for rollback. A resident watcher watches the crash-log directories via OS file events — idle costs nothing, and when the loader dies the report is written within seconds, one file overwritten per crash. Windows only: crash logs are read from %APPDATA% and the watcher autostarts from the Windows Startup folder.
dsh-agentic-word-book
shallinta/dsh-agentic-word-book
Suiji Word Book: a word book panel that shows one word per page with picture, phonetics, pronunciation, five phrases and an example sentence, plus fill-in-the-letters spelling practice and a 12-type word-recognition quiz. Word data is kept as plain files in a local directory, and an included skill lets an AI add cards from a word list. The “+Word” button (hidden until enabled in Settings) starts an AI session and by default switches it to danger-full-access; turn that off in Settings.
aurabot-qq-mac
geng-zy/aurabot-qq-mac
macOS (Apple silicon) fork of aureth-labs/dsh-aurabot-qq: the same QQ persona bot (chat, voice notes, stickers, memory, song covers, modules) with the Windows-only code removed. It connects to a OneBot v11 gateway such as SnowLuma running in OrbStack or Docker, falls back to the macOS `say` voice, sends files over 30 MB to a containerised gateway through a loopback-only temporary download link, and installs the song-cover environment (Applio, audio-separator, uv, Rubber Band, separation models) at pinned versions. It keeps the upstream package name and plugin id (dsh-aurabot-qq), so it replaces upstream and cannot be installed alongside it; use upstream on Windows.
dsh-PEC
huajikano/dsh-pec
Control a DeepSeek Harness session from an Android phone: pair over Wi-Fi or Tailscale, follow the live transcript, send prompts, switch model, mode and permission, browse workspace files, run a terminal and change settings.
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-preset-studio (studio)
hycally/dsh-preset-studio
A panel for editing DeepSeek Harness agent presets. It reads and writes the files inside a preset, switches its prompt injections, documents, skills and tool rows on and off, and installs or uninstalls the preset. Editing is line based, so YAML comments and layout survive. The same package also ships the injector and the doc_update write-back tool that a preset mounts.
dsh-agents-viewer
atrestandbed-bot/dsh-agents-viewer
View and edit the AGENTS.md / CLAUDE.md instruction chain in a native right-sidebar tab — global, shared, and every project directory down to the session working directory — with in-place save that creates missing files, a chat-header toggle, and an /agents command that works without the panel.
agentkit-personal-assistant
kingsoftcloud/agentkit-personal-assistant
Standalone personal assistant DSH plugin with multi-Bot profiles and an explicit Cloud Computer Broker boundary.
dsh-session-recycler
zhezhi33/dsh-session-recycler
Two-stage session deletion for DSH on Windows: move a conversation to the recycle bin and restore it to its original sidebar slot; deletion confirmed in two steps to prevent deleting files by mistake, clearing the whole subagent tree, sidebar ledger, projection cache, log lines and exclusive attachments along the way. It also scans the files a conversation actually wrote, adds a file query that pastes the path information into the conversation so an agent can judge which files are safe to delete, highlights them in Explorer, and copies the paths grouped by type. Both this and iamwuzhanglin/dsh-session-recycler install under the package name dsh-session-recycler, so install only one of them.
dsh-files-menu
smellingtiger/dsh-files-menu
Right-click menu for the DSH workspace file tree: open a file, expand or collapse a folder, copy the absolute path, relative path or name, and reveal the item in the file manager.
dsh-agents-md
sillykjs/dsh-agents-md
Adds an Agent docs tab to the conversation view: it lists the AGENTS.md and CLAUDE.md instruction files DSH actually loads for the current session (the ~/.dsh and ~/.agents roots, plus every directory from the project root to the working directory), previews each as Markdown with per-file sizes and the 64 KiB instruction budget, edits and saves them in place after a sha256 version check, and opens the workspace folder from the path button; a saved file takes effect on the next message.
dsh-translation-assistant
coldgust/dsh-translation-assistant
AI drafts, you review: text, files, screenshots, and whole folders translated with your guidelines attached; scores and comments become AI rewrites. An end-to-end AI translation workflow.
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-artifacts
lucagiftzek/dsh-artifacts
An Artifacts tab in the DSH sidebar that lists the files an agent produced and previews them in place with live reload, plus artifact template tools for agents.
dsh-lab-assistant
oddeye4649/dsh-lab-assistant
Desktop-pet lab assistant for DSH that keeps experiment records, accumulates per-software notes, and generates Word/Markdown lab reports from real step-by-step evidence. The desktop pet and lab panel require the Windows desktop build of DSH; other profiles get the conversational tools only.
dsh-ssh-plugin
dalld/dsh-ssh-plugin
SSH for DSH agents: run commands and move files over SSH while private keys stay inside the Host process. ssh2 transport with an optional system-OpenSSH backend.