Working from your phone
Start a task on the way to work, read the result at your desk. The catch is where the work runs, and that depends on what it touches.
Cowork is on desktop, on the web and on mobile, and a session follows you between them. What changes is not the interface, it is what each surface can reach.
| Desktop | Web and mobile | |
|---|---|---|
| Where the work runs | Cloud by default | Cloud |
| Local files | Yes, folders you connected | Only while the desktop app is open on that computer |
| Browser and computer use | Yes | Only through the desktop app, and it must be open |
| Scheduled tasks | Yes | Yes |
So a task on cloud-stored files can be started from your phone and finished while your laptop is shut. A task on a folder on that laptop needs the laptop awake and the desktop app open.
Dispatching from the phone
Send the job the way you would send a message. It uses the connectors and skills you already set up, so there is nothing separate to configure on mobile. The requirement is the one above: if it needs your machine, your machine has to be awake with the app open.
What phone work is actually good for
- Starting a long job before you are at your desk.
- Answering an approval that is holding a task up.
- Reading what came back and deciding whether it needs another pass.
What it is not good for is writing the brief. A good brief is five things long and editing it on a phone is how details go missing, which is another argument for skills and projects: they are where the detail lives, so the message can be short.
- Start your recurring job from your phone and see whether it needs your laptop.
- If it does, ask whether the input could live somewhere the cloud can reach.
This is what real progress feels like.