OpenClaw Desktop

龙虾智能体官方中文桌面版一键安装部署EXE程序

Official-style Windows installer & desktop app for OpenClaw.
One-click install, bundled runtime, guided setup — run OpenClaw AI agents on Windows without touching a terminal.

⭐  If this project helps you, please give it a star — it takes 2 seconds and means a lot!  ⭐

Language: English · 简体中文

What is this?

OpenClaw Desktop packages the OpenClaw runtime into a standard Windows install experience. Download one .exe, finish a setup wizard, and run OpenClaw from a native desktop shell — no manual wiring, no terminal required.

If you've been searching for how to install OpenClaw on Windows, how to run OpenClaw locally, or an OpenClaw Windows installer with a GUI, this is it.

Quick Start

1. Download the latest installer from Releases
2. Run the Windows setup (filename follows package.json, e.g. OpenClaw-Setup-0.7.0+openclaw.2026.4.2.exe)
3. Finish the setup wizard (provider → channel → gateway)
4. Launch from Start Menu or Desktop shortcut

System: Windows 10/11 x64 · ~350 MB free space · Internet for API calls

OpenClaw Desktop v0.7.0

• Shell version: 0.7.0+openclaw.2026.4.2 (semver + bundled OpenClaw pin in build metadata).
• Git release tag: v0.7.0+openclaw.2026.4.2 — same as package.json version with a v prefix (OpenClaw pin visible in the tag).
• Bundled OpenClaw (npm): 2026.4.2 — same runtime as npm install openclaw@2026.4.2 (current npm latest); pinned in package.json as openclawBundleVersion.
• Desktop highlights (recent train): v0.7.0 ships shell improvements and bundle finalization while keeping OpenClaw 2026.4.2 (see CHANGELOG 0.7.0). v0.6.6 bumped the bundled runtime to 2026.4.2 (0.6.6). v0.6.4 completed embedded Control UI / HTTP 500 hardening (Origin on loopback requests, allowedOrigins: ["*"] when unset on loopback, wizard loopback parity, amazon-bedrock stripped from the installer). v0.6.3 merged iframe auth flags on read/write + write retries (0.6.3). v0.6.2 documents Git tags with bundled OpenClaw (0.6.2). Feishu registerFull guard; MiniMax M2.7-only; Control UI from GitHub tag sources for Electron.

Upstream OpenClaw 2026.4.2 (summary)

Full notes: openclaw/openclaw v2026.4.2 · npm release digest.

Breaking (this bump)

