OpenClaw April 2 Release: Task Flow Engine, Android Assistant Integration & Plugin Config Migrations
OpenClaw's April 2nd evening release is one of its most consequential in recent months, touching three distinct pillars of the platform in a single drop. At the center of the update is the full restoration of the Task Flow substrate — the core engine that enables multi-step, durable background orchestration. The rewrite introduces a clear distinction between managed and mirrored sync modes, along with persistent flow state and revision tracking, giving production automation pipelines the lifecycle control they've been waiting for. Parent and child task relationships are now properly scoped, making complex, nested agent workflows significantly more reliable.
On mobile, the release marks a genuine milestone: OpenClaw now exposes Google Assistant App Actions entrypoints on Android, allowing users to launch OpenClaw directly from an assistant trigger. It's the platform's first native voice and assistant entry point, bridging the gap between conversational AI interfaces and OpenClaw's deeper orchestration capabilities. For power users who run OpenClaw throughout the day, the friction of switching to the app is substantially reduced.
The third major change addresses plugin configuration hygiene. Two breaking migrations — for the xAI x_search plugin and the Firecrawl web_fetch plugin — standardize configuration to the plugin-owned config path. The `openclaw doctor --fix` command automates the upgrade, so existing users can migrate without manually editing config files. Together, these changes reflect a maturing platform increasingly serious about both developer ergonomics and production-grade stability.