Skip to main content

Plugins

Browse, filter, and install DeepSeek-Harness plugins.

417 plugins found

S

dsh-session-remover

sailoumili/dsh-session-remover

Adds Delete conversation and Batch delete to the sidebar session menu; a deleted conversation and its subagent sessions are moved to the Windows recycle bin, from where they can be restored.

325 days agoSessions & MessagesMIT
A

dsh-client-ui-aqua-patched

aliww2468/dsh-client-ui-aqua-patched

Aqua glassmorphism theme for the DeepSeek Harness web UI, forked from upstream and repaired to load on DSH 0.1.2-rc.1: mica and compatibility modes with adjustable blur and frost, fluid or wallpaper backdrop, background brightness, and a master switch that restores the stock UI.

320 days agoThemes & AppearanceAGPL-3.0
L

dsh-memory-delta

lpf20200901/dsh-memory-delta

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

3last monthMemoryMIT
C

dsh-paste-code-block

cjm-m/dsh-paste-code-block

Cherry Studio-style paste: multi-line/indented/fenced text or code pasted into the DSH Web composer collapses into a bordered, collapsible, language-tagged card and is restored as a fenced code block on send.

3last monthUI EnhancementsMIT
S

dsh-versions

shangdi178/dsh-versions

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

310 days agoDev & Plugin ToolsMIT
X

dsh-session-xc

xchannel1987/dsh-session-xc

Session management enhancement plugin for DeepSeek Harness - workspace session count display, archived sessions panel with restore/delete, drag-and-drop session move across workspaces.

38 days agoSessions & MessagesMIT
D

dsh-auto-maintenance

dong3434/dsh-auto-maintenance

Auto maintenance and resilience for DeepSeek Harness: startup self-diagnosis, automatic repair of missing directories, scheduled configuration backups with rotation, one-click restore, smart-start port detection, plugin-change self-check with automatic rollback, startup failure rescue, and a health watchdog that restarts a stuck-but-alive instance. Ships as a Cordis plugin plus a standalone CLI.

33 months agoDev & Plugin ToolsMIT
K

dsh-session-archive

kiligzzz/dsh-session-archive

Sidebar panel for archived sessions in DeepSeek Harness: group by workspace, search by title, preview user questions, one-click restore, or delete with confirmation.

32 months agoSessions & MessagesMIT
M

dsh-archive-manager

moonlitdropofblood/dsh-archive-manager

Archived-session manager for DeepSeek Harness: grouped archive panel with restore and delete.

36 days agoSessions & MessagesMIT
W

dsh-native-session-manager

wsl043/dsh-native-session-manager

Manages archived DSH sessions in the native sidebar with conversation search, restore, and confirmed safe permanent deletion.

33 months agoSessions & MessagesMIT
W

dsh-session-delete

wsl043/dsh-session-delete

Adds a red permanent-delete action with a confirmation dialog to the native session menu.

33 months agoSessions & MessagesMIT
B

dsh-composer-history

baisama-cloud/dsh-composer-history

Command history for the DSH composer: press Up/Down to cycle through previously sent instructions, then restore the draft at the end of the history; works in the official desktop app and web-profile builds.

32 months agoUI EnhancementsMIT
K

dsh-packer

klrsl/dsh-packer

Agent config packer for DeepSeek Harness: pack local agent assets (skills/sessions/profiles/settings/memory) into a zip for migration or sharing, with privacy scanning, diff-based restore, pack management, and a settings UI; memory ships as a read-only Markdown mirror, not the live database.

34 days agoTools & CapabilitiesMIT
Y

dsh-session-hotkeys

yeyeyeyeshifu/dsh-session-hotkeys

Session hotkeys for the DSH Web GUI: switch sessions like browser tabs (positional Alt+1-9, pinned slots, previous/next, new/archive/rename), keyboard model switching via Alt+M, alternate send, Esc focus hand-off, and Alt+W to close or restore a dsh-split-screen workspace — all rebindable with Windows/macOS presets. Verified on DSH 0.1.1 and 0.1.5.

38 days agoSessions & MessagesMIT
Q

dsh-safe-delete

qintsg/dsh-safe-delete

Safe delete plugin for DeepSeek Harness (DSH): move files to trash / staging area instead of permanent removal, with restore and purge support.

33 months agoTools & CapabilitiesApache-2.0
L

dsh-undo

linglambda/dsh-undo

User-side undo/redo for DeepSeek Harness (dsh): the /undo command rolls the transcript back to before the last message and /redo restores it.

33 months agoSessions & MessagesMIT
S

dsh-boot-guard

saisenbox/dsh-boot-guard

Loader-independent startup recovery for DSH Web that detects likely broken plugins, temporarily skips them, and restores only Boot Guard-managed changes.

33 months agoDev & Plugin ToolsMIT
S

uagent-sync (dsh)

severin-ye/uagent-sync

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

34 days agoWorkflow & AutomationMIT
C

voice-call

crease123/voice-call

Start with the author tutorial: https://www.bilibili.com/video/BV1t9sJ6NErV/ . Talk to your current DSH Agent without switching presets: automatic speech transcription and sending, streamed spoken replies, voice interruption, and a five-bar microphone meter. Choose DeepSeek or Doubao independently for ASR and TTS, configure your own credentials, and edit instructions applied only during calls. Includes a Bilibili usage tutorial, phone-button screenshots, and a Restore defaults action for call instructions.

24 days agoVision, Voice & MultimodalMIT
2

dsh-inkwell

2750599332-art/dsh-inkwell

Composer-toolbar button that rewrites the draft prompt into a clearer, more complete version through the Harness LLM route, with a revert control that restores the pre-enhancement text; a settings page holds style keywords and an independent model choice.

26 days agoUI Enhancements
1

dsh-rescue-guard

1250589385/dsh-rescue-guard

Standalone rescue for a broken DeepSeek Harness profile: a CLI that runs without DSH diagnoses the crash logs (six classified causes, from real incidents), pre-flights the profile for command-name collisions and files plugins read at construction time, arms a safe mode that loads only official bundles until a healthy boot restores them, and keeps manifest snapshots for rollback. A resident watcher watches the crash-log directories via OS file events — idle costs nothing, and when the loader dies the report is written within seconds, one file overwritten per crash. Windows only: crash logs are read from %APPDATA% and the watcher autostarts from the Windows Startup folder.

23 days agoDev & Plugin ToolsMIT
T

dsh-rss-news-daily

terry2010/dsh-rss-news-daily

RSS/news reader in the dsh sidebar: built-in source library + custom feeds (real-fetch validated on save) + OPML import; the fetch pipeline auto-translates foreign items and LLM-scores new items, generating a daily digest and hourly briefs to cut through information overload; with data backup/restore and preference customization.

218 hours agoWorkflow & AutomationMIT
Z

dsh-session-recycler

zhezhi33/dsh-session-recycler

Two-stage session deletion for DSH on Windows: move a conversation to the recycle bin and restore it to its original sidebar slot; deletion confirmed in two steps to prevent deleting files by mistake, clearing the whole subagent tree, sidebar ledger, projection cache, log lines and exclusive attachments along the way. It also scans the files a conversation actually wrote, adds a file query that pastes the path information into the conversation so an agent can judge which files are safe to delete, highlights them in Explorer, and copies the paths grouped by type. Both this and iamwuzhanglin/dsh-session-recycler install under the package name dsh-session-recycler, so install only one of them.

212 days agoSessions & Messages
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