Skip to content
AURA Open source·★ Star {{ stars }}
Download
0:00

Open-source hands for AI agents to control your Android.

android-use, open source.
AGPL-3.0 · No root · No cable · No backend
Early, and built by one person.
[ Scroll to explore ]

Voice assistants can talk. They can’t use your phone.

Ask one to book a ride and it opens the app, then stops. It can’t tap, type or scroll, so the actual work is still yours.

The server runs on the phone.

No backend and no cloud computer watching your screen. The MCP server lives inside the AURA app, on the device in your hand.

no rootno cableno backend100% Kotlin

Any AI agent gets hands.

Claude, Cursor, VS Code or any MCP client plugs into the server on your phone. Seven layers, one loop.

Look. Pick. Tap. Check.

Every button gets a number. The agent picks a number, never a pixel, then looks again.

Claude, on your phone.

Pair once with a PIN, and Claude Code on a laptop drives the phone over MCP. Here it shares an Instagram post to a story, uncut and muted.

ClaudeMCP0:00 / 0:59
Voice by Gemini Live

Then we gave it a voice.

“HeyAURA,bookaRapidotoRockBeach,Puducherry.”

A real conversation, not a voice menu. It talks back and uses the phone while it speaks, with the same tools and the same gate.

Interrupt anytime
Talk over it and it stops mid-sentence.
Works while it talks
Tells you the moment the task is done.
Hands-free
Optional “Hey AURA” wake word.
Picks up where it left off
Ask it to finish a task you cut short.

You always win.

The agent asks to open a banking app and the safety gate refuses. You tap Pause and it waits for you.

  • Banking, payment, authenticator apps✕
  • Card numbers, PINs, passwords✕
  • A new computer connectsyour tap

Read every line.

The app, the agent and the MCP server are all open source, under the AGPL-3.0.

Give it something to do.

Keep scrolling to see everything it can reach.

56 tools, on the phone.

Called in any order, checking the screen between each one, all through the same gate.

  1. seeing
  2. touching
  3. typing
  4. apps
  5. browser
  6. notifications
  7. media
  8. contacts
  9. files
  10. deep links
  11. system
seeing 6 / 56

Reads the screen and numbers everything you can touch.

Real apps.
No APIs.

No integrations. It reads the screen the way you do.

Its own keyboard types into React Native and Flutter apps.

Webview apps like Swiggy and Amazon work too.

WhatsApp

“Text Mom that I’ll be home soon”

Talk to AURA
“Message Amma I’m running ten minutes late”“What did Ravi say?”“Book a Rapido to office”“Navigate to Cubbon Park”“Reply to that and tell him I’ll call back”“Where am I right now?”
“Set an alarm for six thirty”“Pause the music”“Open the PDF I downloaded yesterday”“Order my usual from Swiggy”“Put a ten minute timer on”“What’s on my screen?”

No magic words. Type instead of talking, stop any task from the bubble, and if it can’t do something it says so.

It brought a browser.

Half the jobs you want done live on the web. AURA carries its own browser and opens it in front of you. This is its real chrome.

MX Master 3S — Amazon✕ MX Master 3S — Flipkart✕
+
amazon.in/s?k=mx+master+3s
01
02₹8,295

browser_read → price, delivery, seller rating

in-app browser · playing at 2×

“Open Swiggy in the browser and search for coffee. Don’t order.”

browser_openbrowser_actbrowser_findverify_action
two tabs · playing at 2×

“Compare the MX Master 3S on Amazon and Flipkart: price, delivery, rating, warranty, returns. Don’t buy.”

browser_openbrowser_tabsbrowser_readbrowser_act
search + Maps · playing at 2×

“Find a highly rated café near Rock Beach, check it’s open today, and get directions in Maps.”

web_searchbrowser_readresolve_deeplinkopen_deeplink
8

Its tabs are your tabs

Up to eight, with an address bar you can type into. Take over mid-task and you’re just browsing.

∞

You stay logged in

Sessions survive closing the app. Google sign-in is the exception: Google blocks it in every embedded browser.

1

A table in one call

browser_extract reads a whole table at once, so a comparison takes a minute, not ten.

◐

A window, not a takeover

Shrink it to a floating ball. Logins, captchas and payments are handed to you. Only ordinary web addresses open.

Test your app in plain English.

Point Claude Code or Cursor at your build, describe the flow, and it taps through it on a real phone, checking the screen after every step.

Claude Code · test run on a real phone

“Open the expense app, add lunch for ₹250, and check it shows up in today’s list.”

  1. launch_app · Expensesqueued
  2. perceive_screen · numbers every buttonqueued
  3. tap · “+ Add”queued
  4. type_text · “Lunch” · “250”queued
  5. tap · “Save”queued
  6. verify_action · “Lunch ₹250” in today’s listqueued
real

Runs on the phones your users hold, not an emulator you tuned.

logs

Every step is recorded on the phone in Settings → Logs.

any

Native, React Native, Flutter or web views. If it’s on screen, it’s testable.

0

Test IDs to add. It reads the screen the way a person does.

Benchmarked on AndroidWorld, the public suite of real-app tasks. A few we run:

ExpenseAddSingleContactsAddContactClockTimerEntryCameraTakePhotoFilesMoveFileMarkorAddNoteHeaderBrowserMazeAudioRecorderRecordAudio

You’re handing it your phone. Here’s what it can’t do.

