DSH Web
zhu1090093659
An aggregation bundle that brings fifteen Web GUI extensions into one DSH install, mounted through the official web profile.
integration
MCP bridges, remote access, notifications and external systems.
This directory lists 18 DeepSeek Harness plugins for Integrations & Connections. Their verification levels run L1 0, L2 7, L3 11, L4 0, L5 0: no listing here has been installed or run in a sandbox, so none claims L4 or L5. 0 have passed an automated security scan, and the other 18 are marked unverified rather than safe. Declared compatibility targets are unstated 7, >=0.1.0-rc.6 3, 0.1.5-rc.2 2, ^0.1.6-alpha.2 || ^0.1.6-alpha.1 || ^0.1.5-rc.2 || ^0.1.5-rc.1 || ^0.1.5-alpha.1 || ^0.1.3-alpha.2 || ^0.1.3-alpha.1 || ^0.1.2-rc.1 1, >=0.1.2-alpha.2 1, 0.1.0-rc.6 1, 0.1.1-rc.2 1, 0.1.2-alpha.4 || 0.1.2-alpha.5 || 0.1.2-rc.1 || 0.1.3-alpha.1 || 0.1.5-alpha.1 1, 0.1.6-alpha.1 1. Together these 18 listings carry 19,787 GitHub stars, led by DSH Web at 7,730. Licences are mainly MIT 12, Apache-2.0 3, AGPL-3.0 1, and the code is written mostly in TypeScript, JavaScript, Python. Every entry records its source repository, licence, declared harness target and a copy-ready install command; the most recently checked is API Relay Audit (2026-09-18). A verification level measures how far the install path was exercised — it is not a safety guarantee, so read the source before you install.
Integration plugins connect the harness to everything outside it: MCP servers, chat and notification channels, remote access from a phone, browsers, issue trackers, credentials and secret stores, logging pipelines.
Every integration is a trust boundary, so start with read-only connections and widen scope deliberately. Plugins that keep credentials out of the model context are worth preferring over ones that paste secrets into a prompt.
Map the direction of data flow before you install. Inbound (the outside world can message the agent) needs identity and allowlists. Outbound (the agent can call an API) needs least-privilege tokens and a place those tokens cannot be echoed. Bridges that do both — IM bots, remote access — need both stories, not one.
Prefer plugins that document transports (WebSocket, long poll, Socket Mode), name the scopes they request, and keep secrets in profile config. MCP bridges are powerful precisely because they expose many tools; audit the server list as carefully as you audit a plugin.
Mature integrations ship per-channel policy, explicit install scopes, and a clear “do not use this to expose the agent to other people” boundary when that is the real risk. Thin ones are a single webhook URL field and a prayer. Credential managers should show what the model can read, not only what the UI displays.
Leaving a group chat bridge on default-open access. Storing API keys where the tool result can reprint them. Assuming “local first” means “no network” without reading the transport section.
Integration bridges enlarge the trust boundary: every external system is a credential and a data egress. Connect the one system you actually need, document the permission scope, and only then talk about kitchen-sink bundles.
zhu1090093659
An aggregation bundle that brings fifteen Web GUI extensions into one DSH install, mounted through the official web profile.
MeteorNOX
A whale-girl widget for the DSH Web corner that reads DeepSeek balance from the official API and books spend from deltas, stored locally.
superdesigndev
A credential-injecting proxy and shared tool registry: one token reaches 3,000+ catalogued endpoints, and keys stay on the server.
xmanrui
Bridges ten IM platforms to DSH sessions over persistent outbound connections, with per-channel access policies.
shaobeichen
Scan a QR code to use your dsh web session on a phone over your LAN; outside access is opt-in and runs over a Cloudflare Tunnel.
toby-bridges
A DSH plugin that runs a local 14-step audit against an AI API relay, reusing the current provider's endpoint and credential.
vshulcz
Local cross-agent session memory — it indexes the coding-agent histories already on disk and recalls them into DSH, with no LLM.
Lum1104
A Chrome/Firefox sidebar extension that gives DSH a text-only channel into your own browser tabs — no vision model required.
sandbaseai
Local-first self-hosted agent runtime and MCP bridge with sandboxed sessions and audit replay.
zhoushoujianwork
Hands for your AI harness on EasyEDA Pro — typed schematic/PCB actions via Go CLI, Agent Skill, and stdio MCP, with a circuit-block library.
anysearch-team
Routes DSH's built-in web_search and web_fetch to the commercial AnySearch API, plus three vertical, batch and discovery tools.
ZSeven-W
A live iOS Simulator — and a USB-connected iPhone — inside the conversation: 22 agent tools, a tappable MJPEG panel, accessibility and OCR taps, and SwiftUI preview hot reload.
Mars-Sea
Unofficial provider plugin for the paid Command Code relay — live model catalog, plan-aware picker, OAuth sign-in, account rotation.
saya-ch
Use DSH from your phone — Android app or browser over paired LAN HTTPS, with optional remote tunnels and in-chat UI customization.
zh667
Token-usage accounting attributed to the relay site, project and model that actually served each request, with zero configuration.
omdsh-dev
Conversational data analysis for DSH: ask in plain language, the agent writes and runs the SQL, then charts it — with a browsable catalog, read-only guards and offline HTML reports.
THEWOLFWALKER
One notify() API over 27 channels, plus approvals, questions and session control answered from your phone — heartbeats and stall alerts included, zero runtime dependencies.
caoyiwei850
Drive SSH operations from the main conversation with dangerous-command protection and a side terminal.
AllDSH uses Google Analytics to see which pages are read, which plugins people look for and whether an install command or a badge snippet is copied. It stays off until you allow it, and advertising storage is never used. Your choice is kept in your browser only.