Plugins

Contract clause work: build the clause tree, map it against a 12-key playbook, register the playbook and export the unresolved report — 5 `legal.*` tools.

Adds an ARIS agent preset that loads the 84 ARIS research-workflow skills and runs their reviewer as an in-harness subagent from a different model family than the session model. Other presets are unchanged. A fork of wanshuiyin/Auto-claude-code-research-in-sleep's dsh-aris branch: install it instead of the upstream dsh-aris plugin, not alongside it - both register the mcp__codex__codex reviewer tools and the same ARIS skills.

Registers a web-design skill and a compact system-prompt rule set for a three-layer shadcn/ui, Canvas UI and ThreeUI workflow, with Radix UI Colors and strict interface rules.

DeepSeek account-backed web search and page fetching for DeepSeek Harness sessions whose chat model runs through a third-party subscription or gateway (for example OpenCode Go): registers deepseek-account-search and deepseek-account-fetch providers that call the official Search and Fetch APIs with the signed-in DeepSeek account token, so the built-in web_search and web_fetch keep working without a DEEPSEEK_API_KEY.

Computer Use for every DSH session: screen capture, mouse and keyboard, app launch, plan and skill replay, an audit log, guards for dangerous actions, a background code agent, and an OCR workflow (text and coordinates) for apps whose accessibility tree is empty. Verified on macOS only: Windows has a basic GUI backend that is unverified, Linux has no desktop backend (calls fail with unsupported_platform), and the window/AX/browser/clipboard tools register on macOS only.

Look up Chinese companies inside the conversation: name a company and get its business registration, shareholders, executives, outbound investments and registration changes, plus judicial and operating-risk records such as enforcement, dishonest judgment debtor, consumption restriction, abnormal operation, serious illegality and administrative penalties (11 dimension groups). Results render as conversation cards with fields and the raw payload on expand, and the API key is saved from the plugin page into the Harness credential store.

Bilibili companion for DSH (MIT fork of Alterssss/dsh-bili-whale; do not install alongside the upstream — both register the same `/dsh-bili/` settings routes and share `~/.dsh/bili-whale.config.json`): wakes on a schedule, reads videos through subtitles, danmaku, hot comments and covers, writes two diaries, and shares at most one pick per wake by commenting on the video and @-mentioning the owner (daily quota 3; DM when `share.via=dm`). Inbound DMs, commenter names, summary requests and live danmaku are normalized and scanned for injected instructions before they reach the model; only the owner DM channel can carry an authorization prefix.

One settings card that gives every DSH agent mode its own compaction threshold: it registers <mode>-compact-<ratio> preset copies with compaction-basic.thresholdRatio rewritten, re-registers when the value or the selection changes, and can adopt one copy as the default mode (standard > cordis > minimal > ptc).

Actually delete DSH sessions instead of archiving them (Windows only). Clears all six on-disk locations (transcript, title cache, billion-context SQLite index with VACUUM, workspace registry, cost-meter ledger, bridge logs) with a dry run, a backup, byte-for-byte rollback, and an automatic quit-delete-relaunch flow.

Community fork of kingcharleslzy-ai/dsh-purge (do not install both - both register the same `dsh-purge` row as the `dsh-purge-community` package): the community '破甲' (unrestricted-mode) control for DeepSeek Harness - host-policy patches, prompt and rule settings, diagnostics, verified updates, and local backup and rollback, plus a three-layer bootstrap installer (engine, code and prompt layers) with its own verification pass.

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.

Huawei Cloud CodeArts provider for DeepSeek Harness with OAuth2 PKCE/DPoP sign-in, multi-account rotation, model discovery, and credits and usage views. A derivative of elegant01/dsh-codearts (MIT) with added account and image features; do not install it alongside the upstream - both register the same `codearts` provider.

DeepSeek balance, today's spend, peak/off-peak countdown and per-turn cost rendered as one text line embedded in the DSH sidebar footer, plus a low-balance alert. A text-only derivative of dsh-whale-widget (MeteorNOX/DeepSeek-Balance-Whale-Widget); do not install both - they register the same /dsh-whale/* routes and share the same ledger files.

