Why have OpenClaw NPM downloads halved?

Frequent updates (13 releases in one month) led to poor stability. Users stopped updating and some stopped using it entirely.

What is OpenClaw pause week?

The OpenClaw team announced a week with no new features, focusing purely on stability optimization to rebuild user trust.

Why is Nvidia afraid to upgrade OpenClaw?

Enterprise users like Nvidia cannot risk production breakage from frequent updates that each potentially introduce breaking changes.

How many releases did OpenClaw ship in one month?

13 point releases in a single month, roughly one every two days, with v2026.3.2 alone shipping 3 simultaneous breaking changes.

Is OpenClaw still losing users?

NPM downloads halved from their mid-March peak. Community maintainers are split between stability-first and innovation-first approaches.

← Back to dashboard

clawsmith.com/signal/openclaw-downloads-halved-pause-week-stability

⚠ IssueWide OpencoreLive

OpenClaw NPM Downloads Halved from Peak as Team Declares Stability Pause Week

OpenClaw NPM download volumes have halved from their mid-March peak, falling back to early March levels. Frequent updates (13 releases in one month) led to poor stability. Team announced a pause week with no new features, focusing on stability. Nvidia and enterprise users afraid to upgrade.

Product Idea from this Signal

A CLI tool that snapshots your OpenClaw state before updates, runs the upgrade in a sandboxed dry-run against your live config, and auto-rolls back if any health check fails

1667.8k ▲

OpenClaw ships updates every 2-3 days and each one risks breaking exec permissions, crashing the gateway, saturating CPU with plugin loading bugs, or silently deleting cron jobs. Four separate regressions in April 2026 alone (v2026.4.1 sandbox, v2026.4.5 CPU, v2026.4.14 memory timeouts, update command wiping Feishu and crons) hit thousands of self-hosters with no rollback path. The built-in openclaw doctor only validates config schema after the fact. This tool wraps the entire update lifecycle: snapshot state, dry-run the upgrade against your actual agent/cron/channel config, diff the before/after, and block or auto-rollback if anything regresses.

CLIOPEN-SOURCEDEVTOOLSELF-HOSTEDRELIABILITY

CompetitiveView Opportunity →