Android emulator automation

An AI agent that works through your Android interface.

Talos connects to Android through ADB. Give it a goal and it uses UI elements and screenshots to decide where to tap, what to type and when a visible checkpoint is complete.

Try Talos Check setup requirements

What can the agent do?

Tap or long-press elements, swipe and scroll, enter or clear text, press Android navigation keys, open apps by package name, read screen text and wait for text to appear. Text with accented letters or other non-ASCII characters is pasted through the on-device helper (Android 7 or later).

The observation → action → verification loop lets the agent choose a next step from the current interface. You do not have to specify every action in advance. The screen size is read from the current interface, so rotated screens and resolution overrides are taken into account.

Which emulators are compatible?

ADB connectivity is the starting point. Start your Android emulator and confirm it appears as an online device in adb devices. Physical Android phones also work when USB debugging is enabled and authorized.

There is no verified compatibility matrix for specific third-party emulator brands. App behavior, Android version and UI accessibility affect results. Talos does not control iOS simulators.

Your host. Your devices.

One workspace for connected Android devices.

Run Talos on Windows, Linux or a 64-bit Raspberry Pi and open its password-protected browser dashboard. View detected devices, assign one or more tasks to each of them, and watch or control the current screen without starting a task.

ADB is required; if it is not on the PATH, point Talos to it in the configuration. FFmpeg is optional for live streaming. Use your own API key for Claude, OpenAI, Google Gemini or OpenRouter, or a custom HTTP endpoint that implements the Talos protocol — a generic chat endpoint is not automatically compatible.

View available Windows and Linux builds →

Talos device page with an open live screen preview of a connected Samsung Android phone. — Preview a connected phone from the device workspace.

When screen-aware automation helps

Use goal-driven interaction for app setup, repeated form entry and exploratory journeys where describing a result is easier than maintaining every UI action.

The agent can react to current labels and screen content, but this is not a guarantee that every dynamic UI will work. Test your app and use observable milestones. Talos wakes the screen before a run; a lock screen with a PIN, pattern or password must be unlocked by you, otherwise the run is skipped without calling the model.

Explore concrete Android workflow examples →

Choose the right tool for the job
Your workflow	Scripted UI automation	Talos AI agent
Define the task	Write an action sequence and assertions.	Describe a goal and visible success criteria.
Respond to the screen	Use selectors and branches you maintain.	Choose the next action from the current UI and screenshots.
Investigate a run	Inspect the logs and captures your framework provides.	Review observations, actions, results, screenshots, tokens and cost in one timeline.
Best fit	Exact assertions and repeatable regression gates.	Goal-driven app interaction, setup tasks and exploratory workflow checks.
Trade-off	Upfront scripting and maintenance.	Model latency, provider costs and decisions that can vary.

Understand the boundaries before scaling up.

AI decisions can vary and model calls add latency and cost. Talos is useful for visible interaction; it does not provide deterministic test assertions, a built-in CI test runner or guaranteed completion on every app.

The dashboard and run history stay on your host, while observations and relevant screenshots are sent to your selected model provider. Licensed installations check the licence online; a running installation keeps working through licence-server outages of up to 72 hours.

Start with a single emulator and review the timeline. For continuous tasks, set per-cycle limits and a daily budget, and remember that costs accumulate across cycles.

Start with one workflow

Give your next repetitive Android task to Talos.

Try it on your own emulator or phone. Bring an ADB connection, a clear goal and your model provider.

Get a free trial key Read the setup guide

No card required for the licence trial. AI usage is billed separately.