Anthropic Cowork: What It Is and How Businesses Are Using It

What Cowork is -- the one-paragraph answer#

Anthropic Cowork is a desktop AI agent for knowledge workers. Unlike Claude.ai, which responds to prompts in a browser window, Cowork plans and executes multi-step tasks: reading local files, running browser actions, triggering connected services, and scheduling recurring workflows. It connects to external tools through a plugin and MCP connector system. Enterprise teams can deploy private plugin marketplaces and control which employees can access which integrations. It launched in January 2026 as a research preview with macOS support; Windows support followed on February 10, 2026, opening the platform to roughly 70% of the enterprise desktop market (VentureBeat, February 2026).

How Cowork differs from Claude.ai and Claude Code#

If you already use Claude.ai or Claude Code, Cowork is not a replacement for either. It's a different tool for a different job.

Claude.ai: conversational, browser-based, no file or app access#

Claude.ai is a chat interface. You send messages, Claude responds. It can help you think through problems, draft documents, analyze data you paste in, and answer questions. What it cannot do: read files from your computer, interact with your desktop apps, access your local calendar, or execute tasks on a schedule. Every session starts fresh.

Claude Code: terminal-native, built for software development#

Claude Code is an agentic development tool that runs in the terminal. It reads codebases, edits files, runs commands, and executes multi-step development workflows autonomously. It is built for engineers working on code.

Cowork: desktop agent for knowledge workers#

Cowork is the desktop layer. It runs as a native application on your Mac or Windows machine, can see and interact with your local files and applications, connects to cloud services through a structured plugin system, and executes tasks on your behalf. The target user is not a developer -- it's the operations manager, financial analyst, account executive, or HR lead who spends significant time on repetitive, multi-step knowledge work.

The key architectural difference: Cowork has access to your desktop environment. It can open files, fill forms, navigate web apps, and trigger actions in applications it can see on your screen, without needing those applications to have a supported API.

What Cowork can do out of the box#

Reading and editing local files across formats#

Cowork can open, read, and write files across common document formats: PDFs, Word documents, Excel spreadsheets, plain text, and more. A typical workflow: "Read all of the contract PDFs in this folder, extract the key dates and renewal terms, and create a summary table in a new spreadsheet."

This doesn't require the document to be in a specific format or for you to upload it anywhere. Cowork works with files on your local filesystem directly.

Browser automation: filling forms, pulling data, navigating web apps#

Cowork can control your browser -- filling forms, navigating web interfaces, pulling data from pages, and completing multi-step web workflows. This matters most for tools that lack strong API coverage, where the web interface is the only real way in.

Scheduled tasks: daily summaries, weekly reports, recurring document monitoring#

Cowork supports scheduling. You can configure it to run a workflow every morning (produce a summary of overnight emails and flag urgent items), every Friday afternoon (pull data from connected services and compile a weekly status report), or on any schedule that fits your team's rhythm.

Scheduled tasks run without manual triggering -- the agent wakes up, executes the workflow, and delivers the output to wherever you've directed it.

Default connectors: Google Drive, Gmail, Slack, DocuSign, Salesforce, and more#

Cowork launched with a set of pre-built connectors to common business tools. As of Q1 2026, the available MCP connectors include:

Productivity and communication: Google Drive, Google Calendar, Gmail, Slack, WordPress

Sales and CRM: Salesforce, Apollo, Clay, Outreach, SimilarWeb

Finance and legal: FactSet, MSCI, DocuSign, LegalZoom, Harvey

These connectors give Cowork read and write access to the named services, within the permission scope you configure. The agent can query Salesforce for deal data, pull documents from Google Drive, send messages in Slack, and trigger DocuSign workflows, as part of a multi-step task, without you staying in the loop.

How plugins work#

What a plugin actually contains: skills, slash commands, sub-agent definitions#

A Cowork plugin is a packaged bundle of capabilities. It typically includes:

• Skills -- Predefined task templates for specific workflows (e.g., "Review a contract for risk flags," "Analyze a financial model for errors")
• Slash commands -- Quick-access commands that trigger specific skill workflows
• Sub-agent definitions -- Specialized agents configured for a domain (e.g., a legal review sub-agent, a deal analysis sub-agent)

Plugins are additive. Installing a finance plugin doesn't change how Cowork handles legal tasks -- it adds a new set of tools and skills for financial work alongside whatever else is configured.

Anthropic's open-source plugin library#

Anthropic launched Cowork with 11 open-source plugins. On February 24, 2026, it released 10 new department-specific plugins as part of its largest single update since launch (TechCrunch, February 2026). As of mid-March 2026, the public plugin library has over 20 plugins covering finance, legal, HR, engineering, and operations workflows.

All plugins in the public library have published source code -- you can review exactly what they do before installing them in your team environment.

Department-specific plugins: finance, legal, HR, engineering, operations#

The February 2026 update introduced plugins targeting specific business functions:

Finance: Financial modeling assistance, deal analysis, earnings research compilation, portfolio monitoring with FactSet and MSCI connectors

Legal: Contract review and risk flagging, matter research, compliance checklist workflows with LegalZoom and Harvey connectors

