You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(readme): split into English (default) and Chinese versions
README.md is now pure English; README.zh-CN.md is pure Chinese.
Top of each file has a language switcher link to the other version.
Improved typography: dividers around switcher, table layout for
download info, cleaner section spacing.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
<imgsrc="resources/demo.gif"alt="OpenClaw Desktop Demo running on Windows"width="720" />
37
34
</p>
38
35
39
-
<palign="center">
40
-
<imgsrc="resources/demo.gif"alt="OpenClaw Desktop Demo running an AI agent on Windows"width="720" />
41
-
</p>
36
+
---
37
+
38
+
**Language:** English · [简体中文](./README.zh-CN.md)
39
+
40
+
---
42
41
43
42
## Overview
44
43
45
-
`OpenClaw Desktop` packages the OpenClaw runtime into a normal Windows install experience. You download one `.exe`, finish a setup wizard, configure your provider and channel, and run OpenClaw from a native desktop shell instead of wiring everything by hand.
44
+
`OpenClaw Desktop` packages the OpenClaw runtime into a normal Windows install experience. Download one `.exe`, finish a setup wizard, configure your provider and channel, and run OpenClaw from a native desktop shell — no manual wiring required.
46
45
47
-
It is designed for users who want:
46
+
Built for users who want:
48
47
49
48
- A Windows-first installer and GUI for OpenClaw
50
-
- Bundled Node.js and bundled OpenClaw runtime
49
+
- Bundled Node.js and OpenClaw runtime (no global install needed)
51
50
- Guided provider, channel, and gateway setup
52
-
- Built-in update flow from GitHub Releases
51
+
- Built-in updates via GitHub Releases
53
52
- Desktop-native Feishu pairing and allowlist management
54
53
55
-
## What's New In v0.1.1
54
+
## What's New in v0.1.1
56
55
57
-
-**Feishu Settings:** Feishu credentials, DM pairing, and allowlist management now live inside the desktop app. Open **Feishu Settings** from **Settings**, the **Dashboard**, or the **tray menu**.
58
-
-**Desktop approval flow:** Pending Feishu requests can be approved directly in the app. If you only have a pairing code, Desktop falls back to the bundled OpenClaw runtime for approval.
59
-
-**Bundled runtime update:** Bundled OpenClaw is updated to `2026.3.13`.
60
-
-**Kuae proxy fix:** When the gateway inherits `HTTP(S)_PROXY`, Desktop now merges `NO_PROXY`/ `no_proxy`for `coding-plan-endpoint.kuaecloud.net` and `.kuaecloud.net` so Kuae traffic can bypass problematic HTTPS proxies.
56
+
-**Feishu Settings**— Feishu credentials, DM pairing, and allowlist are now managed inside the app. Open it from **Settings**, the **Dashboard**, or the **tray menu**.
57
+
-**Desktop approval flow**— Pending Feishu requests are approved directly in the app. When only a pairing code is available, Desktop falls back to the bundled OpenClaw runtime.
58
+
-**Runtime update**— Bundled OpenClaw updated to `2026.3.13`.
59
+
-**Kuae proxy fix**— When the gateway inherits `HTTP(S)_PROXY`, Desktop now merges `NO_PROXY` for `coding-plan-endpoint.kuaecloud.net` and `.kuaecloud.net` so Kuae traffic bypasses HTTPS proxies that break TLS.
4. Complete the first-run setup for your model provider, channel, and gateway.
86
87
5. Start using OpenClaw from the desktop shell.
87
88
88
-
System requirements:
89
-
90
-
- Windows 10/11 x64
91
-
- About 350 MB free disk space
92
-
- Internet connection for provider API calls and update checks
89
+
**System requirements:** Windows 10/11 x64 · ~350 MB free disk space · Internet connection for API calls and update checks
93
90
94
91
## Features
95
92
96
93
- Native Windows installer with Start Menu and Desktop shortcuts
97
94
- Guided setup wizard for model, channel, gateway, and API key configuration
98
-
- Bundled Node.js runtime so no system-wide Node.js install is required
99
-
- Bundled OpenClaw runtime for a faster first launch
95
+
- Bundled Node.js runtime (no system-wide install required)
96
+
- Bundled OpenClaw runtime for faster first launch
100
97
- Built-in updater powered by GitHub Releases and `electron-updater`
101
98
- Update center with health checks, bundle verification, rollback guidance, and diagnostics
102
-
-Tray integration and auto-start support
99
+
-System tray integration and auto-start support
103
100
- Multi-language UI: English, Simplified Chinese, Traditional Chinese, Japanese, Korean, Spanish, French
104
-
-Support for 50+ AI providers and multiple channels including Telegram, Discord, Slack, WhatsApp, and Feishu
101
+
- 50+ AI providers and multiple channels: Telegram, Discord, Slack, WhatsApp, Feishu, and more
105
102
106
103
## Feishu Settings & Pairing
107
104
108
-
Desktop keeps the Feishu DM flow practical for first-time setup:
105
+
Desktop streamlines the Feishu DM pairing flow:
109
106
110
-
1. Configure Feishu credentials in the setup flow or in **Settings**.
111
-
2. Keep DM mode on `pairing` if you want approval before users can chat.
107
+
1. Configure Feishu credentials in the setup wizard or in **Settings**.
108
+
2. Keep DM mode on `pairing` if you want to approve users before they can chat.
112
109
3. Ask the requester to DM the bot in Feishu.
113
110
4. Open **Feishu Settings** to review pending requests, approve a sender, edit the allowlist, or add an `open_id` manually.
114
111
115
-
If the pending list is empty but you already received a pairing code in Feishu, use the code-based approval path on the same screen. Desktop will use the bundled runtime as a fallback for that case.
112
+
If the pending list is empty but you already received a pairing code in Feishu, use the code-based approval path on the same screen — Desktop will use the bundled runtime as a fallback.
116
113
117
114
## Development
118
115
119
-
Prerequisites:
120
-
121
-
- Node.js `>= 22.16.0`
122
-
-`pnpm`
123
-
- Windows 10/11 for packaging and end-to-end validation
116
+
**Prerequisites:** Node.js `>= 22.16.0` · `pnpm` · Windows 10/11
@@ -166,16 +157,16 @@ No. The installer ships with a portable Node.js runtime.
166
157
<details>
167
158
<summary><strong>Where do I download the installer?</strong></summary>
168
159
169
-
Use the latest release page: <ahref="https://github.com/agentkernel/openclaw-desktop/releases/latest">github.com/agentkernel/openclaw-desktop/releases/latest</a>. The main asset is <code>OpenClaw-Setup-<version>.exe</code>.
160
+
Use the latest release page: [github.com/agentkernel/openclaw-desktop/releases/latest](https://github.com/agentkernel/openclaw-desktop/releases/latest). The main asset is `OpenClaw-Setup-<version>.exe`.
170
161
</details>
171
162
172
163
<details>
173
164
<summary><strong>Where is user data stored?</strong></summary>
Uninstalling the app does not remove user configuration by default.
181
172
</details>
@@ -189,9 +180,9 @@ Desktop checks GitHub Releases and can download updates through the built-in upd
189
180
<details>
190
181
<summary><strong>What does the Kuae HTTPS proxy fix do?</strong></summary>
191
182
192
-
When the bundled OpenClaw gateway inherits <code>HTTP(S)_PROXY</code>, some local proxies break TLS to Kuae's Coding Plan endpoint. Desktop therefore merges <code>NO_PROXY</code> / <code>no_proxy</code> for <code>coding-plan-endpoint.kuaecloud.net</code> and <code>.kuaecloud.net</code> so Kuae traffic can go direct while other traffic still uses your proxy.
183
+
When the bundled OpenClaw gateway inherits `HTTP(S)_PROXY`, some local proxies break TLS to Kuae's Coding Plan endpoint. Desktop merges `NO_PROXY` / `no_proxy` for `coding-plan-endpoint.kuaecloud.net` and `.kuaecloud.net` so Kuae traffic goes direct while other traffic still uses your proxy.
193
184
194
-
To disable this behavior for debugging, set <code>OPENCLAW_SKIP_KUAE_NO_PROXY=1</code> before starting the app.
185
+
To disable this behavior for debugging, set `OPENCLAW_SKIP_KUAE_NO_PROXY=1` before starting the app.
0 commit comments