Product: Claude Cowork URL: https://claude.com/product/cowork Source: Claude Cowork Product Page 2026 04 17
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. Was “ready for enterprise” 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 — enterprise availability (feature access management, spend control, usage tracking, admin toggle). 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. 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. Zapier (automation platform), Thomson Reuters (legal/media), Jamf (Apple device management). Jamf quote is the sharpest: a Cowork skill for performance reviews built in 45 minutes “faster than a custom React app.”
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
| Date | Feature | Notes |
|---|---|---|
| 2026-02-24 | Plugin marketplace | Private plugins + 10 new department plugins + 12 new MCP connectors + cross-app workflows. See 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 | Feature access management, spend control, usage tracking, OpenTelemetry streaming, admin org-wide disable toggle. |
Related
- Cross-Topic Connections — cross-topic synthesis comparing Cowork/Dispatch against Routines and Managed Agents with a decision framework
- 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
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. Enterprise page mentions OpenTelemetry but the product page does not clarify regional data residency commitments for Cowork workloads.
- 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?
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, confirm admin-side feature access controls meet your policy requirements, test spend tracking with a sample user, confirm the org-wide disable toggle.
- Read the related deep dives: Cowork Plugins for the ecosystem; Cowork for Marketing for the marketing angle.