[PR #379] [codex] add dsh-openclaw-acp integration guide #384

Open
opened 2026-10-26 09:48:40 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/awesome-deepseek-agent/pull/379
Author: @BeAChanger
Created: 8/14/2026
Status: 🔄 Open

Base: main ← Head: codex/add-dsh-openclaw-acp


📝 Commits (5)

  • a8cd4d9 docs: add dsh OpenClaw ACP guide
  • 9175e18 docs: pin verified OpenClaw runtime
  • dfa8303 docs: install verified prebuilt bundle
  • 92ac783 docs: add ACPX bridge verification
  • 643988e docs: verify Tencent WeChat channel stack

📊 Changes

4 files changed (+342 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)
📝 README.zh-CN.md (+1 -0)
➕ docs/dsh_openclaw_acp.md (+170 -0)
➕ docs/dsh_openclaw_acp.zh-CN.md (+170 -0)

📄 Description

Summary

Add a bilingual integration guide for dsh-openclaw-acp, an external DeepSeek Harness bundle that mounts the official @deepseek-ai/dsh-acp transport and lets OpenClaw ACPX invoke Harness from configured channels, including WeChat.

This is intentionally an ecosystem plugin, not a Harness core patch:

  • Harness owns the agent, model, tools, sandbox, and session log.
  • OpenClaw ACPX owns process lifecycle and conversation routing.
  • The OpenClaw channel plugin owns WeChat identity and delivery.

Scope

  • add docs/dsh_openclaw_acp.md
  • add docs/dsh_openclaw_acp.zh-CN.md
  • add the tool to both README tables in alphabetical order
  • cover installation, configuration, first run, security boundaries, and current ACP limitations

DeepSeek V4 checklist

  • current model ids only: deepseek-v4-flash and deepseek-v4-pro
  • 1,000,000-token context window configured and documented
  • max reasoning effort configured and documented
  • 384,000-token output cap configured and documented
  • English and Simplified Chinese guides included in one PR
  • README entries are in alphabetical order in both languages
  • one tool/integration only
  • configuration fields verified in the composed Harness profile and stable OpenClaw schema
  • no workaround for a fixed upstream bug
  • pricing not included; pricing verification is not applicable
  • no screenshots required for this CLI/configuration-only guide

Verification

The linked bundle release is pinned to v0.1.3 and was verified against @deepseek-ai/dsh@0.1.0-rc.6:

  • pnpm test ? 2/2 tests passed
  • pnpm run test:acp ? packed-artifact install; direct real-dsh ACP initialize/session/new with JSON-RPC-only stdout; then a second custom-agent initialize/session/new through the published acpx@0.11.2 runtime used by OpenClaw ACPX
  • production dependencies are unchanged from v0.1.2; its pnpm audit --prod --audit-level high --registry https://registry.npmjs.org run reported no known vulnerabilities
  • Prebuilt GitHub release tarball install into a fresh profile ? public URL and SHA-256 51ab3d78a7505448b5827b84a79081ae9fd11a5553949eafa3a317b5ee4763fd were verified; composed config contains the bundle row, 1M context, max reasoning, and 384k output cap
  • OpenClaw 2026.7.1-2 with @openclaw/acpx@2026.7.1 ? openclaw config validate accepted acp.defaultAgent, acp.allowedAgents, and structured plugins.entries.acpx.config.agents.<id>.command/args; the CLI then read the values back unchanged
  • Tencent @tencent-weixin/openclaw-weixin@2.4.6 and @openclaw/acpx@2026.7.1 were installed together in an isolated OpenClaw state; both reported loaded, enabled, all required dependencies installed, and the combined channel/custom-agent/per-account-session config passed validation
  • a live WeChat delivery test still requires operator-owned Gateway and channel credentials and is not claimed here

The OpenClaw test also caught its actual Node safety gate, so the guide now states the supported ranges for that stable release: Node 22.22.3+, 24.15.0+, or 25.9.0+.

Non-overlap with open PRs

  • #378 documents DeepSeek Harness itself (web/headless and general plugin usage). This PR documents a separate installable tool, dsh-openclaw-acp, and its OpenClaw/WeChat ACP boundary.
  • #220 rewrites the existing OpenClaw model-provider guide. This PR does not modify docs/openclaw.md or docs/openclaw.zh-CN.md.

Current limitations called out in the guide

  • Harness ACP 0.1.0-rc.6 rejects non-empty mcpServers, so OpenClaw ACPX MCP bridges must remain disabled for this target.
  • Harness ACP currently exposes new sessions and committed assistant text; it does not advertise resume/fork/session listing or live reasoning/tool events.
  • Persistent conversation binding depends on the OpenClaw channel adapter; one-shot parent relay is the fallback.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/awesome-deepseek-agent/pull/379 **Author:** [@BeAChanger](https://github.com/BeAChanger) **Created:** 8/14/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `codex/add-dsh-openclaw-acp` --- ### 📝 Commits (5) - [`a8cd4d9`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/a8cd4d9b340454471f1d0b7fc50c4539c24033c1) docs: add dsh OpenClaw ACP guide - [`9175e18`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/9175e18345d5917351bfd365dbf9677ea2a5ddc8) docs: pin verified OpenClaw runtime - [`dfa8303`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/dfa8303e5302d16ef449ffa9a97cf1309705b4b4) docs: install verified prebuilt bundle - [`92ac783`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/92ac783ab3589e5f69299e65f7a622167bb69236) docs: add ACPX bridge verification - [`643988e`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/643988e60c77dfa976d2dd27358512e24c8a2e69) docs: verify Tencent WeChat channel stack ### 📊 Changes **4 files changed** (+342 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) 📝 `README.zh-CN.md` (+1 -0) ➕ `docs/dsh_openclaw_acp.md` (+170 -0) ➕ `docs/dsh_openclaw_acp.zh-CN.md` (+170 -0) </details> ### 📄 Description ## Summary Add a bilingual integration guide for [`dsh-openclaw-acp`](https://github.com/BeAChanger/dsh-openclaw-acp), an external DeepSeek Harness bundle that mounts the official `@deepseek-ai/dsh-acp` transport and lets OpenClaw ACPX invoke Harness from configured channels, including WeChat. This is intentionally an ecosystem plugin, not a Harness core patch: - Harness owns the agent, model, tools, sandbox, and session log. - OpenClaw ACPX owns process lifecycle and conversation routing. - The OpenClaw channel plugin owns WeChat identity and delivery. ## Scope - add `docs/dsh_openclaw_acp.md` - add `docs/dsh_openclaw_acp.zh-CN.md` - add the tool to both README tables in alphabetical order - cover installation, configuration, first run, security boundaries, and current ACP limitations ## DeepSeek V4 checklist - [x] current model ids only: `deepseek-v4-flash` and `deepseek-v4-pro` - [x] 1,000,000-token context window configured and documented - [x] `max` reasoning effort configured and documented - [x] 384,000-token output cap configured and documented - [x] English and Simplified Chinese guides included in one PR - [x] README entries are in alphabetical order in both languages - [x] one tool/integration only - [x] configuration fields verified in the composed Harness profile and stable OpenClaw schema - [x] no workaround for a fixed upstream bug - [x] pricing not included; pricing verification is not applicable - [x] no screenshots required for this CLI/configuration-only guide ## Verification The linked bundle release is pinned to `v0.1.3` and was verified against `@deepseek-ai/dsh@0.1.0-rc.6`: - `pnpm test` ? 2/2 tests passed - `pnpm run test:acp` ? packed-artifact install; direct real-`dsh` ACP initialize/session/new with JSON-RPC-only stdout; then a second custom-agent initialize/session/new through the published `acpx@0.11.2` runtime used by OpenClaw ACPX - production dependencies are unchanged from `v0.1.2`; its `pnpm audit --prod --audit-level high --registry https://registry.npmjs.org` run reported no known vulnerabilities - Prebuilt GitHub release tarball install into a fresh profile ? public URL and SHA-256 `51ab3d78a7505448b5827b84a79081ae9fd11a5553949eafa3a317b5ee4763fd` were verified; composed config contains the bundle row, 1M context, max reasoning, and 384k output cap - OpenClaw `2026.7.1-2` with `@openclaw/acpx@2026.7.1` ? `openclaw config validate` accepted `acp.defaultAgent`, `acp.allowedAgents`, and structured `plugins.entries.acpx.config.agents.<id>.command/args`; the CLI then read the values back unchanged - Tencent `@tencent-weixin/openclaw-weixin@2.4.6` and `@openclaw/acpx@2026.7.1` were installed together in an isolated OpenClaw state; both reported `loaded`, `enabled`, all required dependencies installed, and the combined channel/custom-agent/per-account-session config passed validation - a live WeChat delivery test still requires operator-owned Gateway and channel credentials and is not claimed here The OpenClaw test also caught its actual Node safety gate, so the guide now states the supported ranges for that stable release: Node 22.22.3+, 24.15.0+, or 25.9.0+. ## Non-overlap with open PRs - #378 documents DeepSeek Harness itself (web/headless and general plugin usage). This PR documents a separate installable tool, `dsh-openclaw-acp`, and its OpenClaw/WeChat ACP boundary. - #220 rewrites the existing OpenClaw model-provider guide. This PR does not modify `docs/openclaw.md` or `docs/openclaw.zh-CN.md`. ## Current limitations called out in the guide - Harness ACP `0.1.0-rc.6` rejects non-empty `mcpServers`, so OpenClaw ACPX MCP bridges must remain disabled for this target. - Harness ACP currently exposes new sessions and committed assistant text; it does not advertise resume/fork/session listing or live reasoning/tool events. - Persistent conversation binding depends on the OpenClaw channel adapter; one-shot parent relay is the fallback. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/awesome-deepseek-agent#384
No description provided.