The Android app is out, and your phone doesn't have to do the work

2026-08-12 · Alex Wall

The most useful computer you own is the one in your pocket, and it is the worst one to work on.

That is not a complaint about phones. It is what a phone is. There is no project folder on it, no terminal, no build to run, none of the desktop applications you actually use. So "AI on your phone" has mostly meant a chat window — genuinely handy for a question, and not where anything gets finished.

Caiioo for Android is on Google Play starting today. It is a beta, which is what everything we ship is until we call something 1.0. No invite, no waitlist — install it.

And the reason I'm more interested in this release than in "the app exists" is that the phone doesn't have to be where the work happens.

The computer you left at home is still on

Your Mac is sitting on your desk with your repository checked out, your tools connected, and your files where you left them. That machine is where the work lives. The phone in your hand is just the device you happen to have.

So Caiioo treats a conversation as something that has a host device rather than something that belongs to whichever screen you opened it on. Send a message from your phone into a conversation hosted on your Mac and it runs on the Mac — reading the real folder, running the real build, using the tools that only exist on a computer — while the answer streams live on both screens. Your API keys never travel; the host signs in to providers with its own credentials.

The version I use most is the reverse. You start something on the phone because that is when you thought of it, then you put the phone in your pocket and it locks. Ordinarily that is where a mobile agent dies — the operating system suspends the app and the half-finished turn goes with it. Instead, the turn is handed to your preferred desktop, which finishes it, and the answer syncs back and is waiting when you sit down.

We call this your Private Constellation: your own devices, holding one conversation between them, over sync that is encrypted before it leaves any of them. Nothing about it routes through a server of ours that can read your conversation. That is the whole reason it took a while to build.

What the phone does on its own

Plenty, and it is worth being specific, because the parts of Caiioo that need a filesystem are exactly the parts a phone cannot have.

On Android the agent is the real one, not a cut-down chat: the same modes, the same skills, the same hub apps, the same multi-step tool use, web search and page reading, image generation, and your conversation history synced from every other device you use. It integrates with your calendar and reminders through Android's own provider, so "what does my week look like" is answered from your actual calendar. Speech-to-text runs on the device with a local Whisper model — your voice does not go to a transcription service to become text.

What it does not do is read your project folders, run shell commands, or drive desktop applications. Android has no filesystem Caiioo can reach in the way a desktop does, and I would rather say that plainly than ship a button that fails in an interesting way. Those capabilities live on macOS, Windows, and Linux — and now your phone can point at a machine that has them.

Beta means beta

Android is on Google Play as an open beta. iPhone and iPad are still invite-only while we work through TestFlight — if you want in, ask for an invite and we add testers in batches.

Calling it beta is not modesty. Phones are a genuinely harder place to run an agent than a desktop: the system can suspend your app mid-answer, evict it from memory entirely, or kill the network when the screen goes dark. Most of the mobile work this summer was not features, it was making a long-running turn survive contact with that reality — saving progress after each step so at most one step is lost, recognizing a dropped connection and retrying it, and replacing the old silent failure with a notice and a Continue button. A reply that vanishes because you locked your phone is not a small bug. It is the difference between a tool you can rely on and a demo.

There will be more of those. That is what the beta label is for, and it is why the feedback path is short: the report goes straight into the queue I read.

Why a phone app at all

I did not want to build a mobile app so we could say we had one. Phones are where you think of work far more often than they are where you do it, and until now that gap was yours to bridge by remembering the thing later.

One agent, one conversation, following you across the devices you already own — the phone for the moment you thought of it, the desktop for the folders and the compiler, all of it encrypted between your own machines and none of it sitting on ours. That is the product. Android was the missing piece.

Get it on Google Play, and tell me what breaks.