DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

A2a Server — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins

dsh-a2a-server

A2a Server

面向 DeepSeek Harness 的入站 A2A(Agent2Agent)协议服务器:发布 Agent Card,并让任何兼容 A2A 的对等方将任务提交给 harness agent

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add dsh-a2a-server@0.2.0
README兼容性版本

兼容性与来源证明

A2a Server 以 dsh-a2a-server 发布,当前版本为 0.2.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
npm
Registry 更新时间
2026/9/20

版本

0.2.0stable
2026/9/4
0.1.0stable
2026/8/22
0.1.1stable
2026/8/17

相关插件

正在加载相关插件…

最新版
0.2.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
276.1 kB
文件数
69
Surface
any
许可证
MIT
发布源
npm
GitHub
★ 1
周下载
142
最近提交
2026/9/4
查看源码 ↗项目主页 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 agents-orchestration 分类下经过校验的插件。

Headless@deepseek-ai/dsh-headlessdsh one-shot bundle:基于 dsh-base 的直接核心 Agent/Session 运行器,不包含 Host、HTTP 或浏览器层Experimental Agent Team Web Profile@deepseek-ai/dsh-experimental-agent-team-web-profile用于 Agent Teams Remote 和 UI 插件的实验性 Web 配置层Subagent Codex@deepseek-ai/dsh-subagent-codex基于官方 app-server 协议的一次性 Codex 子代理提供程序Subagent Claude Code@deepseek-ai/dsh-subagent-claude-code基于官方 Agent SDK 的一次性 Claude Code 子代理提供方

README

dsh-a2a-server

Inbound A2A protocol server for DeepSeek Harness.
Publish an Agent Card, accept tasks from any compliant peer.
Everything is a plugin — this is one.

English · 简体中文

A community plugin, not an official DeepSeek product.

dsh-a2a-server makes a DeepSeek Harness agent reachable over the A2A (Agent2Agent) protocol. It serves an Agent Card at a well-known URI and implements the v1.0 JSON-RPC binding, so any compliant peer that knows the deployment's URL can discover the agent and submit tasks to it.

The plugin is inbound only: it never connects to another agent. There is no client, no peer directory, and no A2A subagent provider. It is a transport adapter over ctx.agents, not a capability seam.

Install

dsh plugin --profile web add dsh-a2a-server

dsh plugin forwards to pnpm inside the profile directory and appends this bundle to dsh.profile.bundles, because the package declares dsh.bundle.

To work from a checkout instead, point it at the directory:

dsh plugin --profile web add ./path/to/dsh-a2a-server
RequirementSupplied by
ctx.agentsdsh-base
ctx.credentialsdsh-base
ctx.webServerdsh-web-app
ctx.sessionProjections (optional)composition; enables GetTask after settlement

The plugin stays PENDING until the three required services exist. ctx.webServer ships in dsh-web-app rather than dsh-base, so a headless profile needs @deepseek-ai/dsh-host-webserver mounted before this bundle serves anything. dsh --profile <name> --dump-config prints the composed rows.

Quick start

The bundled example composition runs a real model and a listening server.

pnpm install
A2A_PEERS="alice:demo123" A2A_PORT=9922 pnpm serve
$env:A2A_PEERS = "alice:demo123"
$env:A2A_PORT = "9922"
pnpm serve

Peer names are arbitrary — alice is this demo's default, not a protocol fixture. Name as many as you like, and either carry the token inline or store it under the derived credential reference:

A2A_PEERS="ops:tok1,research:tok2"   # inline
A2A_PEERS="ops,research"             # tokens from A2A_PEER_OPS / A2A_PEER_RESEARCH

The model credential is resolved through ctx.credentials, so an existing DEEPSEEK_API_KEY in the harness home, either .env layer, or the process environment is picked up unchanged. A missing credential fails the boot.

Fetch the card and submit a task:

curl -s http://127.0.0.1:9922/.well-known/agent-card.json

curl -s http://127.0.0.1:9922/a2a \
  -H "authorization: Bearer demo123" \
  -H 'content-type: application/json' \
  -H 'a2a-version: 1.0'   -d '{"jsonrpc":"2.0","id":1,"method":"SendMessage","params":{
        "message":{"messageId":"m1","role":"ROLE_USER",
                   "parts":[{"text":"hello"}]}}}'
VariableDefaultMeaning
A2A_PEERSalicename[:token] list; a token is required for each
A2A_PORT9900Listening port
A2A_SEND_MODEblockblock or immediate
A2A_WORKSPACE_ROOTtemp dirParent of the per-peer working directories
DEEPSEEK_MODELdeepseek-v4-flashModel id requested from the adapter

A one-shot probe runs 67 checks against a live server and exits non-zero on any mismatch:

pnpm probe                                        # defaults to :9922 / demo123
node example/probe.mjs http://127.0.0.1:9922 demo123

