Is OpenClaw v2026.6.9 stable?
13/100Fact score: 13/100 · evidence-based, not a YES/NO verdict
“v2026.6.9 picked up fresh Codex heartbeat and video-generation evidence: internal turns wear the wrong channel badge, and Veo calls knock on the wrong Google door.”
Stability Score
13Base
80
Evidence
-76
Votes
-0
Survived
+9
Curated
+0
80 base−76 evidence−0 votes+9 (3×3 days survived)=13
Affected components
codexcompactionconfigdiscordgatewaymemorypluginprovider-routingqqbotreasoningruntimesecuritytelegramuivideo-generationvoicewecom
Install this version
npm install openclaw@2026.6.9openclaw update --tag 2026.6.9Score Evidence
| Issue | Area | Type | Penalty | Reason |
|---|---|---|---|---|
| openclaw/openclaw issue 95495 → | memory | kernel | -5 | Memory store silently relocated on 6.8->6.9 with no migration, forcing a full re-embed (1499 files) |
| openclaw/openclaw issue 95547 → | runtime | kernel | -4 | Codex app-server app closes before long maintenance turn completes; Gateway restart also kills active turn without graceful recovery |
| openclaw/openclaw issue 95515 → | config | runtime | -3 | Upgrade 6.8->6.9 corrupts email channel config with spurious groupAllowFrom field |
| openclaw/openclaw issue 95280 → | reasoning | tool | -2 | OpenAI-completions reasoning merges into the answer; thinking_end only fires at end-of-stream (confirmed on v2026.6.9 c645ec4) |
| openclaw/openclaw issue 95500 → | plugin | tool | -2 | Plugin model provider (opencode-go) cannot be resolved by isolated cron runs; always falls back to deepseek |
| openclaw/openclaw issue 95538 → | telegram | channel-specific | -1 | Telegram /status card collapses into one run-on line (newlines lost) with richMessages on |
| openclaw/openclaw issue 95525 → | telegram | channel-specific | -1 | Telegram /status native command does not respond (polling) while Discord /status works on the same agent |
| openclaw/openclaw issue 95526 → | qqbot | channel-specific | -1 | QQBot splits a long markdown reply into N independent bubbles instead of one message |
| openclaw/openclaw issue 95533 → | wecom | channel-specific | -1 | WeCom separated text+file dual-stream deadlock; 6.9 fixed the mixed branch but not the separated text+file branch |
| openclaw/openclaw issue 95658 → | voice | tool-specific | -2 | Groq voice transcription fails on 2026.6.9 after provider externalization; voice notes arrive empty unless external provider plugin path is repaired. |
| openclaw/openclaw issue 95750 → | gateway | kernel | -5 | Main-session restart recovery can death-loop the gateway across reboots with no persistent retry budget on 2026.6.9. |
| openclaw/openclaw issue 95765 → | provider-routing | runtime | -2 | First-time external provider setup installs DeepSeek plugin but skips the selected API-key/auth flow on 2026.6.9. |
| openclaw/openclaw issue 95696 → | compaction | runtime | -3 | Compaction resets a session model override to a previous provider, so UI model state diverges from actual calls on 2026.6.9. |
| openclaw/openclaw issue 95740 → | provider-routing | runtime | -3 | Google Vertex authorized_user runtime routing remains broken on 2026.6.9 despite earlier catalog fixes. |
| openclaw/openclaw issue 95685 → | ui | runtime | -1 | Session Workspace Rail marks readable non-workspace files as missing on 2026.6.9. |
| openclaw/openclaw issue 95597 → | codex | runtime | -2 | Codex native post_tool_use relay skips agentToolResultMiddleware, so Tokenjuice artifact capture stops on 2026.6.9. |
| openclaw/openclaw issue 95895 → | security | kernel | -5 | GEMINI_API_KEY written as a plaintext literal in the generated systemd service unit on 2026.6.9, exposing it via systemctl show / process env / crash reporters while all other provider secrets use managed runtime injection. |
| openclaw/openclaw issue 95915 → | runtime | kernel | -4 | Heap not released on embedded run abort (released=0) and the session write lock persists after abort cleanup on 2026.6.9, causing gradual memory exhaustion that requires periodic forced restarts. |
| openclaw/openclaw issue 96046 → | gateway | runtime | -3 | Gateway rejects a valid config at startup with plugins.slots.memory: plugin not found for an extensions/ plugin present in the plugins list — 2026.6.9 regression; 2026.6.8 is unaffected. |
| openclaw/openclaw issue 95904 → | runtime | runtime | -3 | Non-Codex fallback models enter code-mode but fail a trivial tool call with internal_error on 2026.6.9, breaking the automatic fallback chain instead of executing or falling through. |
| openclaw/openclaw issue 96007 → | discord | channel-specific | -2 | Discord silently truncates all message content after an inline error line, dropping recommendations/next-steps on 2026.6.9. |
| openclaw/openclaw issue 96098 → | telegram | channel-specific | -1 | Telegram inline buttons stopped working after update to 2026.6.9 (inlineQueries=false); buttons render as plain text. |
| openclaw/openclaw issue 95878 → | telegram | channel-specific | -1 | Telegram long-message auto-split regression still present in 2026.6.9 — multiple truncations in a single session on default config. |
| openclaw/openclaw issue 95891 → | provider-routing | channel-specific | -1 | opencode-go/minimax-m3 thinking content leaks to channel via the Anthropic Messages path on 2026.6.9. |
| openclaw/openclaw issue 96079 → | discord | channel-specific | -1 | Anthropic models on Discord produce reasoning (/reasoning on) and pre-tool narration (/verbose on) that are recorded in the session log but never surfaced in the channel on 2026.6.9. |
| openclaw/openclaw issue 99910 → | memory | kernel | -5 | Memory dreaming promotion can peg the gateway event loop for about 10 minutes and prevent short-term recall persistence on v2026.6.9. |
| openclaw/openclaw issue 96207 → | ui | channel-specific | -1 | Telegram/Discord tool-call progress messages remain visible after successful tool completion on 2026.6.9. |
| openclaw/openclaw issue 95553 → | compaction | kernel | -5 | Budget-triggered preflight compaction is hard-capped around 60s on 2026.6.9, ignoring configured compaction timeout. |
| openclaw/openclaw issue 102206 → | codex | channel-specific | -3 | Codex app-server internal/heartbeat turns are stamped webchat-bound since v2026.6.9, blocking cross-channel heartbeat notifications. |
| openclaw/openclaw issue 103291 → | video-generation | tool-specific | -3 | Google Veo video generation sends generateContent instead of predictLongRunning on v2026.6.9, breaking video_generate. |