fork intermediate active

OpenClaw CN

OpenClaw upstream is built for global conditions. CN networks are not global. openclaw-cn ships pre-configured for China.

openclaw cn chinese fork community localization mainland-china

What breaks without openclaw chinese fork

Upstream mirror config requiring manual CN setup. QQ/WeChat adapters not bundled by default. English docs slowing CN developer onboarding.

→
CN-ready OpenClaw × pre-bundled QQ/WeChat/DingTalk/Feishu with CN mirror config ÷ 20-minute install ÷ no manual mirror configuration = OpenClaw running in China without friction.

openclaw chinese fork — what it actually does

01
Ships with QQ, WeChat, DingTalk, and Feishu adapters pre-bundled by default.
02
Pre-configures npm to use npmmirror.com — no manual registry setup needed.
03
Handles CN network connectivity for platform API calls with local-aware routing.
04
Provides full Mandarin documentation — no English required to get started.
05
Tracks upstream openclaw/openclaw releases and merges CN changes on top.

Security check — openclaw chinese fork

Privacy score: 7/10 — accesses connected platform APIs only. Lock it: review OAuth scopes before install, confirm Linux, macOS, Windows; Node.js ≥18; optimized for CN network conditions compatibility.

Quick start — openclaw chinese fork in 20–30 minutes

Setup time: 20–30 minutes

!
You need:
  • Node.js ≥18
  • npm with CN mirror configured (npmmirror.com)
  • basic OpenClaw knowledge

Install the package:

git clone https://github.com/jiulingyun/openclaw-cn
cd openclaw-cn
npm config set registry https://registry.npmmirror.com
npm install
npm start
1
Clone the repo
2
Set npm registry to npmmirror.com
3
Run npm install
4
Copy .env.example to .env and configure CN platform credentials (QQ, WeChat, DingTalk)
5
Run npm start
6
Consult the Chinese README for platform-specific configuration details

Troubleshooting openclaw chinese fork

1
1. Using global npm registry — set CN mirror first
2
2. Not reading the Chinese README — it contains CN-specific setup notes
3
3. Diverging heavily from upstream openclaw/openclaw — keep an eye on upstream changes

Compatibility & status

Works with: Linux, macOS, Windows; Node.js ≥18; optimized for CN network conditions intermediate Last updated: Nov 2025 ★ 890 on GitHub MIT

Official docs →

View on GitHub →

FAQ — openclaw chinese fork

Is this fork always in sync with openclaw/openclaw?

It's kept close to upstream with regular rebases, but there may be a lag of days to weeks behind the latest release.

Can I use CN platform plugins from the main ecosystem with this fork?

Yes. The fork is API-compatible with the main OpenClaw plugin ecosystem.

Is documentation only in Chinese?

Primary docs are in Chinese, but the codebase has English inline comments.

Related — more like openclaw chinese fork

OpenClaw Setup CN
Step-by-step OpenClaw setup guide optimized for mainland China network conditions.
OpenClaw Docker CN IM
From npm registry timeouts to fast Docker-based OpenClaw installs inside China.
OpenClaw CN Issues
Chinese-language OpenClaw community issue tracker — report bugs and ask questions in Mandarin.
Awesome OpenClaw Usecases (ZH)
A curated collection of OpenClaw use cases with Chinese commentary — the community's favourite starting-point for inspiration.

More by jiulingyun

OpenClaw CN Issues
Docs

CN developers using upstream OpenClaw spend the first hour on configuration that openclaw-cn ships pre-solved.

Every Mandarin-speaking developer hitting English docs first is an unnecessary friction point.

Get it on GitHub →