Claude Cowork: Complete Beginner's Guide (Setup, Plugins, Connectors & More)

This is a comprehensive beginner's guide for getting the most out of Claude Cowork. Whether you're a marketer, operations lead, analyst, or founder — if you do knowledge work on a computer, Cowork can handle significant chunks of it for you. This guide covers everything from first-time setup to building automated workflows with plugins and connectors.

What is Claude Cowork?

Claude Cowork is Anthropic's agentic productivity tool built into the Claude Desktop app. It turns Claude from a chatbot into a digital coworker that can read your files, create documents, research the web, and execute multi-step tasks on your computer — all without writing a single line of code.

Unlike standard Claude chat where you go back and forth one message at a time, Cowork can take initiative. Ask it to organize your downloads folder, turn meeting notes into a formatted report, or research competitors and build a comparison spreadsheet — and it will plan the work, execute across multiple steps, and deliver finished output directly to your file system.

Why use Claude Cowork?

In regular Claude chat, you paste content in and copy answers out. In Cowork, you describe what you want done, point Claude at your files, and supervise while it does the work. It can read entire folders, create polished Excel spreadsheets with working formulas, build PowerPoint presentations, and coordinate complex research — the kind of work that normally takes hours of manual effort.

If Claude Code is built for developers, Cowork is built for everyone else. For a detailed side-by-side breakdown, see Claude Code vs Claude Cowork.

1. Setup and Installation

Getting started with Cowork takes about five minutes. You need the Claude Desktop app and a paid subscription.

What You Need

1. Claude Desktop app — download from claude.ai/download
2. Paid Claude subscription — Pro ($20/month), Max ($100-200/month), Team, or Enterprise

Cowork is available on macOS and Windows (x64). If you're on Windows with an ARM processor, you'll need to wait for ARM support.

How to Install

Mac:

1. Go to claude.ai/download and download the macOS installer
2. Open the .dmg file and drag Claude to your Applications folder
3. Launch Claude Desktop and sign in with your paid account

Windows:

1. Go to claude.ai/download and download the Windows installer
2. Run the installer and follow the prompts
3. Launch Claude Desktop and sign in

Switching to Cowork Mode

Once Claude Desktop is open, you'll see tabs at the top of the window: Chat, Cowork, and Code. Click Cowork to switch modes.

That's it. You're in Cowork.

2. Getting Started

Your First Task

The best way to learn Cowork is to give it something real to do. But start with a test folder — don't point it at critical files while you're still learning.

1. Create a folder called Claude_Test in your Documents
2. Add a few non-sensitive files — old documents, sample spreadsheets, random notes
3. In Cowork, grant access to this folder when prompted
4. Try a simple task: "Organize these files by topic and create a summary document listing what's in each category"

Claude will analyze your files, create a plan, and execute it. You'll see its progress in real time and can steer it if needed.

Granting Folder Access

Cowork runs inside an isolated virtual machine on your computer for safety. It can only access folders you explicitly grant permission to. When you start a task that involves files, Claude will ask which folders it can work with.

What Cowork Can Do

Cowork excels at five categories of work:

3. Working With Cowork

How Tasks Work

When you describe a task, Cowork follows a consistent pattern:

1. Analyzes your request and asks clarifying questions if needed
2. Plans the work, breaking it into subtasks
3. Executes each subtask, often running multiple in parallel
4. Delivers output directly to your file system

You maintain visibility throughout. Cowork shows you what it's doing at each step, and you can redirect it mid-task if something isn't right.

Prompting Basics

Interacting with Cowork is similar to chatting with Claude, but with one key difference: you're describing outcomes, not asking questions.

Good prompts describe what you want done:

• "Take these 12 customer interview transcripts and extract the top 5 recurring themes with supporting quotes"
• "Create an Excel spreadsheet tracking our Q1 marketing spend by channel, with formulas for totals and month-over-month change"
• "Research the top 10 project management tools, compare features and pricing, and create a recommendation memo"

Less effective prompts are vague:

• "Help me with my files" (which files? what help?)
• "Do something with this data" (what output do you want?)

Approval Steps

Cowork asks for your approval before taking significant actions — especially anything that deletes files or accesses sensitive data. Review these carefully.

A good default: always tell Claude "don't delete anything" unless you specifically want deletions. This prevents accidental data loss while you're learning.

