Claude Cowork Comes to Mobile and Web: Complete 2026 Guide
Claude Cowork now runs on iPhone, Android, and the web — not just desktop. Here's how the cloud-hosted beta works, what changed, and how to use it.
Claude Cowork Comes to Mobile and Web: Complete 2026 Guide
For three months, Claude Cowork only lived on your desktop. Start a task on your Mac, and if you left your desk, the task waited for you to come back. That changed the week of July 7, 2026: Anthropic moved Cowork to the cloud and shipped it to iOS, Android, and the web, so a session you start at your desk keeps running whether or not your laptop is open — and you can check on it, approve a step, or grab the finished output from your phone.
This is a bigger architectural shift than it sounds. Cowork was built on Claude Code's agentic engine, which historically needed a machine to run on. Cloud-hosted sessions mean Anthropic now runs that execution loop server-side, which is also what makes background processing and no-device-online scheduled tasks possible. If you've been waiting to bring Cowork into a real workflow instead of a desktop-only experiment, this release is the one that matters.
What Actually Changed
Anthropic's July 7 rollout added three concrete capabilities to Cowork, all currently in beta and starting with Max plan subscribers before expanding to other tiers:
1. Cross-device continuity. Sessions and files now live with your Claude account in the cloud instead of being tied to one machine. Start a task on the web at claude.ai, check progress from the Cowork tab in the iOS or Android app, and open the finished files back on desktop — no manual syncing, no re-uploading. 2. True background execution. Close the laptop, leave your desk, or lose your wifi — the session keeps running on Anthropic's infrastructure. Previously, closing the Cowork window on desktop could interrupt a long-running task. That limitation is gone for cloud-hosted sessions. 3. Scheduled tasks with no device online. You can now schedule a task — say, a Monday 6 a.m. client briefing that pulls from recent emails and news, drafts a summary doc, and leaves a follow-up email ready to send — and it runs even if every device tied to your account is powered off. This is the feature that turns Cowork from "an agent I babysit" into "an agent that works while I sleep."Mobile access itself is new too: previously, Cowork existed only as a desktop app for macOS and Windows. Now you open it from the sidebar of the Claude app on iOS or Android, tap in, describe the task, and it behaves like the desktop version — minus a couple of things covered below.
How to Start Using Claude Cowork on Mobile or Web
If you already use Claude Cowork on desktop, the workflow will feel familiar. Here's the setup:
What's Still Desktop-Only
Not everything moved to the cloud. Two capabilities remain tied to the desktop app specifically:
- Live artifacts — real-time rendered outputs (interactive documents, live previews) currently only render properly in the desktop client.
- Plugins with local MCP servers — if your Cowork setup connects to Model Context Protocol servers running on your own machine (a local database, an internal tool), that connection requires the desktop app to have local network access. Cloud-hosted mobile and web sessions can't reach a server sitting on your laptop.
If your workflow depends on either of these, keep starting those specific sessions from desktop. Everything else — file work, research, drafting, scheduled background tasks — is fair game from any surface.
Why This Matters Beyond the Feature List
The desktop-only constraint was the biggest practical objection to using Cowork for real work: agentic tasks that take 20-40 minutes aren't compatible with "must keep your laptop open and connected." Cloud hosting removes that friction entirely, and it puts Cowork in the same category as tools like background CI jobs or cron-scheduled scripts — except the job description is plain English and the output is a finished document, not just a log file.
It also signals where Anthropic is taking the product generally. Claude Code, Claude Cowork, and now scheduled agentic tasks are converging on the same idea: long-running, semi-autonomous agents that you dispatch and check on later, rather than chat interfaces you babysit turn by turn. Anthropic extended doubled Cowork usage limits across paid accounts through August 5, 2026, which suggests they want heavy real-world testing during this window before wider general availability.
Practical Ways to Use the New Cowork
A few workflows that specifically benefit from cross-device, background-capable Cowork:
- Morning briefings. Schedule a task to run before you wake up: scan overnight emails, summarize what needs attention, draft replies to routine requests, and have it ready when you check your phone.
- Research while commuting. Kick off a multi-source research task from your phone on the way to work; by the time you sit down at your desk, the draft report is waiting.
- Long-running document work. Start a large restructuring or audit task on desktop before a meeting, let it run in the background during the meeting, and review the result on your phone afterward without needing to keep your laptop open.
- Team handoffs. Because sessions live in your account rather than on one machine, you can start a task, step away, and someone with access to the same workspace context can pick up where you left off (subject to your org's sharing settings).
Common Questions
Is this available on the Free or Pro plan? Not yet — the beta started with Max subscribers on July 7, 2026, with other plans expected to get access as the rollout continues over the following weeks. Check your Claude app settings for availability. Does background execution cost more? Anthropic has doubled Cowork usage limits for all paid accounts through August 5, 2026, so testing the new cloud features shouldn't hit a usage ceiling faster than before during this window. Can I still use desktop-only Cowork the way I did before? Yes — desktop Cowork continues to work exactly as it did, and is still required for live artifacts and local MCP server plugins. What happens to a session if I lose internet on my phone mid-task? Because execution happens server-side, the task keeps running on Anthropic's infrastructure regardless of your device's connection. You'll see the completed state next time you reconnect. How is this different from just using Claude Code remotely? Claude Code is built for developers working inside a codebase — it expects a terminal, a repo, and command-line tools. Cowork targets knowledge-work tasks: documents, spreadsheets, email, browser-based research. The cloud hosting update brings Cowork's mobile experience closer to what Claude Code users already get with remote/cloud sessions, but the target task shape is different. If you're debugging a pull request, Claude Code is still the right tool; if you're prepping a client brief or triaging an inbox, Cowork is built for that. Does this replace Claude Projects? No — Projects are a persistent knowledge container (files, instructions, context you reuse across chats). Cowork is the execution layer that acts on that context. You can point a Cowork session at a Project's files and have it work through them autonomously; the cloud update just means that session isn't tied to a single device anymore.How This Compares to Competing Agent Products
The move to cloud-hosted, cross-device agent sessions isn't happening in a vacuum. OpenAI's ChatGPT Tasks and various third-party "AI employee" tools have experimented with scheduled, backgrounded execution, but most stop at simple reminders or single-step actions. What distinguishes Cowork's cloud update is the combination of three things at once: full multi-step agentic execution (not just a scheduled prompt), genuine cross-device state (not just a synced chat log), and mobile-native approval flows for actions that need a human in the loop. For teams evaluating whether to standardize on Claude versus a competing agent platform, the ability to dispatch a task from a laptop and approve a sensitive step from a phone — without losing session state — is a meaningful differentiator worth testing during the extended usage window through August 5.
Key Takeaways
- Claude Cowork moved from desktop-only to cloud-hosted, with iOS, Android, and web access rolling out starting July 7, 2026.
- The beta starts with Max plan subscribers; other plans follow over the coming weeks.
- Background execution and no-device-online scheduled tasks are the headline capabilities — sessions now survive your laptop closing.
- Live artifacts and local MCP server plugins remain desktop-only for now.
- Doubled usage limits run through August 5, 2026, making this a good window to stress-test the feature.
Next Steps
If you're prepping for the Claude Certified Architect (CCA) exam or building agentic Claude workflows professionally, understanding how Cowork's execution model works — desktop vs. cloud, synchronous vs. scheduled — is exactly the kind of architecture question that shows up in certification scenarios. Check out AI for Anything's CCA practice test bank to test your understanding of Claude's agent architecture, or browse our free study guides on building with Claude's agentic tools.
Ready to Start Practicing?
300+ scenario-based practice questions covering all 5 CCA domains. Detailed explanations for every answer.
Free CCA Study Kit
Get domain cheat sheets, anti-pattern flashcards, and weekly exam tips. No spam, unsubscribe anytime.