Run your first automation
Prepare a small, explicit job with your AI assistant and monitor it in Titan.
Before starting, you need a connected PC Agent, a ready iPhone, a usable AI adapter, and an assistant connected to Titan through MCP.
Choose the work
Open Strategies. Find a strategy you own or have access to, and note its name and ID. For the first attempt, choose work you can inspect on one phone with one item.
Strategy source authoring, run setup creation, and queue preparation happen through your connected assistant. The Strategies page lets you discover and review available strategies; it does not have a browser Run button.
Ask the assistant to prepare
Use a request like this, replacing the names with yours:
Find the strategy named “My first workflow” and show me its exact ID and available release. Read its run requirements. Use my selected phone and AI adapter, and identify the resources and manual inputs still needed. Prepare one item only. Show me the proposed setup before starting anything.
Have the assistant resolve names to exact records. If several records match, choose the intended one. A reusable run setup saves your choices for a strategy; it is also called a strategy preset in some places.
Review the setup
Check the strategy and version, device, AI adapter, account or other resources, manual inputs, and intended number of items. For a queue, also check the worker devices and any proxy selection.
Your resource selections must be your own records and match the type and version required by the strategy. Sharing a strategy does not supply the author's accounts or credentials.
Start deliberately
Tell the assistant to start the reviewed job. For a prepared Ready queue, you can open it under Queues and choose Play. A draft must first be finalized through MCP; draft details cannot be opened in the browser.
Some MCP operations create and start work together. Make clear whether your request is preparation only or permission to execute.
Check the result
- Open Queues to observe the batch and its workers, or My Runs to inspect a run.
- Review the overall outcome and the recorded attempts.
- Select an attempt to see its actions and available screenshots.
- If it fails, read the first useful error before retrying. Check what the phone already did.
A finished run can contain failed or skipped attempts. Use the reported outcome and evidence to decide whether the job achieved what you intended.
Continue with Queues, Run monitor, or Automation troubleshooting.