OpenClaw 2026.3.2 Just Dropped and It Is a Big One
OpenClaw just shipped version 2026.3.2 and honestly this might be one of the most feature-packed updates yet. Over 84 contributors worked on this release and it shows. Here is a breakdown of what actually matters for you. π Native PDF Tool This is the headliner. You can now feed entire PDF documents directly into your AI workflows. It works out of the box with Anthropic and Google models. If the model does not natively support PDFs it automatically falls back to text extraction. You can configure page limits and file size caps too. For anyone who deals with contracts, reports, or research papers this is a game changer. π Multi-Platform Messaging Upgrade Discord, Slack, WhatsApp, and Zalo channels all now share a unified payload system. What this means in practice: β’ Your AI agent can send images, files, and long messages across any platform β’ Smart text chunking handles long responses automatically β’ No more worrying about format differences between platforms β‘ Telegram Streaming by Default Streaming responses are now on by default for new Telegram setups. Instead of waiting for the AI to finish thinking you get live partial responses as they are generated. The DM experience also got better with a new draft-based preview system. π§© Plugin SDK Expansion For anyone building extensions or integrations: β’ External channel plugins can now access shared runtime helpers directly β’ New audio transcription API lets extensions process voice files β’ New lifecycle hooks with sessionKey in start/end events β’ New event types: message:transcribed and message:preprocessed π οΈ CLI Config Validation You can now run openclaw config validate to check your entire config before starting the gateway. No more trial-and-error debugging broken configs at launch time. β οΈ Breaking Changes to Watch β’ New installs default tools.profile to messaging mode only. Need coding tools? Enable them manually β’ ACP dispatch is now enabled by default β’ Plugin SDK removed registerHttpHandler in favor of registerHttpRoute with explicit auth