CLAUDE COWORK

What Claude Cowork Is

Claude Cowork is a mode in the Claude Desktop app that lets Claude work on multi-step tasks using files, folders, connected tools, saved instructions, projects, scheduled tasks, plugins, and, in some cases, computer use.

Use Cowork when you want Claude to complete a task, not just explain how to do it. Regular Claude chat is still best for quick answers, short drafts, and questions where you can paste all the context. Cowork is for larger desktop work where Claude needs to inspect files, make a plan, work through steps, and deliver a finished file or organized result.

Cowork is designed for knowledge work beyond coding: reports, spreadsheets, presentations, folder cleanup, briefing packs, recurring summaries, research scans, and document transformation. Anthropic describes Cowork as bringing agent-style task execution into Claude Desktop for non-coding work.

Claude Cowork is generally available on paid Claude plans through Claude Desktop. Some related capabilities, such as computer use and mobile task assignment, may have plan limits, preview status, or additional safety considerations.

Cowork vs Regular Claude Chat

The practical distinction is simple: chat responds, Cowork works.

What Cowork Can Actually Do

• File and folder work: read, write, create, organize, rename, and build outputs from folders you approve.
• Polished deliverables: create reports, spreadsheets, presentations, briefing documents, summaries, and trackers.
• Longer tasks: plan the work, handle subtasks, and complete work that would be awkward to manage in a normal chat.
• Connected tools: work with approved services such as Google Drive, Gmail, Slack, DocuSign, and similar tools when enabled.
• Plugins: use reusable role or workflow packages that combine skills, connectors, and specialist behavior.
• Scheduled tasks: save a recurring task once and run it on a schedule or on demand.

What Cowork Is Not

• It is not magic desktop automation. It still needs clear instructions, careful folder access, and human review.
• It is not ideal for simple one-question tasks. Use regular chat when you only need a fast answer or short draft.
• It can make real changes to files it can access, so do not grant broad access casually.
• It should not be used for regulated workloads or sensitive data unless your organization has reviewed and approved that use.
• Computer use is more powerful and higher risk than basic Cowork file and folder work.

First-Time Setup: The Safest Beginner Path

1. Install or update Claude Desktop for macOS or Windows.
2. Confirm your plan has Cowork access. Anthropic lists Cowork for paid Claude plans.
3. Open Claude Desktop and find Cowork in the mode selector or sidebar, depending on the current interface.
4. Create a dedicated Cowork working folder instead of granting broad access to Desktop, Downloads, or Documents.
5. Copy files into that folder for early tests instead of using originals.
6. Add profile preferences for broad tone and formatting preferences that should apply across Claude.
7. Create a Cowork project for repeated work, such as weekly reports, board packets, client recaps, or research scans.
8. Add project instructions for the specific workflow, including audience, format, naming rules, review steps, and limits.
9. Run a low-risk test task that asks Claude to inspect first, propose a plan second, and act only after you approve.

Start with a dedicated working folder, copied files, and a task that asks Claude to inspect first, propose a plan second, and act only after you approve.

Set Up Cowork Once So You Do Not Repeat Yourself

One of Cowork's biggest advantages over a normal chat is that it can hold reusable workflow context. For repeat work, create a Cowork project, add project instructions, keep the relevant files in that project, and use short task requests after that.

Profile Preferences

Use profile preferences for account-wide communication preferences such as tone, formatting, common terms, and general work style.

Project Instructions

Project instructions are the saved rules for one workspace. They can tell Claude the audience, tone, output format, naming rules, review steps, and limits it should follow each time it works inside that project.

Project Memory

Project memory helps Claude carry forward useful context from tasks run inside the same project. What Claude learns in one project does not automatically carry to every other project.

Scheduled Tasks

Scheduled tasks save a Cowork task as reusable instructions. Use them when the same work should run daily, weekly, monthly, or on demand.

Skills

Skills can act like reusable workflow recipes when a process needs repeatable instructions across tasks.

Example: Weekly Operations Report Project

A simple recurring project can save a lot of repeated prompting. For a weekly operations report, the project can hold the files, standing instructions, and memory from earlier report work.

{
  "project_name": "Weekly Operations Report",
  "standing_context": {
    "audience": "Operations leader who needs a fast summary",
    "tone": "Direct, concise, practical",
    "source_files": "Weekly notes, meeting summaries, spreadsheet exports, and issue logs",
    "output": "One polished weekly report document"
  },
  "standing_rules": [
    "Use the same section structure every week: executive summary, key updates, blockers, decisions needed, and next steps.",
    "Separate confirmed facts from open questions.",
    "Flag missing or conflicting source information.",
    "Do not invent missing data.",
    "Do not rewrite source numbers unless they are clearly formatting changes.",
    "Create a final review checklist before saving the report."
  ],
  "file_naming": "weekly-operations-report-yyyy-mm-dd",
  "future_task": "Create this week's operations report using the latest files in this project."
}

After the project is set up, the weekly request can be short because the project already contains the standing context.

Beginner Workflow: Organize a Folder Safely

Folder organization is a good first Cowork workflow because it teaches the mental model without requiring sensitive data. Use copied sample files in a dedicated working folder.

{
  "task": "Review this folder and propose a safe organization plan.",
  "rules": [
    "Do not move, rename, edit, or delete any files until I explicitly approve.",
    "First, summarize what types of files are in the folder.",
    "Then propose a folder structure.",
    "Flag anything uncertain for human review.",
    "After I approve the plan, organize only the files covered by the approved plan."
  ],
  "output_format": "A short summary, proposed folder structure, and list of files that need human review."
}

How To Write a Good Cowork Task

