Bring an Android device
Install Talos, connect an authorized emulator or phone through ADB, and configure your Claude API key or custom model endpoint.
Talos · AI agent for Android automation
Describe the task.
Let Talos work through Android.
Talos is a desktop automation agent that controls Android devices connected to your computer through ADB. Give it natural-language goals to automate phones and emulators you own or are authorized to control.
Self-hosted · Windows & Linux · Your AI provider
No card required for the licence trial. AI usage billed separately.
Your goal
“In Contacts, add Alex Morgan with the number 5550100. Confirm the saved contact appears in the list.”
- 01Open the contact form
Success: name and phone fields are visible.
- 02Enter the contact details
Success: the fields show Alex Morgan and 5550100.
- 03Save and check the result
Success: Alex Morgan appears in Contacts.
40 iterations15 minutes$0.50 budget threshold
Illustrative task definition, not a recorded run. The final model call can exceed the budget threshold.
Android emulators & physical phonesGoals + visible success criteriaRun history you can inspect
What is Talos?
An AI operator for your Android workflows.
Repeating the same app journey by hand takes attention. Writing a script for every variation takes maintenance. Talos lets you define the outcome and have an agent choose actions from the current screen.
Your dashboard runs on your own machine and controls Android through ADB. Task context and screen observations go to the AI provider you configure.
Explore Android emulator automation →
How it works
Connect. Describe. Run and review.
Start with one app and one observable result.
Tell the agent what success looks like
Select a device and describe the goal. Add context, optional milestones and limits. Choose a one-time or continuous task.
Start the task and inspect the result
Watch the device preview and open the run timeline to see what the agent observed, which actions it took and how the run ended.
Key features
From a goal to a run you can inspect.
Define the outcome in plain language
Describe the goal and add optional milestones. Give each milestone a visible success criterion, or ask Claude to suggest the stages.
Act on the interface in front of you
The agent reads UI elements and screenshots, then taps, scrolls, types, opens apps and checks what changed.
Run once or keep a workflow going
Repeat successful cycles with a configurable pause and a summary carried into the next cycle. Stop the task from the dashboard.
Understand what happened
Inspect the last 10 runs per task, with observations, actions, results, model explanations, token usage and available screen captures.
Set limits before you start
Control iterations, runtime and an estimated budget threshold for each run or cycle. Errors and reached limits stop continuous tasks.
Use your devices and model provider
Manage ADB-connected Android emulators and phones from a self-hosted dashboard. Use Claude or a compatible custom HTTP endpoint.
Who is it for?
Less repetition for developers, QA and technical operators.
Use it where the work happens inside an Android interface.
Developers
Prepare app state for a demo
Create a test contact or adjust a visible setting through a goal-driven task, then verify the final screen before you begin.
QA & app teams
Exercise a multi-screen journey
Describe an app flow with visible checkpoints. Review where the agent succeeded or got stuck, with a timeline to investigate.
Technical operators
Repeat a UI-based workflow
Run successful cycles with a pause and context from the previous cycle. Keep the task under review and stop it when needed.
Why Talos?
Define intent. Let the agent decide the next action.
Talos can reduce the action scripting needed for goal-driven tasks. Its screen-based decisions also need evaluation on your app. Use it alongside the checks that already work for your team.
| 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 and token usage 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. |
Before you start
Questions, answered.
What is Talos?
Talos is a self-hosted AI agent for Android emulator and phone automation. You describe a goal, optionally add milestones with visible success criteria, and let the agent observe the interface and choose actions through ADB.
Which emulators and devices can I use?
Talos connects to Android devices exposed through ADB, including Android emulators and USB-debugging-enabled phones. The device must be online, authorized and unlocked. Check that your emulator appears in adb devices before trying a workflow. iOS is not supported.
Do I need to write scripts or install Appium?
You can define tasks in natural language without writing an action script. Talos uses ADB, UI observations and screenshots; Appium is not required. Clear goals and observable success criteria still matter, and each workflow needs to be tried on your app.
Is AI usage included in the licence?
No. Claude requires your own Anthropic API key and is billed separately by the provider. You can also connect an HTTP endpoint that implements the Talos custom-provider protocol. Talos does not calculate charges for custom endpoints.
Can I control how long an agent runs?
Set iteration, time and estimated USD budget limits, and stop a task from the dashboard. The budget is checked after model responses, so the final call can exceed the threshold. Continuous tasks apply limits per cycle; costs add up across cycles. Errors, cancellation or a reached limit stop the task.
What data leaves my machine?
The dashboard, task definitions and run history are stored on your host. The configured AI provider receives the task context, UI observations and screenshots used for decisions. Licensed installations also contact the licence server. Self-hosting does not mean all processing happens offline.
Can Talos replace my Android test suite?
Talos can help exercise visible app journeys and collect an inspectable run history. Agent decisions can vary and success is evaluated from the screen. Keep deterministic tests for exact assertions, repeatable regression checks and release gates.
Can it repeat a task automatically?
Yes. Continuous tasks repeat successful cycles after a configurable delay and pass a summary into the next cycle. This is model-generated context, not an exact event ledger. Try the workflow on your target app and review actions that must not be duplicated.
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.
No card required for the licence trial. AI usage is billed separately.