From Chatting to Actually Working
Every AI chat tool until now has been a very capable consultant. Ask a question, get a great answer — but you still have to do the actual work yourself.
Claude Cowork changes that model.
Tell it "pull all the receipts from this folder and build an expense spreadsheet," and Claude opens the files, reads the data, generates the Excel, and saves it — start to finish, without you. You move on to something else.
This guide covers the full picture: how Cowork works, how to configure it, the three extension layers (Connectors, Skills, Plugins), safety practices, and a concrete walkthrough using a startup's accounting workflow.
Table of Contents
- What is Claude Cowork?
- How it differs from regular chat
- Requirements and setup
- Basic usage
- Global and folder-specific instructions
- Extension layer 1: Connectors (MCP)
- Extension layer 2: Skills
- Extension layer 3: Plugins
- Using it safely
- Practical example: Startup accounting
1. What is Claude Cowork? {#what-is-cowork}
Claude Cowork is a desktop AI agent from Anthropic, announced January 12, 2026.
It takes the "read files, reason, execute" capability that Claude Code gives developers and opens it up to non-technical users — business people who don't write code but still have repetitive knowledge work to automate.
As Anthropic's developer relations lead Alex Albert put it:
"The Claude Code moment for non-engineers is here. Cowork will become a new foundation for knowledge work."
The key distinction from chat: Cowork has direct filesystem access. It doesn't just tell you what to do — it does it, saves the output, and reports back.
2. How it differs from regular chat {#vs-chat}
| Chat | Cowork | |
|---|---|---|
| File access | Manual upload | Direct access to permitted folders |
| Task completion | Suggests / drafts | Generates and saves files |
| Multi-step work | You re-prompt each step | Plan → execute → deliver automatically |
| Parallel processing | Not possible | Runs sub-tasks concurrently |
| External tools | Limited | Broad via MCP connectors |
Chat is "ask and receive an answer." Cowork is "hand off a task and receive a finished deliverable."
3. Requirements and setup {#setup}
What you need
- Claude Desktop app (macOS or Windows)
- Paid plan: Pro, Max, Team, or Enterprise
- Note: Windows arm64 is not supported at this time
Getting started
- Install the desktop app from claude.com/download
- Click the "Cowork" tab at the top of the app
- Set folder access permissions on first launch
- Type a task and run it
4. Basic usage {#basic-usage}
Granting folder access
Enable the "Work in a Folder" checkbox in the prompt input area, then select the target folder. You can grant one-time access or "always allow" for a specific folder.
How a task runs
When you submit a task, Cowork follows this flow:
- Analyzes the request and creates a plan
- Breaks complex tasks into sub-tasks
- Executes work inside an isolated VM environment
- Runs multiple workstreams in parallel when possible
- Saves finished outputs to the filesystem
Progress is shown in real time. You can give feedback mid-task to redirect if needed.
Writing effective prompts
Bad:
"Organize the files."
Good:
"Read all receipt images (JPEG and PDF) in the expense folder
and create an Excel file with these columns:
- Date, Vendor, Subtotal (pre-tax), Tax, Total, Category (travel/meals/supplies)
Split into sheets by month.
Report a summary when done.
Do not delete any files."
The pattern: be explicit about output format, conditions, and constraints — especially the constraints.
5. Global and folder-specific instructions {#instructions}
When Windows support launched on February 10, 2026, two types of persistent instructions were added.
Global Instructions
Applied to every Cowork session automatically.
Where to set it: Settings → Cowork → "Edit" next to Global instructions
Example:
I'm handling accounting for a small startup.
- All output files should be in English
- Use USD ($) for all amounts
- Always include SUM and SUMIF functions in any Excel output
- Never delete any files
- Always report a summary when a task is complete
Folder-Specific Instructions
Rules that apply only when working in a particular folder.
For example: set the Receipts folder to "rename files to YYYY-MM-DD_vendor_amount format," and the Reports folder to "always output A4 portrait layout." Each folder behaves differently without you repeating yourself.
6. Extension layer 1: Connectors (MCP) {#connectors}
Connectors link Cowork to cloud services. Technically they're based on MCP (Model Context Protocol), an open standard.
Built-in connectors (no code required)
Browse and connect from Settings → Connectors.
| Category | Examples |
|---|---|
| Storage | Google Drive, Dropbox |
| Communication | Slack, Gmail |
| Task management | Notion, Asana, Jira, Linear |
| Calendar | Google Calendar |
| CRM | Salesforce |
Adding a custom MCP
For services not in the list, paste the MCP server URL:
Settings → "Add a Custom Connector" → Enter name and server URL → Done
Using connectors
Once connected, just describe what you want in plain language:
"Fetch all unapproved expense requests from the
'Expense Approvals' database in Notion for this month,
summarize them in Excel, and save to the expense folder."
7. Extension layer 2: Skills {#skills}
Skills let you store recurring workflows and business rules so Cowork doesn't need to be re-instructed each time. They're injected directly into Claude's system prompt when activated.
What Skills can define
- Output format templates
- Business-specific rules and terminology
- Step-by-step procedures for recurring workflows
- Approval gates and confirmation steps
Example skill
[Skill: Monthly Expense Report]
Purpose: Compile monthly expense data into a report
Input: Receipt images (JPEG/PDF) in the expense folder
Steps:
1. Extract date, vendor, amount, and tax from each file
2. Auto-classify category (travel / meals / comms / supplies / other)
3. Create a monthly Excel sheet (with SUM formulas)
4. Assign account codes (reference code table in templates folder)
5. Add a summary sheet with totals and category breakdown
Constraints:
- Do not delete or move source files
- Flag any expense over $500 as "needs review"
Save this once. Every month, just say "run the monthly expense report" and Cowork follows the procedure exactly.
8. Extension layer 3: Plugins {#plugins}
Plugins are the newest extension type, added January 30, 2026. They bundle Skills, Connectors, slash commands, and sub-agents into a single package — think of them as turning Cowork into a specialist for a particular domain.
Anthropic official plugins (open source on GitHub)
| Plugin | Use case |
|---|---|
| Finance | Financial modeling, analysis, KPI tracking |
| Legal | Contract review, NDA pre-screening |
| Sales | Prospect research, CRM integration |
| Marketing | Content creation, campaign management |
| Productivity | Tasks, calendar, daily workflows |
| Data Analysis | Data analysis and visualization |
Installing a plugin
Cowork tab → "+" button → "Plugins" → select the plugin
After installation, the plugin's slash commands become available (e.g., /analyze-cashflow, /review-contract).
Building a custom plugin
The "Plugin Create" plugin lets you build your own custom plugin without writing code.
9. Using it safely {#safety}
Cowork has direct filesystem access, so it requires more care than regular chat.
Safety features Anthropic has built in
- Explicit confirmation before file deletion — Cowork will always prompt you before deleting anything
- VM-isolated execution — work happens in a virtual machine, isolated from your main OS
- Folder-scoped access — Cowork can only touch folders you've explicitly permitted
What you should do on your end
Use a dedicated working folder. Create a folder specifically for Cowork tasks. Only grant access to that folder — never to folders containing sensitive data.
Back up before you run. Copy important files to a backup folder before giving Cowork access to them.
Spell out constraints in your prompts. "Do not delete files," "Do not modify source files" — include these in every task, or put them in your Global Instructions.
Keep regulated work out. Cowork doesn't currently produce audit logs. Avoid using it for tasks with HIPAA, financial compliance, or similar regulatory requirements until that changes.
10. Practical example: Startup accounting {#use-case}
Here's a concrete walkthrough based on a 10-person, 2-year-old startup with no dedicated accountant. The founder or office manager handles bookkeeping part-time, and month-end has historically taken several hours.
The problem
Without a full-time accountant, expense processing, invoice management, and monthly reports fall to people who have other jobs. Every month-end is painful.
Folder structure
/accounting
/receipts_raw ← drop receipt images and PDFs here
/invoices_received ← incoming invoice PDFs
/reports_monthly ← Excel outputs land here
/templates ← Excel templates, account code reference
Global Instructions
I'm handling accounting for a small startup (monthly close, QuickBooks integration).
- Use USD ($) for all amounts
- Reference /templates/account_codes.xlsx for chart of accounts
- Always include SUM and SUMIF formulas in Excel output
- Never delete or move source files
- Flag any expense over $500 as "needs review"
- Always report a summary when done
Step 1: Bulk receipt processing
Team members drop their receipt photos (JPEG and PDF, mixed) into /receipts_raw throughout the month. At month-end, run this:
Process all files in the receipts_raw folder.
Extract from each receipt:
- Date (YYYY-MM-DD)
- Vendor name
- Pre-tax amount, tax amount, total
- Payment method (cash / card / digital wallet)
- Category (travel / meals / comms / supplies / other)
Output: /reports_monthly/expenses_YYYY-MM.xlsx (one sheet per month)
Add a summary sheet with category totals.
What Cowork does:
- Scans all files in the folder
- Reads images via OCR to extract data
- Cross-references the account code table to assign categories
- Generates Excel with formulas
- Reports a summary when done
Time estimate: 30–50 receipts in about 5–10 minutes (vs. 2–3 hours manually).
Step 2: Invoice management
Process all PDFs in the invoices_received folder.
Extract from each invoice:
- Issue date and due date
- Vendor name and invoice number
- Pre-tax and total amounts
- Bank transfer details
Output: /reports_monthly/invoice_list_YYYY-MM.xlsx
Highlight in red any invoices due by end of this month.
Step 3: Monthly summary report
Using the files below, generate this month's expense summary report.
Source files:
- /reports_monthly/expenses_YYYY-MM.xlsx
- /reports_monthly/invoice_list_YYYY-MM.xlsx
- /templates/monthly_report_template.xlsx
Include:
1. Total spend and category breakdown
2. Month-over-month comparison
3. Unpaid invoices list
4. Items flagged as "needs review" (over $500)
Output: /reports_monthly/monthly_summary_YYYY-MM.xlsx
Bonus: Claude in Chrome integration
With Claude in Chrome enabled, you can extend into browser-based accounting software:
Open the "Add Transaction" screen in QuickBooks
and enter each expense from expenses_YYYY-MM.xlsx
one at a time. Ask for confirmation before each entry.
Recommended: use one-at-a-time confirmation for any entries going into accounting software. Don't bulk-import without a human reviewing each one.
With the Finance plugin
Install the official Finance plugin and use slash commands for quick analysis:
/analyze-cashflow
"Using this month's expense data, generate a cash flow forecast for next month."
Time savings (estimated)
| Task | Before | After Cowork |
|---|---|---|
| Receipt data entry (30 items) | ~2 hours | ~10 minutes |
| Invoice management | ~1 hour | ~5 minutes |
| Monthly report | ~3 hours | ~15 minutes |
| Total | ~6 hours/month | ~30 minutes/month |
Key caveats
- Cowork does not currently produce audit logs — final review must always be done by a human
- For entries into accounting software, use one-at-a-time confirmation to catch errors before they propagate
- Keep sensitive financial data in a dedicated, Cowork-only folder with minimal access
Conclusion
The biggest shift Cowork represents isn't the technology — it's the workflow model. You stop being an operator who runs AI commands and start being a reviewer who approves AI-completed work.
Connectors, Skills, and Plugins are the three levers that let you adapt Cowork to your specific workflows rather than adapting your workflows to the tool.
It's still in research preview, which means capabilities and limitations will continue to change. Start with low-sensitivity tasks, small folders, and tasks where mistakes are recoverable. Expand from there.
The transition from "chat with AI" to "work alongside AI" is underway. Cowork is one of the first practical expressions of what that actually looks like.
This article reflects the state of Claude Cowork as of February 2026. As a research preview product, features and specifications are subject to change.