Plugins
Durchsuche, filtere und installiere DeepSeek-Harness-Plugins.
4060 Plugins gefunden
dsh-workspace (dsh-code)
gabrielbav/dsh-workspace
Codex cloud–style coding sessions you host yourself: pick a GitHub repo and branch, and each session gets its own checkout and branch, a live preview of the app it builds and an Environment tab, inside a gVisor sandbox (non-root, no capabilities, no Docker socket) whose traffic passes an egress allowlist you extend host by host; your GitHub token never enters it. Runs on your computer or your own VM over SSH.
dsh-exec
eray114514/dsh-exec
Run DeepSeek Harness from a shell, a script, CI or another agent with one command: the session is created inside the desktop host, so it appears live in the sidebar and can be continued there, stdout carries only the final answer unless the NDJSON stream is requested, and all four agent presets (standard, ptc, minimal, cordis) can be picked per run. It serves loopback HTTP routes that require a bearer token; the settings route additionally accepts a same-origin request from the app page. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
dsh-drop-by
yuyu654/dsh-drop-by
Let your DeepSeek agent proactively reach out to you with its own new discoveries to share. dsh-drop-by keeps your chosen persona and combines recent chats, memory, and daily routines to pick the right moment to speak while leaving you quiet when busy. It can search the web, read pages, and watch videos on its own—switching between research and leisure—and bring back discoveries, progress, and its mood at the time. Choose QQ or Douyin DM as the primary entry sharing one DSH session; send a quick request from your phone to start a search, advance exploration, or organize notes and receive the results when done. Supports burst message merging, natural follow-up during active chats, session context handoff, and optional FishCondition phone health awareness, with full control over frequency, quiet hours, and exploration pace.
dsh-task-toast
kook543/dsh-task-toast
Windows 10/11 desktop notifications for DeepSeek Harness: approval requests, interruptions, questions, and completed tasks. Clicking a notification opens the session that produced it. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
dsh-octagon-alerts
hexa-center/dsh-octagon-alerts
Plays a synthesized chime when a Session needs a choice, needs approval, or finishes while you are away, with a pickable chime and a volume slider for each moment.
dsh-qqbot
chaorenzeng/dsh-qqbot
Fork of tencent-connect/dsh-qqbot that connects QQ Bot API v2 private and group chats to the DeepSeek Harness agent loop, adding a message-handling mode that either queues incoming messages until the running turn finishes or injects them into it right away with agent.followup(); also ships QR-code binding, per-chat session routing, slash commands, approval and question forwarding, and allowlist-based access control. Requires Node.js >= 20.3.0 and a QQ Bot AppID/AppSecret.
dsh-expert-role
yjnmedia/dsh-expert-role
Expert Library (also called Expert Role or Private Think Tank). Domain knowledge libraries for agents: each expert is a folder with SKILL.md, a manifest and references; only its name and one-line description sit in the skill catalog until the model loads it, so a large corpus stays out of the context. Ships two experts (design, DSH plugin) that are copied into the library on first start, fill-only and never overwriting yours. 12 tools create experts, move material in, find documents, plan and record research, dispatch steps to child sessions or open a standalone workspace. A gap list shows which questions went unanswered, a five-star maturity score uses structure, coverage, content, freshness and research closure (the fifth star also needs real usage), and a panel shows per session which expert was loaded and which file was read. It reads and writes files under the expert root; its HTTP routes accept local requests only; dispatching steps or opening a workspace creates child sessions and spends tokens.
dsh-plugin-yanyan-toolkit
sweet560/dsh-plugin-yanyan-toolkit
A DeepSeek Harness toolkit bundling four independently toggleable plugins: a plugin update checker that also covers local git/file sources, session archiving and deletion reusing @linxin666/dsh-session-archive, a subagent manager with physical delete plus session-log retirement, and a plugin-icon generator. It adds its own host route to read component versions from each package and exposes three agent tools for listing, deleting and cleaning up idle subagents.
dsh-plugin-trim
haidai233/dsh-plugin-trim
Trims the tool surface per session. Each session owns a profile — a tool whitelist — applied through `agent.ctx.tools.restrict({ allow })` on that agent scope only, and switching one session never touches another; `full` is the built-in no-restriction profile. The provider only picks the default: a session created or switched onto a local provider (explicit `localProvider`, `routes`, a loopback/private baseURL, or a local-ish id) gets the `local` profile, a cloud one gets `full`, and the re-plan runs on model-selection events plus one delayed pass because the projection can land after the event. Profiles are editable from the panel and persisted under `~/.dsh/plugin-trim-state.json`; an explicit per-session choice overrides the provider default until cleared. A separate, opt-in layer physically disables whole plugin entries through `pluginManager.setPluginEnabled` — that one is profile-scoped by API and the panel labels it as such rather than pretending it can be per-session. A `tool_trim` tool exposes list/status/profile/set/apply/restore to the model. The panel is served by a loopback-only HTTP server the plugin starts on its own fixed port — `http://127.0.0.1:12256/` (auto-bumps on collision, configurable) — because the DSH port changes on every restart and a locally linked package gets no market card in the sidebar; it lists live sessions with their profile and tool count, an editor per profile, a provider picker limited to providers declared in the profile or currently in use, and the full plugin list with search and paging. Two implementation details worth knowing: `tools.restrict()` is an intersection and cannot widen, so the old restriction is released before the visible set is read — otherwise switching to a bigger profile would shrink instead of grow; and every disposer is registered on `ctx.effect`, without which a hot reload leaves an unremovable restriction behind. Measured on a 12GB laptop GPU with a 27B model and a fully resident 256K cache, same conversation: 105 tools / 56,306 prompt tokens / 22.5 tok/s decode, 62 / 34,207 / 43.0 after disabling three tool-heavy plugins, 14 / 12,890 / 66.8 after a session moved to the local profile, with prefill rising from 487 to 1,310 tok/s. Restricting also drops the skill catalog injection, roughly 4.3K more tokens. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
dsh-mcp-bridge
google-q-dot/dsh-mcp-bridge
MCP bridge for the running DeepSeek Harness desktop: 26 tools over a loopback MCP endpoint let Antigravity, Claude Code, Codex or Cursor drive the same live sessions, answer approvals and questions from the MCP side, keep per-session interaction modes, and use a reconnecting stdio proxy with a no-duplicate replay policy.
dsh-workspace (dsh-plugin-aws)
gabrielbav/dsh-workspace
Gives every DSH session AWS's official MCP servers: 59 servers in 14 groups (documentation, IaC, EKS and ECS, Lambda, DynamoDB and Aurora, CloudWatch, cost and billing, Bedrock and more), switched on from a Settings page by group or one at a time. Versions are pinned, servers start read-only where they support it, and secrets stay in the DSH credential store.
dsh-workspace (dsh-connectors)
gabrielbav/dsh-workspace
One Settings page that connects Linear, Jira & Confluence, GitHub, GitLab, Trello, Granola and Azure DevOps to every DSH session, including chats, subagents and automations, with OAuth or a token; add any remote MCP server by URL. Tokens stay in the DSH credential store, and OAuth tokens renew themselves.
dsh-plugin-magic-context
elvisw/dsh-plugin-magic-context
Magic Context frees up context in long DSH sessions and carries project knowledge into the next conversation. It summarizes older exchanges and reclaims tool output that can still be retrieved by tag, so starting a new session means less explaining from scratch.
dsh-subagent-governor
zhengjy273/dsh-subagent-governor
Caps a session's subagent count, including finished children, asks or denies when the cap is reached, and reuses a similar finished child instead of spawning a new one.
dsh-session-delete
ze579/dsh-session-delete
Right-click a conversation and delete it after two confirmations. Removes the session directory, workspace accounting (archive and pin entries) and the projection cache; refuses while the conversation is still running. Supports DSH >=0.2.2-rc.3 <0.3.0. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
dsh-butler
yutouaa/dsh-butler
One dedicated butler session per workspace. A workspace-menu item enables it, creating (or reusing) a session titled "管家" in that workspace. From that session, four tools list what the other sessions in the workspace are doing, digest their memory and skills in one call, name sessions by role, and dispatch a task to a session by role name, unique title or id. Dispatch uses the host in-process delivery with the scheduled-task service as the fallback. Other sessions in the workspace are refused. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
dsh-plugin-restart
threadripper123/dsh-plugin-restart
Checkpoint and restart DSH through an independent watchdog so interrupted sessions resume automatically.
dsh-del-chat
slz2025/dsh-del-chat
Adds a Delete archive item to the sidebar Session menu for archived Sessions. A confirmation dialog shows the JSONL log size and projection cache state first; confirming removes the Session JSONL log, projection cache and Workspace record from disk. Unarchived Sessions never offer it, and attachments plus the cost ledger stay untouched. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
dsh-session-retitle
sirius2alpha/dsh-session-retitle
One-click session title regeneration for the current session: a labelled button beside the title, a row in the session header menu, the /retitle command, and a retitle_session agent tool, all calling the composed session-title service's explicit refresh.
dsh-agent-history-import
sirius2alpha/dsh-agent-history-import
Import conversations from local Codex, Pi, and Claude Code histories into DSH, then continue them with the full transcript or a detailed summary.
my-dsh-message-search
myhylijp/my-dsh-message-search
Message search across sessions: Ctrl+F to search message bodies in the current session, one workspace, or every session.
dsh-workspace (dsh-plugin-session-delete)
gabrielbav/dsh-workspace
Delete sessions for good: DSH can only archive them, and deleting a workspace leaves its sessions behind. Adds a trash button and menu items to delete a session (with its subagent sessions) or a workspace with all its sessions, and never touches one that is still running or open in another process.
dsh-auto-archive-echo
cubersome/dsh-auto-archive-echo
Idle-based automatic session archiving for DeepSeek Harness: archive sessions nobody has touched for N hours, with cooldown between re-archives, dry-run preview, pinned and subagent-session protection, an exclusion list for working directories, and a persisted per-session audit trail.
dsh-session-rehome
bychen47/dsh-session-rehome
Move one conversation into another workspace in place - the session log is relocated and its header cwd rewritten, so the conversation keeps its id, history, title and archive state. The files that conversation changed can travel with it, their recorded paths are rewritten to the new workspace, and the session working directory follows so later work lands there. A conversation that is mid-way through a turn is refused rather than moved. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.