How to Use Claude Cowork for Non-Code Work
How to use Claude Cowork for non-code work
Updated
How to use Claude Cowork comes down to describing a finished result, scoping what it can touch, and reviewing what it hands back. This page is Step 11 of 12 in the Vibe Coding guide. You leave with a working setup for a non-code job, a rule for when to use Claude Code instead, and the current facts on plans, permission modes and cloud tasks.
Cowork changed in 2026. It merged into the main Claude app on September 16, and new Pro and Max tasks have run in the cloud since October 6. Guides that describe a separate Cowork tab or a local-only task are out of date, so this page starts from the current product.
The running example is Bookly, a booking app for a hair salon. Claude Code builds Bookly. Cowork handles the work around it, such as the weekly bookings report and draft reminder emails for clients. The rest of this page shows where the line between the two tools sits.
Related guides: Claude Code deep dive, Codex deep dive, best vibe coding tools, vibe coding security.
Part 1: What Cowork Is Now
Claude Cowork is now part of every Claude conversation
On September 16, 2026, Cowork and chat merged into one Claude. You describe an outcome in any conversation, and Claude decides whether to answer or to do the work. There is no mode to pick.
Rollout: Pro and Max came first, on web, desktop and mobile. Team is in beta. Enterprise is generally available from October 23, 2026, when an owner turns on Chat and Cowork unified. Anthropic says Free plans will get it soon.
Before you move: once your account moves, you cannot switch back. Accounts that have not moved still show separate Chat and Cowork tabs.
The desktop app runs the same engine as the Claude Code CLI. The Claude Code guide covers that engine in full.
The milestones that change how you use it
Two dates matter most: the September 16 merge and the October 6 move of new Pro and Max tasks to the cloud. Older posts that treat Dispatch as the main feature, or Cowork as local-only, predate both.
| Date | Milestone | Scope |
|---|---|---|
| Jan 12, 2026 | Research preview in the Claude Desktop app. Cowork runs locally in an isolated virtual machine. | macOS, Max plan |
| Jan 16, 2026 | Access expands to Pro | macOS |
| Feb 24, 2026 | Plugin marketplace and admin controls | Team and Enterprise |
| Feb 25, 2026 | Scheduled tasks, plus a Customize section for skills, plugins and connectors | - |
| Mar 17, 2026 | Dispatch research preview: one persistent thread you message from your phone | Max first, then Pro |
| Mar 23, 2026 | Computer use research preview | Pro and Max |
| Apr 9, 2026 | General availability on macOS and Windows, with analytics, OpenTelemetry and role-based access for groups | Desktop app, all paid plans |
| May 13, 2026 | Claude for Small Business launches inside Cowork | - |
| Jul 7, 2026 | Web and mobile beta, with remote sessions | Starts with Max |
| Sep 16, 2026 | Cowork and chat merge into one Claude | Pro and Max first |
| Oct 6, 2026 | New Pro and Max Cowork tasks run in the cloud. The local-only option is removed. | Pro and Max |
Part 2: How to Use Claude Cowork
How to use Claude Cowork: from first task to scheduled routine
Seven steps take one job from a first task to a routine that runs on a schedule. Do them in order. Each step limits what the next one can do.
Pick a paid plan. Cowork runs on Pro, Max, Team and Enterprise. The Free plan has no Cowork. Desktop Cowork covers every paid plan. Web and mobile Cowork covers Pro, Max, Team (beta) and Enterprise when an owner enables it.
Install the desktop app or open the web or mobile app. The desktop app runs on macOS (Universal), Windows (x64 and ARM64) and Linux (beta, Ubuntu 22.04 or later, Debian 12 or later). Local folders, the built-in browser and computer use need the desktop app open.
Describe the finished result in a conversation. On the unified experience you start in any conversation. Name the output type, the input folders or files, and what done looks like. Accounts that have not moved still show a separate Cowork tab.
Set instructions at three levels. Global instructions (Instructions for Claude in Settings) apply to every task. Folder instructions apply when you pick a local folder, and Claude can update them. A Project keeps its own files, instructions and memory. Together they are Cowork's counterpart of a context file. Memory covers chat and cloud Cowork, and you edit it under Topics. Turn Memory off in the plus menu before a task that should stay out of it.
Grant the smallest set of folders and connectors. Pick only the folders and connectors this task needs. Set each connector tool to Always allow, Needs approval or Blocked. Keep write tools on Needs approval.
Run the first task by hand. Use Manual mode for the first run, and for any folder with sensitive files. Read each action Claude asks to take, and review the output before you use it.
Schedule the task after a clean run. Create a scheduled task from the Scheduled page, from the sidebar, or with /schedule inside a task. Choose hourly, daily, weekly, weekdays or manual. Each run opens its own session, and you can pause, resume, run on demand or review past runs on the Scheduled page.
Context files such as CLAUDE.md are explained in the workflow guide.
Worked example: Bookly's weekly bookings report
This is an illustration of the setup. It does not report any real figures for Bookly.
Bookly's owner exports the week's bookings and deposits from the app as files into one folder. Claude Code builds and maintains Bookly itself. Cowork produces the report from those exports. The owner writes the finished result in one sentence: a sheet with one row per day, the deposits received, the cancellations and the refunds.
The owner grants that one folder and no connectors. The owner keeps Manual mode for the first runs, because the exports hold client names and payment details. A folder instruction names the input files and says which sheet columns must not change. For the privacy rules that apply to client exports, read the legal guide.
Reminder emails follow the same pattern. The owner asks for one draft per client in a document, reads each draft, and sends it by hand.
A scheduled task that reads a local folder runs on the computer, so the computer must be on and the desktop app open when the schedule fires. A task that needs no local files can run in the cloud with the computer off.
Write the task so it can finish
- Name the output type first: a document, a spreadsheet, a deck, a PDF or a CSV file.
- Name the input folders and files, and say what Cowork must not change.
- Define done in one line you can review, such as one row per day in the sheet.
- Ask for a short list of the assumptions Claude made, and review it before you accept the output.
What people delegate to Cowork
Common jobs for Cowork, with the limits that apply to each one.
File management
Rename, sort, deduplicate and surface what matters in a messy folder. Give it a rule for the file names and the folders it may change.
Documents and research
Structured drafts from scattered notes, and research summaries saved as a file you can review.
Data extraction and spreadsheets
Dense documents, receipts, invoices and screenshots extracted into a spreadsheet, with working formulas where the sheet needs them.
Browser and computer work
The built-in browser opens in a side panel, separate from your logins. Sign in once per session or import cookies from Chrome, Edge or Firefox on macOS, or from Firefox on Windows and Linux. Claude tries connectors first, then the browser, and uses the screen last. Claude in Chrome can start Cowork from the toolbar on all paid plans and read the current tab without the desktop app, but driving a browser needs the desktop app open.
Scheduled tasks
Set recurring work once, such as a weekly report built from a folder of exports. Each run is its own session, and you manage the schedule on one page.
Outputs
Word files, spreadsheets, PowerPoint-compatible decks, PDFs, CSV files and images. Claude Docs, Slides and Design work inside a conversation, and drafts can be edited in place.
Anthropic reports that over 90 percent of Cowork usage is not software development.
Part 3: Safety, Permissions and Connectors
Permission modes: Manual, Auto and Skip all approvals
Cowork has three permission modes. With permissions enabled, Claude shows its plan and waits for your approval before anything significant. Claude asks before it permanently deletes a file in every mode.
| Mode | Default | What it does |
|---|---|---|
| Manual | Enterprise default | You approve the actions Claude takes. Anthropic recommends Manual for sensitive files and accounts, new plugins, and actions that are hard to undo. |
| Auto | Default on Pro, Max and Team | A screen reviews each action and blocks unsafe ones. Use it for low-risk work, after clean runs. |
| Skip all approvals | Not a default | The approval prompts stop. Claude still asks before it permanently deletes a file. |
Connector tools have three settings of their own: Always allow, Needs approval and Blocked. Anthropic warns against putting sensitive data through the Excel and PowerPoint add-ins.
Prompt injection: the two conditions that matter
An attack on a Cowork task needs two things: Claude reads untrusted content, and Claude can take a harmful action. Remove either condition and the risk drops. Anthropic says the chance of an attack is not zero.
Built in: model training, isolated cloud execution, content classifiers, action screening in Auto, deletion protection, and per-app approval for computer use. Each cloud session runs in a temporary isolated environment on Anthropic servers, and it cannot reach your home or company network.
You control the folders, the connectors, the write tools and the sites the browser opens. Network egress settings do not cover web fetch, web search or MCP servers, including Claude in Chrome. Limit browsing to trusted sites, and avoid signed-in sites and sites that handle money. Team and Enterprise owners can turn off web search for Cowork.
For the secret handling and access rules in the apps you build, read the vibe coding security guide.
Computer use: per-app approval and permission tiers
Computer use is off by default. It is a research preview on Pro and Max, on macOS and Windows. Open Settings, select This computer, choose System or Capabilities, and turn on Enable computer use. Windows applies it at once. On macOS, also grant Accessibility and Screen Recording. The first time Claude touches an app, you choose Allow for this session or Deny.
View only
Browsers, trading platforms
Claude can read what is on screen but cannot interact with it.
Click only
Terminals, IDEs
Claude can click, but it cannot take free-form control of the app.
Full control
Everything else
Point, click, type and navigate. Each app still needs your approval for the session.
Extra warning: terminals, Finder or File Explorer, and System Settings show an extra warning before Claude uses them. Keep computer use off unless a workflow needs it.
Connectors and plugins
Connectors are Model Context Protocol (MCP) servers with a setup flow, so you do not edit config files. Plugins bundle skills, connectors and sub-agents in one install. Admins can run private marketplaces, and Enterprise can scan skills and plugins for malicious content.
Microsoft 365 write actions, such as email, calendar, and OneDrive or SharePoint files, need Microsoft Entra admin consent. Teams stays read-only. Enterprise custom roles can control connector access and single tools.
Small-business bundle: Claude for Small Business runs inside Cowork. Turn it on, connect your tools, and pick the job. It bundles 15 + 15 workflows and skills with QuickBooks, PayPal, HubSpot, Canva, DocuSign, Google Workspace and Microsoft 365 connectors.
Part 4: Pricing and Usage
Claude Cowork pricing: which plan you need
Cowork has no separate price. It comes with your Claude plan. The Free plan has no Cowork. Prices exclude tax.
| Plan | Price | Cowork access |
|---|---|---|
| Pro | $20/month billed monthly, or $17/month billed annually ($200 upfront) | Desktop, web and mobile Cowork. Computer use is a research preview on macOS and Windows. |
| Max 5x | $100/month | Desktop, web and mobile Cowork, with 5x the usage of Pro. |
| Max 20x | $200/month | Desktop, web and mobile Cowork, with 20x the usage of Pro. |
| Team Standard | $25/seat/month billed monthly, or $20/seat/month billed annually | Desktop Cowork. Web and mobile Cowork is in beta. |
| Team Premium | $125/seat/month billed monthly, or $100/seat/month billed annually | 5x the Standard usage. Desktop Cowork. Web and mobile Cowork is in beta. |
| Enterprise | US$20/seat/month billed annually, with a 20-seat minimum, plus usage at API rates | Admin controls, custom roles for connectors, and the unified experience when an owner turns it on. Anthropic's product page also points buyers to sales. |
Cowork access is also offered through Amazon Bedrock, Gemini Enterprise Agent Platform and Microsoft Foundry.
Prices across tools: this page covers Claude only. The best vibe coding tools guide compares plans and limits across the main tools.
Usage limits and how to stay inside them
Every Claude surface draws from one usage pool: web, desktop, mobile and Claude Code. Paid plans have a rolling 5-hour window and weekly limits.
- Cowork uses limits faster than chat, because it coordinates sub-agents and many tool calls.
- Group related work into one task. Open a new conversation for each unrelated topic.
- Check Settings, then Usage, to see your own position.
- Anthropic does not publish weekly Cowork usage numbers by plan.
Usage credits: on Pro and Max, you can turn on usage credits to keep working past a limit. On Team and seat-based Enterprise, usage credits keep work going at API rates up to the spend limit; past it, work stops until the next billing period.
Part 5: Routing Work Between Cowork and Claude Code
Claude Cowork vs Claude Code: which one runs which task
Both tools draw from one usage pool and sit on the same paid plans. The difference is the work. Cowork handles documents, spreadsheets, files and operations. Claude Code, a coding agent, handles code in a repository.
| Question | Claude Cowork | Claude Code |
|---|---|---|
| Built for | Documents, spreadsheets, files and operations | Software in a git repository |
| Where it runs | In the cloud by default on Pro and Max for new tasks. Local folders need the desktop app open. | Locally in your terminal or the desktop app, or in the cloud with claude --cloud |
| Output | Word files, spreadsheets, decks, PDFs, CSV files and images | Code changes, tests and commits in a repository |
| Permissions | Manual, Auto or Skip all approvals, with a setting for each connector tool | Six permission modes, including plan and auto |
| Scheduling | Built-in scheduled tasks: hourly, daily, weekly, weekdays or manual | Cloud scheduled tasks with /schedule, /loop, or cron with claude -p |
| Plans | Pro, Max, Team and Enterprise. Not on Free. | Pro, Max, Team and Enterprise. Not on Free. |
Moving work between them: open the Cowork task, choose Download task data, unzip the file, open the folder in Claude Code, and run /port-task-data. For the full developer toolchain, read the Claude Code deep dive.
The routing table
One question decides it: is the deliverable code in a repository, or a document, spreadsheet or organized folder? Code goes to Claude Code. Everything else goes to Cowork.
| Task | Route to | Why |
|---|---|---|
| Fix a bug, write tests, open a pull request | Claude Code | Needs a git repository, tests and review of code changes |
| Turn 40 meeting notes into a quarterly report | Cowork | Document synthesis that ends in a finished file |
| Rename and sort 3,000 photos and PDFs | Cowork | File work that needs judgment, with no code |
| Extract line items from 200 invoices into a sheet | Cowork, Manual mode | Data extraction into a spreadsheet. Invoices are sensitive files. |
| Refactor the auth module behind a feature flag | Claude Code | Needs code changes, tests and a check that the flag works |
| Pull the week's figures into the report template every Friday | Cowork (scheduled) | Recurring, file-based, and ends in a deliverable |
| Work that must stay on this computer | Claude Code in the desktop app | Pro and Max Cowork tasks run in the cloud, so local-only work fits Claude Code |
| Bookly: draft the weekly bookings report from the exports folder | Cowork (local schedule) | Reads a local folder, so the computer must be on |
Limitations and gotchas
Since October 6, 2026, new Cowork tasks on Pro and Max run in the cloud, with no setting to choose. Local files, the built-in browser and computer use need the desktop app open. Cloud tasks copy only the file they need, and deleting a session deletes those copies. Tasks that started locally before October 6 stay local.
Existing users keep Dispatch, which runs in a limited beta on some Pro and Max plans. It needs the desktop and mobile apps and an awake computer, and it allows one persistent thread. Permission requests auto-deny after 10 minutes. Remote instructions can read, move or delete local files and control your browser. New users should use cloud Cowork instead.
It acts on your real screen, not an isolated environment. Anthropic warns about prompt injection from on-screen content. Scope folders tightly, approve apps one at a time, and do not run it unattended on sensitive screens.
Computer use needs Pro or Max. It is not part of Team or Enterprise plans. Usage from Cowork counts toward the same pool as your chat and Claude Code, so a heavy Cowork afternoon also uses your coding limit.
The Linux desktop app is in beta and runs Cowork in a virtual machine. The setup needs are in the FAQ below.
There is no Add from GitHub option and no way to branch a conversation. Incognito chats use the old experience, with no files or code. Search does not cover older Cowork tasks. Before you put regulated data into Cowork, ask your admin to confirm the audit and compliance coverage. The Compliance API covers Cowork web and mobile activity, and your admin should confirm the desktop app too.
Why this matters to a vibe coder
If you already run Claude Code, Cowork is the version you can hand to a co-founder, a client or your own operations backlog without teaching anyone a terminal. The access rules from the Claude Code guide still apply: grant the smallest set of folders, approve the plan, and review the output. Bookly's owner can run the weekly report this way. Claude Code stays with the developer who maintains the app.
Next step: OpenAI Codex
The next guide applies the same method to OpenAI Codex and compares it with Claude Code. Read the Codex guide, the last agent deep dive in the Vibe Coding guide.
Common Questions
Is Claude Cowork free?
No. Cowork is not on Claude's Free plan. It comes with Pro, Max, Team and Enterprise at no separate price, and it draws from the same usage pool as chat and Claude Code. Pro is $20 a month, or $17 a month billed annually. Since September 16, 2026, Cowork is part of the main Claude app rather than a separate tab.
How much does Claude Cowork cost?
Cowork has no price of its own; it is included in the plan. Pro is $20 a month ($17 billed annually), Max starts at $100 a month, Team Standard seats are $25 a month or $20 billed annually, and Enterprise is $20 per seat a month billed annually with a 20-seat minimum, plus usage. Heavy Cowork use spends plan limits faster than chat.
Is Claude Cowork safe?
It is as safe as the permissions you give it. Cowork has three permission modes: Manual, Auto and Skip all approvals, and Anthropic recommends Manual for sensitive files and accounts. Computer use acts on your real screen, not a sandbox. Prompt injection needs two conditions, Claude reading untrusted content and being able to take a harmful action, so limit one of them.
Is Claude Cowork available on Windows?
Yes. Cowork is generally available in the Claude desktop app on macOS and Windows, and it also runs on the web and mobile for plans that support it. Computer use, where Claude controls your screen, works only on macOS and Windows and only on Pro and Max. New Pro and Max tasks run in the cloud since October 6, 2026.
Claude Cowork vs Claude Code: when should I use each?
Send work whose output is a document, spreadsheet, deck or organized folder to Cowork. Send work that changes code in a git repository and needs tests to Claude Code. Dispatch, which routes development tasks to Claude Code, is closed to new users. To move a finished Cowork task into Claude Code, use Download task data and /port-task-data.
Does Cowork use more tokens than Claude Code?
Anthropic publishes no per-task comparison. Both draw from one usage pool with a rolling 5-hour window and weekly limits on paid plans. Cowork coordinates sub-agents and many tool calls, so a Cowork task usually costs more than a chat answer. Group related work into one task, check Settings, then Usage, and on Pro or Max turn on usage credits to keep working past a limit.