MIT-licensed DSH plugin implementing A2A v1.0 in both directions: remote skills as `a2a__<name>__<skill>` tools, an inbound AgentCard plus JSON-RPC/SSE endpoints executed by DSH agent sessions, bearer-token auth, and a UI-only dashboard for all config.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-21
License
MIT
01What can it help you accomplish?
Call a remote A2A agent from a DSH conversation as if its skills were local tools
The remote AgentCard is discovered, each skill becomes a `a2a__<name>__<skill>` model tool, and calls run over A2A JSON-RPC — with one A2A `contextId` reused per local session so the remote side keeps cross-turn memory
DSH users who want to plug a remote agent (research, coding, a partner service) into their own session
Expose this DSH as an A2A agent that other agents can discover and call
A `/.well-known/agent-card.json` plus JSON-RPC endpoints (`SendMessage`, `GetTask`, `ListTasks`, `CancelTask`) and SSE streaming on the DSH webserver, executed by this DSH’s own agent sessions by default
Teams wiring several agents together, or anyone publishing a DSH-backed agent to an A2A network
02How to install into DeepSeek Harness
Prerequisites
- A DSH profile to install into — the README uses `web`, and `dsh --profile web` to start it
- DSH 0.1.7-rc.2, 0.2.0-rc.1–2, 0.2.1-alpha.1–5 or 0.2.1-rc.1–5 (13 versions, each verified by CI and the release pipeline)
- For server mode: a reachable endpoint, and a TLS reverse proxy if the A2A endpoint faces a production network (the spec requires HTTPS for `AgentInterface.url`)
Installation steps
- 01
Run `dsh plugin --profile web add @ryubyte/dsh-a2a` — `dsh plugin` writes the package into the profile and adds it to the plugin layer automatically (the package declares `dsh.bundle.patch`), so no config file needs editing.
$ dsh plugin --profile web add @ryubyte/dsh-a2a
- 02
Start DSH with `dsh --profile web`; the plugin mounts on restart.
$ dsh --profile web
- 03
Outbound: open Settings → A2A connections → connected agents → add agent, paste the AgentCard URL (optionally a Bearer token), preview the remote name/description/skills, then connect.
- 04
Inbound: open the service tab; a fresh install shows a pre-filled form — adjust the fields and press create-and-go-live to write `a2a.json` and start serving.
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
Native DSH plugin (npm package `@ryubyte/dsh-a2a`, Cordis-based) that makes one DSH instance a full A2A v1.0 node: an outbound client that maps remote skills to `a2a__<name>__<skill>` tools, and an inbound server exposing an AgentCard plus JSON-RPC/SSE endpoints
A2A v1.0 protocol surface
An AgentCard URL (outbound) or inbound JSON-RPC requests→Discovery via `/.well-known/agent-card.json`, `SendMessage` / `GetTask` / `ListTasks` / `CancelTask` / `GetExtendedAgentCard`, and streaming through `SendStreamingMessage` (SSE) and `SubscribeToTask`
task lifecycle moves SUBMITTED → WORKING → COMPLETED / FAILED / CANCELED / REJECTED / INPUT_REQUIRED / AUTH_REQUIREDConnection dashboard (both roles)
Nothing beyond the UI — every setting is editable there→Two tabs (connected agents / exposed service) with per-agent reconnect, settings, disable, delete; service identity editing with full skill add/remove/edit; go-live toggle and inbound connection list
the panel refreshes every 3 seconds; `/a2a/api` serves a JSON snapshot and control calls behind loopback/same-origin protection and never returns token valuesBearer-token auth in both directions
A per-agent outbound token, or a shared inbound token on the service tab→Outbound calls send `Authorization: Bearer …`; with an inbound token set, the AgentCard declares the `bearerAuth` scheme and requests with a missing or wrong token get 401
tokens are stored in plaintext in `a2a.json` — file permissions are yours to manageDSH-agent executor with context mapping
Inbound tasks carrying an A2A `contextId`→One DSH session per `contextId`, resumed across restarts, serialised within a context and parallel across contexts; `CancelTask` aborts the running executor signal
inbound sessions use `<profile>/.a2a-sessions` as cwd and appear in the session list as `A2A: <summary>`
04Who is it for? When not to use it?
Good for
- DSH users who want to plug a remote agent (research, coding, a partner service) into their own session
- Teams wiring several agents together, or anyone publishing a DSH-backed agent to an A2A network
Not for
- Never expose server mode to an untrusted network: inbound endpoints are unauthenticated unless you configure `authToken`, and the A2A spec expects HTTPS for the published interface URL while the DSH webServer binds loopback only.
- Every bearer token — outbound per-agent and the inbound `authToken` — sits in plaintext inside `a2a.json`, so protecting that file is the operator’s job.
05Compatibility, maintenance and safety notes
- Never expose server mode to an untrusted network: inbound endpoints are unauthenticated unless you configure `authToken`, and the A2A spec expects HTTPS for the published interface URL while the DSH webServer binds loopback only.
- Every bearer token — outbound per-agent and the inbound `authToken` — sits in plaintext inside `a2a.json`, so protecting that file is the operator’s job.
MIT · actively maintained (latest release v0.3.2, 2026-11-03); 13 DSH versions covered and verified per release
06Frequently asked questions
Do I have to hand-edit `a2a.json`?
No. The README states every setting can be managed in the UI under Settings → A2A connections: add agents by AgentCard URL, edit timeout / skill mapping / token per agent, and on the service tab edit the identity, skills, go-live state and inbound token. Hand-written `a2a.json` is still supported for scripted deployments.
What executes tasks that arrive from other agents?
By default this DSH’s own agent sessions: one session per A2A `contextId`, created with `<profile>/.a2a-sessions` as its working directory, resumed after a restart, serialised within a context and parallel across contexts. A composition-injected `execute` takes priority, and a minimal profile without an agent loop refuses with "no executor configured".
Is server mode safe to expose to the internet?
Not by itself. The README warns that inbound endpoints have no authentication unless you set `authToken`, and that A2A requires HTTPS for the published interface URL while the DSH webServer binds loopback by default — put it behind a TLS reverse proxy first.
Where are the bearer tokens stored?
In plaintext in `a2a.json` (both per-agent outbound tokens and the inbound `authToken`). The `/a2a/api` snapshot deliberately reports only whether a token is configured, never its value, but file permissions are your responsibility.
Which DSH versions are supported?
13 of them: 0.1.7-rc.2, 0.2.0-rc.1–2, 0.2.1-alpha.1–5 and 0.2.1-rc.1–5. The README says CI and the release pipeline verify each version.
07Related DSH workflows
dsh-agent-teams
by nanmicoder
AgentTeams 多智能体团队协作插件:自然语言驱动建团队、拉成员、拆任务声明依赖、成员间消息直达,Web 右上角活动面板
dsh-blender-plugin
by sixtysevenlf
Adds tools for Blender scene editing, viewport capture, render profiling, headless work, and verification.
dsh-free-search
by dddmuc
DSH 免费搜索插件,执行联网检索。
dsh-bili-scroll
by c1overzz
Schedules Bilibili discovery, reads subtitles, writes daily reports, and optionally posts a comment tagging you.
08Data and sources
一个 **DeepSeek Harness (DSH)** 插件,实现 **Agent2Agent (A2A) 协议 v1.0**(Linux 基金会,`a2aproject/A2A`,Apache-2.0)。
让一个 DSH 实例成为完整的 A2A 双端节点:
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-21. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