Fork of FeatherHunter/dsh-prompt with draggable custom template ordering — drag the handle in Settings to reorder custom prompts (saved to the host); preset ordering unchanged. Do not install alongside upstream dsh-prompt: both register the same UI and /_dsh/dsh-prompt/ route.

Right-click menu for file links in chat: open with registered apps, save as, copy path or content, reveal in Finder or Explorer.

Remote-Linux-Serververwaltung in der Harness-Web-UI: Dateien durchsuchen und bearbeiten, Hoststatus prüfen, Docker-Container starten/stoppen/neustarten, Images prüfen, Docker-Registry-Mirrors einrichten, firewalld/ufw-Regeln verwalten, apt-Quellen wechseln sowie Entwicklerwerkzeuge erkennen oder mit apt installieren/aktualisieren.

Stellt vor Arbeitsbeginn die wenigen entscheidenden Fragen zur Vorgehensweise: einmalig, etwa 200 Tokens pro Sitzung, ohne Toolregistrierung und ohne zusätzlichen Modellaufruf.

Local-first-Recherchekit für DSH mit den Modellwerkzeugen kb_grep, kb_list und kb_save. kb_grep durchsucht die Markdown-Wissensbasis mit ripgrep oder, falls es fehlt, mit grep. kb_list und kb_save nutzen den eingeschränkten ctx.fs-Dateisystemdienst; Standardpfad ist ~/dsh-kb. Die Skills local-first-research und session-memory sind ebenfalls enthalten, müssen aber selbst in ein DSH-Skill-Verzeichnis kopiert werden; das Plugin-Bundle installiert sie nicht. Reines Node ESM ohne npm-Laufzeitabhängigkeiten, inklusive frameworkfreiem node-Test-Harness. Installation mit plugin_manager install_bundle; keine Client-Oberfläche enthalten.

VS-Code-artiger Workspace-Keyword-Such-Tab für die dsh-Web-GUI, registriert in `dsh-better-sidebar`.

Registriert Qoder-CN- und internationale Modelle in DSH und ruft die Modellpreise abhängig von Nebenzeiten automatisch ab. Bietet außerdem täglichen Check-in, Usage-Pill und Guthabenabfrage. Erfordert den Qoder-Anmeldestatus auf diesem Gerät.

System-Proxy-Steuerung für DSH: `NO_PROXY`-Richtlinie, Verbindungsdiagnose und Proxy-Umgebungsinventar über die `dsh-flash`-QuickControl-Registry.

Manager für DeepSeek-Harness-Agent-Presets: Registriert und verwaltet Agent-Presets zur Laufzeit, ohne DSH-Konfigurationsdateien zu bearbeiten.

Abgeleitet von WolfGenerals/ncm-player (ncm-player4-1.3.1-Linie; Baseline im Repo-Branch `baseline/ncm-player4-1.3.1`). Nicht zusammen mit ncm-player2/3/4 aktivierbar, da alle das Präfix `/ncm/api` registrieren. Schwebender NetEase-Cloud-Music-Player in der DSH-Weboberfläche mit Suche, Playlists, synchronisierten Texten samt Übersetzung, persistenter Warteschlange, einklappbarer Minileiste und ziehbarem Notizknopf unten rechts, der im Bass pulsiert. Titel ohne abspielbare URL werden automatisch übersprungen.

Verknüpft über eine Composer-Schaltfläche ein GitHub-Konto mit DSH (OAuth device flow oder personal access token) und stellt github_api für REST-Aufrufe bereit: Repositories erstellen, Dateien schreiben, Pull Requests und Workflow-Läufe lesen. Mit Schalter für Nur-Lesen und Aufrufprotokoll. Neu geschriebener Fork von Moon-shiyue/dsh-github-connect (MIT): device-flow-Client-IDs werden akzeptiert, Query-Strings und Nicht-ASCII-Pfade unterstützt, undici ist keine feste Abhängigkeit mehr, Panel mit vier Tabs. Nicht gemeinsam installierbar, da Toolname github_api und Credential-Namespace übereinstimmen.