The Scope-Plan-Execute Flow

For complex work, the most reliable approach mirrors how you'd brief a new hire:

Scope: Start by having a conversation about what you need. Share context, show examples of good output, clarify constraints.

Plan: Ask Claude to write out its plan before executing. Review it. Adjust anything that looks off.

Execute: Once the plan looks right, tell Claude to proceed. Monitor the first few steps, then let it run.

This is iterative. After the first pass, review output, give feedback, and have Claude refine.

4. Instructions and Context Files

This is the single most important section of this guide. Cowork out of the box is mediocre. Cowork with proper context files is a different tool entirely. The gap between those two experiences is about 30 minutes of setup.

Why Context Files Matter

Cowork has no memory between sessions. Every conversation starts completely fresh. It doesn't know who you are, what your company does, or how you like things formatted. Without context, it produces generic output.

The fix is context files — documents that live in your project folders and tell Claude everything it needs to know to do good work.

Global Instructions

Navigate to Settings > Cowork and click Edit next to Global Instructions. These apply to every Cowork session regardless of which folder you're working in.

Good global instructions include:

# About Me

- Name: [Your name]
- Role: [Your role] at [Company]
- I prefer concise, direct communication

# Output Preferences

- Always use tables for comparisons
- Default to bullet points over paragraphs
- Include sources when citing research
- Save output files with descriptive names (not "output.xlsx")

# Safety

- Never delete files without asking first
- Always confirm before sending any emails or messages

Folder Instructions

When you grant Cowork access to a folder, you can add folder-specific instructions. These act like a project brief that Claude reads at the start of every session involving that folder.

For example, a marketing folder might include:

# Marketing Team Context

- Brand voice: Professional but approachable. Never use jargon.
- Target audience: SMB founders (1-50 employees)
- Competitors: [list]
- Style guide: See brand-guidelines.pdf in this folder

# Common Tasks

- Weekly reports use the template in /templates/weekly-report.xlsx
- Blog drafts go in /drafts/ with the naming format YYYY-MM-DD-title.md

What to Include in Context Files

5. Skills

What Are Skills?

Skills are written instructions that teach Claude how to do something specific. Think of them as SOPs (Standard Operating Procedures) that Claude follows when it encounters a matching task.

A skill might teach Claude how to:

• Write blog posts in your company's voice
• Format financial reports following your template
• Run a specific research workflow step by step
• Prepare meeting agendas from your calendar

Skills are just Markdown files. No coding required. You describe the process in plain English, and Claude follows the instructions whenever the skill is relevant.

How Skills Work in Cowork

Skills live inside plugins (more on those in section 7). When you install a plugin, its skills become available to Claude automatically. You can also trigger skills explicitly using slash commands — type / followed by the command name.

For example, the open-source knowledge-work-plugins from Anthropic include skills for:

• Sales: Call prep, deal analysis, pipeline reviews
• Marketing: Content creation, competitive analysis, campaign planning
• Finance: Expense categorization, report generation, reconciliation
• Research: Literature reviews, market analysis, trend synthesis

Creating Your Own Skills

You don't need to be technical to create skills. The simplest approach:

1. Do a task manually with Claude once and get the output right
2. Ask Claude: "Turn what we just did into a reusable skill"
3. Claude generates the skill Markdown file
4. Install it as part of a plugin

For a deeper dive on skill design, see Agent Skills 101: Tools vs MCP vs Skills.

6. Connectors

What Are Connectors?

Connectors link Claude to external services and data sources. Without connectors, Cowork can only work with files on your computer and browse the web. With connectors, it can pull data from your CRM, post to Slack, query databases, and interact with dozens of business tools.

Connectors use the Model Context Protocol (MCP) — the same standard that powers tool integrations across the Claude ecosystem.

Available Connectors

Cowork supports connectors for many popular tools:

Setting Up Connectors

1. Open Claude Desktop and go to Settings > Connectors
2. Click Browse connectors to see what's available
3. Select a connector and follow the authentication flow
4. Once connected, Claude can access that service during Cowork tasks

Using Connectors in Practice

Once a connector is set up, just reference it naturally in your tasks:

• "Pull our Q1 sales data from Salesforce and create a trend analysis"
• "Check Slack #marketing for messages about the product launch and summarize the key decisions"
• "Create a Jira ticket for each action item in these meeting notes"

