AI Agent Hub
Back to plugins
⚙️

dsh-a2a

Workflow Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install huangjuhua-aigc/dsh-a2a

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install huangjuhua-aigc/dsh-a2a inside DeepSeek Harness to install the plugin; source code is available at https://github.com/huangjuhua-aigc/dsh-a2a

About this plugin

You have agents running inside DeepSeek Harness, but there is no standard inbound endpoint for external systems to discover and invoke them. dsh-a2a fills that gap: it starts an A2A (Agent2Agent) v1.0 JSON-RPC server on your Harness instance, publishes the agent card at a well-known URI, and lets any compliant peer discover the agent and submit or track tasks through standard methods such as SendMessage, SendStreamingMessage, GetTask, ListTasks, CancelTask, and SubscribeToTask. It is strictly inbound — it does not dial out to other agents, does not maintain a peer directory, and acts purely as a protocol transport adapter over ctx.agents.

On the capability side, dsh-a2a supports multi-peer identity authentication via credential references (never inline tokens), a trust gate, sliding-window rate limiting, per-peer isolated context sessions and working directories, and injection of file and data parts into model context. Streaming responses flow over SSE, blocking calls carry a timeout, and idle contexts are evicted automatically. Credentials resolve through a four-layer lookup chain so rotating a token takes effect on the very next request without a restart. The protocol surface is A2A v1.0 only; v0.3 field names and structures are not aliased or emulated.

If you already run agents on DeepSeek Harness and need an orchestration platform, another agent framework, or a downstream service to invoke them through a standard protocol — with multi-tenant isolation, authentication, and traffic control — this plugin gives you a ready-made inbound gateway. It does not change your agent logic; it wraps the outside with a standard protocol shell.

Use Cases

  • Let an orchestration platform or external agent framework discover and invoke a Harness agent via the standard A2A v1.0 JSON-RPC protocol
  • Share one agent instance across multiple downstream services with per-peer context and workspace isolation and independent rate limiting
  • Expose a standard Agent Card and JSON-RPC endpoint for an internal agent, replacing a custom HTTP wrapper

Best For

  • Developers running agents on DeepSeek Harness who need a standard protocol endpoint for external callers
  • Architects building multi-tenant agent platforms that require identity authentication and session isolation
  • Agent teams assembling an A2A ecosystem chain that needs an inbound gateway layer