How is "assign tasks from anywhere" different from the mobile task queue people imagine?
Why does Cowork implement cross-device access as a single thread rather than multiple threads?
Mechanically, how does the single-thread system actually work?
What's the practical impact on someone who wants to use their phone as a task inbox?
"Assign tasks from anywhere" sounds like it hands you a task queue: fire off three tasks from your phone during your commute, two more at lunch, then sit down at your desktop in the evening and harvest the results. Anyone who actually tries this quickly discovers that's not how it works.
The actual mechanism behind this feature is that you and Claude maintain a single, persistent conversation that syncs across phone and desktop. You message from your phone, Claude figures out whether it's a dev task or general knowledge work — dev work goes to Claude Code, knowledge work goes to Cowork — then runs it in the background, pushing a notification when it needs your approval or finishes. You can check the result on your phone, or sit back down at your desktop and keep going in that same thread.
That already sounds convenient, but one line in the official docs is easy to overlook: there's currently no way to start a new thread or manage multiple threads — all messages live in a single conversation. So if you fire off Task A in the morning and want to send an unrelated Task B at lunch, B doesn't become an independent new task — it gets folded into the same thread as A. Claude sees the same shared context, and when you scroll back through the history yourself, A and B end up tangled together.
For someone who occasionally fires off one or two things from their phone, this limitation barely registers. It bites the people trying to use Cowork's mobile side as a "task inbox" — assigning three or four unrelated errands over the course of a day: clean up a weekly report, look up a competitor, tweak a bit of code. If all of that gets crammed into one thread, by the time Claude works on the third item, the context is muddied with the first two, and it can genuinely misread what you're asking it to do right now.
Two other easily-overlooked preconditions make the feature look "broken" when it's actually working as designed. First, desktop-side work requires the computer to "stay awake and the Claude Desktop app open" — once the machine sleeps or the app closes, the task pauses rather than quietly continuing in the background. Second, the underlying technology, Dispatch, isn't currently available to new users — only people who were already using it can keep using it. If you're on a newly created account, you might follow the instructions to the letter and still find the feature simply isn't in your interface.
Treating this feature as "extending the same task's conversation" rather than "a mobile task manager" avoids most of the pitfalls. If you have a genuinely new, independent task to hand off from your phone, the safer move is to confirm the previous task has wrapped up — or at least won't collide context with the new one — before you start describing it. If you actually need to run several unrelated pieces of work in parallel, this cross-device feature currently can't do that; opening separate Cowork sessions on desktop is still the more practical approach.
Worth noting: computer-use functionality is unsupported on Linux systems, though tasks involving File Access and connectors aren't affected — another platform difference worth checking before you decide how much you can actually delegate from your phone. The more fundamental fix is resetting your expectations for this feature: rather than treating your phone as a console that manages several task lines at once, treat it as an extension handle for continuing whatever the office desktop is already doing. When you genuinely need to push several unrelated pieces of work forward at the same time, opening separate Cowork sessions on desktop remains the more reliable approach.