Interface

RouteMethodAuth
/.well-known/agent-card.jsonGETPublic by default
/.well-known/agent.jsonGETPublic by default
{basePath} (default /a2a)POSTBearer required
JSON-RPC methodStatus
SendMessageWaiting negotiated per request
SendStreamingMessageSSE
GetTaskIdempotent; answers after settlement
ListTasksCursor-paginated, filterable, resident contexts only
CancelTaskCancels the running turn
SubscribeToTaskLive stream; -32004 on a terminal task
GetExtendedAgentCardExtra skills for an authenticated peer; -32007 when unconfigured
*TaskPushNotificationConfig-32003

Only A2A v1.0 is served. The v0.3 method names, kind discriminators, lowercase enums, and nested file parts are gone rather than aliased: every reply this server writes is v1.0 JSON, which a v0.3 client could not read, so answering a v0.3 request would fail further from its cause than refusing it. A retired method answers -32601 naming its replacement, and an explicit A2A-Version: 0.3 answers -32009 (VersionNotSupportedError). A request with no A2A-Version header is served as 1.0 — the only version this interface declares on its card.

What that means concretely, against v0.3:

Concernv0.3v1.0 as served here
Task referenceparams.taskIdparams.id
SendMessage resultbare Task{ "task": … }
Task state"working""TASK_STATE_WORKING"
Message role"user""ROLE_USER"
Part{"kind":"text","text":…}{"text":…}; file parts flatten to url/raw/filename/mediaType
Stream frame{"kind":"status-update",…,"final":true}{"statusUpdate":{…}}; the stream's close is the terminal signal
Stream openinga non-final status updatethe Task object itself
Wait controlconfiguration.blockingconfiguration.returnImmediately (inverted; blocking is the default)
Card endpointurl + preferredTransportsupportedInterfaces[], each carrying its own protocolVersion
Card authsecuritySchemes + securityschemes wrapped in httpAuthSecurityScheme; securityRequirements
Extended cardsupportsAuthenticatedExtendedCardcapabilities.extendedAgentCard
A2A error detailnoneerror.data[] carrying a google.rpc.ErrorInfo with reason and domain

Inbound messages may carry text, file, and data parts. File and data parts are rendered into the model's context as bracketed references. Replies are text.

Authentication, rate limiting, and the trust gate answer with HTTP 401, 429, and 403; the body remains a valid JSON-RPC error envelope. A task belonging to another peer answers exactly as an absent one.

Configuration

- id: a2a-server
  name: dsh-a2a-server
  config:
    basePath: /a2a
    publicUrl: https://agents.example.com/a2a   # advertised on the card
    provider: deepseek-official
    model: deepseek-v4-flash

    card:
      name: dsh-harness
      description: Reads code, runs commands, reports findings.
      public: true
      skills:
        - id: general
          name: general
          description: General-purpose task execution.
          tags: [coding, research]
      extendedSkills:                             # authenticated peers only
        - id: internal
          name: internal diagnostics
          description: Reports harness internals.
          tags: [internal]
      provider:
        organization: Example Inc.
        url: https://example.com

    peers:
      alice: { tokenEnv: A2A_PEER_ALICE }
      bob:   { tokenEnv: A2A_PEER_BOB }
    trustedPeers: [alice]
    rateLimitPerMinute: 60
    maxContextTurns: 5

    sendMode: block
    blockTimeoutMs: 60000
    contextIdleTtlMs: 1800000
    maxResidentContexts: 64

    isolation:
      workspaceMode: per-peer
      workspaceRoot: /srv/dsh/a2a
      peerWorkspaces:
        alice: /srv/project

    push:
      enabled: false
KeyDefaultMeaning
basePath/a2aJSON-RPC route
publicUrlderived from HostRoutable URL published on the card
provider · model—Model route for every agent this server creates
card.publictrueServe the card without a credential
card.skills[]Declared skills; falls back to one general entry
card.extendedSkills[]Skills revealed only through GetExtendedAgentCard
peers{}Identity → credential reference name
trustedPeersall authenticatedAllow-list of identities that may run tasks
rateLimitPerMinute60Sliding window per identity
maxContextTurns5Messages accepted per context before rejected
sendModeblockDefault when the client sends no returnImmediately
blockTimeoutMs60000After which a blocking request is declined
contextIdleTtlMs1800000Idle time before a context's agent is released
maxResidentContexts64Ceiling on resident contexts
isolation.workspaceModeper-peerper-peer or shared
isolation.workspaceRoot—Required; parent directory or shared cwd
isolation.peerWorkspaces

Configuration is refused at load when isolation.workspaceRoot is absent, a peer name is not [A-Za-z0-9][A-Za-z0-9_-]*, a tokenEnv is not a POSIX identifier, trustedPeers or peerWorkspaces names an undeclared peer, or basePath does not start with /.