Claude knows which connector to use based on context. You don't need to specify technical details.

7. Plugins

What Are Plugins?

Plugins are bundles that package skills, connectors, slash commands, and sub-agents together into a single installable unit. If skills are individual SOPs, plugins are entire departments.

A sales plugin might include:

• Skills: How to research accounts, prepare for calls, write follow-up emails
• Connectors: CRM integration, LinkedIn data, email
• Slash commands: /sales:call-prep, /sales:deal-review, /sales:pipeline
• Sub-agents: Specialized Claude instances for specific sub-tasks

Why Plugins Matter

Without plugins, you'd set up each skill, connector, and workflow manually. Plugins solve three problems:

1. Bundling — everything a workflow needs in one package
2. Sharing — install the same plugin on every team member's machine
3. Versioning — update the plugin when workflows change, rather than editing config files

Finding and Installing Plugins

Anthropic maintains an open-source repository of plugins at github.com/anthropics/knowledge-work-plugins. These cover common knowledge work tasks across sales, marketing, finance, and general productivity.

To install a plugin from the marketplace:

1. Open the plugin browser in Claude Desktop
2. Search or browse available plugins
3. Click to install

To install from the command line:

claude plugins add knowledge-work-plugins/sales

Plugin Structure

Under the hood, plugins are just folders containing Markdown files and a bit of JSON configuration:

my-plugin/
├── plugin.json          # Plugin metadata
├── mcp.json             # Connector configuration
├── commands/            # Slash commands
│   ├── call-prep.md
│   └── deal-review.md
└── skills/              # Skills and instructions
    ├── research.md
    └── email-drafting.md

You can inspect, edit, and customize any plugin after installing it. They're designed to be transparent and modifiable.

Building Custom Plugins

The fastest way to build a plugin is to use the cowork-plugin-management plugin (yes, there's a plugin for managing plugins). Install it, then ask Claude to help you create a new plugin for your specific workflow.

For the complete guide to building plugins, see Beyond Claude Code: Building a Shared Skill Library — the same principles that apply to Claude Code skills apply to Cowork plugins.

8. Scheduled Tasks

What Are Scheduled Tasks?

Scheduled tasks let Claude run workflows automatically on a recurring basis — daily reports, weekly data pulls, automated file organization, or any other repeatable task.

Setting Up a Schedule

Use the /schedule slash command inside any Cowork task to set up automation:

• "Generate a weekly expense summary every Monday at 9am from the receipts in my /finances folder"
• "Every Friday, compile a status report from my project notes and save it to /reports"

You can manage scheduled tasks from the Scheduled option in the Cowork sidebar.

Important Limitations

Scheduled tasks only run when:

• Your computer is awake (not sleeping or shut down)
• The Claude Desktop app is open

If your machine is off when a task is scheduled, it won't execute. For workflows that need to run 24/7 regardless of whether your computer is on, you need a cloud environment.

9. Common Workflows

Here are practical workflows that showcase what Cowork does best. Each can be set up in under 30 minutes.

File Organization

Point Cowork at a messy folder — your Downloads, Desktop, or a shared drive — and ask it to:

• Sort files by type, project, or date
• Rename files with consistent naming conventions
• Create an index document listing everything and where it went
• Identify and flag duplicates

Meeting Notes to Action Items

After a meeting, drop the transcript or your rough notes into a folder and ask Cowork to:

• Extract action items with owners and deadlines
• Create follow-up email drafts for each participant
• Update your project tracker (via connectors)
• Generate a formatted summary for stakeholders

Research and Analysis

Give Cowork a research question and let it:

• Search the web for relevant sources
• Synthesize findings into a structured report
• Create comparison tables with specific data points
• Generate charts and visualizations from the data

Expense Reports

Drop receipts (photos, PDFs, emails) into a folder and ask Cowork to:

• Extract vendor, amount, date, and category from each receipt
• Build an Excel spreadsheet with all expenses categorized
• Add formulas for subtotals by category and grand total
• Flag any potential duplicates or missing information

Competitive Intelligence

Ask Cowork to research competitors and it can:

• Analyze competitor websites, pricing pages, and feature lists
• Build a comparison matrix in Excel
• Identify gaps and opportunities
• Draft a memo with strategic recommendations

10. FAQ