Automation overview
Last updated:Nov 13, 2026
yunyoo offers a few ways to automate, each suited to different work:
| Way | Good for | Where |
|---|---|---|
| Desktop automation tasks | Running a set of actions by hand or on a schedule, without code | Desktop app only |
| Command-line tool | Operating cloud phones from a terminal or script, running several steps at once and flow macros | Your computer |
| MCP | Letting an AI assistant operate cloud phones in plain language | Any AI assistant that supports MCP |
Desktop automation tasks
In the desktop app, open Automation in the sidebar and click New task. A task is a set of actions that runs by hand or on a schedule, using this computer's time. The desktop app has to be running for scheduled runs, and missed runs are not made up. You can also record steps in the viewer to turn them into a task's actions. The desktop app also offers a local API so scripts, the command line and AI assistants on this computer can work on devices through it; see Local API and desktop tasks.
Command-line tool and MCP
Once signed in with a machine token, the yunyoo command-line tool can pick a cloud phone, read its screen, tap and type, manage apps and files, power devices on and off, and make backups. It can also submit several steps at once and run your routines again and again as flow macros. It can run as an MCP server so AI assistants can connect, with the same abilities, and AI assistants can also connect to the remote endpoint without installing anything. For installation and usage, see Command-line tool and MCP.
Programs you write yourself should go through the command line or MCP: the platform's automation API requires request signatures, and the signing method isn't published. The endpoints are listed in the Automation API reference.
Approvals and run records
Clearing app data, uninstalling apps, running commands, and other high-risk steps such as payments, messages or account changes may need your approval. Automation stops and waits at such a step, you get an inbox notification, and the desktop app (1.1.0 and later) also shows a system notification when its window isn't in front. Approve or decline under Confirmations and reports in Automation; an approved step runs only once. The run records in the same place list every step automation took.
When it reaches payment, sign-in, a captcha or another screen only you should handle, automation can ask you to take over. You can also take over a device in the viewer at any time; automation actions are refused while you have control and resume after you click Hand back.
Issue a machine token
From the avatar menu, open Account settings, go to the Automation tab and click Create token. Fill in:
- a name;
- scopes: six are ticked by default — Observe, UI actions, Apps, Files, Lifecycle and Backups;
- Cloud phone scope: all, one group or specific environments;
- Expires: 7, 30, 90 or 365 days, or never; 30 days by default.
Tokens start with wpa_ and are shown in full only once, so save yours right away. You can later Rotate it, and the old token keeps working for a short grace period, or Revoke it, which stops any script using it at once.
Run command and Local bridge are escape hatches and are not granted by default. The first can run any command inside a cloud phone; the second bridges a port on your computer into the cloud phone. Ticking them shows a warning, creating the token asks you to confirm again, and their use is audited.
A token's scopes never go beyond your own permissions. If you can't see the Automation tab or create a token, your role does not have the Machine tokens permission.
Result codes when a step does not succeed
When a tap, typing or a wait run from the command line or an AI assistant does not succeed, it returns a result code. The command line puts it in error_code in the result and ends with exit code 3; an AI assistant gets an error carrying the number.
| Result code | Meaning | What to do |
|---|---|---|
| 1001 | The element is no longer on the screen | Read the screen again and retry with the new element number |
| 1002 | No element matched | Check the text, description or resource ID, or read the screen first and then pick the element |
| 1003 | The wait timed out | Look at what the screen shows now and retry; one wait lasts 30 seconds at most, so wait again if you need longer |
| 1004 | This cloud phone does not support the action, for example typing non-ASCII text | Do it another way; the automation status lists what the phone supports |
| 1005 | Typing did not go through | Try again shortly |
| 1007 | The cloud phone is not running, or is starting or stopping | Retry once it is running |
| 1008 | One element number matches several elements on the screen | Pick the element by text, description or resource ID instead; the result lists the candidates |
These numbers are used only for the results of automation steps. They are a different set from the error codes shown in the web console and the desktop app.
