The biggest highlight of this update is our new advanced module: OpenClaw(Mini).
First, why the name Mini?
It is not a full copy of OpenClaw CLI. The full CLI is powerful, but on Android it is simply too heavy to run well as a deeply integrated, always-available assistant. Instead of forcing the entire stack into Ava, we built a lighter implementation designed specifically for Ava and Android devices. It keeps the best parts of OpenClaw's design, including tool calling, session handling, and heartbeat logic, while being adapted for real device use. In short, this is not a stripped-down toy. It is the practical part of OpenClaw turned into something that can actually live and work inside Ava.
OpenClaw(Mini) now brings most of the core OpenClaw design ideas into Ava in a usable form. It combines model reasoning, tool execution, skills, and Android-side capabilities to handle device control, browser actions, UI inspection, screenshots, automation, file handling, diagnostics, scheduled tasks, heartbeat isolation, and messaging channels such as QQ and Telegram. More skills will continue to be added over time.
To try these advanced features, go to:
Settings -> Advanced Features -> Mod Store -> OpenClaw(Mini)
After installation and setup, you can enable this AI assistant workflow directly from there. Browser control, automation, diagnostics, and channel-related features are all connected through this path.
A key addition in this release is the new heartbeat system.
OpenClaw(Mini) now supports a built-in isolated heartbeat workflow. It runs in its own session, does not pollute the main conversation, and avoids corrupting normal chat context. This follows one of OpenClaw's strongest design principles: periodic checks and background tasks should stay isolated, reliable, and predictable.
On the system side, we also expanded low-level capability support.
OpenClaw(Mini) now supports:
- Root
- Shizuku
- Safe adb-style and shell-style commands
- File reading, diagnostics, and system state inspection
- App UI access and automation control
At the same time, Ava now fully supports accessibility integration.
This matters a lot, because it gives non-root devices a much better way to inspect system UI, read visible controls, and understand on-screen state. That is especially useful for screenshots, UI analysis, and app interaction. To prevent performance issues, accessibility is not left running in a heavy continuous mode. It is only triggered when OpenClaw-related tools actually need it.
Beyond OpenClaw(Mini), this update also fixes a large number of long-standing pain points.
We fixed #52, added a new Stop Alarm action, and reworked the entire alarm flow. Thanks to @yaro24 for helping push that issue forward. Alarms are now much cleaner logically, and users can also set custom alarm sounds, so the system no longer has to attack you with the same default sound forever.
The browser stack also received major work.
We added browser gesture navigation, and this was not a cosmetic patch. It was redesigned specifically for the floating window browser, solving the long-standing gesture problems that usually come with overlay WebView behavior. We also added live browser URL sync, so the frontend can now display the current page address in real time instead of working blindly.
Another important community issue was fixed as well.
When using action: url with an intent:// path, Ava previously treated that as a normal web link and passed it to the browser, which failed or opened the wrong page. This has now been fixed. Intent links are correctly recognized and handed over to Android instead of being misrouted through the browser.
We also continued improving large-screen layout behavior.
The home screen scaling issue on 9-inch and larger devices has been fixed, so tablets and bigger displays no longer look like they are stuck in an over-compressed phone layout. The home screen title area, controls, and status region now scale more appropriately on larger displays.
In addition, this release also fixes:
- ESPHome version visibility, so the current version can now be shown correctly
- A range of issues involving entity display, config pollution, state reporting, screenshot workflows, messaging channels, compilation errors, and runtime failures