Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

408 plugins found

G

draw2code

guchang/draw2code

An Excalidraw prototyping tab for dsh-better-sidebar with structured product clarification, conflict-aware human and Agent board updates, and prototype-guided frontend generation.

43 months agoUI EnhancementsApache-2.0
Q

dsh-plugin-install

qinyre/dsh-plugin-install

Install tab in Settings → Plugins: install, update and remove any plugin by npm spec, `github:user/repo` or local path through the same `dsh plugin add` CLI path; update checks against npm latest or GitHub HEAD with a downgrade guard and resolved-version verification, a pnpm 11 release-cooldown bypass on every add/remove, and service restart via the DSH Desktop shell or a relay process under standalone `dsh web`.

4last monthDev & Plugin ToolsMIT
A

dsh-plugin-tomato-todo (plugin)

anthealaffy/dsh-plugin-tomato-todo

Pomodoro timer, tasks and study planning in DSH, with a chat assistant that can read and update the same local records as the UI. Needs the separate tomato-runtime service (Linux release bundle from the project) running on 127.0.0.1:43987.

310 days agoWorkflow & AutomationMIT
H

MultiGameAssistant (dsh-plugin)

haaahhhis/multigameassistant

Manages game automation scripts from dsh on Windows. Installs and updates scripts such as MAA, runs them in scheduled pipelines, watches their logs and hands failures and stalls to an agent, and tracks game events.

32 days agoWorkflow & AutomationAGPL-3.0
F

dsh-supermemory

fish9988/dsh-supermemory

Cross-session long-term memory backed by Supermemory: pre-step semantic and chunk recall with per-session deduplication, debounced transcript upload, background LLM fact extraction (add/update/delete) with bigram and semantic deduplication, memory_search / memory_save / memory_forget tools, global or per-workspace container scoping, and a Plugins page UI for API key storage, memory CRUD, recall preview and activity log. Requires a Supermemory API key (a free monthly quota is available), and conversation excerpts are uploaded to Supermemory's cloud.

319 days agoMemoryMIT
B

dsh-mcp-center (dsh-plugin)

bai-2008/dsh-mcp-center

Browse, install, inspect, update, and remove MCP server connections inside DeepSeek Harness, with an online catalog and native Streamable HTTP/stdio support.

3yesterdayDev & Plugin ToolsMIT
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.

35 days agoModels & ProvidersMIT
R

companion-memory

root-7-khx/companion-memory

Roleplay companion memory for DeepSeek Harness: per-conversation editable persona documents (1-100 weight per entry, AI may refine them in small story-driven steps), per-speaker favorability and bond in multi-person chats, active memories with AI-scored vectors, a nine-emotion table updated every turn, an AI self-evolution ledger, recent 48-hour transcript search, companion-style conversation compression, sleep-time compute that pre-guesses the next topics while a conversation is idle, per-conversation tone cards learned from its own past replies, a habit-hint small-model bridge that writes the user habits it extracts into this conversation memory, a date-archived local knowledge base with auto-packing by turns or tokens, and a unified integrations page that lists curated plugins and downloads their GitHub releases. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.

36 days agoMemoryMIT
C

dsh-remote-console

cccodder/dsh-remote-console

Right-sidebar SSH terminal for DSH where you and your agent share one PTY: 16 agent tools, configurable transfer limit, session-isolated audit trail, one-click in-place updates.

32 days agoIntegrations & RemoteMIT
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.

38 days agoSecurity & PermissionsMIT
C

dsh-codex-history

chameleonn4/dsh-codex-history

Install it by asking DSH in one sentence, then it reads your local Codex CLI/Desktop chat history from ~/.codex/sessions and makes it usable inside DeepSeek Harness: a panel under the composer lists sessions with keyword and date filters and one-click import, the codex_history tool lets an agent list, read, search and summarize past conversations, a session whose working directory matches is injected automatically when a new agent starts, new Codex messages arrive as incremental updates in the running conversation, and a shared folder can mirror both Codex and DSH sessions across machines. Read-only — nothing is written back to Codex.

326 days agoSessions & MessagesMIT
N

dsh-preset-switcher-fork

neutronslime/dsh-preset-switcher-fork

Switch the current session's agent preset (mode) at any time, including after the conversation has already started, from a session-header dropdown backed by a fenced POST /preset-switch/api route. The route also repairs sessions whose recorded preset was deleted. Fork of jeffcwj/dsh-preset-switcher updated for DSH 0.2.1.

38 days agoSessions & MessagesMIT
T

dsh-kujira-persona

tests4gptplay/dsh-kujira-persona

Model-linked characters and a shared world for DSH, with separate editable personas and memories, optional AI diaries and sleep consolidation, Chinese/English controls, task-aware desktop pets, themes and usage statistics; updates preserve user customizations. Supports Windows, Linux and macOS; see the guide for each system's installation requirements. Diaries and consolidation consume tokens. Before installing or updating, we recommend closing visible desktop pets and bubbles; open files may cause installation to fail. Codex and OpenAI API account queries have been user-validated; other sources await user validation and feedback.

37 days agoIntegrations & Remote
H

dsh-jev-thinkout

han-1413141/dsh-jev-thinkout

Shows JeV-selected task plans, progress updates and stage summaries in DSH chat, with native translation or lightweight summaries. Requires a JeV key; the Jev service is called externally and may bill. and hierarchical serial/parallel task flows.

3last monthUI EnhancementsMIT
T

dsh-skill-center

