Testing your own app on real phones, including flows that cross into other apps, such as a login with a code from a text message.
A shelf of phones running the same routine every day, each through its own network or proxy.
Android automation from code. Test your apps on real phones, script the tasks you repeat, run a shelf of phones, or let an AI agent use one, from Python, Node.js, the CLI, HTTP or Appium clients. No ADB, no USB cable, no root.
2026-10-27
Estrellas
335
Herramientas
—
Disponibilidad
—
Giving an AI agent hands: through MCP, Claude, ChatGPT, Cursor and other agents can look at a phone screen and act on it.
Small personal automations, such as turning Wi-Fi off at night or collecting a value from an app every hour.
Droidline uses only permissions an ordinary app can get, so a few things are out of reach: see What it cannot do.
See it in action
Quick start
You need a PC (Windows, macOS or Linux) and an Android phone with Android 9 or later, on the same Wi-Fi for a first try. The installation guide walks through each step with screenshots.
Run the server on your PC. Download the droidline archive for your system from Releases, put droidline on your PATH, and start it. Leave it running.
droidline serve
Install the app on the phone. Download droidline-agent.apk from the same release page and open it. On the app's Setup tab, turn on the accessibility service, the Droidline keyboard, notifications and unrestricted battery use. On Android 13 and later, allow restricted settings for the app first; the app shows where.
Pair them. Run this on the PC and scan the QR code with the app's Pair tab:
droidline pair
No camera? Tap Pair on this Wi-Fi in the app and type the 6-digit code it shows: droidline pair 482913.
Send a command.
droidline launch com.android.settings
droidline touch text "Network & internet"
No phone at hand? droidline-fakephone, included in every release, simulates one with a small demo app. The first-script tutorial builds a complete login script against it.
Use it from your language
Every interface talks to droidline serve on localhost:8780 and uses the same command names.
Python (pip install droidline, Python 3.9+)
from droidline import connect
d = connect() # the phone paired with this PC
d.launch("dev.droidline.demo")
if d.exists("text", "Close ad"): # conditions never wait and never fail
d.touch("text", "Close ad")
d.input("id", "email", "knife") # waits up to 10 s for the element
d.touch("text", "Log in")
print(d.get_text("id", "greeting"))
Node.js and TypeScript (npm install droidline, Node.js 18+)
With Claude Code: claude mcp add droidline -- droidline mcp. In Claude Desktop you can instead open droidline.mcpb from Releases, which carries its own droidline; it is also listed in the MCP Registry as io.github.KnifeLemon/droidline. To give an agent fewer tools, add --tools dump,screenshot,touch or --read-only to the args; see Limit what an agent can use. Other languages can open a TCP socket and send one JSON line per command; see Other languages for Go, Java and PHP.
Features
Pick the element, not the pixel.dump() returns the screen as a tree with text, id and desc for every element. Commands take the field and the value: touch("id", "login"). When an element refuses a click, Droidline taps its parent or the center of its bounds by itself.
Waiting is built in.touch, input and wait wait for their element, 10 seconds by default. Conditions such as exists, checked and which answer at once and never throw for a missing element.
Clear errors. Every failure has a code, a message in English, Korean or Chinese, and a flag that says whether retrying helps: NOT_FOUND: Could not find text 'Log in' within 10s. Current screen: com.example / .MainActivity.
A shelf of phones. One PC drives many phones. Commands to one phone run in order, different phones run in parallel, and each phone has a name you choose.
Per-app proxy. Send chosen apps through a socks5 or http upstream with a local VPN, one upstream per phone, without root.
Notifications on the PC. Wait for one, react to every one, reply, open or dismiss it, or forward it to a signed webhook.
New mobile IPs. A batch sent with cuts_network keeps running on the phone while it is offline, so airplane mode on, wait, off works as one call. intent opens the Settings page first; the recipes show it step by step.
Nothing runs twice. A phone that drops off mobile data resumes where it left off; a command that was in flight is answered from the phone's cache, not run again.
Selectors that hold up. Combine conditions or name an element by its neighbors: touch({"class": "android.widget.Switch", "row": {"text": "Wi-Fi"}}). find hands back elements you can click and search inside, and wait_idle waits until the screen stops changing.
Optional tools, off until you start them.droidline inspect shows the screen and its elements, suggests selectors with code, and records a script while you use the phone. droidline webdriver lets Appium clients and scripts drive your phones. There is also a pytest plugin, leases for sharing phones between scripts, and picture and text matching for screens without elements.
English, 한국어, 简体中文 in the app, the error messages and the docs.
Screenshots
Reach phones anywhere
The phone always opens the connection, so it needs no open port. Pick the route that fits your network; the phone tries them in order and returns to Wi-Fi when it can.
Route
You need
How it works
Same Wi-Fi
Nothing
The phone finds the PC with a UDP broadcast and connects directly.
Port forward
One forwarded port
The phone connects to your public address over TLS, pinned to the PC's certificate.
Tunnel
cloudflared, ngrok or similar
Your PC keeps a tunnel open; the phone reaches it through the tunnel's address.
Your relay
Cloudflare Workers or a VPS
PC and phone both connect out to a relay you deploy. It forwards lines it cannot read.
Past the two-line handshake every line is encrypted with keys only your PC and phone hold (P-256 and AES-256-GCM), so a tunnel or relay only carries ciphertext. The remote connection guides cover each route step by step.
What it cannot do
Droidline only uses permissions an ordinary app can get, so some things are out of reach. Better to know before you start:
It cannot open another app's screens that the app does not export. launch opens the start screen instead.
It cannot unlock a PIN, pattern or password lock screen.
There is no single command to force stop an app, clear its data or switch the network. Settings differs by phone maker, Android version and language, so the recipes press its buttons, and you may need to adjust the labels for your phone. In the optional device owner mode, clear_data wipes app data directly.
Games and some custom-drawn apps expose no elements. Use tap with coordinates and color(x, y) there.
Android 15 and later hide one-time codes in notifications from apps. You learn that a code arrived and read it in the app.
Requirements: Go 1.26+, Node.js 22, Python 3.9+, and for the app, JDK 17+ with the Android SDK (Android Studio's bundled JDK works).
git clone https://github.com/KnifeLemon/Droidline.git
cd Droidline
go build ./server/cmd/... # droidline, droidline-relay, droidline-fakephone
go test ./spec/ ./server/...
node scripts/gen.mjs --check # SDK methods match spec/commands.json
cd sdk/python && python -m pytest
cd sdk/node && npm ci && npm test
dotnet test sdk/dotnet
cd agent && ./gradlew assembleDebug testDebugUnitTest
scripts/integration.sh runs the server, the simulated phone and both SDK demos together, which is what CI does.
Pull requests are welcome; CONTRIBUTING.md explains how the spec, generator and tests fit together. The most useful contribution right now is a report from a real phone: which brand and Android version, and whether the Settings recipes for force stop, clearing data and the network switches work with its labels. If Droidline saves you some taps, a ⭐ helps other people find it.
Status
Version 0.1. The server, CLI, MCP adapter, relay and both SDKs pass their tests against the phone simulator, and the app passes its unit tests and runs on an Android 13 emulator. Testing across phone brands is the next step. docs/STATUS.md lists exactly what has been verified and how.
Security and privacy
Pairing decides who may control a phone, and everything after the handshake is encrypted end to end. Report security problems privately as described in SECURITY.md.
Droidline collects no usage data and sends no telemetry. The server listens on your own machine; the app talks only to the PC it is paired with, and to GitHub once a day to check for a new release. Use Droidline on phones and accounts you own or may automate; the terms say what it is for.
Android automation from code. Test your apps on real phones, script the tasks you repeat, run a shelf of phones, or let an AI agent use one, from Python, Node.js, the CLI, HTTP or Appium clients. No A
Android automation from code. Test your apps on real phones, script the tasks you repeat, run a shelf of phones, or let an AI agent use one, from Python, Node.js, the CLI, HTTP or Appium clients. No ADB, no USB cable, no root.
Herramientas
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Preguntas
¿Cómo instalo Droidline?
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
¿Qué transporte usa Droidline?
Droidline se ejecuta localmente por stdio.
¿Cuándo se comprobó Droidline por última vez?
Última comprobación: 2026-10-27. Android automation from code. Test your apps on real phones, script the tasks you repeat, run a shelf of phones, or let an AI agent use one, from Python, Node.js, the CLI, HTTP or Appium clients. No ADB, no USB cable, no root.