Enforced in code, in one gate, before any action runs. No tool and no client can skip it.

  1. 01You outrank the AI
  2. 02Banking apps stay shut
  3. 03It won’t type your secrets
  4. 04Nothing connects without your tap
  5. 05Logins come back to you
  6. 06One gate, no side doors
  7. 07It asks instead of guessing
  8. 08You choose where it thinks
  9. 09Everything is logged
SensitivePolicy · the gate1 / 9
incoming from AURA agent
tap {"som_id": 4}
PAUSED
you’re driving now
You outrank the AI
Tap Pause and it stops. Take over and it waits.

Honest limits. AURA uses Android’s accessibility service, the same permission a screen reader uses, and only while running a task you asked for. AI can still misread a screen, so review anything that spends money or can’t be undone.

Read the policy yourself SensitivePolicy.kt

Connect your AI in four steps.

ClaudeCursorVS CodeAny MCP app

The same steps the AURA app shows on its MCP screen. Several AI apps can use the phone at once. Screen and taps travel directly, encrypted end to end; phone and computer need the same Wi-Fi, for now.

  1. Step 1 · one time

    Install the connector (Node.js 18 or newer)

    npm install -g aura-mcp-connect
  2. Step 2 · one time

    Pair this phone with the code AURA shows

    aura-mcp pair <PIN>

    The code works once, for 5 minutes.

  3. Step 3 · one time

    Add AURA to your AI app’s MCP config

    {
      "mcpServers": {
        "aura": { "command": "aura-mcp", "args": [] }
      }
    }

    Claude Desktop: Settings → Developer → Edit Config. On Windows, if AURA doesn’t appear, use "command": "cmd", "args": ["/c", "aura-mcp"].

  4. Step 4 · one time

    Approve on the phone

    Restart your AI app and ask “What’s on my phone screen?” The phone asks “Approve this computer?” Tap Approve once.

This is early and built by one person, so the connection can break sometimes. If it does, open an issue with the run log.

~/your-laptop
$ npm install -g aura-mcp-connect
 
$ aura-mcp pair 482913
 
{ "mcpServers": { "aura": { "command": "aura-mcp", "args": [] } } }
 
> What's on my phone screen?

Sideload it in five minutes.

Free, no account, no subscription. Not on the Play Store yet, so you install the APK yourself.

1

Download the APK

On your Android phone, not your computer.

Tap “Get AURA”

2

Allow installs from your browser

Android asks once. Switch it off after.

Settings › Install unknown apps

3

Play Protect warns? Install anyway

It flags unknown developers, not malware.

More details › Install anyway

4most missed

Allow restricted settings

Android 13+. The step Android hides, and the one everyone misses.

Apps › AURA › ⋮ › Allow restricted settings

5

Open AURA and follow setup

It walks you through each permission, one screen at a time.

Mic · bubble · accessibility · keyboard

→

Full install guide

Your phone brand’s extra switches, every permission, and how to verify the file.

Launch film · 4:25 · with sound

The Barrier Is Down.

What AURA is and what it does, on a real phone.

The things people ask first.

Does AURA watch my screen all the time?

No. It reads the screen only while doing something you asked for, and stops when the task ends. The numbered screenshot and element list go to the AI model you chose, whether that’s a cloud provider or a model you run yourself. AURA itself has no backend and keeps nothing.

What does it cost?

The app is free, with no account and no subscription. Bring your own key from any of 13 providers; Groq and Google Gemini have free tiers. You pay your provider directly, if at all.

Why is the download {{ sizeLabel }}?

The vision models that read your screen ship inside the app instead of on a server. It also carries code for both ARM processor types so one APK works everywhere; per-processor builds are planned.

Why isn’t it on the Play Store?

It’s coming. For now it ships directly so it can improve quickly. The download steps cover every screen, including the one Android hides.

Can I use it to test my own app?

Yes. Connect Claude Code, Cursor or any MCP client, install your build on the phone, and describe the flow in plain English. It checks the screen after every step and logs the run on the phone.

Can it log into websites in its browser?

Yes, when you type the password yourself, and the session stays signed in. Sign in with Google is the exception: Google has blocked its sign-in page inside embedded browsers since 2023, for every app.

Which phones does it work on?

Android 8.0 or newer on ARM. Xiaomi, OPPO, realme, vivo, OnePlus, Samsung, Huawei, Honor, Pixel and Motorola all work, though some brands add permission switches of their own.

Does it update itself?

Not automatically; apps installed outside the Play Store can’t. AURA shows a banner when a new version is out. Updates install over the old app and keep your settings, memory and keys.

Can it work without internet?

Partly. Seeing the screen, the wake word and speaking back work offline. Deciding what to do next needs your AI provider.

Is it stable?

Honestly, not yet. AURA was built by one person and it’s early, so it can break sometimes: some apps trip it up and a run can stall. You can always stop it, and bug reports with the run log help a lot.

What happens if it does the wrong thing?

Stop it any time from the floating bubble or the notification. Every step is logged. It is AI and it can be wrong, so anything irreversible deserves your eyes.

Build android-use with us.

The easiest way in is a skill: one markdown file that teaches AURA a job. Bug reports with the run log attached help more than anything.

Dinesh210805 / aura-android-use
aura-android/mcp-server/The MCP server: tools, safety gate, and the rulebook it gives AIs
aura-android/app/The app: UI, the agent, voice, and the parts that touch the screen
aura-android/app/src/main/assets/skills/Skills. Start here.
aura-mcp-connect/The computer-side bridge that links your AI apps to the phone
scripts/Evaluation and benchmark tools