Introduction

In the DSH ecosystem, plugins can extend the capabilities of DeepSeek Harness, but some scenarios require connecting an existing Harness profile to an external ACP runtime. dsh-openclaw-acp is designed for this scenario: it does not re-implement Harness or embed the WeChat SDK, but rather exposes the Harness profile to OpenClaw via the official Agent Client Protocol (ACP) transport, and then the OpenClaw channel plugins handle message transports like WeChat.

Below is an introduction to its positioning, core capabilities, installation and activation steps, model override methods, security defaults, and known limitations.

What is it

dsh-openclaw-acp is a DeepSeek Harness bundle designed to expose a Harness profile as an OpenClaw-compatible ACP agent.

  • Name: dsh-openclaw-acp
  • Maintainer: BeAChanger
  • License: MIT
  • Installation Form: Installed as a dsh.bundle, mounting the official @deepseek-ai/dsh-acp plugin
  • Integration Method: Exposes the Harness profile to OpenClaw via the official Agent Client Protocol (ACP) transport
  • Boundaries: Does not embed the WeChat SDK, nor does it duplicate Harness

Core Capabilities

The verified capabilities are listed below:

  • Native DeepSeek Harness bundle, exposing the Harness profile to OpenClaw via the official ACP transport.
  • Installed as a dsh.bundle, mounting the official @deepseek-ai/dsh-acp plugin.
  • Does not embed the WeChat SDK, nor does it duplicate Harness.
  • Default route is deepseek-official/deepseek-v4-flash, thinking enabled, max reasoning effort, 1,000,000-token context window, 384,000-token output cap.
  • Can be registered as an agent via OpenClaw ACPX, and supported message transports (like WeChat) are handled via OpenClaw channels.
  • Supports isolation of direct-message sessions across multiple logged-in WeChat accounts, separated by account, channel, and sender.

Prerequisites

The following conditions must be met before installation:

  • pnpm 10 and a Node.js version supported by OpenClaw; stable OpenClaw 2026.7.1-2 requires Node.js 22.22.3+, 24.15.0+, or 25.9.0+.
  • DeepSeek Harness 0.1.0-rc.6.
  • OpenClaw 2026.7.1-2 or newer, using the official @openclaw/acpx plugin.
  • The OpenClaw Gateway process can read DEEPSEEK_API_KEY.
  • Configured available OpenClaw channels, e.g., Tencent’s @tencent-weixin/openclaw-weixin.

Installation and Activation

1. Install DSH and the bundle

First install DeepSeek Harness, then add the dsh-openclaw-acp bundle, and finally view the openclaw profile configuration.

npm install -g @deepseek-ai/dsh@0.1.0-rc.6
dsh plugin --profile openclaw add https://github.com/BeAChanger/dsh-openclaw-acp/releases/download/v0.1.3/dsh-openclaw-acp-0.1.3.tgz
dsh --profile openclaw --dump-config

The installation commands use pre-built release artifacts; the installation process does not execute a repository build. The release page publishes a SHA-256 checksum asset.

2. Register OpenClaw ACPX

Enable the OpenClaw ACPX runtime.

openclaw plugins install @openclaw/acpx@2026.7.1
openclaw config set plugins.entries.acpx.enabled true

3. Connect WeChat Channel

Taking Tencent’s openclaw-weixin plugin as an example, install, enable, and complete channel login.

openclaw plugins install @tencent-weixin/openclaw-weixin@2.4.6
openclaw config set plugins.entries.openclaw-weixin.enabled true
openclaw channels login --channel openclaw-weixin

4. Restart Gateway and Verify ACP Boundaries

After completing the channel connection, verify ACP boundaries first, then test the message channel.

/acp doctor
/acp spawn deepseek-harness --cwd /absolute/path/to/workspace

/acp spawn requires explicitly specifying the workspace path; here an absolute path placeholder is used.

5. Multi-WeChat Account Session Isolation

If multiple WeChat accounts are logged in simultaneously, direct-message sessions can be isolated by account, channel, and sender.

openclaw config set session.dmScope per-account-channel-peer

Override Default Model

The default route is deepseek-official/deepseek-v4-flash, thinking enabled, max reasoning effort, 1,000,000-token context window, 384,000-token output cap.

If you need to override the provider or model in the Gateway environment, you can set:

export DSH_OPENCLAW_PROVIDER=deepseek-official
export DSH_OPENCLAW_MODEL=deepseek-v4-pro

Security Defaults

It is recommended to maintain minimum privileges during deployment and explicitly check boundaries:

  • OpenClaw’s sandbox does not wrap the external ACP process; Harness executes its own boundary control via DSH_PERMISSION_MODE.
  • Keep Harness’s default workspace-write mode unless the deployment explicitly requires higher privileges.
  • The plugin runs with the current dsh process permissions; check the source code and license (MIT) before installing, and restrict allowed workspace roots.
  • Do not enable OpenClaw’s ACPX MCP tool bridges for this target. Harness ACP 0.1.0-rc.6 rejects non-empty mcpServers.
  • Run the Gateway and Harness under a dedicated OS account and restrict allowed workspace roots.
  • danger-full-access should only be used as a break-glass mode, not as a production default.
  • OpenClaw plugin tools are not injected into Harness because the current Harness ACP transport rejects non-empty mcpServers.

Known Limitations

The current version has the following limitations:

  • Harness ACP currently only supports new sessions; it does not advertise load, resume, fork, or session listing.
  • It returns committed assistant text, not including live reasoning or tool events.
  • Channel-level persistent binding relies on the OpenClaw channel adapter; when the channel does not support binding, a one-shot parent relay is used.

Verification Commands

You can execute the following commands locally for basic verification:

npm install
npm test
npm run test:acp
npm run pack:check

Conclusion

The value of dsh-openclaw-acp lies in maintaining separation of concerns: DeepSeek Harness is responsible for profile, models, tools, and boundaries; OpenClaw ACPX is responsible for the ACP runtime and routing; OpenClaw channels are responsible for message transports like WeChat. The plugin itself does not embed the WeChat SDK, nor does it duplicate Harness.

GitHub Repository: https://github.com/BeAChanger/dsh-openclaw-acp.

Directory page clues: The plugin is named dsh-openclaw-acp, the repository path is BeAChanger/dsh-openclaw-acp; this article does not cite unverified directory URLs.