OpenClaw’s 2026.4.24 and 2026.4.29 releases caused gateway slowdowns, plugin dependency repair loops, and broken messaging channels; team is shrinking core and moving optional features to ClawHub.
Key Takeaways
Plugin dependency repair ran in both startup and update paths, creating visible breakage for users across Discord, Telegram, and WhatsApp channels.
The root cause was a bad middle state: too much moved to plugins while bundled plugins were still being staged, checked, and dependency-loaded at boot.
Supply-chain concerns (transitive npm packages, postinstall scripts) drove the core-shrinking direction even though OpenClaw had no direct Axios dependency.
OpenClaw was too founder-driven; release, review, and packaging work concentrated in one person; the OpenClaw Foundation and OpenAI support are funding a real team.
An LTS release will be announced separately later in May alongside the faster update cycle.
Hacker News Comment Review
Commenters flagged the post’s writing style as AI-generated, with specific complaints about punctuation patterns (colons, semicolons), not the technical content.
No one confirmed running OpenClaw in production; the thread’s main substantive exchange questioned what legitimate use cases exist beyond spam/scam bots.
Notable Comments
@whalesalad: Confirmed real-world breakage after a routine update and provider key switch, with even a downgrade to IRC failing to restore function.
@stavros: Advocates small-core, plugin-first bot design with API keys kept outside the bot process as a direct architectural contrast to OpenClaw’s current problems.
