Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

292 plugins found

V

dsh-docdesk

velestia-star/dsh-docdesk

An add-only Markdown library for DeepSeek Harness with a workspace file picker, a fixed icon grid with pointer-first hysteresis drag targeting, marquee selection and bulk folder moves, drag-to-folder and dissolve/delete folder actions, persistent move and line highlights, full-screen tabs, immersive reading, GFM tables, bookmarks, and local Mermaid/chart rendering.

26 days agoTools & CapabilitiesMIT
C

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.

223 days agoTools & CapabilitiesApache-2.0
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.

2yesterdayModels & ProvidersMIT
W

dsh-docdesk

wei238982377/dsh-docdesk

An add-only Markdown library for DeepSeek Harness with a workspace file picker, a fixed icon grid with pointer-first hysteresis drag targeting, marquee selection and bulk folder moves, drag-to-folder and dissolve/delete folder actions, persistent move and line highlights, full-screen tabs, immersive reading, GFM tables, bookmarks, and local Mermaid/chart rendering.

213 days agoTools & CapabilitiesMIT
S

yueling

sdsaewq/yueling

Yueling (月令) — a solar-term card for the DSH Web UI: a dot under the conversation header unfolds into today's term, its three pentads, how long until the next term, a day-pillar reading, and a year table of all 24 terms. The hexagram page casts coins and keeps a seven-day log; the jieqi skill is bundled.

210 days agoUI EnhancementsMIT
L

dsh-novel-reader

laoganr/dsh-novel-reader

Local TXT novel reader in the DSH right sidebar: bookshelf with file, directory and path import, chapter table of contents with jump, click-to-turn or vertical-scroll paging, reading progress restored across restarts, and font, line-spacing, background and night themes.

2last monthUI EnhancementsMIT
L

visionforge

lr611415/visionforge

Vision understanding + image generation/editing for DeepSeek Harness (read images with Qwen/OpenAI/Anthropic/Gemini, generate and edit with Qwen-Image). A rework of liustack/modlens (MIT). Remove @liustack/modlens first — both register the same vision providers and image interception hooks, so co-installation breaks image reading.

2last monthVision, Voice & MultimodalMIT
2

dsh-context-guard

2jumpsina/dsh-context-guard

Long sessions get expensive, and the platform compacts the context on its own. This plugin adds an occupancy badge (hover to see how it is computed), writes a handover draft into HANDOVER.md from 45% — files changed, money spent, what recent turns were about — and reminds you once at 60% to wrap up. On compaction it records the reading from just before, so you can check it later. No model calls, nothing added to the conversation; it does not prevent compaction.

224 days agoSessions & MessagesMIT
P

dsh-skill-intelligence

polinnizhong/dsh-skill-intelligence

Read-only Skill inspector for DeepSeek Harness. It shows which Skills a conversation actually loaded — from observed loading evidence only — and which Skills the current environment can discover, and gives each Skill a detail page whose left column switches between the framework, the evidence, validation, evaluation, step evidence, run logic, the before/after of a modification when there is one, the definition facts and the raw SKILL.md. Declaration and run stay apart: the body is split into structure, declared workflow and progressive disclosure, the run logic is read from local receipts, and every declared step carries its own evidence — no observed evidence is reported as exactly that, not as executed or not executed, and the run's instruction hash sits beside the current definition as match, mismatch or unavailable. The evidence view gives each subject one of three states (declared, observed, unavailable), walks definition → load → use → outcome, names what each stage cannot reach, declines to attribute an outcome to the Skill, and can copy the snapshot out as byte-stable JSON. Validation checks the Agent Skills open standard and the platform profiles separately, each finding on a rule id and labelled standard compliance or platform compatibility. Evaluation keeps repeatable cases with the conditions each run was recorded under and the four stages of runtime evidence, comparing two runs of one case item by item without scoring them. The trigger boundary keeps should-trigger and should-not-trigger prompts, has you run them in a real new session, then records what was observed — whether a load record appeared and whether it was model-invoked or user-explicit; a typed /name is not a natural trigger, and an absent load record is reported as not observed, not as not triggered. The same projections are exposed to the agent as a read-only skill_review tool, which returns a structured review packet and says what it omitted when the packet will not fit whole. The inspector, the evidence chain and these reviews are computed on this machine from the definition and the session receipts; the Chinese reading version sends the body through the host's model when you ask for it, keeping code fences, paths and frontmatter verbatim and storing the result on this machine. A Skill can also be cloned into a local copy. It does not write back to the source Skill and does not run its scripts.

2last monthSkillsMIT
X

dsh-reading-companion

xling001/dsh-reading-companion

Local TXT reader in a right-sidebar tab plus a spoiler-safe AI reading companion: the model only sees what you have already read — the current chapter, the tail of the previous chapter, and a per-book background file it grows as you go. Excerpts, thoughts and the companion replies become structured Markdown notes exportable to Obsidian; raw text unlocks only for a book you mark as finished.

