Claude Cowork Goes Web and Mobile: A Team Rollout Guide

Claude Cowork is leaving the laptop. On July 7, 2026, Anthropic announced on Claude’s blog that Cowork — previously a desktop-app-only product — is expanding to the web at claude.ai and to mobile on iOS and Android, in beta, starting with Max plan subscribers.

The platform expansion is the headline, but it is not the most consequential change. The new surfaces run on a genuinely different execution model: remote sessions hosted on Anthropic’s servers, saved to your Claude account, able to keep working — and to run scheduled tasks — with no device online at all. That is a different mechanic from anything Cowork shipped before, and teams that adopted the earlier phone-to-desktop Dispatch feature can easily mistake one for the other.

If you are new to Cowork itself — Anthropic’s agentic workspace for delegating multi-step knowledge work, live on desktop since January 2026 — the fundamentals of tasks, plugins, and connectors are covered in our Cowork enterprise guide. This post stays on the new ground: the web and mobile surfaces, the cloud-session architecture behind them, what still requires the desktop app, and the two overlapping July promo windows that keep getting merged into one.

The July 7 post — titled “Claude Cowork is coming to mobile and web” and published on claude.com’s blog, not the Anthropic newsroom — confirms the shape of the rollout. Cowork sessions can now start from the claude.ai home screen on the web, and from the sidebar of the Claude app on iOS and Android. Beta access is rolling out over the next several weeks, starting with Max plan subscribers, with more plans to follow. No fixed date exists for non-Max plans, so plan around an open-ended window rather than a calendar entry.

Two quieter changes shipped in the same announcement. First, on web and desktop, Chat and Cowork now share a single home tab, with Projects and artifacts unified across both — a UI consolidation that makes Cowork a first-class mode rather than a separate app experience. Second, Anthropic explicitly names a new audience: users who couldn’t install a desktop app — think IT-locked-down corporate machines with no admin rights — can now use Cowork through the browser.

The most important sentence in the entire launch is not in the blog post — it’s in the Help Center article that accompanies it. It defines what a remote session actually is, and it is worth reading precisely, because it is not “your desktop keeps running in the background.”

The downstream consequence is the launch’s most quotable line: “Close the laptop and head to your meeting; Claude keeps going. Scheduled tasks now run with no device online.” Until this release, some form of powered-on hardware sat underneath every Cowork execution. Now a recurring scheduled task can fire at 6am with every device in the house asleep. The worked example in Anthropic’s own post is exactly that: a 6am task works through email threads, transcripts, and recent news, builds a briefing document, and leaves the follow-up email drafted but unsent for human review over coffee.

“Drafted but unsent” is the load-bearing phrase. Human approval remains a hard gate — the post is explicit that nothing ships until you’ve reviewed and approved it, and when Claude hits a decision only a human can make, the question reaches your phone. Cross-device handoff is likewise a defined product behavior, not marketing garnish: remote sessions follow your account, so you can switch surfaces mid-task, and a push notification lands when Claude finishes or needs input.

Here is the confusion this post exists to prevent. Cowork already had a “work from your phone” story before July 7: Dispatch’s phone-controls-desktop model, which lets you assign tasks from anywhere — by remote-controlling a specific desktop machine. Per Claude’s Help Center, a Dispatch task executes only if that desktop stays awake with the Claude Desktop app open, because the work runs on the local machine, not in Anthropic’s cloud.

The new web/mobile remote sessions invert that: execution happens on Anthropic’s servers, sessions and files live in your Claude account, and no device needs to be powered on. A team member who has used Dispatch will reasonably assume the new mobile experience is “the same thing, but easier.” It isn’t — it’s an architecturally different execution model, and no source suggests the new sessions replace or deprecate Dispatch. They coexist. The table below is our own side-by-side; to our knowledge neither Anthropic’s materials nor the launch coverage puts these two mechanics next to each other.

Anthropic is candid that desktop remains “the full Cowork experience.” The Help Center’s own comparison table marks local file access, browser use, and computer use with an asterisk on web and mobile — fully native only on the desktop app — and lists live artifacts as the one capability unavailable on both new surfaces. The same article notes that some capabilities need the desktop app open on your machine even when the session itself is remote, covering work that has to reach your local computer.