Credentials

Configuration carries credential references, never values:

peers:
  alice: { tokenEnv: A2A_PEER_ALICE }
# ~/.dsh/.credentials.yaml
A2A_PEER_ALICE: <32-byte-hex-from-openssl-rand>

ctx.credentials resolves the reference per request across four layers — the process environment, the managed document, <cwd>/.env, and $DSH_HOME/.env — so rotating a token takes effect on the next request without a restart. Peer identity comes from the presented credential only; nothing in a request body can assert it. There is no shared bearer token: isolation is built on distinct identities.

Isolation

LayerGuaranteeMechanism
Model contextOne peer's conversation cannot enter another's model requestSeparate contextId → separate Session → separate log
Protocol accessA peer cannot read, continue, or cancel another's context or taskOwnership by authenticated identity
ToolingA peer's agent cannot use tools to read another peer's sessionworkspaceMode: per-peer

per-peer (the default) derives each identity's cwd from workspaceRoot. shared places every peer in one directory, which suits peers collaborating on a single repository; under it, files written by one peer are readable by another.

Boundaries

  • Inbound only. No outbound client, peer directory, or A2A subagent provider.
  • JSONRPC binding only. gRPC and HTTP+JSON are not served, and the card says so.
  • Push notifications are not implemented. push.enabled selects which error the push methods return; the card advertises pushNotifications: false.
  • No stateTransitionHistory, protocol extensions, or card signatures.
  • Streaming emits committed assistant messages. Per-chunk streaming is not implemented.
  • No orphan-task watchdog: a task wedged non-terminal stays that way.
  • Cross-session tool denial is not implemented; isolation rests on workspaceMode.
  • A token ceiling settles a task as completed; the real turn ending travels in Task.metadata.dsh.stopReason, which A2A's state enum cannot express.
  • Task state survives settlement but not a process restart: session persistence is not composed, so the projection has no log to cold-fold after a reboot.
  • ctx.webServer provides no TLS. Any non-loopback exposure belongs behind a reverse proxy.
  • A configuration change restarts the plugin and cancels in-flight tasks.

Architecture

src/
├── protocol/          dependency-free library: no Cordis, no HTTP, no harness
│   ├── wire.ts        the A2A v1.0 vocabulary: one shape, no translation
│   ├── parse.ts       inbound parsing and the method table
│   ├── jsonrpc.ts     framing and the A2A error codes
│   ├── card.ts        Agent Card construction
│   └── sse.ts         SSE frame encoding
├── index.ts           the Cordis plugin: wiring, agent ownership, teardown
├── router.ts          HTTP + JSON-RPC dispatch, free of Cordis so it unit-tests
├── contexts.ts        contextId -> Activation registry and residency policy
├── tasks.ts           task slots and the three-stage turn correlation
├── projection.ts      the a2aTask fold over the session log
├── security.ts        authentication, rate limiting, defanging, redaction
├── config.ts          schema plus the cross-field checks that fail at load
└── types.ts           declaration merges into SessionEventMap / MessageSourceMap

A task is an interval, not a turn. One submitted message may span several turns if tools queue more work, so settlement uses three hooks: agent/inbox/claimed binds the message to a turn, turn/end records that turn's ending, and agent.whenIdle() settles once the whole agent is quiet.

Task state lives in the session log. Lifecycle transitions are a2a/task events; a projection unit folds them into the read model. The terminal edge carries the committed output, so the fold serves the answer without reaching back into message history.

Residency is explicit. HTTP has no connection lifetime, so each contextId maps to an Activation evicted when idle, leaving the durable Session behind.

Development

pnpm install
pnpm typecheck
pnpm test       # 167 tests across 10 files
pnpm serve      # a listening server
pnpm probe      # 67 checks against a running server
pnpm build      # emit lib/

The end-to-end suites boot a real Cordis composition with a real agent loop and drive it over HTTP, using a deterministic stub adapter so assertions do not depend on model output.

Relationship to the official project

Built against deepseek-ai/deepseek-harness.

The official project supplies the agent runtime, the plugin system, and the capability seams this plugin consumes. This project supplies:

  • The A2A v1.0 JSON-RPC binding, served inbound
  • Agent Card construction and inbound request parsing
  • Mapping between A2A tasks and harness turns
  • Per-peer authentication, isolation, and workspace policy

The harness is pre-release and does not promise compatibility across renames or repackaging, so peer dependencies are pinned exactly to 0.1.0-rc.6.

Community

Scan to join the WeChat group A2A 产品应用和探索 — discussion of A2A in practice, this plugin included.

WeChat group QR code

If the code has expired, open an issue and we will refresh it.

License

MIT

{}
Per-identity working-directory override
push.enabledfalseReserved; see Boundaries