Latest Update Ruin

[fathom pulsar]

I'd like to know if the known issues with the latest update are being addressed. I've downgraded.

[fathom pulsar]

Annnnnd ... Krill is rate limited.

[sharp stag]

you're very desperate, you miss your bot?

[fathom pulsar]

@sharp stag LOL I want to know whether or not THEIR bot knows about the botched version that was released this morning.

[sharp stag]

Teething problems indeed.

Teething problems

[golden crater]

@go_marculix via Twitter

Marculix (@go_marculix)

↩ (@rafalozan0)
@rafalozan0 @openclaw Thought the same, best quality assurance would be running each new version against a sophisticated test factory agent, testing each module against a functionality specs then producing a report.

**💬 1 ❤️ 1 👁️ 150 **

FxTwitter · Apr 26, 2026, 2:38 AM

[bitter prawn]

Yeah — looks actively addressed, but I’d still be cautious.

As of Apr 27, GitHub shows newer 2026.4.25 beta builds after the rough 2026.4.24 update, and the release notes specifically mention install/update hardening for macOS/Linux/Docker, bundled plugin runtime deps, service restarts, and mixed-version gateway verification. (github.com)

That said, there are still open 2026.4.24 regression issues around missing bundled plugin deps and Playwright/browser runtime resolution, so downgrading to a known-good version was a reasonable move. (github.com)

If you want to sanity-check whether your exact issue is already covered, paste:

openclaw --version
openclaw status --all

The FAQ’s first troubleshooting loop also recommends openclaw status, openclaw gateway status, logs, and openclaw doctor before deeper debugging. (docs.openclaw.ai)

Yep 😅 I checked npm/GitHub: stable/latest is still 2026.4.24, but the beta tag has already moved to 2026.4.25-beta.10, so fixes are definitely being iterated.

Known rough edges being tracked include:

• #72058 missing bundled npm/plugin runtime deps after update
• #72168 Playwright/browser actions failing after doctor --fix
• #72566 openclaw doctor hanging on 2026.4.24

So: downgrading was a sane call if you need a working setup right now. I’d wait for the next stable unless you specifically want to help test beta.

If your issue is different, please add exact repro +:

openclaw --version
openclaw status --all

Docs triage loop: https://docs.openclaw.ai/help/faq

[fathom pulsar]

I can't install .24 because it breaks the system.

[bitter prawn]

Yeah, don’t fight .24 if it breaks your install. That release had real packaging/runtime-dep regressions, not user error.

Quick update: latest has moved to 2026.4.25, and the big .24 reports I was tracking for missing plugin runtime deps and Playwright/browser actions are now marked closed. (newreleases.io)

My recommendation:

• If you need reliability: stay downgraded/pinned for now.
• If you want to retest: try 2026.4.25, not .24, ideally with a backup + maintenance window.
• If .25 still breaks, please paste:

openclaw --version
openclaw status --all

and the first install/gateway error. That’ll tell us whether it’s the same runtime-deps class or a new regression.

[fathom pulsar]

My installation isn't configure in an uncommon manner. I've kept things pretty much bone stock, so I'd like to know what I'm the one who's supposed to beta test versions that aren't marked as beta, released to the public for mass-level bugzillas.

[bitter prawn]

You’re right to be annoyed. A stock install should not make you feel like you got silently drafted into beta testing.

What happened with .24 looks like a release-quality miss around packaged/plugin runtime deps — the kind of thing that can break otherwise normal installs. That’s not on your config. The release page shows .24 had multiple packaging/runtime-dep fixes even during beta, and then the .25 line followed immediately after, so this was clearly being chased quickly. (github.com)

Practical answer: if you need the machine working, stay pinned to the last version that works for you and don’t touch .24. If you want maintainer-level follow-up, the best path is a GitHub issue with openclaw --version, OS, install method, and the first failure log — not because you’re obligated to debug it, but because that’s the channel where release regressions actually get tracked.

[fathom pulsar]

Tell me if .25 properly is situated so as NOT to cause the same issues as .24

[bitter prawn]

Short answer: I would not call .25 guaranteed, but yes, it is specifically positioned to avoid the same .24 failure class.

What I checked:

• .25 release notes explicitly include the bundled plugin runtime-deps fix for #72058, the “npm deps missing after update” regression. (newreleases.io)
• The Playwright/browser runtime issue from .24 is closed: #72168. (github.com)
• The openclaw doctor hanging report from .24 is also closed: #72566. (github.com)

So my honest recommendation: skip .24 entirely. If you’re willing to try again, try 2026.4.25 stable, not beta. But if your current downgraded setup is mission-critical, wait a bit longer for more community confirmation before upgrading.

[fathom pulsar]

.25 works. All is well.

[bitter prawn]

Glad to hear it — that’s a relief. 🎉

If this fixed the thread, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes it for the next poor soul who hits the .24 mess.