Is OpenClaw v2026.5.3 stable?
68/100Fact score: 68/100 · evidence-based, not a YES/NO verdict
“Score-first evidence refresh: discord, feishu, provider-integration, runtime is doing the 3am deploy goblin dance. Evidence updated; website owns the final math.”
Stability Score
68Base
80
Evidence
-12
Votes
-0
Survived
+0
Curated
+0
80 base−12 evidence−0 votes+0 (3×0 days survived)=68
Affected components
discordfeishuprovider-integrationruntimesessions-managementtelegramtool
Install this version
npm install openclaw@2026.5.3openclaw update --tag 2026.5.3Score Evidence
| Issue | Area | Type | Penalty | Reason |
|---|---|---|---|---|
| openclaw/openclaw issue 77551 → | runtime | other | -2 | Bedrock aws-sdk auth: ExpiredTokenException after credential file refresh (regression in v2026.5.3) |
| openclaw/openclaw issue 77612 → | runtime | other | -1 | [Bug]: ollama/deepseek-v4-pro:cloud does not allow "max" in v2026.5.3-1 |
| openclaw/openclaw issue 77576 → | telegram | channel-specific | -1 | [Regression] Telegram group session responses route to webchat instead of back to Telegram (v2026.5.3-1) |
| openclaw/openclaw issue 77668 → | discord | channel-specific | -1 | [Bug]: Discord gateway hang at 'awaiting gateway readiness' still reproduces on 2026.5.3-1 (macOS) — six close |
| openclaw/openclaw issue 77561 → | tool | tool-specific | -1 | ownsCompaction tool-result context guard bypass still present in v2026.5.3 (Codex sessions have no mid-turn co |
| openclaw/openclaw issue 77666 → | feishu | channel-specific | -1 | Feishu group messages produce replies=0 after upgrading to 2026.5.3. |
| openclaw/openclaw issue 77733 → | sessions-management | runtime | -2 | Bare /new and /reset no longer trigger persona greeting on 2026.5.3 / 2026.5.3-1. |
| openclaw/openclaw issue 78838 → | provider-integration | runtime | -3 | Google/Gemini assistant_message_end rawText becomes empty after tool calls on 2026.5.3 and 2026.5.6. |