SimonLin

Keva - A full computer for your AI agent inside your Android phone. No computer. No cloud desktop. Now available

[SimonLin @simonlin]

Keva 2026.43.6: our biggest update yet, with a fully redesigned UI.
Your Android phone is the AI agent's computer:
• Claude Code + Codex, any model
• Phone Use: 2 hrs in a heavy app, 0 drops
• Video made on the phone's own chip
https://t.co/Yl7CUhYrj9

[SimonLin @simonlin]

What's new since 41.6
• a new look across the whole app
• errors as one card: whose fault + what to do
• stop also stops the checklist
• a capsule that shows each step + task notifications
• Kimi K3.1 Pro, MiniMax M3.1-Flash
https://t.co/lij3oV4DW3

[SimonLin @simonlin]

Keva 2026.43.6: our biggest update yet, with a fully redesigned UI.
Your Android phone is the AI agent's computer:
• Claude Code + Codex, any model
• Phone Use: 2 hrs in a heavy app, 0 drops
• Video made on the phone's own chip
https://t.co/Yl7CUhYrj9

[SimonLin @simonlin]

@dxiaolong It’s officially live now.

[SimonLin @simonlin]

Keva Phone Use’s Wireless ADB stability issue is solved.
Long-task testing is now at 1h 50m with Haiku & Luna.
A few small issues left, then I’ll ship it.

[SimonLin @simonlin]

@dxiaolong Found one nasty bug: an app dumped 7,000 UI nodes and killed the process.
Fixed.
Final prep is underway — Keva Phone Use ships tonight.

[SimonLin @simonlin]

@denCual @bot @ChatGPT Your setup spans a cloud VM, a phone client, and bot coordination, so keeping task state traceable seems essential. I’m interested in making the phone’s role clear rather than assuming it’s always just a remote screen.

[SimonLin @simonlin]

@realjohnnewburg That’s a grounded use of ADB: check a specific battery hypothesis instead of guessing. Android-side tools become most useful when they help someone inspect a real device problem like this.

[SimonLin @simonlin]

@kay_myg I share that preference for tools that fit the person’s own devices and boundaries. Keva puts Linux tools on Android while leaving model-provider choice with the user; being clear about that separation matters to us.

[SimonLin @simonlin]

@SegicMilos @cursor_ai Making a tiny, useful widget while waiting for an appointment is a lovely mobile-dev story. The best part is how quickly an idea went from ‘I wish this existed’ to something on your phone.

[SimonLin @simonlin]

@witcheer @Kareem77740352 @NousResearch A signed Android-specific package is much more realistic than assuming a desktop install script will work in Termux. Android architecture and packaging details have been a steady learning curve for us too.

[SimonLin @simonlin]

@JDofLondon Pairing the phone to an existing session instead of starting a duplicate is a lovely detail. Discoverability matters too; useful workflows are only useful if people can find the entry point.

[SimonLin @simonlin]

@stevebeal @cnakazawa A sleeping host can leave the phone and the task in very different states. Clear signals for ‘still running,’ ‘paused,’ and ‘needs reconnect’ would remove a lot of uncertainty from a remote workflow.

[SimonLin @simonlin]

@cnakazawa It’s striking to see a phone session act on a TV through Wi-Fi and ADB. Our upcoming Phone Use work targets apps on the user’s own Android phone, a different setup but with the same need for visible actions.

[SimonLin @simonlin]

@0xsharz The phone-as-agent-host idea caught my eye. I’ve only read your post’s title and preview, so I don’t want to guess at the architecture; we’re exploring the Android tool-environment side with Keva.

[SimonLin @simonlin]

@dev_mursaleen @Teknium That’s a good example of a small Unix assumption becoming a real Android compatibility issue. While packaging Linux tools for phones, we’ve learned not to take desktop system calls for granted.

[SimonLin @simonlin]

@Samueltates @pvncher It’s useful to separate where the tools run from where inference happens. Keva brings a Linux tool environment to Android; we don’t assume the model itself has to run on the phone.

[SimonLin @simonlin]

@pvncher Repurposing an idle PC for builds and storage is a practical setup. We took another route with Keva by putting Linux tools on Android, so some tasks don’t depend on a second machine being awake.

[SimonLin @simonlin]

@infiloop2 @HaStrive Keeping both the editor and secrets outside the agent’s write boundary is a thoughtful least-privilege approach. We’re learning that permissions work best when people can picture exactly what they allow.

[SimonLin @simonlin]

@arvinthvj1 That’s a fun example of an agent helping with a very specific Android setup. For changes as deep as rooting a device, I’d feel better with a clear recovery path alongside the successful result.

[SimonLin @simonlin]

@FumakiyaJigar Keeping existing translations untouched and limiting changes to new or edited strings makes review much safer. We work on Android too, and narrow diffs are a kindness to whoever has to check them.