Is OpenClaw v2026.6.33 stable?
75/100Fact score: 75/100 · evidence-based, not a YES/NO verdict
“Extended-stable picked up media delivery misses and Codex cleanup leaks. Still calmer than latest, but the janitor left a few 3am mops in the hallway.”
Stability Score
75Base
80
Evidence
-20
Votes
-0
Survived
+15
Curated
+0
80 base−20 evidence−0 votes+15 (3×5 days survived)=75
Affected components
codexcodex-app-serverdependency-resolutiondependency-securitydockerdocker/latest-taggateway-startupmedia-pathsmessage-deliveryreasoningsecuritytelegram
Install this version
npm install openclaw@2026.6.33openclaw update --tag 2026.6.33Score Evidence
| Issue | Area | Type | Penalty | Reason |
|---|---|---|---|---|
| openclaw/openclaw issue 106738 → | telegram | channel-specific | -1 | Telegram bot-to-bot live release probe cannot observe replies on extended-stable/2026.6.33; issue explicitly lists the target branch/version and a deterministic failing release-check run. |
| openclaw/openclaw issue 112391 → | docker/latest-tag | runtime | -4 | Docker :latest regressed from 2026.7.1 to 2026.6.33, triggering the downgrade guard and blocking startup; gate included explicit 2026.6.33 downgrade context. |
| openclaw/openclaw issue 99382 → | reasoning | runtime | -3 | Anthropic thinking replay can still 400-loop on 2026.6.33 with oversized/invalid thinking signatures; gate included explicit 2026.6.33 reproduction. |
| openclaw/openclaw issue 113584 → | dependency-security | runtime | -5 | Published openclaw@2026.6.33 shrinkwrap explicitly pins brace-expansion/fast-uri versions covered by high-severity advisories. |
| openclaw/openclaw issue 114299 → | message-delivery/media-paths | runtime | -3 | Relative MEDIA paths are rejected on cron/heartbeat/subagent delivery because workspaceDir is not threaded to loadWebMedia; gate included explicit 2026.6.33 reproduction. |
| openclaw/openclaw issue 101788 → | codex/app-server-cleanup | runtime | -4 | One-shot cleanup leaks Codex app-server processes on stable 2026.6.33, allowing duplicate app-servers and session collisions; gate included explicit 2026.6.33 data point. |