Plugins

Adds a Chats/Files switch to the left-sidebar Workspace header that swaps the session list for a lazily loaded tree of the current session's workspace. Files and folders can be dragged into the composer as @path references; clicking a file opens the built-in preview; the right-click menu reveals a file in the system file manager or copies its path; entries carry VS Code-style Git status (modified, untracked, added, deleted, conflict, ignored) relative to the last commit.

Pick a Git branch, or name a new one, on the New Session screen and start the conversation inside an automatically created worktree, so the current checkout stays untouched.

Import Agent Skills from Git repositories, group them by repository, and enable or disable each one in DSH settings.

Dynamics 365 CE / Dataverse toolkit for DSH: 15 tools for querying metadata and solution layers across environments, snapshots and diffs, field impact analysis, migration risk assessment, GitLab merge-request checks, contract drift, environment health, and review-gated metadata writes.

Session-header environment and branch chips: Local git-switches the checkout; Worktree creates an isolated git worktree under .agents/worktrees, registers it as a workspace, and offers merge, squash, delete, and auto-cleanup.

Merged commit timeline for the Git repositories in a DSH workspace, with per-repository dirty and ahead/behind state, fetch, and right-sidebar file diffs.

Qoder-style workspace mode and branch chips on the session row; picking a branch arms it, and the first message creates a dedicated git worktree and moves the session into it. Windows only: the write grant runs PowerShell Set-Acl; elsewhere Worktree mode reports an error and stays in the main checkout.

GitLab panel in the DSH right sidebar: commit graph, branches, changes, merge requests (inline diffs, review submission, pipelines), issues, and agent tools with an approval queue for triage and batch actions. GitLab data needs a personal access token or a logged-in `glab`; local git data works without either.

Resolve a shared URL into title, author, body text, cover and direct video links: Bilibili, Douyin, Xiaoheihe and GitHub are parsed structurally, while WeChat, Zhihu and other pages fall back to an OpenGraph summary (title, description, cover). Includes an optional download step for sending the media back through chat.

GitHub Trending radar inside the Harness Web UI: fetches the daily, weekly or monthly board (optionally filtered by a language), analyzes each repository into description, star gain, tech stack, highlights and risks, renders the result as a filterable card panel with paging, and registers the github_trending tool plus the /github-trending command.

Long-term memory for dsh with defense-in-depth hardening. Two tiers (project `.dsh-memory/` and user `$DSH_HOME/memory/`), each a plain hand-editable JSON file with bounded entries and tags. Writes are atomic (unique temp file + rename, previous revision kept in a bounded history/) and serialized across processes by a per-tier lock with stale reclaim; a disk-revision check refuses lost updates instead of silently overwriting another writer. Memory text is wrapped in explicit untrusted-data boundaries (forged wrappers stripped on write) to blunt prompt injection from remembered content, load-time validation rejects out-of-bounds stores, and symlink escapes out of the tier directory are refused with MEMORY_STORE_ESCAPE. No content-heuristic filtering and no confirmation step, so headless auto-consolidation stays intact. Install: dsh plugin --profile web add github:RocoFish/deepseek-memory.

Lingshu (灵枢) is a brain-inspired persistent memory, persona and growth system for AI coding agents: pure Python standard library, zero dependencies, local-first, requires Python 3.9+. Hippocampus/cortex layered memory with forgetting curves, dream consolidation, fuzzy associative recall, emotion system, persona drift protection, knowledge base, self-authored skills, and a local web panel. Ships as a DSH bundled skill; the separately installable cordis startup-injector plugin auto-injects sessions only when Lingshu is installed at ~/.dsh/skills/lingshu (or brainPy is configured) and Python 3 is available; the optional update check contacts GitHub/Gitee.

Loads a workspace's VSCode/Copilot AI configuration into every DSH session: `.github/copilot-instructions.md` is injected as standing instructions, `.github/instructions/**/*.instructions.md` are gated by their frontmatter `applyTo` and join once the session has touched a matching file, and `.github/skills/*/SKILL.md` are registered as DSH skills. Configuration directories outside the workspace, by default `~/.copilot`, are read as well, and a settings page edits that path list.

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.

Manage GitHub and npm from inside DeepSeek Harness: multi-account switching, repository management, workspace Git tree with one-click push, pre-push Agent review, and npm package browsing, packing, pre-publish review and publishing.

Open file references from the DeepSeek Harness chat output in your IDE (VS Code family or JetBrains, Visual Studio Code by default), positioned at the referenced line, in its project window, brought to the foreground, and self-updating from GitHub.

DeepSeek Harness 的 GitHub 与 Git 管理插件：多账号登录切换、仓库浏览与管理、工作区版本树、一键推送、推送前 Agent 审查。

Plugin discovery for DeepSeek Harness: multi-source, star-ranked search across GitHub's dsh-plugin topic and the awesome-dsh-plugin curated list, with a bundled offline index and a real offline keyword engine.

Control DeepSeek Harness Desktop sessions from WeCom on your phone, with session and model switching, tool approvals, task results and generated files, and QR setup in Desktop settings. Needs a dedicated WeCom smart bot; the first person to send it a direct message within 10 minutes of the QR scan (or the 6-digit code from the settings page) becomes the owner, and only the owner's direct messages are accepted afterwards.

Local development facts for Harness: environment and runtime-health probes, git status/diff/log/commit, write-time snapshots with version-by-version restore, and project checks for Node, Python and Go.

Wire up Feishu/Lark from a four-step wizard that discovers your chats instead of asking for a 32-character id, creates the app by scan, and runs a nine-item live self-test that names the exact scope to enable when a check fails. It drives a companion MCP server of 25 tools, including ones that move local files into a chat and pull a message's attachments back to disk. The MCP server is a separate install: take dsh-feishu-mcp-<version>.mjs from the dsh-feishu Releases (or npx github:yinsang0910-star/dsh-feishu-mcp); until it is in place the self-test reports MCP as not mounted and no mcp__feishu__* tool exists.

Syncs the DSH home directory and Mnemon memory data through a git remote: pull, push, sync on an interval, cross-device migration, initialization backups, and conflict detection that stops before pushing and keeps local commits. A panel lists up to 100 recent operations with their backup paths.

Lists Claude Code and Codex sessions in the DSH Workspace browser, where they can be opened, continued, pinned, renamed and archived, with terminal, file and git tabs.

Token usage dashboard for DeepSeek Harness. A dedicated settings page shows cumulative input / output / cache-read / cache-write token totals, a green GitHub-style daily heatmap colored by usage, and a pie / bar chart toggle for per-model (provider/model) usage shares — all read from local session logs, no upstream API calls.