HR and operations: Resume screening and candidate comparison, onboarding checklist execution, recurring reporting workflows

Engineering: Code review assistance, documentation generation, incident response workflows with engineering tool connectors

Sales: CRM enrichment, prospect research compilation, follow-up sequencing with Apollo, Clay, and Salesforce connectors

Private plugin marketplaces: how enterprise admins curate and distribute plugins to their team#

The February 24, 2026 update also introduced private plugin marketplace support for enterprise admins (TechCrunch, February 2026). For larger teams, this is what makes Cowork actually deployable rather than a free-for-all.

A private marketplace lets IT admins:

• Curate which public plugins are approved for company use
• Publish internal plugins built for company-specific workflows
• Control which employee roles can install which plugins
• Audit plugin usage and access logs

Without this, every employee independently finds and installs plugins. With it, the IT team maintains a curated set of verified, approved tools that employees can install from a company-branded marketplace -- and the team keeps governance control as it scales.

How MCP connectors extend Cowork to your internal tools#

What MCP is and why it matters for enterprise integration#

The Model Context Protocol (MCP) is Anthropic's open standard for connecting AI systems to external tools and data sources. It defines a standardized way for an AI agent to discover what capabilities a connected service offers and call those capabilities during task execution.

For Cowork, MCP is the integration layer. Every connector in the marketplace is an MCP server. When you install the Salesforce connector, Cowork gains access to a set of defined Salesforce actions (query records, create tasks, update deals) that it can call as part of a workflow.

MCP was donated to the Linux Foundation in December 2025, making it an open governance standard co-founded with OpenAI and Block, with AWS, Google, Microsoft, Cloudflare, and Bloomberg as platinum members. The practical consequence: the ecosystem of compatible tools is growing across the industry, not just within Anthropic's own products.

The difference between Anthropic's native connectors and custom MCP connectors#

The connectors in Cowork's marketplace are Anthropic-developed or partner-developed integrations. They cover the tools that most knowledge-worker teams share: Google Workspace, Salesforce, Slack, DocuSign.

Most companies also have internal tools that aren't in the public marketplace: a proprietary CRM, an internal analytics platform, a custom project management system, a data warehouse. These require custom MCP connectors.

A custom MCP connector is a relatively lightweight piece of software: it wraps your internal API with the MCP protocol so Cowork can discover and call its functions. The connector defines what Cowork can do with that tool (read, write, specific operations) and what data it can access.

When you need a custom MCP connector built#

You need a custom connector when:

• Your team's most important data or workflows live in a tool not covered by the public marketplace
• Your Salesforce or HubSpot configuration is heavily customized and the generic connector doesn't surface the right fields and workflows
• You have internal systems -- data warehouses, custom CRMs, proprietary analytics tools -- that hold the data Cowork needs to actually be useful
• You're building department-specific automations that require combining internal data with external connectors in ways the default plugins don't support

How businesses are using Cowork right now#

Worth noting up front: Cowork launched in January 2026 and is under 10 weeks old as of mid-March. The use cases below are early adopters, not broad rollouts. According to a February 2026 CrewAI Enterprise Survey (a vendor survey, so take the number with appropriate skepticism), 65% of enterprises report active AI agent deployments in production, with 100% planning to expand. The appetite is real. Here's where Cowork specifically is showing up.

Finance teams: financial modeling, deal analysis, document review#

Finance teams are using Cowork for work that involves pulling data from multiple sources, running analysis, and producing a formatted output. The FactSet and MSCI connectors do the data retrieval the analyst would otherwise do manually. A typical workflow: pull this company's financials from FactSet, combine them with the internal model in this folder, flag discrepancies, produce a summary briefing.

Deal analysis -- reviewing pitch decks, extracting key terms, comparing structures across multiple documents -- is where the time savings are most obvious. Cowork reads the documents, applies the finance plugin's analysis framework, and produces structured output. It's faster than manual review, though you still need a human to decide what the output means.

Legal teams: contract review, compliance flagging, matter research#

The clearest fit is contract review workflows that previously required an associate to read through dozens of pages looking for specific clauses, risk flags, and non-standard terms. With the legal plugin and Harvey or LegalZoom connectors, Cowork reads contracts against a defined checklist, flags items that need attorney review, and produces a structured summary.

Compliance flagging -- checking documents or processes against regulatory requirements -- works similarly. The agent runs against a specific compliance framework; new documents get checked against it as part of an intake workflow. The value is consistency, not judgment.

HR and operations: resume screening, onboarding workflows, recurring reporting#

HR teams are using Cowork for candidate screening: read this batch of resumes, score them against these criteria, produce a ranked shortlist with notes. It's first-pass triage, not a hiring decision. The candidates worth a closer look surface faster; the rest stay in the pile.

Onboarding is a good fit too -- generating personalized checklists, scheduling meetings, sending intro messages, setting up access requests. These steps are well-defined and repetitive, which is exactly what Cowork handles well.

Operations teams are using recurring reporting: pull data from connected services, compile into a standard format, deliver by a set time each week. Low drama, reliably done.

