Plugins

Kaipu Workstation — a cross-cloud, cross-platform console where agents collaborate on one workspace. Any agent runtime that speaks plain HTTP can take a seat, each with its own device credentials: project context is shared, files are kept per seat, and tasks rotate between seats with a trace of who did what. Workstation data lives on the server — this plugin is only the interface, so uninstalling loses no data and reinstalling restores it. The panel renders the persisted workstation state (no live stream yet). Workstation data is stored on the author's hosted server (agent.ak2029.com/kai-pu) unless you override baseUrl in the profile config.

An audit workspace for DeepSeek Harness: a multi-agent consultation venue where each review seat is filled by an agent, every judgment is routed to a named review face, and the whole run is kept as a traceable record. Works out of the box: the service endpoint is built in, a workspace is provisioned automatically on first launch, and review scenes come with their seats and agents listed. The built-in service endpoint is the author's hosted server (agent.ak2029.com/kai-pu): scenes, runs and review records are stored there unless you override baseUrl in the profile config.

A multi-project todo board inside DSH: capture notes in a global capsule overlay, group them into projects and mind maps, and export a todo into the composer as a task for the agent. Notes and todos are read and written on the author's hosted service (todo.memorymap.cn) after you sign in; set config.apiBase to point it at your own backend. Its HTTP routes have no DSH access check.

Back up and restore a whole DSH environment (installed plugins, DSH and plugin settings, skills, sessions and explicitly registered workspace files) into one private GitHub repository. Multiple machines share a single repo through per-device namespaces that never overwrite each other, and a pull can restore from this device, the latest backup or a chosen device. Push previews a read-only plan before writing, pull backs up local data first, secret-looking settings are redacted and key files are never uploaded. It calls api.github.com with the GitHub token you save in the panel (kept host-side only); its HTTP routes (/one-pack/api/...) require DSH browser auth.

Confluence and Jira over Atlassian remote MCP as a configuration-only bundle: one MCP client row, OAuth handled by mcp-remote with the token cached in ~/.mcp-auth, no login command and no in-app UI. Exposes mcp__atlassian__* tools (CQL search, pages, comments, JQL issues, transitions).

Deletes the dsh-auth-* login cookies DSH Desktop appends on every launch, which otherwise pile up past the 16 KB request-header limit and make the app fail with HTTP 431.

One credential store for many API platforms: keeps keys for GitHub, Cloudflare, Vercel, npm, Docker Hub, Hugging Face and custom platforms in the DSH credential store rather than in configuration or the session log, and gives the model three tools. apikey_call takes a path rather than a URL, so a key only reaches the host its platform fixes; apikey_platforms lists platforms and accounts without values; apikey_key gets, sets or clears one. Supports five auth shapes (bearer, custom header, x-api-key, basic, query string), verifies a key against the identity the platform returns, and reports transport failures as readable results instead of ending the turn. By default (exposeKeys on) the apikey_key tool can return a stored key's value to the model, which puts it in the session log; turn exposeKeys off to keep keys inside the Host.

Unofficial Loomy (iFlytek) model provider: signs in with an SMS code or by adopting the Loomy desktop app session already on the machine, registers one provider route per account from the live per-account catalog, and renews the daily 5000 free credits on startup and at local midnight. Unofficial: the endpoints and the desktop client's own application key pair were reverse-engineered from the Loomy desktop app, and automated traffic may conflict with Loomy's account terms. On first start it silently imports the login the desktop app keeps in a plain-text auth-session.json (on Windows it scans every C:\Users\Public\Loomy\*\userData folder and takes the most recently updated session), keeps sessions in $DSH_HOME/dsh-loomy/accounts.json, claims the daily credits at startup and every local midnight, and sends chat requests to loomyad.xunfei.cn.

A fork of dougen/dsh-deepseek-usage (the upstream repository has no license file; its manifest declares MIT) that adds IKunCode account balance queries alongside the upstream provider readers, subscription usage windows and model price snapshots. For IKunCode, your key is sent as a Bearer token to api.ikuncode.cc. It installs as @elsebit/dsh-deepseek-usage-extended from GitHub Releases with its own routes and settings, so disable the original usage plugin if you want a single card; the OAuth credential references it inherits are shared with the original.

Mobile gateway plugin that pairs DSH Mobile App with a self-hosted DeepSeek Harness host over an authenticated WebSocket. Fork of Clarklevis1995/dsh-plugin-mobile-gateway (same package name, install only one) that adds an optional encrypted address book deployed to your own Cloudflare account as a Worker with wrangler, an experimental WebRTC P2P transport, and a public-DoH fallback for its endpoint check.

Maintained continuation of dsh-network: authenticated LAN, Tailnet and HTTPS access to a DSH host, with pairing QR and current Web browser-auth support. Replaces the upstream dsh-network (remove it first; both register the same /dsh-network routes); the gateway listens on 0.0.0.0:3081 by default, set bindHost to restrict it.

Email assistant forked from dsh-email with host-side 163 IMAP monitoring that creates DSH conversations for summaries and reply suggestions, manual suggestions for selected messages, and persistent automatic/manual processing records with session links. Includes multi-provider mailbox browsing; automatic monitoring currently supports 163 IMAP only. Install it instead of dsh-email, not alongside (both mount the same tool-email row). It registers no send or draft tools; mail text goes to your configured model and is kept in the session logs; monitoring needs DSH running continuously and a 163 IMAP authorization code.

