OpenClaw 2026.5.27 is live 🦞 🔒 tighter runtime/security boundaries ⚡ faster gateway + reply paths 🧠 steadier Codex/app-server memory 📡 better channels, providers, Pixverse video Less wedge, more claw. https://t.co/SoYGC4T0mt
OpenClaw Hardens Security Boundaries and Stabilizes Agentic Coding Runs
· Updated
OpenClaw released version 2026.5.27, a hardening update for the open-source AI assistant that implements tighter security boundaries and stabilizes its Codex agentic coding mode. The release moves beyond simple chat by enforcing admin-only approvals for device roles and ensuring agent runs survive sub-process failures.
- New video provider
- PixVerse
- Embedding support
- Core OpenAI-compatible providers
- Model parameters
- VLLM thinking params
- Security requirement
- Admin authority for device roles
- Availability
- GitHub, Docker, and npm
As self-hosted agents move toward autonomous tasks, the fragility of long-running processes is a primary failure point. By resolving models earlier and ensuring app-server clients survive helper crashes, this release addresses the reliability gap in complex runs. The update adds to the OpenClaw security hardening seen in previous releases by further restricting untrusted inputs.
You can now use PixVerse for native video generation and connect OpenAI-compatible embedding providers as a core service for RAG (grounding AI responses with external knowledge). The update also fixes duplicate notifications on iMessage and Telegram. It is available now on GitHub, Docker, and npm.
Still wondering? A few quick answers below.
Every HeadsUpAI update is written based on its original source and reviewed before it's published. Read our editorial standards →