tuoluosuan/dsh-skill-center

Browse, preview and install public Agent Skills from inside the DSH web GUI, aggregating five sources (claudeskills.info, skillsmp.com, the awesome-claude-skills repository list, the official anthropics/skills repo, and skill packs shipped by installed DSH plugins). Skills install pinned to a commit rather than a branch name, so what you previewed is what lands; the panel reports provenance, whole-tree update checks and a trash instead of deleting. Before writing anything it validates the skill name and frontmatter against the rules the harness silently enforces, lists files that SKILL.md references but the fetch did not bring, flags partial fetches, and offers overwrite, rename or skip when a name is taken.

3last monthSkillsMIT
T

dsh-find-ideas

tianyao2003/dsh-find-ideas

GitHub project search and analysis: describe your idea in one sentence and the agent searches GitHub for related projects, ranks them by relevance weighted with stars, and returns a structured card — last updated, relevance, stars, weighted score, language and a one-line description for each project. Pick a few repositories and it reads their README, dependency manifest, directory tree and key files to lay out their architecture — so you stand on the shoulders of giants before you start building.

3yesterdayTools & CapabilitiesMIT
L

dsh-plugin-genshin-launch

link258qaq/dsh-plugin-genshin-launch

Windows only. On every DSH start it checks, with no configuration, whether Genshin Impact is already installed — if it is, the game is launched (falling back to the miHoYo launcher when the game exits immediately, e.g. while an update is pending); if it is not, the launcher installer is downloaded to the desktop behind a size gate that rejects any link whose payload is more than 15 MiB away from the expected ~224 MiB, and a failed download falls back to opening the official download page.

3last monthJust for FunMIT
L

dsh-memory-delta

lpf20200901/dsh-memory-delta

Layered cross-session memory for DSH that pushes only what changed - the first round injects every active entry, later rounds push only added / updated / removed ones, and nothing at all is injected when nothing changed, with keys that merely repeat an entry id left out of the text so the baseline is about 26% smaller. Facts and decisions carry semantic keys (one active truth per key), the model may only write to an inbox that a human promotes, an entry can carry a review date that raises a one-time reminder when due, and search is relevance-ranked with journal lines down-weighted and Chinese matched by bigram. A sidebar tab tells the lifecycle story instead of listing files - entries are grouped by stage (awaiting confirmation / in use / archived) along four axes (topic - one level, human-assigned, type, tag, date), each group can be ticked for batch promote / withdraw / archive / restore / delete / assign topic, and topics can be renamed store-wide or searched on their own. The archived stage reads in three levels - the category says why an entry left (distilled into the docs / useless for good / not needed right now, the first two being defaults you can add to), below it the entry topic stays collapsed until you click it, and entries with no topic sit right under the category. The tab also shows the global and workspace instruction files plus the current injection size. A zero-dependency CLI ships with it, so the store is usable without DSH.

3last monthMemoryMIT
S

dsh-versions

shangdi178/dsh-versions

Version manager for the dsh host in a settings section of its own: shows the installed version against npm dist-tags, checks for updates, and installs, upgrades, downgrades or reinstalls any published version with a pre-upgrade local snapshot, failure rollback, snapshot-based rollback and an upgrade history. Before a cross-minor install it compares the @deepseek-ai/dsh-settings exports of the target release with the named imports of installed plugins to flag those that would stop loading, and it can apply or remove reversible compat shims that port removed legacy APIs back into framework files. Upgrade, restore and restart engines are Windows-only; version listing and checks work on every platform.

313 days agoDev & Plugin ToolsMIT
O

dsh-plugin-mgr

oxlyn/dsh-plugin-mgr

Card-style plugin manager in Settings: enable/disable each plugin through the profile patch layer, install-source details, npm update check with one-click update, uninstall, search, and load-error badges.

314 days agoDev & Plugin ToolsMIT
D

dsh-openwiki

d2moqi/dsh-openwiki

Brings the codebase knowledge-base capability of langchain-ai/openwiki into DSH — one-click generate/read/update of the repository Wiki, Grounded Claims (source-traced knowledge cards) and a project knowledge base built from uploaded local files, reusing the model DSH already has configured, with no second API key.

33 months agoTools & CapabilitiesMIT
L

orca-dsh-launcher

lheyang/orca-dsh-launcher

Windows desktop companion for DeepSeek Harness: update checker, server start/stop, system tray, graphical console, and one-click installer.

33 months agoTools & CapabilitiesMIT
G

claude-in-dsh

geekricardo/claude-in-dsh

Hand a DSH web session to the locally installed Claude Code CLI: a per-session engine selector (DSH | Claude Code), Claude models and reasoning effort in the model seat, Claude permission modes in place of the access-mode selector, and permission requests, AskUserQuestion and ExitPlanMode routed to the native DSH approval, question and plan-review cards. The stream is written as native DSH session events, so the built-in transcript, tool cards and nested subagents render it; Claude slash commands merge into the command palette; the CLI is held by a detached broker, so plugin updates and DSH restarts do not interrupt a running turn.

311 days agoModels & ProvidersMIT
J

dsh-unified-market

jing-hy/dsh-unified-market

Unified plugin marketplace built for the DSH Desktop (EAC) shell, aggregating the curated catalog, the GitHub dsh-plugin ecosystem and the npm registry into one storefront, with source whitelisting, conflict pre-checks, trial-boot install verification, manual/batch/auto updates and .dshpack feature-pack management.

32 months agoDev & Plugin ToolsMIT