The practical read for a team: treat web and mobile as the surfaces for account-bound knowledge work — documents, research, briefings, connector-driven workflows — and keep desktop in the loop wherever a workflow genuinely touches local files or drives a browser. One more compatibility note that matters during July specifically: per Anthropic’s support article, using the Fable 5 model inside Cowork requires the latest version of Claude Desktop. A team standardizing on the web surface should know that constraint before assuming every model works everywhere.

July 2026 has two Claude promotions running at once, and nearly every outlet covering the Cowork launch reported “doubled usage limits through August 5” without explaining what, exactly, is doubled. To be precise: the Cowork usage promotion and the Fable 5 promotional access are separate offers with different scopes, different eligible surfaces, and different end dates. An operations lead who conflates them will misplan capacity in both directions.

The Cowork promotion doubles only the 5-hour usage limit inside Claude Cowork specifically. Anthropic’s support article is unambiguous: “The 2x usage increase applies to Claude Cowork only. Usage limits for other Claude products, like Claude (web, desktop, and mobile) and Claude Code, are unchanged.” Weekly limits are untouched. The window is documented as June 5 through August 5, 2026 (11:59 PM PT), covers Pro, Max, Team, and legacy seat-based Enterprise plans — excluding Free plans and consumption-based Enterprise seats — and applies automatically, no action needed.

The Fable 5 promotional access is a different lever entirely: eligible users can spend up to 50% of their weekly subscription limits on the Fable 5 model at no extra cost, across Claude web, mobile, and desktop, Cowork, Claude Code, Design, Microsoft 365, Teams, and Tag — plus a separate 50% increase to Claude Code weekly usage limits. That promo runs through July 19, 2026 (11:59:59 PM PT), extended for a second time on July 13. We covered the planning-whiplash side of that story in the separate Fable 5 promo window, extended again through July 19. One offer doubles Cowork session limits until August 5; the other grants Fable 5 model access and a Claude Code bump until July 19 — they share nothing but a calendar month.

Why is Anthropic pushing Cowork onto phones and browsers at all? The launch post answers with its own usage analysis: over 90% of Cowork usage is not software development — it’s everyday knowledge work — and business operations plus content creation together make up roughly half of all usage. The granular numbers come from press coverage rather than the claude.com post itself: TestingCatalog and TechCrunch, reading the same underlying dataset — an analysis of 1.2 million sessions across more than 600,000 organizations, dated to May 2026 — both report business process operations at 33.4%, content creation and copywriting at 16.4%, and software development at just 8.7%.

Our read: that distribution explains the entire roadmap. If nine in ten Cowork sessions are business operations, content, research, and admin work rather than coding, then the product’s natural home is wherever knowledge workers already are — the browser tab and the phone — not a developer-grade desktop install. TechCrunch frames the competitive stakes the same way, citing OpenAI’s Codex evolving from a software-dev tool toward reports, spreadsheets, presentations, and research, and noting Anthropic’s June 2026 launch of the Slack-integrated Claude Tag as part of the same beyond-coding push. The agentic-AI land grab has moved from the IDE to the office suite.

One adjacent stat deserves a careful frame: an Anthropic-cited 2026 workplace survey, reported by PYMNTS, found 81% of Claude users rate AI as “essential” or “significantly enhancing” to their productivity — ahead of rival assistants on that perceived-value measure. Treat that as vendor-adjacent survey data, not an independently audited benchmark; it signals how Anthropic is positioning Cowork, not a neutral market measurement.

A useful rollout plan starts from what is confirmed. Max subscribers get the beta first; everyone else follows over several weeks on no announced schedule. Remote sessions are account-bound and cloud-executed, with human approval gating anything that ships. And — important for governance planning — no source in Anthropic’s launch materials confirms admin controls specific to the new web and mobile surfaces, so if your rollout depends on centrally restricting them, verify what your plan’s admin console actually exposes before promising it internally. Until then, treat rollout discipline as a policy-and-training exercise: customizing Cowork for your team — instructions, connectors, and shared conventions — is the lever you demonstrably control today.

Looking forward, the projection we’d plan around: cloud-hosted sessions become the default Cowork mechanic, with the desktop app repositioned as the power-user surface for local-machine work — the same trajectory web-first office software followed a decade ago. Teams that establish approval conventions, connector hygiene, and per-surface expectations now will absorb the plan-by-plan beta expansion without churn; teams that wait for general availability will do the same work under deadline pressure. If you want help designing that rollout — from workflow audit to per-team configuration and usage governance — our AI transformation engagements start with exactly this kind of adoption planning.