Plugins
Browse, filter, and install DeepSeek-Harness plugins.
373 plugins found
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.
dsh-request-params
xiaohai-78/dsh-request-params
Add your own parameters to the model requests dsh sends: OpenRouter provider routing and fallback models, reasoning, sampling and custom body fields, and headers, for OpenRouter or any other gateway. Parameters are organized by the channels dsh already has; a live preview shows what each request will carry, and a request log shows what was sent and what the gateway answered.
dsh-video-preview
orderg-x/dsh-video-preview
Plays local video and audio inside the conversation. Media files the model writes during a turn - screen recordings, transcodes, voiceovers - get a player under its final reply automatically when their paths appear in its commands, the command output or the reply; the play_video tool plays any other file. Video shows as compact cards with a hover preview, audio as a slim seek bar, streamed over HTTP Range so long files seek instead of loading into memory. Also registers a sidebar media preview renderer, since the built-in previewer treats mp4 as unviewable. The look_video tool lets the model see a video itself: a hidden local Chrome or Edge grabs frames into a time-labelled contact sheet (or big frames at given times, or a short range frame by frame), checks the audio (silence, too quiet, clipping, one channel only) and the picture (black or frozen frames), and reads MP4 / MOV headers for phone compatibility (codec, HDR, faststart and more), with ffmpeg fixes.
dsh-session-drag-move
furrybear2025/dsh-session-drag-move
Drag a session onto another workspace in the DSH sidebar and it really moves: the session-log header cwd is rewritten and the log directory is re-homed under the target project, with a progress bar while it runs.
dsh-terse-mode
cspyz/dsh-terse-mode
Four terse levels in the conversation header — less thinking, no web search, shorter answers — plus independent switches for reasoning effort, web search and subagents, mirrored in Settings. Changes apply immediately. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
dsh-webfetch
tyeclipse/dsh-webfetch
Web reading tools for text-only agents. Five read-only tools: web_fetch (any URL rendered as clean Markdown or plain text), web_links (inventory of a page's links), web_feed (RSS 2.0 / Atom entries), web_headers (HTTP status, response headers and redirect chain without downloading the body, HEAD with automatic GET fallback), and web_table (HTML tables extracted as structured rows with header detection and colspan/rowspan grid expansion). Transport is Node fetch plus a zero-dependency HTTP proxy implementation (CONNECT tunnelling, absolute-URI requests, NO_PROXY with suffix/wildcard/IPv4-CIDR matching, Proxy-Authorization). Zero runtime dependencies.
dsh-mobile-upgrade
langyo/dsh-mobile-upgrade
Requires DSH 0.1.5-rc.1. Mobile UI fixes for the dsh web profile: narrow-screen drawer and settings tabs, a full-width model menu, a stuck-request network chip, and a narrow-header collector that folds the lineage, subagent and background-job chips into one tappable sheet.
dsh-plugin-width-slider
djs326/dsh-plugin-width-slider
All-in-one UI plugin for DSH Desktop (Windows): conversation-width slider with fullscreen preview and follow-window mode, thinking-block enhancements (forced Chinese, expand/collapse, Markdown rendering), an Open With header button, UI label localization, a resizable settings dialog, session delete, and workspace tabs.
dsh-llm-commandcode
noirbright/dsh-llm-commandcode
Command Code Provider API chat for DSH with a Host-held API key, discovered model catalog, effort defaults, an optional zero-data-retention header, quota meters, and per-model OpenAI or Anthropic protocol selection.
DeepSeek-Harness-chat-billing
rayadesune/deepseek-harness-chat-billing
DeepSeek account balance, this session's billed spend, and today's total spend in the session-header badge; a turn-cost row in the message actions strip, a detail panel with per-model pricing and a today session-spend ranking. Official peak/off-peak pricing; balance from the real /user/balance API.
dsh-edex-jarvis-ui (bundle)
ph4310822/dsh-edex-jarvis-ui
JARVIS-style sci-fi HUD shell over the DSH web GUI: electric-cyan VITAL SIGNS / RT-MONITOR / RT-LOG left bar, POWER CORE gauges and a rotating RADAR scan disc on the right with up/down traffic chart, filesystem browser with file preview, and a terminal-styled composer with a JARVIS header strip that follows the active workspace.
dsh-plugin-open-with
hyrinx/dsh-plugin-open-with
Adds a capsule split-button to the conversation header: launch VS Code, terminal, or File Explorer at the current workspace directory in one click.
dsh-token-pet
pk7j7sqryy-ops/dsh-token-pet
Cute token-usage pet in the session header: live context occupancy, per-session usage and breakdown, plus date/weekday, weather, 3-day forecast and severe-weather alerts, all theme-aware.
dsh-peak-status
xiaoyi-xx/dsh-peak-status
Header chip for the DSH web GUI that shows whether the current Beijing time is inside DeepSeek's API peak window, with a live clock and countdown to the next transition.
dsh-focus-overlay
boogoo619/dsh-focus-overlay
Focus mode with a full-screen reading overlay that hides the header and composer and folds AI tool calls into summaries.
dsh-session-grep
chenshanhan0711/dsh-session-grep
Literal substring search across every conversation in the workspace, from a search box in the conversation header. The built-in index tokenizes with unicode61 and only matches whole tokens; this plugin scans the local session logs directly, so mid-token fragments and two-character Chinese words match too. Searches user and assistant message text (tool output is opt-in), rotates results across sessions so one long conversation cannot fill the list, and opens the matched conversation scrolled to the hit. Read-only over local session logs, no network access.
dsh-plugins-sidebar-manager
hightoward/dsh-plugins-sidebar-manager
Sorts the entries of the DSH sidebar panel list into one or two levels of categories, draws a titled collapsible header for each group, and shows or hides each entry, all edited from a Plugin Sidebar page in Settings and mirrored to $DSH_HOME/plugins-sidebar-manager.json.
dsh-skillbox
fenshal/dsh-skillbox
One page for every skill on your machine: lists what DSH, WorkBuddy, Claude Code, Codex and Doubao have installed, imports any of them as a DSH skill, and discovers more on GitHub or the ClawHub directory (sorted by real downloads). Experts can be attached per session with a per-turn avatar header.
dsh-session-transfer
xiaolin233-ctrl/dsh-session-transfer
Adds a "Move to another workspace…" row to every conversation menu: copies the full event log into the target workspace under a new session id (header, title and model preset preserved, delivery markers retargeted), reads the copy back to verify it, attaches it, then archives the original unless you keep it.
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.
dsh-content-search
appthin/dsh-content-search
Searches the whole conversation — not just the loaded window — from a button in the conversation header, opens the results in the right sidebar, paints every keyword yellow in both your messages and the replies, and jumps the conversation to the hit. History search runs on the host log, so it still works when the full-text index is disabled.
dsh-agents-viewer
atrestandbed-bot/dsh-agents-viewer
View and edit the AGENTS.md / CLAUDE.md instruction chain in a native right-sidebar tab — global, shared, and every project directory down to the session working directory — with in-place save that creates missing files, a chat-header toggle, and an /agents command that works without the panel.
dsh-local-trim
leonlee114514/dsh-local-trim
One-step local model onboarding plus a light harness for DSH. On load it probes loopback and private-network inference endpoints (llama.cpp, Ollama, vLLM, LM Studio), reads each model's context window and output budget from the backend, and registers the provider through settings, so a local model becomes selectable without hand-writing config. It then trims only that provider: masks the tool list through tools.restrict, drops named system-prompt sections and memory contexts, swaps the injected instruction block for a short one while preserving its first 80 and last 96 characters, and truncates tool-schema descriptions without touching structure or required fields. Cloud providers are returned as the same assembly object, untouched. The injected block is re-read from disk on every assembly, so editing the file takes effect on the next request with no reload. The panel in the plugin detail page is a live operations view: it shows whether the takeover is active and by which hook, how many characters the last assembly was trimmed from and to, and which providers are online (probed concurrently, with a real one-shot completion reporting latency and reply text per provider). If a local backend is not running, the panel offers a one-click launch: it probes the port first (never starting a duplicate), then starts the matching server (ollama serve, or a custom command you supply) detached and polls until the endpoint answers, clamping the wait to 3-600 seconds, reaping the child it just spawned if it never answers, and naming the paths it searched when it cannot find the binary. A stop button kills backends this plugin started (SIGTERM, then SIGKILL) and refuses to touch a server somebody else launched. When a model has just been downloaded and no backend exists yet, the panel can also scan the machine for .gguf files with hard caps (300 models, 20000 directory entries, Downloads only one level deep), start llama-server on the chosen one (skipping the .mmproj. vision projection and reusing a server that already answers), register the provider under the model id the backend reports, and run one real completion to prove it works. Before spawning anything it does a fit check that counts only the part of the file the GPU cannot hold: hostBytes = fileSize - VRAM, compared against max(total RAM - 2GB, free RAM). A file far larger than RAM is refused outright; a heavy host-side remainder is refused unless you confirm; the same remainder under mmap is only a warning, because the weights land in reclaimable page cache. A load-mode selector (auto / mmap / none / mlock / mmap+mlock) maps to llama.cpp --load-mode, and the default is whatever the engine picks. From 0.4.2 everything above is derived from the platform instead of assumed: home and data directories come from os.homedir() and the OS conventions (LOCALAPPDATA on Windows, ~/Library/Application Support on macOS, XDG_DATA_HOME elsewhere); backend binaries are looked up in the official install locations of each OS and can be pinned with OLLAMA_BIN, LLAMA_SERVER_BIN, VLLM_BIN or LMSTUDIO_BIN; model discovery walks DSH_LOCAL_MODELS_DIR, ~/models, ~/llama.cpp/models, ~/.cache/llama.cpp and the LM Studio data directory, with the WorkBuddy layout demoted to one candidate among them. VRAM is asked from nvidia-smi, then rocm-smi, then sysctl hw.memsize on Apple Silicon (flagged unified, so the same bytes are not charged twice), and any flip to a unified-memory budget is handled explicitly. Before building a command line the plugin runs llama-server --help once and keeps only the flags that build actually has, so older engines get --n-gpu-layers 99 and no KV quantization while newer ones get auto plus q8_0; anything it cannot probe is passed through rather than dropped. LM Studio is started with lms server start --port N rather than being lumped in with the engines that need a model argument, and vLLM gets its own --model example instead of llama.cpp syntax. Windows, macOS and Linux are all exercised in CI, including a windows-latest and a macos-latest job, because a cross-platform claim that has only ever run on one OS is not a claim. Two of those suites exist specifically to catch this machine's blind spots: one replays the whole suite with process.platform rewritten to each OS, and one deletes every advantage this development box has — no nvidia-smi, no rocm-smi, no sysctl, an empty PATH, a home directory with no models — and requires graceful degradation rather than a crash. That last one caught a real class of bug: several assertions hardcoded 'lms.exe', which cannot pass where the executable has no suffix. Measured on the reference machine: a 16.9GB 27.2B MoE with 14.5GB of VRAM holds a 285-691MB working set and sustains 76 tok/s after a 1000-2000 token warm-up, so file size alone is not a fit signal. From 0.4.3 the scanned models are shown as a table rather than a dropdown (one row per gguf, with its size and any fit warning), so you can see what is on disk before choosing. From 0.4.4 the delete button on the provider table removes the provider entry, not the weights file on disk. That distinction matters: what people actually want to clear out is the dead entry - one pointing at a port that never answered, one registered twice for the same port, one whose model file was deleted long ago - not a 15.8GB gguf. Deleting a config is undone by importing again; deleting a gguf is not. The removal goes through settings.mutate with an unset op on \['providers', id], because update merges layers: writing null there leaves a null provider key that the loader reads as a broken config rather than an absent entry, and only mutate/unset is implemented as Reflect.deleteProperty. The result is read back afterwards, because unset on a key that comes from a lower layer (the profile cordis.patch.yml or a home patch) does not delete it - it restores the inherited value, so the call succeeds while the entry stays. When the entry is still there the panel says so and points at the file to edit instead of reporting success, and a DSH whose settings service predates mutate() is told plainly rather than silently ignored. Deleting takes two clicks and clearing the confirmation is as easy as clicking another row; on success the online and baseURL caches are cleared and the tool surface is recomputed, since the provider list changed. The gguf itself is never touched by this plugin - the scanned-model table is display and selection only.VRAM reporting is driver-dependent. From 0.4.5 model discovery also reads Ollama's own storage: its blobs are named sha256-… with no extension, so extension matching could never list them. Weights are now accepted by extension OR by GGUF magic header (only dot-free files of at least 8MB, capped at 600 header reads per scan; obviously-not-weights extensions like .json/.md/.safetensors/.part are never opened). Ollama models are resolved from their manifests: the model layer is picked by mediaType application/vnd.ollama.image.model (never adapter/mmproj layers), the human-readable name is restored from the manifest path (…/qwen3/8b becomes qwen3:8b, …/latest stays bare), tags sharing one blob merge into a single row, and the metadata kv supplies name, quantization and context length. Adopting an Ollama model does not start a duplicate llama-server over the same weights: it confirms ollama serve answers on 11434 (launching it if not) and registers the provider under the tag the endpoint itself reports — the blob's sha256 name would never match anything, since 11434 lists qwen3:14b, not sha256-a8cc…. Two real-machine-only traps fixed on the way: existsSync('<file>/') returns true on Windows, so manifest-vs-directory branching now goes by parseable content instead of trailing-slash semantics; and the quantization label table had been copied from a stale ggml enum generation, labelling ggml_type 15 as Q5_K_S while ollama show reports Q4_K_M. Same-blob dedup is by (dev,ino), keeping whichever entry has a name. Verified on the reference machine: the scan goes from 1 row to 4 — qwen3:14b (8.64G) and qwen3:8b (4.87G) now appear with Q4_K_M badges — in 4ms; npm run verify exits 0 (launcher 57, portable 35, panel-host green including the linux/darwin simulated-platform runs); the new panel-host suite builds a real miniature Ollama store in tmpdir and points OLLAMA_MODELS at it, so results no longer depend on whether the test machine happens to have Ollama installed. From 0.4.6 the panel shows each model its real name instead of its file name, because some download tooling stores every weight under one generic file name, leaving the real name only inside the GGUF header. The scan now reads each file GGUF KV section - not a fixed-size head buffer, because tokenizer.ggml.tokens (hundreds of thousands of strings on a large MoE model) and the chat template push general.file_type past any window; and GGUF string arrays are interleaved (u64 length plus payload per element), so treating them as a length table walks the cursor off the rails and produces astronomically large reads. Reading and skipping are accounted separately: key names and types are always read, string values over 256KB and string arrays are only walked past without copying, non-string arrays over 64 elements are skipped outright, and a cursor past the file size stops the read, because an out-of-range position means the cursor is wrong rather than that a limit should be raised. The displayed name goes Ollama tag, then general.basename plus size_label, then general.name, then the file name, with the full string kept for the hover text since it usually carries internal build numbers; mmproj files are now identified by general.type as well as by name. A short read (truncated file) no longer feeds half a value into the parser. On the reference machine, reading one file header parses 44 keys in about 16ms, and a whole scan takes about 31ms. From 0.4.7 the smoke test no longer fails the first time and passes the second. The old code gave both request attempts one shared AbortController and one shared 30-second timer, so the total budget covered both rounds: a cold load of a large model burned it in round one, the abort left the signal permanently aborted, and the second round (the Ollama-style reasoning_effort: none retry) could not even be sent - which is exactly why the first click returned This operation was aborted and the second succeeded. Now each attempt gets its own controller and timer, a timeout retries once automatically (retryOnTimeout, on by default) because a first-request timeout almost always means the weights are still being read from disk, and non-timeout errors (refused connection, HTTP error) are not retried at all. Timeouts report themselves: the message says the wait exceeded smokeTimeout, whether a retry already happened, and points at the new smokeTimeout setting (seconds, default 60, clamped to 5-600) - port responding is not the same as tokens coming out, so it is a separate knob from launchTimeout. Unrelated: an example naming one specific model was dropped from the panel copy, since not every machine has that model downloaded, and the explanation now describes the mechanism instead. From 0.4.8 adopting a plain .gguf no longer registers an unrelated Ollama model. The port field used to follow the last click rather than the file: selecting an Ollama entry moved it to 11434, selecting a plain .gguf did not move it back, so a 11434 left over from an earlier click stayed. The server accepted it as given, probed the port, found Ollama answering and borrowed it (the skipped-launch log line about the port already answering is this path), and then the model id - derived from the file name - could not be matched against Ollama's /v1/models, where the fallback was to grab the first entry in the list. Embedding models tend to sort first, so the adopt registered a model the user never selected. Now the port follows the file: a plain .gguf landing on another engine's port (ollama 11434, vLLM 8000, LM Studio 1234) is moved to 8090 and the panel says so. Only ports belonging to a known engine are overridden - a hand-typed 9999 aimed at your own llama-server is left alone. The model-id fallback no longer guesses either: it takes the only entry when there is exactly one (a single-model backend may legitimately report a different id than the file name) and otherwise reports an error listing the ids it did see, rather than registering a wrong provider. From 0.4.9 the panel can no longer vanish. It used to be possible for the whole section to disappear from the plugin detail page while the host stayed up, the HTTP bridge kept answering, and no crash log appeared. The cause was a scope error: a helper was declared inside one component and referenced from another, which is valid JavaScript and passes a syntax check, so it only threw at render time - when the user pressed the scan button and React ran the state updater. The host wraps every slot entry in an error boundary whose fallback is an empty anchor, so the throw was contained silently: the panel was not uninstalled or crashed, it was replaced by an empty div. The helpers now live in the module scope both components share. The client half also gained its own test - a minimal React stand-in loads the real panel module, really calls the components, really runs the state updater at render time, and presses the scan button, so this class of error can no longer reach a release.
dsh-cookie-guard
kevindawn11-hash/dsh-cookie-guard
Caps the lifetime of DSH desktop's dsh-auth-* session cookies at 7 days, so they stop piling up in the Cookie header until startup fails with HTTP 431.