Product: Claude Cowork
URL: https://claude.com/product/cowork
Source: Claude Cowork Product Page 2026 04 17; mobile/web beta (2026-07): raw/x-bookmarks-recent-digest-2026-07-09.md (@claudeai), upgraded 2026-07-16 to the first-party announcement ai-research/claude-blog-cowork-web-mobile.md (claude.com/blog/cowork-web-mobile); enterprise admin-controls launch (~2026-04-08): upgraded 2026-07-16 from the April 17 product page to the first-party announcement ai-research/claude-blog-cowork-for-enterprise.md (claude.com/blog/cowork-for-enterprise) — one of a same-period cluster of admin-console upgrades alongside admin spend visibility (Chat/Claude Code spend analytics) and the Claude apps gateway (self-hosted Bedrock/GCP access layer), this one Cowork-specific; September 2026 chat/Cowork merge (“One Claude”): ai-research/claude-blog-cowork-is-now-claude-2026-09.md (claude.com/blog/cowork-is-now-claude, 2026-09-16), with secondary coverage from The AI Daily Brief (raw/Why_Everyone_is_Now_Getting_Excited_About_Personal_AI_Agents.md, raw/7_Ways_How_We_Use_AI_Is_Changing.md) and Matt Wolfe (raw/AI_News_-OpenAI_Made_a_Massive_Move_Against_NVIDIA.md, raw/AI_News-The_AI_Slowdown-What_You_Need_to_Know.md); October 2026 hands-on state: raw/Everything_You_Know_About_Claude_Cowork_Is_OUTDATED.md (Eliot Prince, YouTube, https://www.youtube.com/watch?v=VX2G7De8Oj8, 18:34, published 2026-10-27) and raw/5_Claude_Cowork_Tricks_I_Wish_I_Knew_Day_1.md (Eliot Prince, https://www.youtube.com/watch?v=AseH0yIySN4, 21:25, published 2026-09-28); day-after field notes on the September merge: raw/Anthropic_Just_Dropped_Claude_2.0_Full_Breakdown.md (Brock Mesarich, YouTube, https://youtu.be/lrsW8k-dHSk, 8:48, uploaded 2026-09-17); January 2026 launch-week analysis: raw/Anthropic-_Our_AI_just_created_a_tool_that_can_automate_all_white_collar_work_Me.md (AI Explained, YouTube, https://www.youtube.com/watch?v=wYs6HWZ2FdM, 19:02, uploaded 2026-01-14)
Anthropic’s “delegate and come back later” workspace product — distinct from Claude Code. Pitch: hand off a task, Claude executes end-to-end (files, spreadsheets, reports, decks, connectors), and you return to a polished deliverable. Marketed at non-developer business users across Pro / Max / Team / Enterprise tiers. Reached general availability on all paid plans alongside a dedicated enterprise admin-controls launch as of 2026-04-08.
Key Takeaways
- September 2026: Cowork stops being a separate place. Per Anthropic (2026-09-16), “Claude Cowork and chat are merging into one Claude”: Claude decides what a task needs, and what Cowork and Design can do is available from any conversation. Rolling out to Pro and Max first; Team and Free later; Enterprise admins get 30 days’ notice. Details in One Claude (September 2026) below.
- October 2026: what the merged product looks like. Eliot Prince’s 2026-10-27 walkthrough: the chat/Cowork toggle is gone on Pro and Max; Team admins switch the merge on or off under Organization settings → Capabilities → “Chat and Cowork unified”; Cowork runs on web and phone, and can still reach your computer’s files while its desktop app is running; projects are one kind with a local folder plus uploaded context; scheduled tasks attach to projects; memory spans the whole account; a built-in browser and Claude Docs, Sheets and Slides are live on his account. Details in The merged product in practice (October 2026) below.
- Positioning: delegation, not chat. Tagline “Delegate to Claude, delight in the result.” The product is framed around async task handoff — describe the goal, Claude works, asks for approval on risky actions, delivers the output.
- Three recent feature drops, each load-bearing. Apr 8 2026 — Cowork reaches general availability on all paid plans alongside a dedicated enterprise admin-controls launch: role-based access control (SCIM group provisioning + custom roles gating which Claude capabilities each group can use), group spend limits (per-team budgets from the admin console), usage analytics (an admin-dashboard view plus a separate Analytics API exposing per-user activity, skill/connector invocations, and DAU/WAU/MAU alongside Chat and Claude Code figures), expanded OpenTelemetry (events for tool/connector calls, file reads/edits, skill use, and manual-vs-automatic approval status — Splunk/Cribl-compatible, correlatable with Compliance API records via a shared user identifier), a new Zoom MCP connector (AI Companion meeting summaries/action items/transcripts), and per-tool connector controls (admins restrict specific actions within an MCP connector org-wide — e.g. Gmail read-only, no send). Mar 23 2026 — Dispatch, a computer-use capability for desktop automation. Feb 24 2026 — private plugin marketplace for admins (see Cowork Plugins).
- Pricing ladder. Pro 20 monthly) includes Cowork but “consumes limits faster.” Max 5x 200/mo for power users. Team $20/seat/mo (5–75 seats) includes Slack connector. Enterprise custom with OpenTelemetry streaming for SIEM.
- Integrations marketed up front. Slack, Chrome, Google Drive, GitHub, Notion, CRM tools, Linear, Zapier, and (added 2026-04-08) Zoom — AI Companion meeting summaries, action items, transcripts, and smart recordings surfaced directly inside Cowork workflows. Bundled plugins include Brand Voice (Tribe AI), Legal, Finance.
- Dispatch = computer use inside Cowork. The Mar 23 announcement is significant: Claude can now drive the desktop (click, type, navigate) as part of Cowork task execution. This is what enables “message a task from your phone, come back when it’s done.”
- Explicit permission model. User picks folders/connectors accessible to Claude; Claude requests approval before significant actions; admins can disable Cowork org-wide.
- File-type coverage is broad. Office formats (docx/xlsx/pptx and older .doc/.xls/.ppt), PDFs, images (including SVG/WebP), data formats (JSON/CSV/TSV/YAML/XML/TOML/SQL), and major programming language files.
- Customer proof mixes vendor and verticals — now four named accounts. Zapier (automation platform, connected Cowork to their org database + Slack + Jira to surface engineering bottlenecks, producing a dashboard Product and Design Ops then adopted for themselves), Jamf (Apple device management — the original 45-minutes-vs-custom-React-app performance-review skill, since extended to vendor reviews and incident response), Airtree (VC firm — a board-prep workflow pulling a portfolio company’s Drive, Slack updates, and competitor news, cross-referenced against the previous prep), and Thomson Reuters (legal/media — a distinct engagement from Fable-5 case study elsewhere in the wiki, quoted here on Cowork’s org-wide scale specifically: “the human role becomes validation, refinement, and decision-making, not repetitive rework”). Full detail in Customer case studies below.
Implementation
- Tool/Service: Claude Cowork (claude.com/product/cowork)
- Setup: Download Claude desktop app; sign in on Pro or higher; opt into Cowork; connect folders and approved connectors (Slack, Drive, GitHub, Notion, Linear, etc.). Since the merge there is no separate Cowork mode to opt into on Pro and Max, and “Cowork in the cloud” runs it from the web and phone apps; the desktop app is still needed for local folders and the built-in browser (October 2026, see below).
- Cost:
- Pro: 20/mo (monthly) — Cowork included, limits tighter
- Max 5x: $100/mo — longer tasks, everyday use
- Max 20x: $200/mo — heavy daily handoff
- Team: $20/seat/mo — Slack connector included, 5–75 seats
- Enterprise: custom — OpenTelemetry/SIEM, admin controls, usage analytics
- Integration notes: Plugin ecosystem covered in Cowork Plugins (11 → 21+ plugins, 12 new MCP connectors in the Feb 2026 upgrade, private marketplace for enterprise). Marketing-specific use cases covered in Cowork for Marketing.
Feature timeline
| Date | Feature | Notes |
|---|---|---|
| 2026-01 (days before 01-14) | Launch (Max tier, macOS only) | Per AI Explained (video uploaded 2026-01-14, “released in the last couple of days”): Max plan only, not Pro, and macOS only, not Windows. The Claude Code lead said the tool was written in Claude Code by Claude Opus 4.5, with humans planning and designing. The exact launch date is not stated in the source. See AI Explained analysis (2026-01-14) below. |
| 2026-02-24 | Plugin marketplace | Private plugins + 10 new department plugins + 12 new MCP connectors + cross-app workflows. See [[claude-ai/cowork-plugins |
| 2026-03-23 | Dispatch | Computer-use capability inside Cowork — enables desktop automation and the “message from phone, execute on desktop” pattern. |
| 2026-04-08 | Enterprise deployment + GA on all paid plans | RBAC (SCIM groups + custom roles), per-team spend limits, usage analytics (dashboard + Analytics API with DAU/WAU/MAU), expanded OpenTelemetry (Splunk/Cribl SIEM + Compliance API correlation), new Zoom MCP connector, per-tool connector action controls, admin org-wide disable toggle. Four named customer case studies (Zapier, Jamf, Airtree, Thomson Reuters) accompanied the launch — see Customer case studies below. |
| ~2026-04-22 | Live Artifacts (desktop app only at launch) | Creator launch-day walkthrough (Eliot Prince, raw/Wait._Whaatttt…_Claude_LIVE_ARTIFACTS_Just_Dropped…md), not a first-party post. See Cowork Live Artifacts. |
| 2026-07 | Mobile + web beta | Cowork expands beyond the desktop app. Three concrete changes per the first-party blog post (claude.com/blog/cowork-web-mobile): (1) work follows you across devices; (2) work continues in the background — scheduled tasks now run with no device online at all (example given: a 6am client-prep task works through email/transcripts/news and leaves a drafted-but-unsent follow-up email for review over coffee); (3) decisions Claude can’t make itself route to your phone, and nothing ships until reviewed/approved. Chat and Cowork now share one home on web/desktop, with projects and artifacts unified across both. Desktop remains the full experience (local files + browser); users who couldn’t install a desktop app can now use Cowork at all. Doubled Cowork usage limits extended through August 5, 2026 to mark the launch. Beta rolling out over the next several weeks, Max plan first, more plans to follow. Grounded in [[claude-ai/cowork-usage-report-2026 |
| 2026-07-21 | Record a skill (teach Claude by screen recording) | Per @claudeai (raw/x-bookmarks-recent-digest-2026-07-24.md, permalink): “Record your screen while you do a task, talk through it as you go, and Claude turns it into a skill it can run again.” Found under Record a skill in the + menu of the Claude desktop app. Available on Pro, Max, and Team plans. Announcement-only — no first-party doc or blog post ingested yet, so the recording length limits, what the generated skill looks like, whether it is editable afterward, and how it relates to Cowork plugins are all unknown. Update 2026-10-27: hands-on coverage now answers most of these (editable before saving, asks clarifying questions, uses connectors or Claude in Chrome, schedulable): see Record a Skill. |
| 2026-08 | Shared home, two modes — chat and Cowork in one home behind an input-bar toggle, cloud execution, unified projects, Cowork on web + phone | Hands-on walkthrough of what the July beta actually became. Full mechanics in the section below. Relabelled 2026-09-29: this row previously read “The merge, as shipped”, but chat and Cowork were still two modes you chose between. The full merge came in September (next row); see the resolved callout below. |
| 2026-09-16 | One Claude — chat and Cowork merge; Claude Docs and Claude Slides launch; Claude Design works inside conversations | First-party (claude.com/blog/cowork-is-now-claude). No mode to pick: Claude decides what a task needs. Docs, Slides and in-conversation Design are beta on paid plans. Rolling out to Pro and Max over the coming weeks, then Team and Free; Enterprise admins get at least 30 days’ notice. See One Claude (September 2026) below. |
| 2026-09 | Built-in browser (announced), Claude in Chrome GA, memory shared between chat and Cowork | Reported by Matt Wolfe, not checked against a first-party post. The built-in browser for the Claude desktop app rolls out over the coming weeks to Pro, Max and Team on macOS, Windows and Linux; it was not live for Matt. Claude in Chrome is generally available. Chat and Cowork use one memory, including Cowork tasks run in the cloud; by default Claude does not store personal or sensitive topics (health, race, ethnicity, religious beliefs, politics). |
| ~2026-10 | Chat + Cowork unified for Enterprise (GA) | First-party (claude.com/resources/articles/unified-claude-enterprise, ~October 2026). The September 2026 Pro/Max unification rolls out to Enterprise plans. No mode to pick: conversations start as chat, and tasks that need code or files move to cloud execution and return finished documents, analyses, or decks. Cloud work continues after the user closes their laptop; chats, projects, connectors, skills, and plugins carry over. New cost controls added for Enterprise admins: (1) Efficient mode — keeps Claude on Sonnet and Haiku models; (2) Model entitlements — set which models each role can access; (3) Spend limits — apply at the organization, group, and member levels; (4) Pooled group budgets — give a group one shared monthly amount. Pricing update: Claude Opus 5.5 costs 40% less than Opus 5 on typical workloads; Sonnet 5.5 costs up to 30% less than Sonnet 5. Exceptions: organizations using zero data retention for Claude Code, a HIPAA-ready configuration, or customer-managed encryption keys stay on their current setup; admins manage rollout in Organization settings. Source: ai-research/claude-blog-cowork-chat-enterprise-2026-10-25.md |
| 2026-10 | Merge reaches Pro/Max and Team — no mode toggle; Team admin switch; Cowork in the cloud; built-in browser and shared memory live | Hands-on walkthrough by Eliot Prince (2026-10-27), not a first-party post. Toggle removed on Pro and Max; Team admins control “Chat and Cowork unified” in organization settings, and turning it off restores classic chat and Cowork. Built-in browser and account-wide memory, reported in September as announced, are working on his account. He also shows Claude Sheets alongside Docs and Slides. See The merged product in practice (October 2026) below. |
| 2026-10-06 | Claude for Google Workspace (beta, paid plans) | Sidebar add-on for Google Docs, Sheets and Slides that brings your skills and connectors (Eliot Prince, raw/Claude_for_Google_Workspace_just_dropped_and…md). First-party coverage: Claude for Google Workspace; hands-on: Claude in Office and Google Workspace. |
One Claude (September 2026)
Source: Anthropic, “Claude Cowork and chat are now one Claude” (claude.com/blog/cowork-is-now-claude, saved as ai-research/claude-blog-cowork-is-now-claude-2026-09.md). The page is undated; 2026-09-16 comes from same-day press coverage. Reactions and field notes from The AI Daily Brief (NLW) and Matt Wolfe, cited inline.
What changed.
- “Starting today, Claude Cowork and chat are merging into one Claude.” You no longer pick a mode: “Claude can now figure out what a task needs, so what Cowork and Design can do is available from any conversation, with the context, skills, and connectors you already have.”
- Anthropic’s reason: “We built Cowork as a separate place for bigger work, and Design for visual work. People used both, and told us the frustrating part was deciding where a task belonged. What they’d started in one also didn’t carry into the other. So we stopped making you choose.”
- Shipped the same day: Claude Docs and Claude Slides are new, and Claude Design now works inside conversations. All three are beta on paid plans, and Enterprise admins choose when to turn them on. Standalone Claude Design keeps working. Output lives at one shareable link: edit it directly, present from Claude, or download it as PowerPoint or PDF.
- Check-in control: by default Claude asks before taking an action. You can switch it to keep working and check in only when something needs a closer look.
- Nothing to migrate: existing Cowork users keep their chats, projects, artifacts, connectors and skills, and there is nothing to turn on.
The launch video (Anthropic, 2026-09-16). “Claude Cowork and chat are now one Claude” (youtube.com/watch?v=qMUf-jwSpMo, 1:11, raw/Claude_Cowork_and_chat_are_now_one_Claude.md) is presented by Meaghan Choi, who leads design for Claude apps. What it adds to the post:
- The problem it names is the “half-second when you open your laptop to give Claude something… and you hesitate”: you “no longer have to figure out where a task belongs before you start.”
- Why Cowork was folded in: “Cowork is where we worked out how Claude should take on bigger, multi-step work. It got so good at deciding what a task actually needs, keeping it in a separate place just stopped making sense.”
- What carries over: “your chats, tasks, skills, and memories are all still intact.”
- Her example task: “hand it last week’s numbers and have it draft the deck or other visuals, and it’ll build it all right there.” You can still “keep, edit, or steer any piece you want.”
- She calls it “the first step”, with the experience to improve as the models do.
Anthropic’s September recap (2026-10-07) repeats the merge and adds one mechanic: a bigger task “keeps going even after you close your laptop, because the work now runs in the cloud”, so you can start on a laptop and follow along from your phone (raw/What_s_new_in_Claude_-_September_recap.md; see What’s New in Claude — September 2026).
Rollout. Pro and Max first, on web, desktop and mobile, “over the coming weeks”. Team and Free “will follow soon”. Enterprise admins “will hear from us at least 30 days before anything changes for their organizations.” Matt Wolfe, on the $200 Max plan with the latest app, still saw separate Chat and Cowork options after the announcement (raw/AI_News_-_The_AI_Slowdown_-_What_You_Need_to_Know.md). That fits a staged rollout; if your app still shows the toggle, the August mechanics below still apply to you. Brock Mesarich saw the same on 2026-09-17 and expected the toggle to go “over the next couple of weeks” (raw/Anthropic_Just_Dropped_Claude_2.0_Full_Breakdown.md).
What the composer showed the day after (Brock Mesarich, desktop app, Cowork mode). Before the toggle went, the new pieces were already in the Cowork composer: a project selector; approvals set to manual, automatic, or skip all approvals, which look like the settings behind Anthropic’s check-in control ^[inferred]; and an Output picker for Docs, Slides or Design. His demos turned one CSV into an editable doc and into a slide deck in a design system he had made in Claude Design. A deck can be presented with speaker notes, shared by link, exported to Canva, Gamma or Miro, or downloaded as HTML, PDF or PowerPoint. He also pulled Drip email stats into a doc through Zapier MCP, because Drip has no Claude connector. The step-by-step is in The Revamped Claude Desktop App. He calls the whole release “Claude 2.0”, a creator nickname rather than an Anthropic name.
The worked example Anthropic gives is a usable template for a first delegated task. Before leaving for work, ask what moved in the pipeline last week, then: “Write it the way we always do, flag anything that slipped, and put the highlights in five slides for the leadership meeting.” Check progress from your phone. The report arrives as a doc and the slides match it, because both came out of the same conversation. Then “schedule it for every Monday, and Claude starts on the report without being asked.”
Reactions (The AI Daily Brief, raw/Why_Everyone_is_Now_Getting_Excited_About_Personal_AI_Agents.md).
- Boris Cherny, as read out by NLW: “Claude Code showed that AI could do real work, not just answer questions… Cowork proved knowledge workers could do the same. Hand Claude the brief, come back to finished files.”
- NLW’s reservation as a heavy user: he keeps different model settings for work and personal tasks, so without the mode switch he may end up toggling the model selector instead. He also admits some hesitation about letting the platform choose the model for him. He calls himself the minority; most reactions he saw were positive.
Projects moved the same way that week (The AI Daily Brief, raw/7_Ways_How_We_Use_AI_Is_Changing.md). NLW quotes the Claude account: “Projects now run from one conversation starting in Claude Code. You describe what needs doing, and Claude directs parallel threads that keep working after you close your laptop.” Cherny: “I stopped managing sessions. I just send thoughts as they come. Claude splits them into threads and the project remembers how I work.” Mechanics are in Claude Projects.
Watch subagent models. In the same episode, NLW describes Fable 5.1 users handing over a standard task and finding “a major percentage of our current usage cap tapped” because the five or ten research subagents it spun up all ran on the top Fable model. As Claude takes over more of the routing, check which model its subagents use and pin cheaper ones where the task allows.^[inferred — NLW describes the failure and calls model allocation “an important discipline”; the pin-the-subagent-model step is this wiki’s reading]
The merged product in practice (October 2026)
Source: raw/Everything_You_Know_About_Claude_Cowork_Is_OUTDATED.md — Eliot Prince, youtube.com/watch?v=VX2G7De8Oj8, published 2026-10-27, auto-caption transcript. Eliot runs Claude on a personal account and on a Team account with 50+ members, and shows both. A creator walkthrough, not a first-party post: it records what the UI showed him on the upload date. His wider tips are collected in Claude Cowork Field Guide (Eliot Prince).
The toggle is gone, and Claude picks. The desktop toggle went from chat / Cowork / code, to a chat-or-Cowork switch beside the input box, to nothing. Claude now turns Cowork on and off underneath, depending on whether you are talking something through or handing over a task. Eliot’s September video already found the toggle disappearing on his account (raw/5_Claude_Cowork_Tricks_I_Wish_I_Knew_Day_1.md). This is the September One Claude merge (above) reaching his plans.
Team plans have an admin switch. On Pro and Max the change arrives on its own. On Team, the admin decides: Organization settings → Capabilities → “Chat and Cowork unified” (“Let members use the new unified chat and Cowork experience… where Claude can run code, work with files, and keep longer tasks going in the cloud. When off, everyone keeps classic chat and Cowork”). The panel links a setup guide and a security guide. Eliot recommends turning it on. Anthropic’s September post said “there is nothing to turn on” for users and that Team would “follow soon”; it did not mention a Team admin switch, so this is new detail rather than a conflict.
Cowork no longer needs the desktop app. Settings → Cowork → “Cowork in the cloud” lets Cowork tasks use Anthropic’s cloud instead of your computer, so tasks keep running across desktop, web and mobile. On the web app Eliot ran a multi-step skill (his “company DNA builder”) that used code, connectors, web search, memory and skills in one run.
The web and phone apps can reach your computer. On the web app a banner read “MacBook Pro’s connected. Claude can use the files and apps on my computer.” While the computer is on and the desktop app is running, the web and phone apps can use its files. When it is off, Cowork still runs in the cloud but without local files, so anything it needs has to be uploaded to Anthropic’s servers first. This extends the August “bridge” behaviour (next section) rather than replacing it.
Projects: one kind, two context sources. Chat projects and Cowork projects were merged once, then again: “all of our projects are just projects.” Each project now shows:
- Folder — a local folder on the connected computer (editable, to point Cowork somewhere else);
- Context — files uploaded with + → Upload from device, stored on Anthropic’s servers, which work whether the computer is on or off;
- the project’s chats and tasks, filed underneath.
Scheduled tasks attach to projects. The sidebar’s Scheduled page still offers templates (daily briefing, inbox triage, weekly review). A task can now live inside a project, using its context files, skills and project memory, on a time or a trigger. Eliot’s example: a “live Q&A prep” task in his community’s project that runs every Wednesday at 1:49 p.m. He says he runs 10-20 such tasks in his main project. He describes scheduled tasks as having “kind of killed” n8n-style flows for simple recurring work; that is his opinion.
Memory covers Cowork now. Cowork used to have no account memory and ran only on files. Memory now spans the whole account, Cowork included. Settings to turn on: search and reference chats and generate memory from chats (including sensitive topics is optional). The memory panel groups what it holds by you, topics, people and projects. This matches the September report of one shared memory (timeline above).
Built-in browser. At the top right of the desktop app is a browser pane. Cookies can be imported, both you and Claude can use it, and Claude asks permission per site (“Allow Claude to use browser on bbc.com”). Driving Claude in Chrome from the desktop app still works, but Eliot finds the built-in browser “way more stable”. Tell Claude which one to use if it picks the wrong one.
Claude Docs, Sheets and Slides. Ask for “a Claude doc” rather than a Word or Google document and Claude writes it in a side pane you can edit together: highlight, strike through, comment, and delegate edits through comments (“can we merge these two sections”). Export as Word, PDF, Markdown, Google Docs or Notion, or invite teammates to view or edit. Anthropic’s September post named Docs and Slides; Sheets appears only in Eliot’s walkthrough. He finds the Google Sheets and Workspace connectors slower than working in Claude’s own formats.
What the merge looks like in practice (2026-08-07 addition)
Merge timing: August "as shipped" vs September "merging"
Existing claim: (from claude-cowork.md, 2026-08 timeline row) — “The merge, as shipped — chat/Cowork unified, cloud execution, unified projects, Cowork on web + phone” New source says: (from raw/AI_News_-The_AI_Slowdown-_What_You_Need_to_Know.md, Matt Wolfe, late September) — Anthropic “announced that Claude Co-work and their chat are now just one thing… rolling out to pro and max plans first… over the coming weeks”, while Matt “still see[s] a chat and co-work option”. Status: resolved (2026-09-29). Anthropic’s own post (ai-research/claude-blog-cowork-is-now-claude-2026-09.md, 2026-09-16) settles it. In August, chat and Cowork shared one home but stayed two modes on an input-bar toggle, which is what this section documents. The merge into one Claude, with no mode to choose, was announced on 2026-09-16 and is still rolling out. The 2026-08 timeline row has been relabelled to match; the mechanics below describe the pre-September state.
Source: raw/The_NEW_Claude_COWORK_Clearly_Explained_desktop_browser_phone_versions.md — Elliot (community walkthrough), youtu.be/5GRhAKz3R_Y, auto-caption transcript. This is the shipped-mechanics companion to the 2026-07 announcement row above: that row records what Anthropic said would happen, this records what a user actually finds in the UI. The presenter’s own framing — “your head is absolutely spinning” — is a fair summary of why this needed writing down.
The top-level toggle lost a mode. The desktop app’s top-left toggle used to read chat / Cowork / code. It now reads home and code only. Home is where both Claude chat and Claude Cowork live, and the chat-vs-Cowork choice moved into a toggle on the main input bar.
- Chat mode works only against your Claude cloud account — memory and cloud projects. It does not touch files on your computer.
- Cowork mode unlocks selecting a project or folder on your computer, with create/edit/move/delete on that folder. Described as “essentially a watered-down version of Claude Code under the hood” — fewer commands, same execute-work-rather-than-chat model.
The run-location toggle is the genuinely new capability, and it has a sharp edge. Top-right of the window, two options:
| On your computer | In the cloud | |
|---|---|---|
| Runs while machine is off | No | Yes |
| Reads local files | Yes | Only while the machine stays on |
| Writes local files | Yes | No — the bridge closes |
| Best for | Anything touching local files | Connector-to-connector work, long runs |
The failure mode to design around: “there’s like a bridge between the two that gets shut down if you close your computer off.” A cloud task started against local files keeps running but loses both read access and the ability to write results back. Two patterns that work: pull everything you need off local files while the machine is on and have the output land in Claude or a cloud connector (Notion, Gmail); or run wholly cloud-to-cloud — e.g. Notion connector in, Gmail out — never touching local files.
Projects merged, and now come in two kinds. Chat projects and Cowork projects previously lived in separate places; they are now in one projects area. The distinction still exists and still matters:
- Local projects carry a
localtag. Context comes from folders on your computer; they support memory, custom instructions, and scheduled tasks, but need the “on the computer” setting to be useful. They do not appear on web or phone at all. - Cloud projects are the traditional chat projects — instructions and memory, with files in the cloud UI. Available on every surface.
The upgrade worth knowing: you can now run Cowork on a cloud project. Previously agentic autonomy required local files. Now a plain chat project can be handed a goal and left to plan and execute across connectors and knowledge bases — “Claude chat, you get one response at a time… Claude Cowork, you give it a problem or a goal or a grand task, and it’s going to lay out all the steps it needs to execute.”
The one-way door. Any project can run in chat or Cowork mode — except a local-file project. Once a project carries the local tag, it can only run in Cowork mode with files on your computer, and cannot be switched back to chat mode. Worth knowing before you create a project against a local folder.
Cowork on the web (claude.ai) mirrors the desktop UI and is new — Cowork previously required local files. Local projects are absent there by construction. Terminology follows the mode: in chat mode they are chats, in Cowork mode they are tasks.
Cloud scheduled tasks no longer need your computer on. Scheduled tasks previously required desktop Cowork against local files, so the machine had to stay awake. They can now be scheduled inside cloud projects — set frequency (the example given is daily at 9am), set auto-approve, and the run happens in the cloud. This is the mechanic behind the July announcement’s “scheduled tasks now run with no device online at all.”
Phone. Cowork mode is in the phone app, working because Cowork can now run in the cloud. One asymmetry: messaging a task that is running on your computer prompts an additional sign-in to link to that machine, whereas cloud chat projects use the normal phone login.
The chat-vs-Cowork decision rule, in the presenter’s terms: chat is for writing, thinking, exploring, and one focused task at a time (an email, a post, a summary). Cowork is for handing over a goal and walking away — “it might take minutes, half an hour, an hour, several hours to run this, and you come back to finished work.”
Why the record-a-skill drop matters beyond the feature list: every other route to a reusable skill in this wiki is written — a prompt, a SKILL.md, a plugin. This is the first documented path where the authoring input is a demonstration rather than a specification, which lowers the skill-creation floor to “do your job once while narrating.” That is squarely aimed at the >90% of Cowork sessions that aren’t software development, where the user can perform the task but would never write a skill file for it.^[inferred — the connection to the usage report is this wiki’s synthesis, not stated in the announcement]
AI Explained analysis (2026-01-14)
Source: raw/Anthropic_-_Our_AI_just_created_a_tool_that_can_automate_all_white_collar_work_Me.md — AI Explained, youtube.com/watch?v=wYs6HWZ2FdM, 19:02, uploaded 2026-01-14, auto-caption transcript. A launch-week reaction after 48 hours of use, set against claims that Cowork shows all white-collar work will be automated in 2026. Historical: it describes the January launch, months before the GA, merge and pricing changes above.
- Launch facts as he gives them. Max tier only (he cites a ~$100/month minimum), macOS only. The launch announcement had gone viral at 42 million views. The Claude Code lead said all of Cowork’s code was written by Claude Opus 4.5, then clarified: “It was not zero intervention. We the humans had to plan, design, and go back and forth with Claude.”
- His test task, and the result. He asked for a chart of one football club’s league position on today’s date for each of the last five seasons, as a PowerPoint on his desktop, with clarifying questions and a plan first. The plan was good and the deck “visually quite impressive”, but two of the dates he checked were wrong: it put Stockport third on 13 January 2025, when BBC and 11v11 both had them seventh. Cowork’s summary gave no caveat that it lacked a reliable source.
- His conclusion: edit, don’t redo. Most other facts in the deck were right, so fixing a couple of numbers was faster than building it from scratch. He cites OpenAI’s GDPval paper (October 2025): with blind human grading, letting the model retry while a human reviews and edits now beats the human doing the task alone.^[inferred — he says this is the tipping point; the “edit, don’t redo” wording is this wiki’s summary]
- Failure anecdote. He mentions one user’s report, two days before the video, of Cowork deleting 11 GB of files from their desktop. One unverified report; it supports keeping approvals on for anything destructive.
- Labor-market context. He quotes an Oxford Economics report (7 January 2026): new-graduate unemployment is slightly higher but within historical range, labor productivity growth in 2025 was not markedly higher, and firms may cite AI for layoffs because it reads better to investors than weak demand or past over-hiring. Its authors don’t expect AI to raise US joblessness significantly over the next year or two.
- Why models are brittle. A paper he credits to Beckman and Quaos (spelling from auto-captions, unverified) describes three tiers of understanding: conceptual, contingent (state-of-the-world) and principled. LLMs mix all three and switch to shallow heuristics when those reduce loss more cheaply, which is why a model can find a tiny bug in a large codebase and still fail to infer “Mary Stone’s husband is Tom Smith” from “Tom Smith’s wife is Mary Stone”.
- The predictions he disputes. He names Anthropic and Sholto Douglas (captioned “Schultto Douglas”) and plays a clip predicting that in 2026 other knowledge work gets “the Claude Code experience” and that continual learning probably gets solved. His verdict after using Claude Code daily and Cowork for 48 hours: “those predictions are just not true”, but the productivity gains are real.
Customer case studies
Four named accounts accompanied the 2026-04-08 enterprise launch (claude.com/blog/cowork-for-enterprise):
- Zapier — connected Cowork to their org database, Slack, and Jira to surface engineering bottlenecks. The output (a dashboard plus team-by-team analyses and a prioritized roadmap) was good enough that Product and Design Ops copied the workflow for their own use, independent of the original engineering ask.
- Jamf (Apple device management) — turned a seven-facet performance review into a 45-minute guided self-evaluation (the “faster than a custom React app” comparison cited above), then extended the same pattern to vendor reviews and incident-response workflows.
- Airtree (venture capital) — built a board-prep workflow that pulls from a portfolio company’s Drive, Slack updates, and competitor news, cross-referenced against the firm’s previous prep for that company. Quote: “Claude Cowork became shared firm infrastructure rather than just an individual productivity tool.”
- Thomson Reuters (legal/media) — a distinct engagement from Fable-5 case study elsewhere in the wiki; this quote addresses Cowork’s org-wide scale specifically: “Claude Cowork helps teams do work at a scale that was hard to justify before. The human role becomes validation, refinement, and decision-making. Not repetitive rework.”
Community-discovered use cases
[Reddit signal — r/ClaudeAI 2026-05-18] Source: raw/reddit-1tggzm5.md (511 score / 69 comments, OP TheCoffeeLoop, Claude Workflow flair).
Cowork-driven personal-data removal from data brokers. Operator pattern: use Cowork’s Chrome plugin + Gmail connection to file removal requests against the major personal-data aggregators (Spokeo / Whitepages / etc). The agent fills the per-broker forms, sends the verification emails, and tracks the removal-confirmation replies — automating the workflow that paid services like Incogni charge a subscription for. Before-weekend run → following Monday inbox full of confirmation emails. Pattern is novel because Cowork’s Chrome plugin + Gmail combo is the exact integration shape data-removal automation needs (browser-side form-filling + email handling for the verification round-trip) — no API exists for these brokers so traditional automation can’t do it.
Related
- How People Are Using Claude Cowork (May 2026 Usage Data) — the first-party usage-share data (business ops 33.4%, content creation 16.4%, software dev only 8.7%) that the mobile/web-beta launch cites as its rationale
- How Anthropic’s Own Marketing Operations Team Uses Claude Cowork — a worked internal case study (dispatcher/specialist/audit/manager skill pipeline) sitting inside the largest usage category above
- Claude for Government — the FedRAMP High / public-sector deployment of Claude Code and Cowork together, with its own governance/audit-log model
- Cross-Topic Connections — cross-topic synthesis comparing Cowork/Dispatch against Routines and Managed Agents with a decision framework
- Claude Cowork Field Guide (Eliot Prince) — dated setup tips from February to October 2026, including the October state in brief
- Dispatch in Claude Cowork (Tutorial) — how the Mar 2026 computer-use / mobile-to-desktop feature actually works
- Cowork Plugins — deep dive on the plugin/marketplace layer (Feb 2026 upgrade details, department plugins, MCP connectors)
- Cowork for Marketing — marketing-specific Cowork use cases
- Claude Managed Agents — the developer-facing hosted-agent primitive (Cowork is arguably a consumer surface over similar infrastructure)
- Claude Code Routines — scheduled cloud automation for developers; Cowork’s “set it once, skip the ask” is the business-user analog
- The Advisor Strategy — cost/intelligence control pattern for agent loops; relevant to any Cowork workflow using Sonnet/Haiku
- Skills Ecosystem — skills are the building block beneath Cowork plugins
- Plugins and Marketplaces — contrast with Claude Code’s developer plugin registry
- WEO AI Governance — admin-controls, SIEM, and spend-limit features align with the WEO governance program’s requirements
- Thomson Reuters — Fiduciary-Grade AI (CoCounsel Legal, Fable 5) — a separate Thomson Reuters engagement (Claude API / Fable 5, not Cowork); the two share a customer but not a product context
- Giving Admins More Visibility and Control Over Claude Spend and Claude Apps Gateway — sibling posts from the same admin-console upgrade wave (Chat/Claude-Code spend analytics, and the self-hosted gateway, respectively); this article covers the Cowork-specific member of that cluster
Open Questions
- Dispatch scope. Does Dispatch run locally on the user’s machine, or in Anthropic-hosted sandboxes like Managed Agents?
- Advisor tool compatibility. Can Cowork workflows declare
advisor_20260301for cost-controlled intelligence scaling, or is that only via raw Messages API? - Plugin/skill portability. Do Cowork plugins and Claude Code plugins share any format, or are they entirely separate ecosystems?
- Data residency. Even with the 2026-04-08 post’s added detail (Compliance API correlation via a shared user identifier, Splunk/Cribl SIEM compatibility), no source clarifies regional data residency commitments for Cowork workloads specifically.
- Zoom connector tier requirement. The 2026-04-08 post doesn’t state whether the Zoom MCP connector’s AI Companion features require a specific paid Zoom tier, or work with any Zoom account.
- Cowork vs Routines overlap. Both enable scheduled/recurring automation. What’s the line — Cowork for business users, Routines for devs? Or is there deeper architectural separation?
- Record-a-skill mechanics are undocumented. The 2026-07-21 announcement is a single tweet. Unknown: recording length limits, whether the narration is required or optional, what artifact the recording compiles into (a
SKILL.md? something Cowork-internal?), whether the result is human-editable, whether it can call connectors, and whether a recorded skill is portable to Claude Code plugins. This sharpens the plugin/skill-portability question above rather than answering it. - September items not yet checked first-party. The built-in desktop browser, Claude in Chrome GA and shared chat/Cowork memory come only from Matt Wolfe’s news roundup (2026-09 row); their announcement dates and plan details need Anthropic’s own posts. The merge post also points to a Help Center capability list that has not been ingested. Eliot Prince’s 2026-10-27 walkthrough shows the built-in browser and shared memory working, which confirms they shipped but still gives no first-party dates or plan list. Claude Sheets also lacks a first-party source.
- Team admin switch defaults. Is “Chat and Cowork unified” on or off by default for a Team organization, and does Enterprise get the same switch after its 30-day notice? Eliot shows the switch but not its default.
- What happens to the local-folder “one-way door” after the merge? The August section says a
localproject can only run in Cowork mode. The September post says nothing about local-folder projects once there is no mode to pick. Partly answered by the October walkthrough: a merged project can hold a local folder and uploaded cloud context together, and the web app can use the folder while the desktop app runs. It doesn’t show whether a folder-backed project opens on the web when the computer is off.
Try It
- See Dispatch in action. On Pro+ with Cowork enabled, give a task that requires desktop navigation (“rename every screenshot in my Downloads folder by the date it was taken and move them to ~/Documents/Screenshots/YYYY-MM”). That exercises the Mar 23 computer-use drop.
- Test the phone→desktop handoff. Message Claude from mobile with a spreadsheet task; watch the execution happen on your desktop.
- Install one plugin from the marketplace that matches your primary workflow (Marketing, Finance, Legal, Sales). Use it on a real task. Compare against your existing tool.
- Enterprise evaluation checklist if considering the Enterprise tier: validate OpenTelemetry ingestion into your SIEM (Splunk/Cribl-compatible) and check whether you need Compliance API correlation; set up role-based access control via SCIM and confirm custom roles match your policy requirements; test per-team spend limits and the Analytics API with a sample group; configure per-tool connector action restrictions (e.g. read-only Gmail) for any connector handling sensitive data; confirm the org-wide disable toggle.
- Once the September merge reaches your plan, run Anthropic’s worked example on a real recurring report: one request that yields a doc plus matching slides, then schedule it weekly. Decide first whether to keep the default ask-before-acting check-in or let it run and check in only on exceptions.
- Team admins: decide on the merge switch. Check Organization settings → Capabilities → “Chat and Cowork unified”. With it off, members keep classic chat and Cowork and the August mechanics below still apply.
- Move recurring work into a project. Upload the context files a task needs (so it runs with the computer off), then attach the scheduled task to that project rather than leaving it standalone.
- Read the related deep dives: Cowork Plugins for the ecosystem; Cowork for Marketing for the marketing angle.