[Harness]: DeepSeek Harness #1

Integration

Integrate DeepSeek Harness (DSH) with kagent through the existing BYO/A2A contract.

Following the maintainers’ recommendation, this contribution moves the implementation from kagent-dev/kagent#3195 into this repository as a community-maintained experiment.

The integration supports persistent conversations and workspaces, HTTP MCP tools, and protected-tool approvals. It adds no native runtime type or CRD fields and requires no changes to DSH source.

Maintainers

@Jacob953

Integration and build approach

The implementation lives under harnesses/deepseek/, with independent dependencies, a Dockerfile, deployment examples and tests.

Compatibility has been tested with DSH 0.2.0-rc.2 and kagent commit 0a57368aca33, which includes the shared DATA restoration contract from #3165.

docker build --tag byo-ext/deepseek:local harnesses/deepseek

The build requires no credentials or additional arguments. Runtime credentials are supplied through kagent configuration. The companion PR will document build results and runtime verification.

Known limitations and dependencies

• Production execution requires Linux.
• Native ACP permissions require a live DSH process. Durable MCP approval restoration does not reconstruct the native execution stack.
• Pending tasks cannot be checkpointed. Uncertain remote operations are not automatically retried.
• Shared task-recovery limitations tracked in #3010 remain applicable.
• An optional external approval service requires its own PostgreSQL database and credentials.
• Unsupported configuration, dependency licenses and verification boundaries are documented with the harness.