Explore with AI, replay without a model

Give an AI task a goal once. When it has found its way, save what it did as a workflow. The workflow then does the same thing on any phone, as often as you like, with no AI model: no model cost, no waiting for answers, and the same steps every time.

This is part of the Pro and Team plans. Running the AI task itself needs a model (AI with your own model).

How to do it

1. Run an AI task on a phone (Runs → AI task…, or a phone's agent) and let it finish.
2. Open the task on the Runs page. At the end of its transcript, choose Save as workflow….
3. Check the proposal:
   • Steps: what the workflow will do, in order. A step marked review needs a look, for example a tap at a screen position because nothing on the screen had a name.
   • a person takes over: where the task met a check only a person may pass (a CAPTCHA, a sign-in code, a fingerprint prompt), or where the AI asked for a person. The workflow stops there and waits for a person.
   • Inputs: what the AI typed. Each becomes an input of the workflow, with what it typed as the default value.
   • Secrets from the vault: passwords the AI typed from the vault, by name. Their values are never in the workflow.
   • Left out: what the AI tried that did not work, what it only looked at, and dead ends.
4. Give the workflow an ID and a name, then Save as a draft. The draft opens in the workflow editor.
5. Look it over, try it with Test run if you like, and Publish it. From then on it runs like any other workflow: on one phone, a group or every phone, on a schedule or from CI.

What it keeps and what it leaves out

• The elements, not the screen positions. Each tap, long press and scroll names the element the AI used (its ID, label or text), as the recorder does, so the workflow still works on another screen size.
• Waits. After a tap, a long press or Back, the workflow waits for the next screen before it goes on.
• Checks. When the AI looked for an element or waited for one, the workflow does too, and fails if the element is not there. A value the AI read and reported, such as a balance or a version, becomes an output of the workflow.
• Dead ends are left out. If the AI opened the wrong screen and went back, those steps are dropped. Tick Keep the steps it went back from if that screen did something you need, such as adding an item to a cart.
• Approvals stay. If a person had to approve a step during the task, the workflow asks a person again before that step.

Safety

The workflow goes through the same checks as every other workflow: the phone must be in Auto mode, checks only a person may pass are never automated, and every action is in the audit log. A simulated task cannot be saved, because nothing it did was carried out.

When a task cannot be saved

• It did not finish. Only a task that succeeded, or that stopped for a person, can be saved.
• There is nothing to save. The task took no action or ran as a simulation.
• It is too old. Tasks can be saved for 30 days.
• The ID is taken. Choose another workflow ID; saving never overwrites a workflow.

Related: AI agents per phone, Workflows and schedules.