Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

382 plugins found

R

dsh-plugins (dsh-automations)

romany-saad/dsh-plugins

Keep your automation tasks in files you can version and review: write each task's schedule, prompt, model, permission and working folder in YAML, JSON or JS, and DSH's own Schedule is kept exactly in line, creating, updating, disabling and deleting tasks within a second of a save. Each task runs in its own conversation, persistent or fresh per run; /automations syncs on demand and names any file mistake; and a sync that finds no tasks never wipes the Schedule.

37 days agoWorkflow & AutomationMIT
N

dsh-prompt-chain

nihao7-l/dsh-prompt-chain

One-click 💪 prompt enhancement (prompt): thin draft? continue 🔜, unhappy? regenerate 🔄; auto-archive history 🕐 with rollback ↩️; result syncs back to the composer with a line-by-line diff; 🗺️show the panel 🎨 customise the 🪄 prompt-button icon 📍 and button position yourself.

320 days agoUI EnhancementsMIT
J

dsh-wait-subagent

john-walks-slow/dsh-wait-subagent

Active wait for background subagents in DeepSeek Harness: registers a wait_subagent model tool that blocks until a named background continuable subagent settles, then returns its stop reason and closing message — optional timeout, membership gate rejects unknown ids, event-driven with zero polling. Closes the gap between run_in_background fire-and-return and the async settlement notice; wait for a background subagent without polling list_agents.

322 days agoTools & CapabilitiesMIT
Y

dsh-tool-lipsync

yu-wenchao/dsh-tool-lipsync

Free lip-sync video generation plugin for DSH with 3000+ voices and 500+ languages.

32 months agoVision, Voice & MultimodalMIT
J

dsh-xiaoyuzhou

jerryqx/dsh-xiaoyuzhou

Listen to Xiaoyuzhou (小宇宙) podcasts in the DSH web UI: paste a share link to play anonymously (host proxies the audio with Range/seek), or log in via QR code to sync subscriptions, keyword-search shows/episodes, page full episode lists, and unlock purchased paywalled episodes; a `podcast_play` tool lets the agent play by link, podcast pid, or episode eid.

33 months agoJust for FunMIT
T

taxue-dsh-artisan

taxueseek/taxue-dsh-artisan

Integrated visual creation toolchain for DSH: prompt reverse-engineering and audit optimization plus multi-provider image generation with async background rendering.

3last monthVision, Voice & MultimodalMIT
X

math-research-dsh

xsoc1/math-research-dsh

Rigorous open mathematics research suite: four agent skills (rigorous-open-math-research, manage-math-research-program, math-research-workflow, lean-verify) for theorem solving with adversarial audit, research program management, pipeline orchestration, and Lean 4 formalization audit; CI-verified tests and mechanical upstream sync.

38 days agoSkillsMIT
J

dsh-model-sync

jiay98528-dev/dsh-model-sync

Writes live provider model lists into DSH settings and shows 5h/7d plan windows or metered balance for the current session model.

33 months agoModels & ProvidersMIT
S

uagent-sync (dsh)

severin-ye/uagent-sync

Cross-device workspace backup, restore, and ecosystem update via the uagent-sync CLI.

32 days agoWorkflow & AutomationMIT
L

gemini-quota-widget-dsh

lizhuonya/gemini-quota-widget-dsh

DSH Web catgirl companion and quota widget: tracks DSH balance and per-turn spend, syncs Gemini 5h/weekly quota via agy, Refresh Token, or OAuth, and adds a 1:1 sprite cropper, audio chimes, and custom dock positioning.

2yesterdayUI Enhancements
W

dsh-wdx-git

wdxtub/dsh-wdx-git

Git inside your DSH session: a right-sidebar panel for the current workspace and a global page listing every workspace, one sync button that becomes Fetch, Pull, Push, Publish branch or Sync, a commit tab that opens first with every change checked, AI-written commit messages from the staged diff, plus history, branches, stash and in-panel conflict resolution.

212 hours agoGit & Code ReviewMIT
K

tmem

kentzjh-cmd/tmem

Project-scoped deterministic execution trace memory and zero-token session digest plugin for DSH (v0.3.0), compiling session histories via temporal causal slicing and AST symbol attribution into guarded L0/L1/L2 playbooks with inline session_id lineage. Registers /tmem (status, list, forget, gc, telemetry, bench, evaluate, inspect, replay, diff, sync), recalls memories in agent/pre-step only on explicit file-path or error anchors (skipping unchanged repeated steps), and intercepts tools/post-execute errors and code edits with same-origin L2 fixes, failure-loop warnings, statistical L1 co-change partner hints, and runtime adoption telemetry (skipping idle read calls). Requires Python 3 on PATH (or TMEM_PYTHON) and spawns python3 -m tmem.cli asynchronously with a 5-second timeout; stores all data strictly inside each project's .tmem/ directory (no ~/.tmem/ global store) and makes no network requests. Needs Python 3 on PATH (or TMEM_PYTHON); it runs python3 -m tmem on every agent step and tool result.

