Claude Cowork expands to web and mobile with cloud-backed background execution

The headline feature is deceptively mundane and technically significant: you can close your laptop and Claude keeps going. Until this update, Cowork ran on your machine, which meant a task that needed twenty minutes of uninterrupted execution also needed twenty minutes of an awake, connected device ^[1]. The July 7 change moves scheduled tasks into the cloud, so execution is no longer hostage to your Wi-Fi, your battery, or whether you shut the lid to catch a train ^[2].

The more interesting design choice is how the human stays in the loop without staying at the desk. When Claude reaches a point where only a person can make the call - a permission, a judgment, an ambiguous fork - it surfaces that question to the user's phone and waits ^[3]. Everything else runs unattended, but nothing ships until the user reviews and approves it ^[4]. That turns the phone from a second screen into a control surface: you start a job at your desk, glance at progress from a browser, tap approve on a decision from your pocket, and collect the finished output later ^[1]. The agent became ambient; the oversight stayed synchronous.

The timing is not accidental. Anthropic analyzed 1.2 million anonymized Cowork sessions drawn from more than 600,000 organizations, sampled between May 11 and 31, 2026 ^[5]. The finding that reframes the whole product: more than 90% of Cowork usage is everyday knowledge work rather than software development ^[2].

That data explains the strategic pivot. A macOS-only agent aimed at power users made sense when you thought Cowork was Claude Code for developers. But if nine in ten sessions are business operators drafting reports and running repeatable processes, then a desktop-tethered, engineer-shaped tool is leaving its actual audience stranded. Moving to phones and browsers with cloud execution meets those users where they are. As one publication put it, the coding agent wars are spilling into the rest of the office ^[1], and Anthropic is repositioning Cowork from a coder's utility into a general-worker platform. The parallel to OpenAI is explicit: Codex also started as a coding tool and is increasingly used by non-developers, and for both companies the wager is that winning depends less on the best chatbot and more on owning the space where work actually gets done ^[1].

The session study makes the non-coding reality concrete. Business process operating was the single largest category at 33.4% of usage, followed by content creation and copywriting at 16.4% ^[1]. Software development - the thing Cowork's lineage would suggest it is for - came in at just 8.7%, behind or near DevOps and infrastructure at 7%, research and intelligence at 6.4%, and data analysis and business intelligence at 5.8% ^[6].

Read as a whole, the breakdown shows an agent whose center of gravity sits in administrative and knowledge work, not engineering. That is the empirical basis for every product decision in this release: the cloud-backed scheduling, the phone approval loop, and the beta's framing around documents, presentations, and repeatable business tasks all follow from a usage curve where the developer use case is a minority slice, not the main event.

An agent you can no longer see - running in the cloud while your laptop sleeps - is a productivity win and a security liability in the same motion. Bhupendra Chopra of Kanerika frames the upside as a role change: employees will increasingly shift from executing tasks to supervising AI-generated outputs, reviewing exceptions, and applying business judgment. But he pairs it with a warning that persistent agents expand the attack surface because they continuously access enterprise systems and data ^[7].

The context makes that concern hard to wave away. Chopra cited Gravitee research surveying 445 IT and security leaders in which 88% reported confirmed or suspected AI-agent security incidents over the past year, while only about 14% said their agents were deployed with full security and IT approval ^[8]. That gap - near-universal incidents against a sliver of governed deployments - is the quiet counterweight to the demo-friendly nap metaphor. Pareekh Jain of Pareekh Consulting sees genuine operational value in letting teams keep business processes moving while away from their desks and reducing delays ^[7], but the same always-on posture that delivers that value is exactly what widens the exposure. Cowork's human approval gate is a real mitigation; whether it scales to background agents running across hundreds of thousands of organizations is the open question.

Not everyone is convinced. Among developers, the sharpest pushback is a blunt one - why use Cowork at all when Claude Code exists and, in their view, strictly dominates for engineering work? The complaints are specific: no mid-session model switching, no rewind, no slash commands, weaker document output. From an engineer's chair, Cowork can look like a downgrade wearing a friendlier interface.

That critique is real but it targets the wrong yardstick. The session data already showed developers are a minority of Cowork's users, so a feature set that underwhelms Claude Code power users is not the failure it looks like - it is the product finding its actual audience. The community's own enthusiasm points the same direction: the use cases people keep singling out as the killer application are scheduled personal-assistant tasks - daily briefings, email triage, recurring job scans - which is precisely what cloud-backed background execution unlocks and what Claude Code, a terminal-bound coding tool, was never meant to do. Meanwhile users have started noticing Cowork being folded into the main chat interface, matching Anthropic's apparent direction toward a single agentic surface where you can converse and delegate computer tasks in one place ^[3]. The developer skeptics are measuring a delegation tool against a coding tool - and the roadmap is quietly resolving the confusion by merging the two.