• Plugins / xAI: Move x_search settings from legacy core tools.web.x_search.* to plugin-owned plugins.entries.xai.config.xSearch.*; standardize auth on plugins.entries.xai.config.webSearch.apiKey / XAI_API_KEY. Migrate with openclaw doctor --fix (#59674).
• Plugins / web fetch: Move Firecrawl web_fetch config from tools.web.fetch.firecrawl.* to plugins.entries.firecrawl.config.webFetch.*. Migrate with openclaw doctor --fix (#59465).

Notable for desktop / loopback users (fixes in this train)

• Gateway / exec loopback: Restores legacy-role fallback for empty paired-device token maps so local exec and node clients avoid pairing-required failures after 2026.3.31 (#59092).
• Agents / subagents: Admin-only subagent gateway calls pin to operator.admin so sessions_spawn no longer fails loopback scope-upgrade pairing (#59555).

Still in effect from earlier pins (e.g. 2026.3.31)

• Nodes / exec: No duplicated nodes.run shell wrapper; use exec host=node and nodes invoke where appropriate.
• Plugin SDK: Prefer openclaw/plugin-sdk/*; legacy shims are deprecated.
• Feishu / hooks: hooks.mappings[].channel accepts runtime plugin ids such as feishu (#56226).
• Qwen / Doctor / channels: See v2026.3.31 and v2026.3.28 for earlier breaking and large trains.

Tip (MiniMax 401): MiniMax Anthropic-compatible endpoints expect x-api-key, not Bearer. This shell sets authHeader: false for MiniMax and migrates existing configs on load. Other third-party anthropic-messages hosts may still need authHeader: true where documented.

Older desktop releases are listed in CHANGELOG.md.

Compatibility with upstream OpenClaw (bundled 2026.4.2)

Each release pins the bundled OpenClaw npm version in root package.json (openclawBundleVersion). pnpm run download-openclaw installs that exact version (unless you override with a CLI arg or OPENCLAW_DESKTOP_BUNDLE_VERSION). For local packaging, run download-openclaw before prepare-bundle. The committed resources/bundle-manifest.json is informational only — the bundled version is whatever prepare-bundle writes to bundledOpenClawVersion.

• Runtime: Bundled portable Node.js 22.16.0 (pnpm run download-node), matching upstream openclaw.mjs / engines (Node ≥ 22.16).
• State & config: Same as upstream: %USERPROFILE%\.openclaw, main config openclaw.json. Use OPENCLAW_* env vars (CLAWDBOT_* / MOLTBOT_*, .moltbot, etc. were removed upstream).
• Control UI: The npm package does not ship dist/control-ui/; we fetch GitHub tag v<version> sources (ui/ plus repo-root src/, etc.) and run Vite. CI builds static assets on Linux and merges them into the Windows installer.
• Embedded console auth: For local gateways (not remote), the shell auto-maintains gateway.controlUi.allowInsecureAuth and dangerouslyDisableDeviceAuth in openclaw.json so OpenClaw 2026.3.x Control UI works inside the Electron iframe (see CHANGELOG 0.6.1). If you switch to remote gateway or hand-edit these keys, follow upstream docs.
• Bundled plugin list: Upstream ships built-in channel/provider plugins under dist/extensions/*; the desktop shell scans that path and still falls back to legacy top-level extensions/.
• Breaking changes: Plugin SDK (openclaw/plugin-sdk/*), browser/install behavior, and other breaking items are covered in upstream OpenClaw releases and upstream docs for the version you ship. Installer-only users usually need no action; custom/third-party plugin authors should follow upstream migration guides.

Same section in Chinese: README.zh-CN.md.

Features

Ecosystem

         OpenClaw
             |
    ┌────────┴────────┐
    │                 │
  Desktop           GUI
    │            Plugins
Installer          ...

OpenClaw Desktop is a community-maintained Windows distribution for the OpenClaw ecosystem. Part of the OpenClaw ecosystem — not affiliated with the core project.

Download

→ github.com/agentkernel/openclaw-desktop/releases/latest

Screenshots

Installer	Setup Wizard	Dashboard

Feishu Settings & Pairing

If you use Feishu with pairing mode, Desktop keeps the whole flow inside the app:

1. Configure Feishu credentials in the wizard or in Settings
2. Keep DM mode on pairing to approve users before they can chat
3. Ask the requester to DM the bot in Feishu
4. Open Feishu Settings to review pending requests, approve senders, edit the allowlist, or add an open_id manually

If the pending list is empty but you have a pairing code, use the code-based approval path on the same screen — Desktop will call the bundled OpenClaw runtime as a fallback.

FAQ

Development

git clone https://github.com/agentkernel/openclaw-desktop.git
cd openclaw-desktop
pnpm install
pnpm dev

Prerequisites: Node.js >= 22.16.0 · pnpm · Windows 10/11

Common commands:

pnpm type-check   # Type check
pnpm build       # Build
pnpm run package:prepare-deps   # download-node + download-openclaw (before installer)
pnpm run prepare-bundle
pnpm run package:win   # Output: dist/OpenClaw-Setup-<version>.exe

Bundled OpenClaw: Pinned in package.json (openclawBundleVersion). After prepare-bundle, see bundledOpenClawVersion in resources/bundle-manifest.json (currently 2026.4.2 for desktop v0.7.0). Local checks: pnpm run check-openclaw-versions (omit OPENCLAW_SKIP_NPM_LATEST_CHECK to also compare against npm latest).

Related docs: CHANGELOG.md · CONTRIBUTING.md

License

GPL-3.0

⭐ Star History · Contributors · Community