SafeBump / 2026.8.35
Is OpenClaw 2026.8.35 safe to update?
No known blockers No open P0, crash-loop or release-blocker issues reported against it yet.
Line: extended-stable. Released 2026-10-02 (release notes). Issues opened in the 14 days after release that name this version: 9, of which 5 are still open, 0 open P0 and 0 open crash-loop or release-blocker. Updated 2026-10-12 05:57 UTC.
Top open issues reported against 2026.8.35
- #165961 [2026.8.35] pdf / image tools and inbound image pre-analysis fail with "No API key found for provider openai" when OpenAI is connected only P1 · 2 comments · opened 2026-10-06
- #164895 Control UI renders one assistant message three times (server stores a single copy) P2 · 2 comments · opened 2026-10-04
- #165226 Bug: isolated scheduled agent turns fail on extended-stable 2026.8.35 P1 · 1 comments · opened 2026-10-05
- #165967 [Bug]: [Backport extended-stable] claude-opus-5-5 fails with HTTP 400: thinking.type.disabled is not supported P1 · 1 comments · opened 2026-10-06
- #165025 [Bug]: Reasoning-prefixed NO_REPLY not detected when closing line isn't an exact "silent intent" phrase P1 · 1 comments · opened 2026-10-04
Want stability over features? The newest extended-stable (LTS) release without known blockers is 2026.8.35.
Update already failed? Look up your reason code.
Did an update already break your agent?
Update Rescue: $149 fixed, and you only pay once it works
Gateway stuck in health: starting, a crash loop after openclaw update, Doctor refusing your workspace, memory or CPU running away, or a Telegram, WhatsApp or Discord channel gone silent. We get you back to a stable, pinned version with your sessions, memory and channels intact, then write down the pin and a safe update routine for your setup.
- Run by an engineer who has run OpenClaw agent fleets in production for paying clients since early 2026 and has rolled back silent regressions on client machines.
- Async by default: you paste logs and run the commands we send, or share your screen. We never ask for your API keys or passwords.
- Most fixes take under 24 hours. If we can't fix it, you pay nothing.
- Pay after the fix in USDT on Arbitrum One, or by card through Whop on request (payment details).
Request a rescue (GitHub)
Request by email
Would rather keep it private? Use email. A GitHub request is public, so don't paste secrets or logs that contain tokens there.
All releases