Is OpenClaw v2026.4.23 stable?
64/100Fact score: 64/100 · evidence-based, not a YES/NO verdict
“Score-first evidence refresh: cron-runtime, gateway, image-tool, plugin-system is doing the 3am deploy goblin dance. Evidence updated; website owns the final math.”
Stability Score
64Base
80
Evidence
-19
Votes
-0
Survived
+3
Curated
+0
80 base−19 evidence−0 votes+3 (3×1 days survived)=64
Affected components
cron-runtimegatewayimage-toolplugin-systemruntimewhatsappwindows
Install this version
npm install openclaw@2026.4.23openclaw update --tag 2026.4.23Score Evidence
| Issue | Area | Type | Penalty | Reason |
|---|---|---|---|---|
| openclaw/openclaw issue 72370 → | plugin-system | runtime | -2 | Workspace hooks rejected/replaced with backup stub on 2026.4.23 lineage. |
| openclaw/openclaw issue 79380 → | gateway | kernel | -3 | Gateway CPU spin/crash loop regression from 4.23 to 4.x lineage. |
| openclaw/openclaw issue 77443 → | runtime | -3 | WhatsApp first inbound blocks event loop with high delay. | |
| openclaw/openclaw issue 76275 → | gateway | kernel | -3 | Gateway restarting loop. |
| openclaw/openclaw issue 71717 → | windows | runtime | -2 | Windows exec returns EPERM and commands fail. |
| openclaw/openclaw issue 72703 → | runtime | runtime | -2 | Background task updates are injected as user-role messages, confusing weaker models. |
| openclaw/openclaw issue 72954 → | cron-runtime | runtime | -3 | Cron announce delivery can strip owner-only tools from follow-up owner DMs on 2026.4.23. |
| openclaw/openclaw issue 75634 → | image-tool | tool-specific | -1 | Sharp prebuilt binary fails on SSE2-only KVM hosts; reproduced on 2026.4.23 and newer. |