Plugins
Browse, filter, and install DeepSeek-Harness plugins.
2140 plugins found
dsh-MusicPlayer
xiekai886/dsh-musicplayer
A collapsible/expandable draggable floating music player with NetEase Cloud Music playlist import and song/artist search — chat and listen at the same time.
dsh-codex-tools
spyqwer1/dsh-codex-tools
Codex-backed `web_search`, `image_gen`, and `image_vision` tools for DeepSeek Harness, reusing ChatGPT OAuth login state.
dsh-web-preview
zoumutou/dsh-web-preview
Side web-preview panel: local static hosting, Markdown/code/image preview, one-click run of non-static projects (Cargo/npm/Go/Python) with live logs, drag files into the chat (saved to the workspace), element mark & annotate, workspace file search on 404, and link-click takeover into the side panel.
dsh-freebie-radar
stallenlu/dsh-freebie-radar
DSH plugin for ZiChuanLan/freebie-radar with a freebie_radar agent tool and a sidebar workbench panel mirroring the original site, with channel feeds, search, detail drawer and dark/light themes. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
dsh-workspace-status-board
cyf736222347/dsh-workspace-status-board
Status-first workspace board for the DSH sidebar: sorts workspaces and tasks by needs-input, running, then done; adds search, same-status drag ordering, task archive/restore, and three distinct status markers.
find-nyaa-anime-release
divisioncassini05-lab/find-nyaa-anime-release
Anime search and tracking for DSH: Nyaa release checks, scheduled catch-up, qBittorrent delivery, Bangumi lists and manual progress sync.
apk-reverse-skill
xiaotianya14/apk-reverse-skill
Mobile-first Android APK reverse-engineering skill for DSH and DSH Go — decode with jadx/apktool, locate ad SDKs and entitlement logic, patch smali or values, repack/align/sign, then verify on a real device. Installs the apk-reverse skill; all tooling runs locally in proot Ubuntu on the phone or on PC Linux.
dsh-recollection
cqxsg/dsh-recollection
Lets DeepSeek Harness agents autonomously search and revisit original history from the current session that has been removed from the model's context by compaction. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
find-nyaa-anime-release (dsh-find-nyaa-anime-release)
divisioncassini05-lab/find-nyaa-anime-release
Search Nyaa anime releases with quality and Chinese subtitle checks, manage scheduled tracking and qBittorrent delivery, and browse Bangumi lists with manual progress sync (dsh-find-anime). Needs Python 3.11 or newer on PATH.
tunetune
nanshine/tunetune
TuneTune for DeepSeek Harness: train, test, and improve small models with your Agent, with a workbench beside the conversation.
dsh-ai-search
745403lkh/dsh-ai-search
AI 搜索模式:答疑 / 百科 / 浏览三模式,联网检索、广告过滤、AI 排序摘要与百科词条,支持结果语言、百科档位、浏览三指标权重、页面状态保留与搜索历史;兼容 dsh-better-sidebar(侧边栏页签多开、引擎栏、自定义搜索引擎)。
dsh-onmyoji-guide
free-swallow1/dsh-onmyoji-guide
Onmyoji game helper with five tools: shikigami and soul lookup, skill text, crit and panel math, NetEase Dashen guide search, and intro card paths.
dsh-baidu-netdisk
justinzyc271828-sys/dsh-baidu-netdisk
Connects DeepSeek Harness to Baidu Netdisk's official MCP service for file search, file metadata, and storage quota. Requires Baidu account authorization after installation.
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.
dsh-comfyUI-control
xingxue-ux/dsh-comfyui-control
Adds a Drawing Mode agent preset whose 19 comfyui_* tools drive a local ComfyUI: Anima and Krea2 generation, LoRA search and download, Danbooru character tags, PNG metadata, an upstream repro check, and xiaofanqie de-obfuscation.
dsh-hierarchical-fishmemory
marsstorm/dsh-hierarchical-fishmemory
Layered long-term memory for DeepSeek Harness - a merge of AirPineApplea/feiyu-memory 4.0.2, dsh-soul-md and dsh-shallow-memory (do not install it alongside those plugins): a diary distilled from finished turns, a hand-written feelings diary, a persona card with version history, a hand-note injected in full every turn, and a short-TTL note layer, each capped separately so per-turn injection stays small; ships agent tools and a sidebar panel for recall, editing, compaction, and backup or restore from a local file, WebDAV or a gzip archive.
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-recent-sessions
tianxiaz/dsh-recent-sessions
A Workspaces-native Recent sessions section for the DSH left sidebar: favorites, running, waiting-for-you and unread sessions at a glance, with a one-click ☆ on every session row, one-line collapse and in-section search. It takes over the sidebar shell (the shipped sidebar package is disabled) and renders the official workspace/session browser inside it; its recent-sessions panel id conflicts with huangxp12/whybebabo, so do not install them together.
dsh-autocad-bridge (bundle-autocad-ui)
cmm00100/dsh-autocad-bridge
Drives the installed AutoCAD over COM and exposes it to the agent as 18 mcp__autocad__ tools: connect and status, cancel the current command, list registered ProgIDs, list or create documents, save, create and list layers, draw lines, circles, rectangles, polylines, arcs and text, list entities, zoom to extents, and pass any native command through. A sidebar panel owns the Python bridge process — start, stop, restart, dependency bootstrap, live logs and crash recovery — and resolves every path at runtime, so the same bundle serves both the web app and the desktop app. Windows only, Python 3.10-3.12, AutoCAD 2022-2024 documented (2024 is the default; other versions require setting CAD_PROG_ID to the matching ProgID).
dsh-memory-plugin
2132774831/dsh-memory-plugin
Fully local long-term memory for dsh: cross-conversation and cross-project, stored as a single JSON file on your machine with no network calls, no model calls and no API key. Ships memory_save, memory_search, memory_list, memory_forget and memory_review tools, keyword-and-tag recall injected before each turn with adjustable ranking weights, Markdown import (including Kun and Hermes Agent formats) and export (native and Hermes Agent formats), and a settings page to browse and edit memories.
dsh-model-visibility
tzyceng/dsh-model-visibility
Manage which models appear in the composer model menu. A settings page lists every provider's models with a per-model switch, provider-level show/hide, collapsible groups and filters by kind; switched-off models leave the menu while the model in use in the current session stays. The list can be searched by name or ID and filtered by capability (multimodal, reasoning) and by minimum context window (128K / 256K / 512K / 1M). Rows show the model kind, and chat models also show reasoning support with the adapter's effort levels, their context window and input modalities. Labels merge manual overrides, the settings document, the adapter, the relay's GET /models response, a built-in pi-ai / models.dev catalog, name inference and vendor corrections in that priority order, with the source named on hover and dashed borders marking inferred values. Any model can be edited by hand (kind, context window, modalities, effort levels); those edits are stored outside the profile and can be written back into the model provider's settings. A hard re-fetch drops every cache and asks the adapter and all relays again. A switch, on by default, lets relay routes whose models declare text-only input accept images in memory, without editing configuration files. The hidden list is stored in the profile patch and mirrored to $DSH_HOME.
dsh-obsidian-notes
revive123456/dsh-obsidian-notes
Obsidian-style notes panel in the DSH right sidebar: a tree over a local folder, Markdown preview with line numbers, edit and save, Obsidian callouts, tables and wikilinks, screenshot paste into the vault, one-click insert of a note path into the chat input, and batch archive or delete for sessions and workspaces.
dsh-memory-palace
dafantong01/dsh-memory-palace
Local long-term memory for DSH sessions: archives older turns under context pressure, with a turn-summary index for faster turn lists, statistics, window probing and archive planning (rebuilt automatically when unavailable, with a manual full verification), four tiered hot-memory boards, project documents with enabled/disabled/archived filters and optional owner-controlled family sharing, project hot memory, dual user/assistant turn previews, memory families with editable names and root transfer, root-abdication recovery, orphan-family takeover, summary keyword locator with segment-level candidates and paging, manual injection, 20K segmented reads, and tag-related retrieval. Includes staged recall cues, automatic compatibility with older memory layouts, and post-install version verification. Off in each new session until you turn it on with `/palace on` or the Memory Palace tab. All data stays in the workspace.
xander-zaozao-xiaban
gx18391303625-afk/xander-zaozao-xiaban
Xander Amazon seller-operations toolkit for DeepSeek Harness: 33 native xander_* tools and 7 skills for competitor research, keywords, listings, ads, replenishment and profit, with exact proposals, explicit approval and read-back verification for Amazon changes.