214 days agoJust for FunMIT
D

dsh-pptx-sidebar

drscrewdriver/dsh-pptx-sidebar

A dsh-better-sidebar reading view for .pptx decks: slides in deck order, bullet levels, speaker notes and inline pictures. Ceilings on archive size, per-part inflated bytes and slide count keep a deck from freezing the tab.

22 months agoTools & Capabilities
D

dsh-docx-sidebar

drscrewdriver/dsh-docx-sidebar

A dsh-better-sidebar reading view for .docx files: headings from the style map, paragraphs, lists, real table cells, inline pictures and header notes. Ceilings on archive size, per-part inflated bytes and rendered blocks keep a document from freezing the tab.

22 months agoTools & Capabilities
M

dsh-approval-explain

martlet-tech/dsh-approval-explain

Adds an Explain button to the approval card: one model call returns exactly three lines reading the pending operation, covering what it does, which files or system state it reads, writes, modifies or executes, and a risky/attention/safe verdict with a one-sentence justification. It also renders the detail area for `write` and `edit` calls, which the shipped renderer leaves blank because it only reads a `command` field.

22 months agoSecurity & PermissionsMIT
H

dsh-conversation

huangfuren/dsh-conversation

Conversation outline panel for the DSH web surface: user questions as root nodes (index, time, tool count and text volume per turn) with the Markdown headings of assistant replies hanging beneath them, plus level slider, search scope, bookmarks, copy and export as Markdown, section jump, keyboard navigation, a right-edge density rail and per-session reading-position memory. Read-only UI: it never touches prompts, tool results or provider traffic, and writes nothing outside its own localStorage keys.

25 days agoUI EnhancementsMIT
V

dsh-clearview

vinzelles/dsh-clearview

Adds a Reading tab to the DSH web client that shows process steps and live reasoning in source order, collapses successful turns to the final answer, and keeps the original tabs, composer, and tooling intact.

212 days agoUI Enhancements
Z

dsh-x-connect

zmh2000829/dsh-x-connect

X (Twitter) connector for DeepSeek Harness: OAuth 2.0 credential binding, posting tweets with per-post cost estimation, and reading/summarizing related posts. Ships a settings card in the Web plugin page.

23 months agoIntegrations & RemoteMIT
W

dsh-reader

wodexinhaoleng-kasssa/dsh-reader

In-browser novel reader for the dsh web GUI: online book-source search, chapter-by-chapter reading in a chat-style view, and whole-book TXT download.

23 months agoJust for FunApache-2.0
A

dsh-thumb

aliceljy/dsh-thumb

A phone shell for the web GUI - the sidebar becomes an overlay drawer that closes when a session is tapped, the settings sheet goes full-screen single column, and the transcript is retuned for phone reading.

228 days agoUI EnhancementsMIT
Z

weread-export

zhengjy01/weread-export

WeChat Reading (WeRead) multi-target export for DeepSeek Harness via the official Skills API gateway: browse your bookshelf, export highlights & thoughts to flomo, a local Markdown file, or Notion, optionally reworked by a configurable LLM prompt.

22 months agoTools & CapabilitiesMIT
L

dsh-quick-toc

lyaxz/dsh-quick-toc

Conversation outline for DeepSeek Harness: the Markdown headings of the whole session, grouped by turn, in a side panel or a full-width curtain; hover previews can be pinned for comparison, bookmarks keep the places you come back to, and a right-click jumps to a section or copies a heading and the levels below it. Six theme colours and a translucent material, title/prompt/full-text/cross-session search, reading-position follow and a Chinese/English interface.

25 days agoUI EnhancementsMIT
A

dsh-agentmail

agentmail-to/dsh-agentmail

Gives an agent its own email inbox through AgentMail — eleven tools for sending, reading and labelling mail, plus inbound mail delivered into one harness session per email thread, with an approval gate and recipient allowlist on everything outbound.

23 months agoTools & CapabilitiesMIT
O

dsh-kb-sieve

omdsh-dev/dsh-kb-sieve

Build auditable KB packs (SQLite FTS5) from md/txt/docx/pdf with deterministic retrieval and original-text reading.

23 months agoMemoryApache-2.0
N

dsh-compaction-weave

nightfrost42/dsh-compaction-weave

Incremental context compaction plugin for long conversations in DeepSeek Harness, condensing earlier dialogue into structured checkpoint summaries, retaining user requirements and task progress, and archiving original messages and attachments locally for history search and reading as needed. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.

1yesterdaySessions & MessagesMIT
M

english-reading-analysis (dsh-plugin)

melanthacode/english-reading-analysis

English article and exam-paper analysis: paragraph-by-paragraph translation, answer keys, and long-sentence syntax breakdown, exportable as a print-ready PDF. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.

117 hours agoSkillsMIT