Jonathon's AI Wiki

Claude Cowork (Product Overview)

15 min read

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

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

  • 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.).
  • 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

DateFeatureNotes
2026-02-24Plugin marketplacePrivate plugins + 10 new department plugins + 12 new MCP connectors + cross-app workflows. See [[claude-ai/cowork-plugins
2026-03-23DispatchComputer-use capability inside Cowork — enables desktop automation and the “message from phone, execute on desktop” pattern.
2026-04-08Enterprise deployment + GA on all paid plansRBAC (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-07Mobile + web betaCowork 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-21Record 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.

| 2026-08 | The merge, as shipped — chat/Cowork unified, cloud execution, unified projects, Cowork on web + phone | Hands-on walkthrough of what the July beta actually became. Full mechanics in the section below. |

What the merge looks like in practice (2026-08-07 addition)

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 computerIn the cloud
Runs while machine is offNoYes
Reads local filesYesOnly while the machine stays on
Writes local filesYesNo — the bridge closes
Best forAnything touching local filesConnector-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 local tag. 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]

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.

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_20260301 for 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.

Try It

  1. 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.
  2. Test the phone→desktop handoff. Message Claude from mobile with a spreadsheet task; watch the execution happen on your desktop.
  3. 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.
  4. 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.
  5. Read the related deep dives: Cowork Plugins for the ecosystem; Cowork for Marketing for the marketing angle.

Graph View

Backlinks