Anthropic Claude Cowork
YouTube ... Quora ...Google search ...Google News ...Bing News
- Agents/Assistants ... Robotic Process Automation ... Personal Companions ... Productivity ... Email ... Negotiation ... LangChain ... Memory
- OpenAI dots | OpenAI ... ChatGPT
- Google Gemini Spark | Google ... Gemini ... Gemini Enterprise Agent Platform, Google Antigravity
- Anthropic Claude Cowork | Anthropic ... Claude ... Claude Code, Claude Agent SDK
- Microsoft Copilot Autopilot | Microsoft ... Bing/Copilot ... Copilot Cowork, Researcher with Computer Use, Copilot Studio
- Apple Siri AI | Apple ... Apple|Siri, Apple Intelligence
- Meta Muse | Meta ... Muse Code, Muse Spark
- Perplexity Computer | Perplexity ... Comet Assistant, Agent API
- You Research Agent | You ... ARI
- Grok Bot | Grok ... xAI, Grok Automations
- Baidu Qianfan Agent Development Platform | | Baidu ... Ernie, Wenxin AgentBuilder
- DeepSeek Harness | DeepSeek ... DeepSeek Tool Calls
- Alibaba Qwen | Alibaba ... Qwen Code, Qwen-Agent, Agent-Native Cloud
- Groq ... agent-framework integrations
- phind ... no comparable persistent first-party agent currently identified
- Get started with Claude Cowork | Claude Help Center ... Official guide.
- Release notes | Claude Help Center ... Dated history of Cowork features.
- Claude Cowork and chat are one Claude | Claude Help Center ... September 16, 2026 merger.
- Schedule recurring tasks in Claude Cowork | Claude Help Center
- Agent Skills | Open standard ... The skills format Cowork uses, adopted across AI platforms.
- First impressions of Claude Cowork, Anthropic's general agent | Simon Willison
- Anthropic Claude wants to be your helpful colleague | The Register
- Anthropic updates Claude Cowork tool built to give the average office worker a productivity boost | CNBC
- Anthropic merging Claude Cowork with chat | Zac Hall - 9to5Mac
- Anthropic merges Claude chat and Cowork in one interface | TechCrunch
Claude Cowork is Anthropic's general-purpose agent for knowledge work. It brings the highly capable agentic architecture behind Claude Code to everyday office tasks, with no terminal or programming experience required. By abstracting complex API calls and file-system navigation into a conversational interface, Cowork allows users to simply describe an outcome. Cowork then translates that natural language request into a series of executable steps, managing the entire lifecycle of the task.
When you describe an outcome, Cowork executes the following core behaviors:
- Works with your files and tools: It reads, edits, and creates files in folders you grant access to, and works seamlessly through connected apps such as Google Drive, Gmail, Microsoft 365, and DocuSign. This is not merely reading text; Cowork understands document structures, spreadsheet formulas, and presentation layouts, allowing it to manipulate data natively within those formats.
- Splits up big jobs: When presented with a massive, multi-faceted project, Cowork does not attempt to process the entire request in a single linear thread. Instead, it utilizes a recursive task-decomposition algorithm. It breaks large projects into discrete, manageable subtasks, evaluates the dependencies between them, and runs independent pieces in parallel using concurrent agent threads.
- Shows its work: Transparency is a core design principle of the Cowork interface. As the agent operates, you see exactly what Claude is planning and doing through a real-time execution log. This log exposes the agent's internal chain of thought, the specific tool calls it is making, and the raw data it is retrieving. You can actively steer it or let it run on its own.
- Keeps going: It runs scheduled tasks and continues working in the cloud after you close your laptop. This asynchronous capability transforms the AI from a synchronous chatbot into a persistent digital employee that can monitor inboxes, compile end-of-day reports, and trigger alerts without human intervention.
Anthropic launched Cowork as a research preview on January 12, 2026, made it generally available on April 9, 2026, and brought it to the web and mobile in July. On September 16, 2026, Anthropic began merging Cowork into the main Claude experience. Users no longer choose a "Cowork" mode: Claude dynamically decides whether a request needs a quick conversational answer or a longer, multi-step agentic job based on the complexity of the prompt.
- The Mechanism: Cowork uses the exact same underlying agentic architecture as Claude Code, built natively on the Claude Agent SDK, but wrapped in a friendlier, consumer-facing interface. Its execution model has evolved significantly over its lifecycle:
- At launch: It ran locally in an isolated virtual machine on your computer, utilizing a strict folder-permission model. Users granted read, write, and create access to specific directories, and Claude could also use local Model Context Protocol (MCP) integrations to interact with desktop applications safely.
- Since July 2026 (beta): Sessions run remotely in an highly secure, isolated environment on Anthropic's servers, completely separate from your local computer and corporate network. Sessions and files are saved to your Claude account and follow you across devices, enabling true cross-platform continuity.
When a task contains independent subtasks, Cowork spawns multiple Claude instances that run concurrently and then combines the results into a unified output. It extends its capabilities through:
- Skills: reusable workflows authored in the open Agent Skills format, allowing users to define standard operating procedures for the AI.
- Connectors: authenticated links to business apps and data silos, managing OAuth tokens securely.
- Plugins: comprehensive bundles of skills, connectors, slash commands, and specialized sub-agents tailored for specific roles or teams (such as a Legal Review Plugin or a Financial Audit Plugin).
- The Physics: Giving an autonomous agent real access to files and accounts trades convenience against significant security risks. Anthropic engineered several physical and algorithmic safeguards:
- Prompt injection: Anthropic launched Cowork with explicit cautions regarding prompt injection attacks. It advised users not to grant access to local files containing sensitive information, and to strictly limit Claude in Chrome to trusted websites to prevent malicious instructions hidden in web pages from hijacking the agent.
- Layered defenses: Anthropic says it uses advanced reinforcement learning from human feedback (RLHF) to train Claude to refuse malicious instructions. This is augmented by secondary classifier models that act as a firewall, attempting to catch malicious content or unauthorized data exfiltration attempts before they reach the primary model.
- Permission by default: In the merged Claude experience, Claude asks for explicit human permission before taking any destructive or high-stakes action (like sending an email or deleting a file) by default, ensuring a human-in-the-loop safety net.
- Cloud by default: On October 6, 2026, new Cowork tasks on Pro and Max plans will run in the cloud, and the "Only on your computer" option will be removed. Tasks already started locally stay there, reflecting a shift toward centralized compute and security monitoring.
- Why This Matters: Cowork successfully moved agentic AI from the domain of developers to general office workers, democratizing complex automation.
- Market impact: Its January launch rattled software stocks, as investors weighed AI's potential to disrupt existing business software and traditional robotic process automation (RPA) vendors.
- Real usage: In a sample of 1.2 million anonymized Cowork sessions, Anthropic found the largest share (33.4%) involved business process and operations work, and 16.4% involved producing decks, documents, and proposals, proving its utility beyond simple coding tasks.
- Open ecosystem: Anthropic released its launch plugins as open source, and the Agent Skills format behind Cowork's extensibility has been adopted beyond Anthropic's own products, creating a standardized way to teach AI new workflows.
- Competitive pressure: Rivals followed quickly. Microsoft shipped its own Copilot Cowork and redesigned Copilot partly to compete with Anthropic (see Microsoft Copilot Autopilot).
- Enterprise focus: Enterprise customers account for roughly 80% of Anthropic's business, and Cowork added robust admin controls, detailed analytics, and enterprise-grade connectors to match the strict compliance requirements of Fortune 500 companies.
Recent Developments
January 2026: Initial Research Preview
On January 12, 2026, Anthropic launched Cowork as a research preview for Max subscribers in the macOS Claude Desktop app, running in a local isolated VM. Anthropic noted that the tool was built in about a week and a half, largely by Claude Code itself, demonstrating remarkable self-hosting capabilities. The initial pass rates on internal multi-step reasoning benchmarks exceeded 82%, giving the team the confidence to release it to early testers. On January 16, 2026, the preview expanded to Pro subscribers. Late in the month, Anthropic added plugin support, featuring 11 open-source plugins at launch, establishing the foundation for community-driven extensibility.
February 2026: Platform Expansion and Enterprise Launch
Cowork expanded rapidly across platforms and user tiers. On February 10, Cowork came to Windows, utilizing a specialized Hyper-V sandbox for local execution. On February 12, self-serve Enterprise plans launched, bundling Claude, Claude Code, and Cowork into a single unified seat license. By February 24, Anthropic introduced a plugin marketplace equipped with admin controls for Team and Enterprise users, alongside official connectors for Google Drive, Gmail, DocuSign, and FactSet. On February 25, scheduled tasks were introduced, allowing users to set up recurring or on-demand tasks, managed through a new Customize section for skills, plugins, and connectors.
- Anthropic updates Claude Cowork tool | CNBC Venue note.
March 2026: Dispatch and Computer Use Previews
March saw the introduction of highly requested autonomous features. Dispatch launched on March 17, providing a persistent agent thread that users could message from their mobile phones to assign Cowork tasks asynchronously. On March 23, the computer use feature arrived as a research preview for Pro and Max users. This allowed Claude to open files, run local tools, and physically point, click, and navigate on the user's screen using computer vision and coordinate mapping, bridging the gap between API-driven tasks and legacy GUI applications.
April 2026: General Availability
On April 9, 2026, Cowork officially exited the research preview phase and became generally available on macOS and Windows. This release included robust infrastructure upgrades, notably adding Analytics API and OpenTelemetry support for enterprise monitoring. Furthermore, Enterprise plans gained granular role-based access controls (RBAC), allowing IT administrators to restrict specific agent capabilities based on user departments or security clearances.
June to August 2026: Cloud Transition and Security Upgrades
On June 12, 2026, Anthropic introduced inline editing, allowing users to edit Claude's drafts in place by highlighting text and describing the desired change. On July 7, 2026, Cowork expanded to the web and mobile platforms. Sessions began running remotely in beta, meaning work could continue with the laptop closed and scheduled tasks could execute without any local device being online. During this period, Anthropic shared usage data from 1.2 million Cowork sessions, validating the product's market fit. In August, Enterprise plans gained automated skill and plugin security scanning (August 6), and persistent memory began working seamlessly across chat and Cowork in the cloud (August 25).
September 2026: The Great Merger
September marked a structural shift in how users interacted with the AI. On September 15, a Salesforce in Claude plugin featuring 37 distinct sales skills launched in beta. On September 16, Anthropic began merging Cowork and standard chat into one unified Claude experience. This update also launched Claude Docs and Claude Slides in beta, with Claude Design moving directly into conversations. Finally, on September 25, a developer portal opened for submitting third-party plugins to the official public Claude directory.
What Remains Under Investigation
Despite rapid feature deployment, several technical frontiers remain under active investigation by Anthropic and independent researchers. Multi-turn consistency over extended timeframes (e.g., a scheduled task running daily for a month) occasionally suffers from context degradation. The boundaries of authority delegation are also being tested, specifically regarding how the agent handles expired OAuth tokens during a long-running asynchronous task without halting the entire workflow. Finally, the efficiency of the computer use vision models is being optimized to reduce the latency between screen observation and cursor action.
Technical Architecture
Evolution from Claude Code to Claude Cowork
The architectural foundation of Claude Cowork is a direct evolution of Claude Code, Anthropic's developer-centric agent. Claude Code operated primarily through a read-eval-print loop (REPL) in the command-line interface, requiring users to understand terminal commands, environment variables, and local pathing. It was highly effective but fundamentally inaccessible to non-technical users.
Claude Cowork abstracts this CLI architecture into a visual, cloud-synced workspace. The core transition involved replacing the terminal REPL with a rich graphical interface that parses natural language into the same underlying system commands.
- File-System Interactions: In Claude Code, the agent interacted directly with the host OS file system. Cowork introduced a dual-mode file system architecture. In local mode, it utilizes a restricted, chroot-like virtualized environment to prevent the agent from accessing unauthorized directories. In cloud mode, it utilizes ephemeral, containerized storage volumes that spin up for the duration of the task and sync state back to the user's persistent Claude account.
- Business Tool Integration: Where Claude Code relied on developers writing custom Python scripts to hit APIs, Cowork introduced a standardized API translation layer. This layer handles OAuth2 token lifecycle management natively. When a user connects Google Drive, Cowork securely stores the refresh tokens and automatically injects short-lived access tokens into the agent's context window only when a specific tool call requires it, minimizing the risk of token leakage.
System Components and Failure Modes
The architecture relies on several interconnected subsystems to maintain state, execute actions, and ensure safety.
| Component | Responsibility | Known Failure Modes to Test |
|---|---|---|
| Orchestration Engine | Manages the OODA loop (Observe, Orient, Decide, Act). Spawns concurrent sub-agents for parallel tasks and aggregates their outputs. | Deadlocks during parallel execution if sub-agents require the same locked file; context window overflow if too many sub-tasks return massive data payloads simultaneously. |
| Context Manager | Maintains the state of the conversation, active files, and memory topics across sessions. | Hallucination of file contents if the document exceeds the token limit and is improperly chunked; failure to recall user preferences stored in older memory topics. |
| Tool Execution Sandbox | Provides an isolated environment (local VM or cloud container) for the agent to run code, format documents, or execute API calls. | Timeout errors on long-running API requests; memory exhaustion within the container if the agent attempts to process excessively large datasets in memory. |
| Safety Classifier Firewall | Intercepts all outgoing tool calls and incoming data to scan for prompt injection, data exfiltration, or policy violations. | False positives blocking legitimate business workflows (e.g., blocking a legal contract review because it contains sensitive terms); latency overhead added to every tool invocation. |
Technologies Implemented
Agent Skills and Plugins Ecosystem
The extensibility of Claude Cowork is driven by the Agent Skills and Plugins ecosystem. Rather than hardcoding every possible integration, Anthropic adopted the open Agent Skills standard (agentskills.io). This allows developers to write declarative YAML or JSON files that define exactly what a tool does, what inputs it requires, and what outputs it produces, which the Claude Agent SDK then translates into native model tool-calling formats.
- The Claude Agent SDK: This is the underlying engine powering the ecosystem. It is a robust library that handles the complex state management required for multi-step agentic workflows. It standardizes how the model requests a tool, how the system executes that tool, and how the result is fed back into the model's context window, complete with error handling and retry logic.
Structured Capabilities Matrix:
| Connector / Plugin | Supported Modalities | Scheduled Task Capabilities | Execution Environment |
|---|---|---|---|
| Google Workspace | Docs, Sheets, Gmail, Drive | Automated daily inbox triage; weekly metric aggregation from Sheets to Docs. | Cloud API (OAuth2) |
| Microsoft 365 | Word, Excel, Outlook, OneDrive | End-of-day calendar summaries; automated drafting of responses to flagged emails. | Cloud API (OAuth2) |
| Salesforce (Beta) | CRM Records, Lead Data, Reports | Daily pipeline updates; automated lead enrichment and logging. | Cloud API (OAuth2) |
| Local Computer Use | Screen Vision, Mouse/Keyboard Control | Automated data entry into legacy desktop applications without APIs. | Local Hyper-V / macOS Sandbox |
| Custom Internal APIs | REST, GraphQL, SOAP | Scheduled database queries; automated internal system health checks. | Hybrid (via local MCP or Cloud) |
Enterprise Controls and Security
To meet the stringent requirements of enterprise deployments, Claude Cowork implements a comprehensive suite of administrative and security controls. This ensures that while the agent is autonomous, it operates strictly within the boundaries defined by corporate IT policies.
- Administrative Oversight: Team and Enterprise admins have access to a centralized dashboard. From here, they can utilize an admin toggle to turn Cowork features on or off globally or for specific organizational units. The dashboard integrates with OpenTelemetry and an Analytics API, allowing security teams to ingest agent activity logs directly into their existing SIEM (Security Information and Event Management) tools like Splunk or Datadog.
- Permission Management (SCIM): Access is not managed manually. Cowork integrates with identity providers (like Okta or Microsoft Entra ID) via SCIM (System for Cross-domain Identity Management). This allows role-based access controls (RBAC) to sync automatically. If an employee changes departments, their Cowork agent instantly loses access to the previous department's plugins and data silos.
- Security Protocols for Computer Use: The computer use feature is heavily sandboxed. Admins can enforce restricted domain lists, preventing the agent from navigating to unauthorized websites. Furthermore, the vision model incorporates pixel-level redaction capabilities, automatically blurring sensitive information (like passwords or personal identifiable information) before the screenshot is processed by the cloud model, ensuring data privacy even during autonomous GUI navigation.
- Private Plugin Marketplaces: Organizations can run private plugin marketplaces, ensuring that proprietary internal tools are not exposed to the public directory. Admins can also enforce mandatory security scanning for any third-party skills before they are approved for employee use.
Building Blocks
| Component | What It Does | Notes |
|---|---|---|
| Folders and files | Claude reads, edits, and creates files you give it access to, including documents, spreadsheets, PDFs, and slides. | Launched with a folder-permission model. Files are now saved to your Claude account in cloud sessions, ensuring cross-device continuity. |
| Connectors | Links to tools such as Google Drive, Gmail, DocuSign, FactSet, and Microsoft 365. | The Microsoft 365 connector gained write tools in July 2026 for email, calendar, OneDrive, and SharePoint. Teams remains read-only due to API limitations. |
| Skills and plugins | Package repeatable workflows, connectors, slash commands, and sub-agents for a role or team. | 11 open-source plugins at launch. Organizations can run private plugin marketplaces, and a developer portal for the public Claude directory opened in September 2026. |
| Scheduled tasks | Run recurring or on-demand work automatically, such as morning briefs or weekly reports. | Available on all paid plans. Tasks run remotely, so they continue while your computer is asleep or disconnected from the network. |
| Dispatch | A persistent agent thread you can message from your phone to assign Cowork tasks. | Research preview for Pro and Max, launched March 2026. Acts as a mobile command center for asynchronous workflows. |
| Computer use | Claude can open files, run tools, and point, click, and navigate on your screen. | Research preview for Pro and Max, launched March 2026. Utilizes advanced vision-to-action coordinate mapping. |
| Memory | Claude remembers context across chat and Cowork, listed as editable Topics in Settings. | On by default for Free, Pro, and Max, and off by default for Team and Enterprise to comply with strict corporate data retention policies. |
| Docs, Slides, and Design | Create living documents, presentations, and visual designs inside any conversation. | Added with the September 2026 merger. Docs and Slides are in beta, providing a native workspace alternative to Google Workspace or Office. |
Ecosystem Fit
Claude Cowork occupies a unique position in the AI ecosystem, bridging the gap between highly technical developer frameworks (like LangChain or AutoGPT) and rigid, deterministic automation tools (like Zapier or traditional RPA). By leveraging the reasoning capabilities of the Claude model family, it provides a probabilistic, goal-oriented automation platform that can handle edge cases and unstructured data that would break traditional scripts.
Getting Started
- Plans: Cowork is available exclusively on paid tiers: Pro, Max, Team, and Enterprise. It is not included on the Free plan due to the high compute costs associated with agentic loops.
- Where to use it: Use the Claude Desktop app on macOS or Windows 10 or later, claude.ai on the web, or the iOS and Android apps. Web and mobile access are currently in beta.
- Start a task: In the new merged Claude experience, simply describe the task in any conversation and Claude dynamically takes it from there. In the older legacy experience, users must select the Cowork toggle in the message box first. Either way, review Claude's proposed approach in the execution log, then let it run.
- Give it context: Grant explicit access to the folders and connectors the task needs. Add specific skills and plugins from the Customize section to tailor the agent's capabilities to the task at hand.
- Automate: Open the "Scheduled" tab in the sidebar to create recurring or on-demand tasks using natural language (e.g., "Run this report every Friday at 4 PM"). Review past and upcoming runs in the dashboard.
- Work from anywhere: Use the Dispatch feature to hand Cowork tasks to Claude directly from your smartphone, allowing you to initiate complex workflows while away from your desk.
- For admins: Team and Enterprise admins can manage the entire deployment through the centralized dashboard, handling SCIM provisioning, analytics, and security policies.
Known Limitations
- A product in transition: The merger into one unified Claude experience is rolling out gradually. Pro and Max users received the update first, with no announced date for Team and Free plans. Enterprise admins are guaranteed at least 30 days' notice before structural changes reach their organizations to allow for internal training. Claude Code remains a separate, dedicated product for software engineers.
- Cloud sessions are in beta: Remote execution on web and mobile is still labeled beta. The October 6, 2026 shift to cloud-by-default may present compliance challenges for users or organizations who preferred strict local-only processing for sensitive data.
- Security caveats: Anthropic explicitly warns that agents with broad file and browser access remain exposed to sophisticated prompt injection attacks. They advise against granting the agent access to highly sensitive files unless absolutely necessary.
- Preview features: Computer use and Dispatch remain research previews, meaning they may exhibit unexpected behavior or latency. Docs and Slides are in beta, and are strictly off by default on Enterprise plans until an organization owner explicitly turns them on.
- Paid plans only: Free users cannot access Cowork features.
Practical Workflow Examples
To understand the ecosystem fit, consider these testable workflows:
- Automated Quarterly Business Review (QBR) Generation:
- *Input:* "Read the Q3 sales data from the connected Salesforce plugin, cross-reference it with the marketing spend in the Google Sheet 'Q3 Budget', and generate a 10-slide Claude Slides presentation summarizing the ROI."
- *Acceptance Criteria:* The agent successfully authenticates with both platforms, accurately extracts the data, performs the necessary ROI calculations, and formats a coherent presentation without hallucinating figures.
- Inbox Triage and Drafting:
- *Input:* "Every morning at 8 AM, scan my Microsoft 365 inbox for emails from the 'Legal' department. Draft polite responses acknowledging receipt and summarizing the key action items, but save them as drafts for my review."
- *Acceptance Criteria:* The scheduled task triggers reliably, correctly filters the emails, generates accurate summaries, and successfully utilizes the write-access connector to save drafts without sending them autonomously.
How to Evaluate a Deployment
When evaluating Claude Cowork for enterprise deployment, organizations should structure their testing around these dimensions:
| Evaluation Dimension | Questions to Verify | Evidence to Request |
|---|---|---|
| Authentication & Authorization | Does the agent respect existing SCIM roles? Are OAuth tokens handled securely? | Audit logs showing token lifecycle; demonstration of access denial when a user switches departments. |
| Task Decomposition Accuracy | Can the agent break down a 10-step workflow without losing context by step 7? | Execution logs of complex tasks; pass/fail rates on internal standardized workflows. |
| Interruption Handling | If a user interrupts the agent mid-task to provide a correction, does it seamlessly integrate the feedback? | Live demonstration of steering the agent during a long-running data compilation task. |
| Failure Classification | When a task fails, is it due to API timeouts, context window limits, or model hallucination? | OpenTelemetry dashboards categorizing error codes and failure points. |
Glossary
- Agentic Architecture
- A system design where the AI model is given autonomy to plan, use tools, and execute multi-step workflows in a loop, rather than just generating text in a single pass.
- Dispatch
- Anthropic's mobile interface feature that allows users to initiate and monitor long-running Cowork tasks asynchronously from their phones.
- Model Context Protocol (MCP)
- An open standard that allows AI models to securely interface with local desktop applications and file systems.
- Prompt Injection
- A security vulnerability where malicious instructions embedded in a file or webpage trick the AI agent into executing unauthorized actions.
- SCIM (System for Cross-domain Identity Management)
- An open standard for automating the exchange of user identity information between identity domains, used by Cowork for enterprise permission syncing.