A Cowork prompt is closer to a task brief than a normal chat message. Tell Claude the outcome, source material, output format, permissions, what it may change, what it must not change, review requirements, and where to save the result.

{
  "outcome": "Create a weekly operations summary from the files in this folder.",
  "source_material": "Use only the files in the selected Cowork working folder.",
  "output": "Create a formatted document and a short executive summary.",
  "permissions": {
    "allowed": [
      "Read files in the selected folder",
      "Create new files in the output folder"
    ],
    "not_allowed": [
      "Delete files",
      "Rename files",
      "Move original files",
      "Use outside sources unless I approve"
    ]
  },
  "review_step": "Show me your plan before creating the final document."
}

Projects: The Best Way To Manage Repeat Work

A Cowork project is a local workspace for related tasks. It can have its own files, context, instructions, scheduled tasks, and memory. Projects are ideal for recurring reports, client work, policy work, board packets, content operations, and ongoing research.

Key limits matter: Cowork projects are desktop-only, stored locally, and do not have cloud sync for project data at this time. Cowork projects also do not support project sharing for Team and Enterprise members.

Plugins, Skills, and Connectors

Connectors let Claude reach approved services such as Google Drive, Gmail, Slack, DocuSign, and similar tools. Skills provide reusable workflow instructions. Plugins bundle skills, connectors, and specialist behavior into one package.

Use plain Cowork for simple file-based tasks. Use a project for repeat workflows. Consider plugins when the workflow is role-specific, such as sales, finance, legal, marketing, HR, operations, or data analysis.

Scheduled Tasks and Recurring Routines

Scheduled tasks let you describe a Cowork task once and run it automatically on a recurring basis or on demand. They can produce daily briefings, weekly reports, recurring research scans, monthly folder cleanup, and standing team updates.

Scheduled tasks save your prompt as task instructions and can use the connected tools, skills, and plugins configured in Cowork. They only run while the computer is awake and Claude Desktop is open.

{
  "scheduled_task": "Every Friday, create a weekly project summary from the latest files in this Cowork project.",
  "rules": [
    "Use only project files and connected sources I have approved.",
    "Create a short executive summary first.",
    "List open loops and missing information separately.",
    "Do not send, publish, delete, or move anything automatically.",
    "Save the finished report in the project output folder."
  ]
}

Do not schedule tasks that send messages, make purchases, delete files, access sensitive files, or take actions that are hard to undo.

Computer Use: Powerful, But Not the First Thing To Try

Computer use is a related Cowork capability that lets Claude interact with desktop apps when a connector or browser path is not enough. It should not be the first thing a beginner tries.

Computer use is in research preview for Pro and Max plans. In Cowork, Claude prefers connectors first, browser interaction second, and direct screen interaction last. Connectors are usually faster and more reliable than screen navigation.

Avoid computer use with sensitive legal, financial, medical, credential, personnel, or private information. Close unrelated sensitive windows, apps, and tabs before using it.

Best PromptedWork Workflows for Claude Cowork

Start with workflow types that match Cowork's strengths: multiple files, repeated reports, and tasks where Claude can inspect first, plan second, and create a finished output after approval.

• Admins and office work: build a board or leadership meeting packet, organize meeting folders, or create a weekly update from reports.
• Freelancers and consultants: review a deliverable folder against a client checklist, summarize call transcripts, or synthesize project files.
• Educators and coaches: turn readings, notes, and slides into a workshop pack, or turn session notes into follow-up materials.
• Local business work: organize vendor files, turn receipts into an expense report, or create a weekly operations summary from approved files.
• Nonprofit work: prepare board packets, volunteer onboarding packets, donor update drafts, and impact summaries from approved source material.
• Healthcare administration: use only for non-clinical administrative work from approved, de-identified source material unless your organization has formally approved a broader use.

Safety Rules for Everyday Users

• Use a dedicated working folder.
• Start with copied files.
• Do not grant broad folder access.
• Do not include sensitive financial, legal, medical, credential, personnel, or personal files.
• Ask Claude to propose a plan before acting.
• Keep backups.
• Review outputs before using them.
• Pause scheduled tasks you no longer need.
• Use connectors before computer use when available.
• Close unrelated sensitive apps and tabs before computer use.
• Stop the task if Claude starts accessing files, websites, or tools you did not ask it to use.

Troubleshooting and First-Run Mistakes

• Cowork is not visible: update Claude Desktop and confirm you are on a paid plan with Cowork access.
• A task does not run: confirm Claude Desktop is open, your computer is awake, and your internet connection is active.
• Claude gets confused: narrow the task and provide clearer source files.
• Outputs are too generic: add project instructions and an example finished output.
• Claude changes too much: tighten permissions and require plan approval before action.
• A scheduled task misses a run: the computer may have been asleep or Claude Desktop may have been closed.

Sources Checked

Sources checked on April 18, 2026:

• Anthropic Claude Cowork product page
• Get started with Claude Cowork
• Organize your tasks with projects in Claude Cowork
• Understanding Claude's personalization features
• Use Claude Cowork safely
• Schedule recurring tasks in Claude Cowork
• Use plugins in Claude Cowork
• Assign tasks from anywhere in Claude Cowork
• Let Claude use your computer in Cowork

Quarterly Refresh Flag

Recommended review date: July 18, 2026.

Recheck plan availability, feature status, computer use preview status, scheduled tasks behavior, project memory behavior, plugin availability, desktop and mobile requirements, and enterprise compliance or monitoring limitations.

Why PromptedWork Cowork Workflows Are Useful

PromptedWork Cowork workflows are designed for higher-friction administrative tasks where execution depth matters: collecting files, comparing sources, producing polished outputs, and reducing manual window-switching.