Add deepseek-acp

[xintaofei]

Adds deepseek-acp — an unofficial, community-maintained ACP adapter that wraps DeepSeek Harness as a full editor-facing coding agent.

Not affiliated with or endorsed by DeepSeek. DeepSeek Harness ships its own ACP server, but it is automation-only by design (its README: "a transport adapter, not a UI integration") — it does not surface tool calls, diffs, streaming, sessions, or MCP. This adapter fills that gap on the same harness core.

Entry

• Distribution: npx, deepseek-acp@0.5.0 (npm)
• Repository: https://github.com/xintaofei/deepseek-acp
• License: MIT
• Icon: 16×16, single monochrome path using currentColor (the DeepSeek mark from Simple Icons, CC0-1.0)

Authentication

Terminal Auth. initialize advertises {"id": "terminal", "type": "terminal", "args": ["--setup"]}, and deepseek-acp --setup reads the API key interactively (no echo) and stores it in $DSH_HOME/.credentials.yaml (0600), exiting 0 on success.

The method is only advertised to clients that opt in via clientCapabilities.auth.terminal === true or _meta["terminal-auth"] === true; everyone else still gets authMethods: [], so no client sees a method type it didn't ask for. DeepSeek issues API keys rather than OAuth, so Agent Auth isn't applicable.

Verification

Ran the repo's own tooling locally against the published package:

$ SKIP_URL_VALIDATION=1 uv run --with jsonschema .github/workflows/build_registry.py
Added agent: deepseek-acp v0.5.0

$ python3 .github/workflows/verify_agents.py --auth-check --agent deepseek-acp
[1/1] deepseek-acp (npx)
    ✓ Success: Auth OK: terminal(terminal)
  Passed:  1    Failed:  0

🤖 Generated with Claude Code