Multi-workspace agent federation with persistent ticket trees, parallel worker sessions, structured evidence reports, independent acceptance checks, retry/stop and restart recovery. Workers get shell and file tools in the ticket's directory, company_verify re-runs the ticket's acceptance commands in a shell on the host, and scope lists are task authorization rather than a sandbox. State is stored in ~/.dsh/ai-company; the optional company_repo_* tools run separately installed aoci/codegraph commands on any path they are given.

Continuous voice conversation for DSH: auto sentence splitting, a 2-second confirm window before sending, and spoken replies you can interrupt by speaking. Speech is recognised by DSH's own speech service by default (a local Whisper bridge or an OpenAI-compatible endpoint can be set instead), the recognised text is corrected by a DSH model call, and replies are read aloud through Microsoft Edge's online text-to-speech service, so reply text is sent to Microsoft. A daily check of PyPI and Hugging Face for faster-whisper updates is on by default; settings and any API keys are stored in plain text in ~/.dsh/voice-tutor-config.json. Its /voice-tutor routes require an authenticated DSH session (admission is checked per request), API keys are never returned, and applying an update needs a one-time confirmation token.

Postman-style HTTP workbench in the Harness Web GUI: collections and environments with {{var}} substitution, a request builder covering method, params, headers, body and auth, a response inspector, cURL import and export, and a CDN origin probe that fetches the same URL twice so a deleted file can be told apart from an edge cache. It also exposes an http_request_desktop agent tool that shares the panel send path, so a request debugged in the panel can be replayed by the agent. Zero runtime dependencies; state lives in $DSH_HOME/postman-desktop/store.json.

SMTP/IMAP email bridge with five tools: send, list, read, download attachments, and list folders. Needs Python; the send tool sends real email from your account, and the mailbox authorization code is kept in the profile's cordis.patch.yml.

Zotero bridge: search, read, add, update and trash items in a local Zotero library, read PDF annotations and notes, pull indexed full text, and find related papers by DOI. Needs Zotero 7 or later with its local API enabled; the first write triggers a Zotero authorization prompt (the key is stored in plugin-data/dsh-zotero/auth.json) and permanent deletion asks for confirmation. Finding and adding items query OpenAlex, Crossref, arXiv, PubMed and Open Library. Uses the same package name (dsh-zotero) as Vncntvx/dsh-zotero, so only one of the two can be installed per profile.

Download only a time range of a video (yt-dlp segments; long videos fall back to HLS when the DASH URL cannot be seeked), verify the cut with ffprobe and sampled frame contact sheets, and serve the clip over a temporary LAN HTTP link with byte-range support. Exposes video_clip_download, video_clip_verify and file_share tools plus a video-clip skill; requires ffmpeg/ffprobe. Installs yt-dlp with pip into $DSH_HOME/cache/video-clip when it is missing; file_share serves a file or directory over unauthenticated HTTP bound to 0.0.0.0 (visible on the LAN) for 30 minutes by default.

Local-first memory nebula for DeepSeek Harness with graph views, evidence chains, hygiene checks, and offline snapshots. Reads the memory stores of every workspace and of other memory plugins (read-only, for example meow-memory's SQLite) and writes only under $DSH_HOME/memory-nebula. Registers 9 agent tools and a system-prompt section (usage rules every turn, plus not-yet-read neighbouring memories after a few reads); its /export and /share endpoints return the full memory text without authentication on the local server, and an optional standalone engine listens on 127.0.0.1:7890.

Exposes the chat models of a locally signed-in QwenWork desktop app as a Harness provider, with a multi-account pool, session affinity and failover, pre-expiry credential renewal, a health watchdog, per-model enable/context-window/input-type settings, and account status with credit balance. Unofficial local integration that reuses your own signed-in client credential; your own account only. Windows only: needs the QwenWork desktop app signed in, and keeps its account pool in a DPAPI-protected file under %LOCALAPPDATA%. The author warns that reusing the client credential may conflict with the vendor's terms.

A Desktop 0.2.2-rc.1 adaptation of DSH WebTokens that registers a signed-in Chrome DeepSeek web session as the deepseek-web model in DeepSeek Harness, with tool-call transport, reply validation, a Chrome bridge extension, plus install and rollback scripts. It cannot be installed with the one-line plugin add shown on this page: it needs its own installer (node scripts/install-desktop.mjs, which backs up the whole profile first). Prompts, project content and tool results are sent to the DeepSeek website through your Chrome session; the author has tested it on macOS only.

Sticky notes wall in the sidebar: rich text, images, ink, drag-to-reorder, per-note alarms, and scheduled delivery of a note into a session. Its read-only /state and /media routes have no authentication.

Edit the session's working folder in code-server inside DeepSeek Harness, served through DSH's authenticated web server

Open the full DeepSeek Harness running on your computer from a phone browser, with QR pairing over LAN HTTPS and shared sessions and workspace; cross-network access needs your own HTTPS entry or a self-hosted relay (no public relay is provided). Connection and auth code is adapted in part from saya-ch/dsh-mobile.