Creating an assistant no longer means filling out forms. Just describe what you want in a conversation, and the wizard configures everything for you.
Two improvements to help you understand and manage running assistants faster.
Your assistant is no longer limited to a single messaging platform. You can now deploy to Telegram, Slack, Discord, or any combination of the three.
Until now, editing assistant files meant working through openclaw UI or redeploying from scratch. The new file editor gives you direct access to your assistant's files right from the dashboard.
This update improves how managed assistants preserve state, so restarts are less disruptive and recovery is more dependable.
We made this change because cloud browser automation setups were too fragile and required too much manual configuration. The goal of this release is to give you safer defaults, fewer deployment steps, and more reliable assistant behavior in isolated environments.
We are introducing first-class support for fully customizing your openclaw.json, alongside making assistant configuration easier to understand and more dependable.
This release focused on product clarity and assistant configuration flow.
This update focused on clarity and usability.
This release made external integrations more complete while improving day-to-day stability.
This patch focused on making managed usage more dependable.
A full pass on the landing experience improved readability and conversion-oriented messaging.
This was a major milestone for managed assistant billing and reliability.
Payments and production reliability moved from setup to functional rollout.
This release focused on improving security for critical user actions.
This is the first public foundation of the product.
