OpenClaw has been available on Android for a while, but the relationship with Google's assistant layer has always been awkward — you opened the app manually, spoke your prompt, and hoped for the best. OpenClaw 2026.4.2 changes that with official Google Assistant App Actions integration.
What Are App Actions?
Google App Actions is the Android framework that lets apps declare they can handle specific assistant intents. When a user triggers the assistant — by holding the home button, using a Pixel launcher squeeze, or saying "Hey Google" — Android routes matched intents directly to the declaring app.
OpenClaw now ships App Actions metadata in the Android app manifest, which means Android recognizes OpenClaw as a valid assistant entrypoint. PR #59596 by @obviyus adds both the assistant-role entrypoints and the App Actions XML metadata needed to make this work.
How It Works in Practice
The flow is straightforward:
- Trigger the assistant — hold home or say "Hey Google, ask OpenClaw…"
- Android routes the intent to the OpenClaw app
- OpenClaw opens and the spoken prompt drops directly into the chat composer
- Your agent responds as it normally would — via whatever model and skills you have configured
No gateway changes are needed. The Android app owns the intent handling and forwards the prompt as a plain chat message to the gateway over your existing connection.
Gateway Configuration Not Required
One of the nicer aspects of this implementation is that it is entirely client-side. The assistant intent is captured by the Android app, the spoken text is extracted, and it arrives at your gateway as a normal user message. Your server-side config — model selection, skills, system prompt — all applies unchanged.
This also means it works regardless of whether your gateway is local (LAN) or remote (VPS, Tailscale). As long as the Android app has a paired connection, the assistant trigger reaches it.
Current Limitations
The Android app is still described in the official docs as being in early development. A few things to keep in mind:
- App Actions intent routing works best on stock Android and Pixel devices; heavily customized Android skins may handle home-hold differently
- Wake word activation ("Hey Google, ask OpenClaw…") requires Google Assistant to be configured as the default assistant app
- Multi-turn follow-ups via the assistant overlay are not yet supported — each invocation is a fresh message to OpenClaw
- The Android app itself is still maturing; expect rough edges around notification handling and background operation
Pairing with Voice Wake on macOS
If you use OpenClaw across both Android and macOS, this release also ships macOS Voice Wake in the same changelog (#58490 by @SmoothExec). That feature adds a Voice Wake toggle to trigger Talk Mode on macOS. Combined, you now have assistant-style invocation on both major mobile and desktop platforms.
Upgrade and Test
To get Google Assistant App Actions on Android:
- Update the OpenClaw gateway:
npm update -g openclaw - Update the OpenClaw Android app from the Play Store or your sideload source
- Open the app → Settings → ensure assistant permissions are granted
- Hold the home button and say "ask OpenClaw" followed by your prompt
Full release notes for 2026.4.2 are on GitHub. The Android source is in the openclaw/openclaw monorepo.