Common Questions

Release notes for every version.

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.
View all releases on GitHub →