Sales: CRM enrichment, prospect research, follow-up sequencing#

Sales reps know they should research prospects and keep the CRM current. They also know it takes time away from selling. Cowork can research a prospect using SimilarWeb and Apollo connectors, enrich the Salesforce record, and draft a personalized follow-up -- as a background task. The rep gets the output without doing the legwork.

Enterprise controls: what IT and security teams need to know#

Admin controls: per-user provisioning, company branding, Customize feature#

Enterprise admins can:

• Configure which users have access to which plugins and connectors
• Brand the Cowork interface with company identity for consistent employee experience
• Use the Customize feature to configure agent persona, default behaviors, and approved tool scopes

Zero data retention, SSO, and audit logging on Team and Enterprise plans#

Claude Team and Enterprise plans include zero data retention -- inputs and outputs are not stored or used for training. SSO integration (via SAML) allows the IT team to manage Cowork access through their existing identity provider. Audit logging captures agent actions, tool calls, and accessed resources for compliance review.

OpenTelemetry support for tracking usage and tool activity#

Cowork supports OpenTelemetry for usage monitoring and observability. This means you can pipe Cowork's agent activity into your existing observability stack -- Datadog, Honeycomb, Grafana -- alongside the rest of your infrastructure telemetry. For compliance and security teams, this is the mechanism for tracking what the agent accessed, when, and what it did with it.

Folder-level sandboxing and how Cowork's security model works#

Cowork operates within the folder scopes you define. The agent can only read and write files within the directories you've authorized. This sandboxing is enforced at the configuration level -- the agent cannot access files outside the defined scope even if a task prompt asks it to.

For IT teams evaluating whether to allow Cowork access to sensitive document stores, this folder-level scope definition is the primary security control at the filesystem level.

Where the default setup falls short#

Cowork launched in January 2026. The public connector library and plugin marketplace cover the obvious cases well. The gaps are predictable.

Internal tools. Your most important proprietary systems almost certainly aren't in the public connector library. Getting Cowork to actually work with how your team operates requires custom MCP connectors for internal tools. This is engineering work, not configuration work.

Custom plugins. The public plugins cover generic departmental workflows. A finance plugin shaped around how your specific team works -- your data structure, your analysis framework, your output format -- requires a custom build. The plugin format is documented and open, but building something well-structured requires understanding both the workflow and the MCP architecture.

Integration with existing automation. Most companies already have some automation in place. Getting Cowork to work alongside Zapier workflows, internal scripts, or enterprise automation platforms requires intentional integration design, not just installing connectors.

Silverthread Labs builds custom Cowork plugins and MCP connectors for teams that need to go beyond the default marketplace. If your workflows depend on tools that aren't in the public library, or if the generic plugins don't match your actual processes, reach out through our audit page to talk through what a custom build would look like.

Frequently Asked Questions#

What is the difference between Cowork and Claude.ai?

Claude.ai is a browser-based chat interface -- you send messages, Claude responds, nothing is saved between sessions, and Claude has no access to your files or applications. Cowork is a desktop agent -- it runs as a native app, can access your local files and applications, executes multi-step tasks autonomously, connects to external services through a plugin and MCP system, and supports scheduled recurring workflows.

Does Cowork work on Windows?

Yes. Windows support launched on February 10, 2026, with full feature parity to macOS (VentureBeat, February 2026).

What is an MCP connector in Claude Cowork?

An MCP connector is a program that connects Cowork to an external service using the Model Context Protocol. It defines what Cowork can read and do within that service -- for example, a Salesforce MCP connector defines specific Salesforce operations (query contacts, create tasks, update deals) that Cowork can call during task execution. Anthropic provides connectors for major SaaS tools; custom connectors can be built for internal systems.

How do enterprise admins control what Cowork can access?

Enterprise admins configure folder-scope permissions (which directories the agent can read/write), connector access (which plugins and MCP connectors each user role can install), and audit logging. A private plugin marketplace feature allows admins to curate a company-approved set of plugins that employees can install, rather than having employees independently install from the public library.

Is Cowork the same as computer use agents?

Cowork builds on computer use capabilities but is a product layer on top, not raw computer use. Computer use is Anthropic's capability that lets Claude perceive a screen and execute clicks and keystrokes in any application. Cowork adds structure on top of that capability: plugins, skills, MCP connectors, a permissions model, and a plugin marketplace -- making the capability deployable in a governed, organized way rather than as a raw API. For a deeper look at how computer use agents work, see Computer Use Agents: How AI Is Learning to Use Your Desktop.

Gartner projects 40% of enterprise applications will embed task-specific AI agents by end of 2026, up from less than 5% in 2025 -- is Cowork part of that trend?

Yes, and no. Cowork is Anthropic's desktop-side answer to the enterprise agent category, and the Gartner number covers the broader market -- Cowork is one platform among several. What's worth knowing specifically about Cowork: it connects through MCP rather than replacing existing systems, and MCP is now an open governance standard with major cloud vendors as members, so the integration ecosystem will keep growing outside Anthropic's control. Whether that makes it better or just more interconnected is something each team will have to figure out.