mirror of
https://github.com/deepseek-ai/awesome-deepseek-agent.git
synced 2026-11-05 01:07:37 +00:00
[PR #379] [codex] add dsh-openclaw-acp integration guide #384
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/awesome-deepseek-agent#384
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 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)
a8cd4d9docs: add dsh OpenClaw ACP guide9175e18docs: pin verified OpenClaw runtimedfa8303docs: install verified prebuilt bundle92ac783docs: add ACPX bridge verification643988edocs: 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-acptransport and lets OpenClaw ACPX invoke Harness from configured channels, including WeChat.This is intentionally an ecosystem plugin, not a Harness core patch:
Scope
docs/dsh_openclaw_acp.mddocs/dsh_openclaw_acp.zh-CN.mdDeepSeek V4 checklist
deepseek-v4-flashanddeepseek-v4-promaxreasoning effort configured and documentedVerification
The linked bundle release is pinned to
v0.1.3and was verified against@deepseek-ai/dsh@0.1.0-rc.6:pnpm test? 2/2 tests passedpnpm run test:acp? packed-artifact install; direct real-dshACP initialize/session/new with JSON-RPC-only stdout; then a second custom-agent initialize/session/new through the publishedacpx@0.11.2runtime used by OpenClaw ACPXv0.1.2; itspnpm audit --prod --audit-level high --registry https://registry.npmjs.orgrun reported no known vulnerabilities51ab3d78a7505448b5827b84a79081ae9fd11a5553949eafa3a317b5ee4763fdwere verified; composed config contains the bundle row, 1M context, max reasoning, and 384k output cap2026.7.1-2with@openclaw/acpx@2026.7.1?openclaw config validateacceptedacp.defaultAgent,acp.allowedAgents, and structuredplugins.entries.acpx.config.agents.<id>.command/args; the CLI then read the values back unchanged@tencent-weixin/openclaw-weixin@2.4.6and@openclaw/acpx@2026.7.1were installed together in an isolated OpenClaw state; both reportedloaded,enabled, all required dependencies installed, and the combined channel/custom-agent/per-account-session config passed validationThe 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
dsh-openclaw-acp, and its OpenClaw/WeChat ACP boundary.docs/openclaw.mdordocs/openclaw.zh-CN.md.Current limitations called out in the guide
0.1.0-rc.6rejects non-emptymcpServers, so OpenClaw ACPX MCP bridges must remain disabled for this target.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.