CLAUDE COWORK
Claude’s multi-step work capabilities across desktop, web, and mobile. Cowork can use approved files, folders, and connected tools, follow project instructions, and prepare reports, spreadsheets, briefings, and other finished work products for review. Local computer folders are accessed through Claude Desktop.
Where It Fits
Claude Cowork on PromptedWork
Claude’s multi-step work capabilities across desktop, web, and mobile. Cowork can use approved files, folders, and connected tools, follow project instructions, and prepare reports, spreadsheets, briefings, and other finished work products for review. Local computer folders are accessed through Claude Desktop.
- +Multi-step knowledge work using approved cloud files, connected services, or scoped desktop-connected folders
- +Recurring reports, briefings, trackers, and document packets that benefit from project instructions and source review
- +Folder organization, file synthesis, and polished deliverables with an inspect-first, approve-before-change workflow
Start Here
Best Starting Workflows
Start with these to understand how Claude Cowork is used on PromptedWork, then use the full workflow list below as the broader hub.
How Coaches Can Capture Session Notes on a Phone and Let Claude Cowork Turn Them Into a Follow-Up Email and Action Tracker
Capture coaching session notes on a phone, then let Claude Cowork turn them into a follow-up email and action tracker.
How Educators Can Use Claude Cowork to Turn a Folder of Readings, Notes, and Slide Drafts Into a Workshop Pack
Use Claude Cowork to turn a local teaching folder into a workshop pack with slides, a handout, and a missing-items list.
How Educators Can Use Claude Cowork to Turn a Semester Folder Into a Course Retrospective Packet
Use Claude Cowork to inspect a semester-review folder, map strengths and friction points across course artifacts, and draft a practical end-of-term retrospective packet.
Anthropic Navigation
Anthropic Workflows Hub
Use the Anthropic hub as the directory page for Claude Skills, Claude Cowork, Claude for Small Business, and the workflow articles that sit under each layer.
Open Anthropic HubRelated Anthropic Page
Claude Skills
Saved workflow instructions that help Claude repeat the same process, format, and quality checks across recurring tasks. Claude Skills are best when you want consistent outputs without rebuilding the same prompt every time.
Related Anthropic Page
Claude for Small Business
Anthropic’s connected small-business workflow layer inside Claude Cowork. It is designed for owners and lean teams who want Claude to work across approved business tools before they review the result.
Jump to workflows
Need a practical example first? Skip to the task-specific Claude Cowork guides. If you are new to Cowork, read the safety note and first-run steps below before granting file or tool access.
Skip to workflowsImportant Safety Note
- Cowork is part of Claude on desktop, web, and mobile. Access requires a paid Pro, Max, Ultra, Team, or Enterprise plan. Team functionality can be in beta; Enterprise access depends on organizational settings.
- Use a dedicated working folder and copies of files for your first test. Never grant broad access to all your documents or a client archive just to complete one job.
- Start in Manually approve mode. Have Claude inspect the sources, propose a plan, and wait for your approval before making changes. Automatically approve uses safety checks, but it does not replace your review; Skip all approvals bypasses those checks. Permanent deletion still requires explicit approval.
- Cloud execution is not local-only processing. A cloud Cowork session can process copies of files fetched through the Desktop app on Anthropic's servers. Do not assume that keeping the original folder on your computer keeps the data on your computer.
- Sensitive or regulated work needs organizational approval first. Check the plan's data-handling rules, Compliance API coverage, audit logging, exports, retention, connectors, and administrator controls for the exact workload before using real records. Never treat Cowork's availability as proof that it is approved for healthcare, student, legal, financial, or personnel information.
- Computer use is distinct from normal Cowork file work. It operates a screen and carries extra risk. Do not enable it for a beginner's first task.
What Claude Cowork Is
Claude Cowork is Claude's multi-step work capability for knowledge tasks. Instead of stopping at an answer, Claude can inspect approved files or connected services, organize information, carry out a plan, and produce a report, spreadsheet, slide deck, briefing, or other finished work product for review.
Cowork is no longer confined to a separate Claude Desktop mode. On accounts with the unified Claude experience, begin in a regular Claude conversation and describe the result you need. Where a separate Chat/Cowork selector is still visible, choose Cowork for the task. Cloud sessions can continue while your computer is off, and you can review them from desktop, web, or mobile.
Access depends on the source. Files uploaded to a cloud session or saved to a cloud project can be used without your laptop being awake. Files in a folder connected from your computer still depend on Claude Desktop as a bridge. A task that needs that folder must begin on desktop or be a scheduled task, and the Desktop app must be open when Claude accesses the files.
Cowork is useful for reports, spreadsheets, presentations, briefing packets, repeated summaries, research scans, file comparison, and document transformation. It does not verify that your source material is true or that every action is appropriate.
Cowork vs Regular Claude Chat
| Use Regular Claude Chat When... | Use Cowork Capabilities When... |
|---|---|
| You need a quick answer or short draft. | You need a multi-step result rather than only an answer. |
| You can paste the necessary context. | Claude needs to inspect several approved files or connected sources. |
| You want to supervise every step yourself. | You want Claude to propose a plan, then complete the approved steps. |
| The answer can remain in the conversation. | The output needs to be a file, report, presentation, tracker, or organized workspace. |
| A simple request is enough. | The job involves recurring work, source comparison, file organization, or multiple deliverables. |
On unified accounts there may be no separate Chat/Cowork choice. This table describes the type of work, not a menu that every account must use. Quick requests may stay conversational; complex requests can move into multi-step execution in the same conversation.
What Cowork Can Actually Do
- Files and folders: read, compare, organize, and prepare documents from files it has permission to access; create outputs and, where permitted, change files.
- Finished deliverables: prepare reports, spreadsheets, presentations, meeting packets, summaries, and trackers using supplied sources.
- Multi-step tasks: inventory the inputs, identify gaps, propose an approach, and complete the work after any required review.
- Connected tools: work with approved services through connectors available to the account and permitted by its administrator.
- Plugins and skills: use reusable specialist workflows and instructions; the user must still check their permissions and the particular plugin's effects.
- Recurring tasks: run approved briefings, reports, or research tasks on a schedule and return results for review.
These are possible task types, not a guarantee that every source, connector, or file format is supported in every account.
What Cowork Is Not
- It is not a substitute for source verification, professional judgment, or human sign-off.
- It is not necessary for a one-question task that ordinary chat handles cleanly.
- It is not automatically granted access to all folders on your computer. You choose which folders or services to connect, and you should keep that access narrow.
- Cloud work is not the same as offline or on-device processing.
- It is not inherently approved for regulated or confidential information just because your organization uses Claude.
- Computer use is a separate, higher-risk capability, not a default requirement for most file-based Cowork tasks.
First-Time Setup: The Safest Beginner Path
- Confirm your plan and surface. Cowork is available on paid Pro, Max, Ultra, Team, and Enterprise plans. Use current Claude Desktop, Claude on the web, or the Claude mobile app. Team and Enterprise users should also check administrator enablement.
- Choose how to start. If you see a Chat/Cowork option, select Cowork. If you do not see a selector because your account is unified, simply describe the multi-step task in an ordinary Claude conversation.
- Decide where the source files are. For uploaded or cloud-project files, begin on a supported surface. For a computer folder, install or update Claude Desktop and connect only the intended folder. Start that local-folder task on desktop; do not assume that a new mobile session can browse it.
- Make a small test workspace. Create a dedicated folder with copies of non-sensitive documents or upload a similarly limited test set. Avoid broad Desktop, Downloads, Documents, drive, or mailbox access.
- Use Manually approve. Ask for an inventory and a plan before file changes. Automatically approve performs safety screening, but does not promise human approval for each action. Skip all approvals has no automatic action screening and is unsuitable for this introductory workflow.
- Set useful standing instructions. Add audience, format, naming conventions, sources, exclusions, and a requirement to mark uncertain items.
- Create a project if the workflow repeats. Keep a separate project or working set for a weekly report, board packet, or client recap.
- Run the first task in read-only form. Ask Claude to list its sources, propose an output, and stop before modifying originals, sending messages, or publishing.
- Review the output. Compare claims and numbers against originals, confirm what files were used, and approve only the specific subsequent actions you actually want.
Set Up Cowork Once So You Do Not Repeat Yourself
For repeat work, use a consistent project, saved instructions, and a small source set. This reduces repeated setup, but does not make source verification optional. The current week's files still need to be distinguished from historical examples, and local folders still require the desktop bridge when accessed.
Profile Preferences
Use account-level instructions for general tone, preferred terms, and output style. Do not store confidential client or student material in global instructions when that material only belongs to one task.
Project Instructions
A project's instructions can define its audience, output format, naming rules, permitted sources, exclusion rules, and required approval checkpoints. Use a separate project or approved source set for each client or recurring job.
Project Memory
Cowork projects can carry useful context from related tasks. Project memory is not a substitute for checking current files and source dates. Review the project's memory settings if you need separation from account-level memory.
Scheduled Tasks
Use scheduled tasks for repeating work that you have already tested manually. Cloud schedules run without an online device; locally connected folders still require Desktop to be open when accessed. Keep the scheduled result as a draft for review, not authority to send or change records.
Skills
Skills provide reusable instructions and output conventions. Use them to standardize a report or workflow after the source material has been gathered and verified. Check whether a skill is available and enabled in your own account before a workflow depends on it.
Example: Weekly Operations Report Project
A weekly operations report can reuse the same structure, while the facts come from the current reporting period. Separate current inputs from archive material and require a review before the report is circulated.
{
"project_name": "Weekly Operations Report",
"standing_context": {
"audience": "Operations leader who needs a fast summary",
"tone": "Direct, concise, practical",
"source_files": "Current-week notes, meeting summaries, spreadsheet exports, and issue logs",
"output": "One reviewed weekly report document"
},
"standing_rules": [
"Use the same sections each week: executive summary, key updates, blockers, decisions needed, and next steps.",
"Use current-week sources unless I authorize a comparison with past weeks.",
"Separate confirmed facts from open questions.",
"Flag missing or conflicting source information.",
"Do not invent missing facts, owners, dates, or numbers.",
"Propose an evidence summary first; wait for my approval before final drafting.",
"Create a final review checklist before the report is shared."
],
"file_naming": "weekly-operations-report-yyyy-mm-dd",
"future_task": "Prepare this week's report plan from the latest approved project files."
}Use the project to hold standing instructions. If the workflow needs a local folder, start on desktop or use a scheduled task with Desktop available for the local-file step. Do not assume the folder's files have been copied to the cloud project.
Beginner Workflow: Organize a Folder Safely
A folder of copied, non-sensitive sample files makes a good first task. Use a desktop-started session if you want Claude to inspect a connected folder; otherwise upload the sample set to the cloud session.
{
"task": "Review this approved sample folder and propose a safe organization plan.",
"rules": [
"Do not move, rename, edit, or delete files unless I approve each specific operation.",
"First list the files you actually inspected and their types.",
"Then propose a folder structure and any naming changes.",
"Flag anything uncertain for my review.",
"Stop after the plan. Do not change the source files."
],
"output_format": "Source inventory, proposed structure, and items needing review"
}Check the inventory and proposed names yourself. If you approve one operation, specify the file and change. Prefer a copy of the source when testing edits.
How To Write a Good Cowork Task
Treat a Cowork request as a task brief. State the outcome, approved sources, deliverable, allowed changes, prohibited actions, quality checks, and where to save the result. A JSON prompt is a structured instruction, not a special executable command.
{
"outcome": "Create a weekly operations summary from the approved source files.",
"source_material": "Use only the files I have explicitly attached or connected for this task.",
"output": "One formatted report and a short executive summary.",
"permissions": {
"allowed": [
"Read the approved sources",
"Draft new files in the designated output area after I approve the plan"
],
"not_allowed": [
"Delete or rename source files",
"Move originals",
"Send or publish anything",
"Use outside sources without permission"
]
},
"review_step": "First list the sources, uncertainties, and plan; wait for my approval before final output."
}Use Manually approve when enforcing your intended review gate in the product. Do not rely on prompt wording alone for actions with financial, privacy, or reputational consequences.
Projects: The Best Way To Manage Repeat Work
Cowork projects organize related sessions, context, instructions, and memory so you can continue recurring work without rebuilding the setup every time. Projects can follow your Claude account across desktop, web, and mobile where the relevant account experience is enabled.
A project is not the same as a local folder. Projects created in Cowork can have account-saved names, instructions, context, and memory while folders linked from your computer remain on that computer. Claude Desktop must be open when a supported task needs local files, and a locally connected-folder task must have started on desktop or be scheduled.
Anthropic documents project sharing on Team and Enterprise plans with view and edit roles, subject to organizational controls. Sharing a project does not mean that another user automatically has access to files stored on your computer. Keep sensitive materials in approved scopes and check the permissions of every shared project.
Plugins, Skills, and Connectors
Connectors link Claude to approved services. Skills define repeatable instructions or methods. Plugins package skills, connectors, and specialist workflows for particular kinds of work. The same plugin can be saved to your Claude account rather than installed only on one computer, though connector and admin permissions still govern what it can access.
Choose the smallest tool set that can complete the task. Use a project for recurring context; a skill for consistent structure; a connector for an approved source; and a plugin when a ready-made workflow genuinely reduces setup. Review permissions before enabling external actions. A plugin may have capabilities that are not appropriate for a particular organization or task.
Scheduled Tasks and Recurring Routines
Scheduled tasks save instructions that Claude can run on a schedule or on demand. They can prepare daily summaries, weekly reports, research scans, or recurring document packets from available connected tools and cloud files.
Use the Scheduled sidebar to create, review, edit, and pause recurring tasks. Since October 29, 2026, /schedule is no longer a slash-menu item; typing it fills in a scheduling request instead.
New cloud scheduled tasks run remotely, so the computer does not need to be awake and Claude Desktop does not need to remain open merely for the schedule to run. However, an operation requiring a local folder, local browser, or computer use still needs the appropriate desktop connection and local surface available for that operation. Older tasks explicitly configured to run locally may behave differently.
{
"scheduled_task": "Every Friday, prepare a weekly project summary from the latest approved sources.",
"rules": [
"Use only approved project files and connected sources.",
"Separate current-week information from archives.",
"Create a short executive summary and an open-items list.",
"Flag missing data, access failures, and unresolved questions.",
"Prepare a draft for human review; do not send or publish it.",
"Do not delete, rename, purchase, or change customer records."
]
}Test the workflow manually first, inspect its initial scheduled runs, and stop it if sources or output requirements change. Do not schedule irreversible actions, sensitive-data processing, or externally visible activity without specific organizational authorization.
Computer Use: Powerful, But Not the First Thing To Try
Computer use is separate from ordinary Cowork file analysis. It lets Claude interact with local apps by clicking and typing when a connector or browser operation cannot do the job. Anthropic currently lists computer use as beta on desktop for Pro, Max, and Ultra plans. It can access a much broader interaction surface than a small, approved document set.
Cowork normally tries a suitable connector first, then browser tools, then direct screen interaction when necessary. Use a dedicated, low-risk environment and close unrelated windows, tabs, and apps. Never give computer use unrestricted access to accounts containing sensitive legal, financial, medical, credential, personnel, or client information.
Best PromptedWork Workflows for Claude Cowork
Start with workflows that match Cowork's strengths: several source files, repeat reporting, and a clear inspect → plan → approve → create sequence.
- Admins and office work: build a board or leadership meeting packet, create a meeting follow-up packet from phone notes, or prepare a weekly 3P update from current reports.
- Freelancers and consultants: review a deliverable folder against a client checklist, turn a discovery call into a proposal draft, or consolidate a monthly client recap.
- Educators and coaches: turn readings, notes, and slide drafts into a workshop pack, or prepare an evidence-based course review. Never include identifiable student information without the institution's permission and an appropriate data-processing arrangement.
- Local business work: prepare approved vendor summaries, expense-review drafts, or operating briefings from permitted files and tools.
- Nonprofit work: prepare board material, volunteer onboarding drafts, and source-based program updates, with donor and personnel information excluded unless approved.
- Healthcare administration: use only approved, de-identified non-clinical material unless your organization has assessed and authorized the specific handling of protected information.
The complete related-workflows list is rendered from the tool registry below this hub.
Safety Rules for Everyday Users
- Use a narrow, dedicated workspace and copies of source files for initial tests.
- Never grant access to a complete drive or unrelated client folders simply to simplify one task.
- Check which sources are being read, especially untrusted websites, messages, and documents that could contain malicious instructions.
- Ask for a source inventory and plan before changes. Prefer Manually approve for consequential work.
- Treat Automatically approve as safety-screened execution, not as human approval; do not use Skip all approvals for sensitive work.
- Keep backups. Inspect all outputs before sending, sharing, publishing, or acting on them.
- Do not include private or regulated information until your organization has approved the specific use, permissions, and data handling.
- Use the Scheduled sidebar to review or pause recurring tasks you no longer need.
- Prefer an appropriate connector to direct computer use when possible; computer use carries additional risk.
- Close unrelated sensitive apps and tabs before computer use.
- Stop or redirect a task that accesses a file, tool, site, or system outside the approved scope.
Troubleshooting and First-Run Mistakes
- Cowork is missing: confirm the plan, app version, and organizational availability. On unified accounts there is no Cowork selector; enter the task in the normal Claude message box.
- Claude cannot find your local folder: confirm it was connected from Claude Desktop, that Desktop is open, and that the task began on desktop or is a scheduled task. A newly started mobile Cowork task cannot simply browse that local folder.
- A cloud task seems paused: inspect the session for a permissions request, missing connector, inaccessible data, or account-specific restriction. An awake computer is not a general requirement for cloud work.
- A scheduled task misses or produces an incomplete report: review its history in Scheduled, check source/connector access, and determine whether it depended on a local folder whose Desktop bridge was unavailable.
- The output is generic: narrow the input scope, add the audience and required format, and provide a reviewed sample.
- Claude changes too much: use copied files, Manually approve, and a plan-before-action request. Approve specific operations instead of saying "fix everything."
- A project cannot use local files from another device: project context may sync, but connected computer folders remain local. Begin on desktop if that is the required source.
Sources Checked
Sources checked on November 1, 2026:
- Anthropic: Get started with Claude Cowork
- Anthropic: Use Claude Cowork on web, desktop, and mobile
- Anthropic: Cowork product guide, getting started
- Anthropic: Cowork changelog
- Anthropic: Claude Cowork and chat come together for Enterprise
- Anthropic: Organize your tasks with projects in Claude Cowork
- Anthropic: Schedule recurring tasks in Claude Cowork
- Anthropic: Use Claude Cowork safely
- Anthropic: Let Claude use your computer in Cowork
- Anthropic: Assign tasks from anywhere in Claude Cowork
- Anthropic: Use plugins in Claude
Quarterly Refresh Flag
Recommended review date: January 30, 2027.
Recheck plan-by-surface access, project sharing and memory, local-file bridge behavior, scheduled-task and approval controls, Dispatch availability, computer-use limitations, and enterprise retention, audit, and compliance mechanisms. Recheck the revised Cowork workflow articles and their links after the full batch deploys.
Why PromptedWork Cowork Workflows Are Useful
PromptedWork's Cowork workflows focus on the work that takes more than one prompt: collecting source files, comparing records, preparing a plan, producing reviewable deliverables, and keeping the necessary human checkpoints. Start with a narrow, repeatable task, verify the result against its sources, and expand access only when that makes the workflow materially better.
Platform Availability
Cowork tasks can run on the web with an eligible paid plan, including the unified Claude experience. Sessions, cloud files, projects, and scheduled work can follow the account; access to local computer folders requires an open Claude Desktop app and an eligible desktop-started or scheduled task. Team access may be in beta; Enterprise access is controlled by an owner.
Claude Desktop is available for Cowork on paid Pro, Max, Ultra, Team, and Enterprise plans. It is the bridge for connected local folders, local browser work, and computer use. New Cowork tasks on Pro, Max, and Ultra run in the cloud by default; access to a local folder still requires Desktop to be open.
Claude Cowork supports cloud tasks on mobile on eligible paid plans without keeping a computer awake. Sessions and files follow the account. Local-folder and computer-use access still depend on the Desktop bridge, and a local-folder task must start on desktop or be scheduled. Dispatch is a limited legacy beta not available to new users.
Best For
Related search guides
Where Claude Cowork fits
These pages compare this tool against adjacent workflows, task hubs, and hardware or software alternatives.
best
Best AI Tools for Meeting Notes
Choose the right AI meeting notes workflow for transcripts, documents, recurring folders, portable recorders, and desk or phone-call capture.
Open guidebest
Best AI Tools for Business Reporting
Compare tools for leadership summaries, board briefs, KPI exports, weekly owner briefs, and recurring business reports.
Open guiderole task
AI Proposal Generator for Consultants
Turn discovery calls, statements of work, redlines, and renewal notes into consultant proposal drafts and change orders.
Open guidetool task
NotebookLM for Meeting Notes
Use NotebookLM when meeting notes depend on transcripts, agendas, policy packets, prior notes, and multi-document prep.
Open guidecomparison
Claude Cowork vs ChatGPT Projects
Compare Claude Cowork and ChatGPT Projects for recurring files, folders, context, summaries, and multi-step work.
Open guidetool task
Claude Cowork Workflows for Small Business
Use Claude Cowork for owner briefs, reports, proposals, recurring summaries, document packets, and folder-based workflows.
Open guidetool task
Claude for Small Business Workflows
Explore owner briefs, slow sales promo campaigns, quote workflows, commercial lead research, and proposal workflows.
Open guidetemplate
AI Report Generator for Business
Use AI for leadership summaries, board briefs, issue reports, weekly risk summaries, KPI recaps, and finance narratives.
Open guidebest
Best AI Tools for SOPs and Policies
Compare ChatGPT, Claude Skills, Claude Cowork, NotebookLM, and Gemini for SOPs, policies, staff guides, and process documentation.
Open guideClaude Cowork Workflows on PromptedWork
How Coaches Can Capture Session Notes on a Phone and Let Claude Cowork Turn Them Into a Follow-Up Email and Action Tracker
Capture coaching session notes on a phone, then let Claude Cowork turn them into a follow-up email and action tracker.
How Educators Can Use Claude Cowork to Turn a Folder of Readings, Notes, and Slide Drafts Into a Workshop Pack
Use Claude Cowork to turn a local teaching folder into a workshop pack with slides, a handout, and a missing-items list.
How Educators Can Use Claude Cowork to Turn a Semester Folder Into a Course Retrospective Packet
Use Claude Cowork to inspect a semester-review folder, map strengths and friction points across course artifacts, and draft a practical end-of-term retrospective packet.
How Educators Can Use Claude Cowork to Turn Past Exam PDFs and a Syllabus Into a Revision Guide
Use Claude Cowork to compare past exam PDFs against the current syllabus and build a revision guide that highlights likely topic emphasis without promising exact repeats.
How to Use Claude Cowork to Turn a Folder of Drafts Into a Board or Leadership Meeting Packet
Use Claude Cowork to inventory meeting drafts, resolve missing or duplicate files, and assemble a board packet with human approval and without overwriting sources.
How to Build a Meeting Follow-Up Packet From Your Phone With Claude Cowork
Dictate a short meeting recap into Claude on your phone, then create a reviewed follow-up email, action list, and decision recap in one downloadable packet without Dispatch or a running desktop.
How Freelancers Can Use Claude Cowork to Turn a Sales Call Into a Personalized Proposal While Traveling
Capture a sales call recap while traveling, then use Claude Cowork with approved proposal templates and scope rules to draft a personalized proposal for review.
How Freelancers Can Use Claude Cowork to Review a Deliverable Folder Against a Client Checklist
Use Claude Cowork to compare a deliverable folder against the client brief and catch missing files before delivery.
How to Combine Claude Cowork and the Internal-Comms Skill for a Recurring Weekly 3P Update
Use Claude Cowork to gather the week's project material, then apply the internal-comms skill pattern to produce a consistent weekly 3P update.
How to Combine Claude Cowork and a Client Brand-Guidelines Skill to Build a Monthly Recap
Use Claude Cowork to verify monthly client evidence, draft a source-grounded recap, then apply the client's own approved brand guidelines without changing facts.