219 hours agoMemoryMIT
Z

dsh-plugins (dsh-opencode2api)

zhiqiangme/dsh-plugins

Runs the standalone opencode2api backend (jasonxu114514/opencode2api, Windows x64/ARM64, no Docker or OpenCode CLI) with DSH and on exit stops only the process it launched; its settings card installs, updates or rolls back the backend from checksum-verified GitHub releases, copies the initial admin password and syncs /v1/models into an opencode2api provider with context, vision and reasoning efforts, re-syncing every 10 minutes. Frozen archive: 26.10.31 is the last version, and the author points to dsh-magpie as the replacement.

22 days agoModels & ProvidersMIT
W

DSH-PaperReading

wuke-luke/dsh-paperreading

Paper-reading workspace for DeepSeek Harness — page-by-page bilingual PDF translation, select-to-translate, paper-aware chat with page citations, notes, diagrams and cloud sync.

211 days agoTools & Capabilities
Z

dsh-plugin-zsxq

zhangcaiqian/dsh-plugin-zsxq

Knowledge-planet (zsxq) knowledge base toolkit: sync posts and attachments, extract docx/PDF text and images, rebuild an index, search, and self-check — pure JS, no Python. Requires a Knowledge-planet subscription and its Cookie, pasted into config.json.

28 days agoTools & CapabilitiesMIT
J

dsh-calendar-board

jy007/dsh-calendar-board

Month calendar panel in the DSH main column: add and edit a day's entries inline, overlay the Host's scheduled reminders for today and tomorrow coloured by run state, and merge iCalendar subscriptions with the calendars already synced into this Mac's Calendar.app; a calendar_board tool exposes the same entries to any agent session.

28 days agoUI EnhancementsMIT
X

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.

28 days agoMemoryMIT
Q

dsh-memory-sync

qic-9821/dsh-memory-sync

Sync a git-backed memory folder with a peer machine every time DeepSeek Harness starts — no daemon, no cron, no manual pull.

28 days agoMemoryMIT
J

dsh-plugin-syncup

jijijitian/dsh-plugin-syncup

Keeps plugin inventories in sync across machines through a secret GitHub Gist, and updates installed plugins to their newest npm or GitHub release. Push shows a diff first: version conflicts default to the newer side, entries only the Gist has stay by default, and entries only the local machine has are pushed. Each update can pick the npm or the GitHub channel, and every install goes through the plugin manager with a live log.

27 days agoDev & 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.

22 days agoModels & ProvidersMIT
Z

dsh-plugins (dsh-magpie)

zhiqiangme/dsh-plugins

Manages a Magpie model list and writes the checked models into a Magpie provider group: full sync from /v1/models, manual entries, per-model context, output limit, image input and reasoning efforts, sorting and drag reordering. On Windows x64/ARM64 it also downloads and upgrades Magpie from yetone/magpie-releases with SHA-256 verification and rollback, auto-upgrades once a release is 30 minutes old and all conversations are idle, starts Magpie in the tray with DSH, and toggles its lite mode and sleep prevention.

22 days agoModels & ProvidersMIT
P

dsh-user-sync

pandablessing/dsh-user-sync

Sync DSH user-level assets (skills, plugin manifest, config, memory) across machines with one-click restore, automatic plugin reinstall and secret scanning.

2yesterdayWorkflow & Automation
S

dsh-sync

shangshuo/dsh-sync

Encrypted, scheduled backup and restore of a DSH profile — plugins, settings, skills, UI preferences and optional MCP connector or API keys — to S3-compatible storage, WebDAV or a local folder.

220 days agoTools & CapabilitiesMIT
A

dsh-backup-sync

arlenman/dsh-backup-sync

Backup, restore and machine-migration for DSH: packs skills (which live outside ~/.dsh, in ~/.agents/skills), plugin manifests, core config, memories, todos and optionally sessions into a tar.gz with a sha256 sidecar, then imports it on another machine as a three-way merge against a baseline, listing per-file differences instead of overwriting changes made there. Credentials never enter an archive (filename deny-list of 27 names plus 7 private-key suffixes plus a content gate, enforced again on the import side), every import writes a pre-restore snapshot first, and an archive can be uploaded to any WebDAV server and pulled back on the new machine. Also includes scheduled backups, a read-only viewer for individual files, and an in-panel cloud card; no npm runtime dependencies (packing uses the system tar).

2last monthDev & Plugin ToolsMIT