# Several devices from one chat

One message, several devices. Silan's lead writes one job per device, one device can wait for a value another finds, and flows carry roles for two or more devices.

Some tasks need two devices: compare an app on an iPhone and an iPad, read a value on one phone and type it on another, or run the same check on every device on the desk at once. In Silan one chat message does that. Silan's lead reads your words and writes one job per device before any device starts. Then one worker agent runs per device, and a worker can wait for a value another worker finds.

## A worked example

You pick an iPhone and an iPad in a new chat and send:

`On the iPad, open Settings, then General, then About, and read the iOS version. On the iPhone, open Settings and type that iOS version in the Settings search field. Change nothing and save nothing.`

Before anything moves, the chat shows the plan: one job for the iPad (read the version) and one for the iPhone (type it), plus a wait: the iPhone's job waits up to 300 seconds for a value named `ios_version` from the iPad. You can edit the jobs, or send a note like `On the iPhone, open Calculator instead`, and the lead writes the plan again. Then you start it.

Two worker cards appear, one per device. The iPad's worker opens Settings and reads the version. The iPhone's worker opens Settings and waits. The moment the iPad shares the value, the iPhone types it. Stop, a message, **Take over** and **Hand back** work per worker, so you can stop one device and let the other finish.

## Steps

1. Set each iPhone or iPad up with the Developer way ([Devices](/devices/)).
2. Open a new chat and pick two or more devices.
3. Type one message. Name the devices by their roles when the jobs differ ("on the iPad", "on the iPhone"), or write one task to run on all of them.
4. Read the plan. Edit a job, or send a note to change it. Then start it.
5. Follow each worker card. Answer an ask card when one shows ([Agent tasks](/features/agent-tasks/)).

For a flow, give it two or more roles. The flow editor asks **Which device?** when you add a step to a two-device flow, and **Run** asks for a device per role ([Flows](/features/flows/)). From your own program, `claim_devices` takes a list of device ids, and one lease covers them all ([claim_devices](/reference/mcp/claim-devices/)).

Several agents can also share one device and take turns: start each with a team name and an agent name, and each one's taps show under a coloured ring on the live picture.

## What is supported today

| What | Status |
|---|---|
| One chat message on an iPhone and an iPad at once, one worker per device | Supported |
| Silan's lead writes one job per device, you edit it or change it with a note | Supported |
| One device waits for a value another device finds | Supported |
| An iPhone and an Android device from one chat | In testing |
| A flow with roles for two or more devices | Supported on simulators and in tests. Not yet proved with two real phones |
| Your own AI app holding several devices through `claim_devices` | Supported in tests. Not yet proved with two real phones |
| Several named agents sharing one device with coloured rings | Supported |

:::note[Proof]
Proved on an iPhone 11 (iOS 27) and an iPad Air together, both on the Developer way, 31 Oct 2026, by Silan workers: a group of two workers from one message, the lead's plan with one job per device and a change by note, and a wait where the iPhone's job used the iOS version the iPad's job read. Not run by the owner. Several agents on one device proved on the iPad Air the same day. Source: verify-silan feature map, agent-tasks (groups, lead, waits, team).
:::