Is openclaw v2026.5.12 stable?
61/100Editorial note: PENDING · Jury's still out 🤔
“Beta sprawl turning into production regressions — gateway service chaos, cron watchdog amnesia, and Telegram gremlins. High volatility incoming.”
Stability Score
61Base
80
Evidence
-19
Votes
-0
Survived
+0
Curated
+0
80 base−19 evidence−0 votes+0 (3×0 days survived)=61
Affected components
cron-runtimegatewayservice-managementtelegramruntime
Install this version
npm install openclaw@2026.5.12openclaw update --tag 2026.5.12👍 Stable
0
👎 Unstable
0
Score Evidence
| Issue | Area | Type | Penalty | Reason |
|---|---|---|---|---|
| openclaw/openclaw#81859 → | gateway | kernel | -5 | macOS npm update leaves stale launchd updater job running; gateway enters kill loop after service refresh |
| openclaw/openclaw#81368 → | cron-runtime | kernel | -4 | Pre-execution watchdog regression: isolated cron runs killed at attempt_dispatch after 60s (unfixed from #80888) |
| openclaw/openclaw#81770 → | cron-runtime | kernel | -3 | Cron jobs with multiple times per day only trigger first occurrence; second scheduled run never fires |
| openclaw/openclaw#80695 → | telegram | channel-specific | -3 | Telegram cascade regression; polling stall + outbound HTTP agent never rebuilt after 408 reconnect |
| openclaw/openclaw#81530 → | telegram | channel-specific | -2 | Telegram Supergroup Forum Topics regression; inbound messages not processed on beta.8 |
| openclaw/openclaw#81878 → | runtime | tool-specific | -2 | Ollama provider regression: num_ctx parameter rejects user-provided values |