Why does openclaw update crash the gateway?

The update command runs npm install -g without first stopping the LaunchAgent service. npm tries to update files locked by the running Node.js process, causing version mismatches and crashes.

How to fix OpenClaw Feishu disconnection after update?

The config file gets overwritten during npm update, corrupting Feishu credentials. Backup your config before updating. If already affected, re-enter Feishu channel credentials manually.

Why are all my OpenClaw cron jobs gone after update?

The jobs.json file is deleted or emptied during the update process because the runPackageInstallUpdate function never stops the running service before modifying files, causing data loss.

How to safely update OpenClaw without losing data?

Stop the LaunchAgent service manually before running openclaw update. Backup your jobs.json and channel config files. Consider using pnpm instead of npm for more reliable installs.

Is the openclaw update bug fixed?

As of April 2026, issue #66401 remains open. The reporter identified the problematic function in update-cli-C4j9u3np.js and suggested a fix involving service cessation prior to npm install.

What OpenClaw version introduced the update crash bug?

The bug affects openclaw update across 2026.4.x versions. It is 100% reproducible on any existing install that has the LaunchAgent running when the update command executes.

Can I recover lost OpenClaw cron jobs?

If you have no backup of jobs.json, the cron jobs are permanently lost. You must recreate them manually. Going forward, always backup jobs.json before running any update.

← Back to dashboard

clawsmith.com/signal/openclaw-update-destroys-gateway-feishu-cron-jobs

⚠ IssueWide OpenLive

openclaw update Command Destroys Running Gateway, Disconnects Feishu, and Wipes All Cron Jobs

GitHub issue #66401 reports that running openclaw update causes cascading failures: npm install runs without stopping the LaunchAgent service first, gateway crashes from file lock conflicts, Feishu channel config gets corrupted, and all 9 scheduled cron jobs are permanently deleted. 100% reproducible on any existing install.

Product Idea from this Signal

A CLI wrapper that safely updates OpenClaw by backing up state, stopping services, running the update, and restoring on failure

Running openclaw update on a production instance destroys the running gateway, corrupts channel configs (Feishu, Telegram), and permanently deletes all cron jobs because npm install runs without stopping the LaunchAgent first. GitHub issue #66401 documented the 100% reproducible cascading failure. Multiple related issues (#62051, #42883, #37605) show this is a systemic pattern across versions. This tool wraps the update process with pre-flight checks, automatic state backup, graceful service shutdown, and rollback on failure.

CLIOPEN-SOURCEDEVOPSRELIABILITY

UnderservedView Opportunity →