Real fix for the "MyClaw service did not become ready" timeout. v0.1.29's 300 s cap turned out to be plenty — the gateway was actually finishing its boot at the 263 s mark — but our readiness probe was silently mis-classifying the working gateway as not-ready. The probe sent a WebSocket upgrade request without an auth header; the real gateway responds by closing the TCP connection with no HTTP status line (it logs this as code=1006), so the probe's data event never fired and we kept retrying until the cap. v0.1.30 reads the gateway's own "http server listening" stdout line as the authoritative ready signal — the gateway saying "I'm ready" is more reliable than us guessing from outside. WS handshake stays as a fallback for the e2e fake-gateway. Users who hit the v0.1.28 / v0.1.29 timeout should now bootstrap successfully on the first try.
v0.1.29
Bumped first-launch timeouts so slower Windows machines no longer fail bootstrap. One real-user report (4 cores, 5 GB RAM, Defender real-time scan active) hit the previous 120 s gateway timeout — Node + openclaw CLI + plugin discovery took 67 s before the gateway even printed its first stdout line, and by the 120 s cap the WebSocket handler still wasn't up. Gateway timeout now 5 min (was 2 min), Studio timeout now 5 min (was 3 min). Subsequent launches stay sub-30 s once Defender's file cache is warm; we just give the first one room to breathe. The timeout error message now hints at antivirus + tells the user to relaunch.
v0.1.28
First launch on Windows now lands directly on the Studio chat panel instead of the gateway connect screen. The previous build relied on Studio falling back to read ~/.openclaw/openclaw.json for its gateway URL + token, which had silent failure modes (try/catch swallowing parse errors, loopback normalization rewriting 127.0.0.1 to localhost while Chromium on Windows sometimes prefers ::1). Bootstrap now writes ~/.openclaw/openclaw-studio/settings.json directly with the explicit gateway URL + auth token, so Studio's frontend connects on first render with no fallback chain involved.
v0.1.27
New build line. Ships openclaw + Studio pre-installed inside the installer, so first launch no longer waits on npm install to finish — the splash goes from "Installing…" to a working chat in seconds rather than 10+ minutes.
Faster Windows install. Total file count cut from ~36k to ~21k (-42%) and installer size from 246 MB to 191 MB (-22%) by switching the embedded Studio to Next.js standalone output, dropping the bundled npm + Node headers we no longer need at runtime, and broader pruning of build-time artifacts. Translates directly to less time waiting on Windows Defender to scan every file the installer writes.
Auto-update via electron-updater + delta blockmaps. From 0.1.22 onward, future releases arrive as ~tens-of-MB delta downloads instead of the full installer.
OpenRouter provider key bundled with the installer — chat works out of the box without you pasting a key. Default model pinned to anthropic/claude-haiku-4.5 via OpenRouter.
Studio now waits for the gateway's WebSocket handler to actually be ready before connecting, instead of racing it on TCP-up. Fixes the "ws closed before connect: connect failed" log line that appeared on first launch when the gateway took 10–15 seconds to finish plugin init after binding its port.
Studio gateway auth token is now seeded into ~/.openclaw/openclaw.json on first launch, so Studio finds the token it needs to talk to the local gateway. Previously surfaced as "no access token for openclaw connection".
Version label is now visible: shown next to the brand on the splash and in the OS window title after the swap to Studio.
v1.7.4
Hotfix #3 for OAuth login: 1.7.3 fixed the browser-launch problem for OpenAI Codex + Anthropic + most providers via stdout snooping, but Google Gemini OAuth uses a separate code path inside openclaw that does NOT print the auth URL when its own browser launcher silently fails — leaving the spinner stuck at "Requesting secure login code". MyClaw now monkey-patches child_process.spawn inside the openclaw subprocess so any explorer.exe / open / xdg-open / wslview launch announces the URL to stdout, where MyClaw's main process picks it up and opens the system browser via shell.openExternal. Covers Google, OpenAI, Apple and any future provider uniformly.
v1.7.3
Hotfix #2 for OAuth login: after 1.7.2 cleared the TTY guard, the flow still hung at "Getting auth code" because openclaw's own browser launcher (which spawns explorer.exe / open / xdg-open from inside Electron's utilityProcess) was failing silently and no browser window was opening. MyClaw now intercepts the auth URL from openclaw's stdout and opens it directly via Electron's shell.openExternal — works for OpenAI Codex and most providers.
v1.7.2
Hotfix: Google / Apple OAuth login now works again. openclaw 2026.4.x added a hard "interactive TTY required" guard at the top of models auth login that fired before the OAuth flow could run, breaking sign-in for every browser-based provider. MyClaw now spawns openclaw through a small shim that spoofs the TTY check; the actual OAuth flow (openUrl + callback listener) needs no real TTY.
v1.7.1
Uninstaller now offers a scope picker: full clean (default, removes all data), keep configuration, or keep everything. Default silent uninstall now actually wipes %APPDATA%\myclaw-desktop on Windows — earlier builds left it behind, causing reinstalls to skip the first-launch wizard.
First-launch runtime install now shows a determinate progress bar driven by package-extraction count and an honest 1–10 minute time estimate, so users can tell the install is making progress instead of staring at a sliding spinner.
Bundled Node.js runtime is now shipped on Linux and macOS too (was Windows-only), so first-launch openclaw install no longer depends on a system-installed Node.
Bumped openclaw to 2026.4.26, picking up upstream's last four patch releases.
v1.7.0
New Settings status panel: a glance-able view of "what is installed and what is configured" — runtime version, provider count, channel count — plus one-click buttons to repair the runtime or re-sign in to a provider. Advanced diagnostics tucked into a collapsible section so the main view stays clean.
OAuth flows are now delegated to openclaw's own models auth login CLI instead of being re-implemented in MyClaw. ~2000 lines of OAuth protocol code removed from the desktop app, fixing Apple/macOS sign-in failures caused by Dock-launched apps having a minimal PATH.
Channel doctor validation now runs through Electron's utilityProcess instead of shelling out to a global node binary, eliminating ENOENT failures on user machines without a system-wide Node install.
Bundled @google/gemini-cli-core into the runtime install so Google OAuth has a guaranteed local oauth2.js — first-launch sign-in no longer depends on user PATH, network, or pre-existing global installs.
Bootstrap workspace files (.md templates) are now merged only after the gateway is running, eliminating "missing after retries" warnings caused by racing the gateway's own seed step.
Removed the unused "Reset OpenClaw data" menu item and the auto-login hint popup that ran every launch.
Cross-platform install-smoke tests: macOS DMG and Linux AppImage now have dedicated CI workflows verifying that packaged binaries actually launch and complete first-launch openclaw runtime install on a clean machine.
中文界面 "Agents" 统一翻译为 "智能体"。
v1.6.4
Self-heals broken installs from v1.6.2/1.6.3: an install-complete marker is now written only after both install passes succeed; missing/mismatched marker on launch triggers a clean reinstall instead of starting a half-broken runtime that crashed the gateway with module-not-found errors.
v1.6.3
Fixed runtime install on clean Windows boxes without Git Bash on PATH (plugin postinstall scripts using bash-only 2>/dev/null || true syntax now skipped via two-pass install with --ignore-scripts).
Fixed npm pruning openclaw + 446 transitive deps during plugin install pass; runtime now writes a manifest declaring all top-level deps before the second install pass.
v1.6.2
Fixed runtime install crash on Windows machines without a global Node.js installation (preinstall script could not find 'node' on PATH).
Initialization splash now shows a progress bar with a live stage label and scrolling install log, so first-launch progress is visible at a glance.
v1.6.1
Fixed a crash on first launch on Windows where the app would silently exit after installing the runtime, before the gateway could start.
Hardened main-process startup with crash handlers so any future top-level errors surface cleanly instead of leaving the app idle.
v1.6.0
MyClaw is now a dashboard, not a fork — we no longer patch openclaw at build time or write into ~/.openclaw/extensions/. First launch fetches the pinned openclaw via npm install and starts it with a minimal config; everything else is openclaw’s own runtime defaults plus whatever you configure through the UI.
Version range instead of exact pin — if you upgrade openclaw yourself, MyClaw respects it (within a tested-compatible range) instead of clobbering your install.
Plugin install delegated to openclaw plugins install — we don’t copy local files anymore, we just ask the CLI. Matches what upstream expects.
v1.5.0
Stripped bundled openclaw — first launch fetches the pinned version into ~/.myclaw/runtime/ via bundled Node + npm. Installer is smaller and you always get the openclaw version this release was tested with.
Splash-style progress window during first-launch init — shows npm install progress so you know it’s not frozen.
Bundled npm with Node so subsequent updates can npm install without needing a system Node toolchain.
v1.4.4
Reset your OpenClaw data from the app menu — wipes ~/.openclaw (config, memory, skills) with a confirmation dialog on macOS, Linux and Windows. Useful when an agent’s state is corrupt or you just want a clean slate.
Opt-in reset during Windows install/uninstall — a new wizard page lets you wipe ~/.openclaw when upgrading or removing the app. Unchecked by default; your data stays put unless you ask.
Windows installer: fixed three NSIS regressions from the reset feature (FileFunc.nsh include, page function scoping, ${isUpdated} evaluation) so the installer builds and runs cleanly.
v1.4.3
Maintenance release with assorted under-the-hood improvements and updated dependencies. See the GitHub release page for the full asset list (Windows, Linux x64/ARM64 AppImage / .deb / .rpm).
v1.4.2
Sleep prevention (opt-in) — keeps the OS awake while MyClaw is running so long-lived messaging channels don’t drop when the machine would otherwise sleep. Off by default to protect laptop batteries.
Smart reconnect after wake — Gateway is restarted automatically when its WebSocket is still dead after a Windows suspend/resume, instead of waiting out the heartbeat timeout.
Windows power-outage recovery — first-run guide to enable launch-at-startup and auto-login so MyClaw is back up on its own after an unexpected reboot. Revisitable from the tray menu.
v1.4.1
Fixed Windows Gateway hang after 1.4.0 — disabled the Bonjour/mDNS advertiser that was stalling the startup handshake on machines with Apple Bonjour, VPN, or Hyper-V network adapters (symptom: 20-second connect timeout loop).
v1.4.0
Upgraded OpenClaw runtime to 2026.4.12.
Updated channel plugins: WeChat 2.1.8 and Lark / WeCom / DingTalk to their latest stable releases.
v1.2.0
Compatible with OpenClaw 2026.4.5’s new channel SDK layout (Discord, Telegram, Slack, WhatsApp). Falls back to 4.2 paths automatically for older Gateways.
Discord guild config migration — the old per-channel allow flag is rewritten to the new enabled shape on startup so Gateway stops failing config validation.
Bundler reliability on Windows: corrected promotion ordering and surfaced previously-silent dependency copy errors.
v1.1.7
WhatsApp login no longer stalls at the end of pairing — fixed a credential/connection race that caused a ~15-second hang before the flow completed.
Dev-mode startup loads the right OpenClaw build (with all bundled dependencies) instead of the pnpm internal store, which was missing ~379 runtime deps.
QQ Bot and Feishu plugins now bundle into the correct directory names.
Plugin bundling supports decoupled directory name vs plugin id, unblocking plugins whose manifest id differs from their folder.
v1.1.6
First release tracked in this changelog. Earlier beta history is available on GitHub.