Claude Cowork Just Reached Your Whole Team: The Desktop Agent That Does Real File Work

What you'll learn in this article:

• What Claude Cowork actually does on your desktop, and how it differs from a normal chat window
• Why the January 23 expansion to Team and Enterprise plans changes who can use it
• The exact way to scope a task so the agent stays safe and predictable
• Three first tasks that pay back the setup time in one week
• The folder-access model and how to keep confidential files out of reach

Most AI tools answer questions. They sit in a chat box, wait for a prompt, and hand back text you then copy somewhere useful. The work of moving that text into a spreadsheet, renaming the files, building the report, that part still lands on you. For an operations lead or a founder, that gap is where the hours go: not in thinking, but in the mechanical assembly that follows.

Claude Cowork closes that gap. It is a desktop agent that reads, edits, and creates files directly inside folders you approve. You do not paste output into a spreadsheet; the agent builds the spreadsheet. You do not rename forty screenshots; the agent renames them. On January 23, Anthropic expanded Cowork from Pro accounts to Team and Enterprise plans, which means the people who do the most repetitive file work in your organization can now hand it off.

The catch is that an agent with file access is only useful if you know how to scope it. Give it a vague task across your entire drive and you get an unpredictable mess. Give it one folder and one bounded output and you get an hour of work back. The difference is entirely in how you set it up, and that is what most people get wrong in the first week.

What Cowork Is, Precisely

Claude Cowork launched as a research preview on January 12, rolled out to Pro subscribers on January 16, and reached Team and Enterprise plans on January 23. It runs as a macOS desktop application. Anthropic built it by repackaging the computer-use capability that already powered Claude Code, the tool developers use, and aiming it at people who are not developers.

The defining feature is folder access. In a normal Claude chat, you can attach a file and ask about it, but Claude cannot reach into your file system. Cowork can, but only where you let it. You grant access to specific folders. Inside those folders, Claude can open files, read them, edit them, and create new ones. Outside them, it sees nothing.

That single design choice is what makes Cowork an agent rather than a chatbot. It plans a multi-step task, then executes the steps against real files. Anthropic's own examples are deliberately mundane: reorganize a downloads folder by sorting and renaming files, turn a folder of receipt screenshots into an expense spreadsheet, or produce a first draft of a report from a folder of notes. Mundane is the point. These are the tasks that quietly eat an afternoon.

Why the Team and Enterprise Expansion Matters

When Cowork was Pro-only, it was a single-seat tool. An individual could use it, but the repetitive file work in a company rarely sits with one person. It sits with coordinators, analysts, EAs, and ops staff who each spend hours a week on the same mechanical tasks: compiling, formatting, renaming, and drafting.

The January 23 expansion to Team and Enterprise plans puts Cowork in front of those people. A finance team can use it for expense compilation. An operations group can use it for file organization and report drafting. The value compounds because the tasks are repetitive: once someone defines a good Cowork task, it can be run every week.

For an executive deciding where to deploy it first, the rule is simple. Find the task your team does most often that involves moving information between files. That is the highest-return place to start.

The Setup That Keeps the Agent Safe

The mistake that ruins the first week with Cowork is over-granting. People point it at their whole Documents folder, give it a loose instruction, and then cannot predict what it touched. The fix is to scope tightly on both ends: one folder in, one new output out.

Here is the prompt pattern that works. Notice that it names the folder boundary, defines the exact output, and forbids changes to originals.

CLAUDE COWORK BOUNDED TASK PROMPT

Look only in the folder I have granted you. Read every receipt image and PDF in it. Build one new spreadsheet named Expenses_[Month] with columns: date, vendor, amount, currency, category, and source filename. Do not modify or move any original files. When done, give me a one-line summary of total spend by category.

Three things make this prompt safe. First, "look only in the folder I have granted you" reinforces the boundary. Second, it specifies a single new file as the output, so you know exactly what was created. Third, "do not modify or move any original files" protects your source data. Review the new spreadsheet before you trust the result, then run the same task next month.

Three First Tasks That Pay Back Setup Time

Task 1: Receipts to Expense Sheet

Create a folder, drop in your receipt screenshots and PDFs, grant Cowork access, and run the bounded prompt above. A month of receipts that would take an hour of manual data entry becomes a single reviewed spreadsheet in minutes. Finance leads and founders who self-manage expenses get the clearest, fastest win here.

Task 2: Downloads Folder Cleanup

Point Cowork at your downloads folder with a clear renaming and sorting rule.

DOWNLOADS CLEANUP PROMPT

In the folder I have granted you, sort files into subfolders by type: Documents, Images, Spreadsheets, and Installers. Rename each file to a clear, dated name in the format YYYY-MM-DD_description based on its contents or creation date. Do not delete anything. Give me a summary of how many files moved into each subfolder.

This turns a chaotic folder into a navigable one without you opening a single file.

Task 3: Notes to First Draft

Drop a set of meeting notes or research snippets into a folder and ask for a structured first draft.

NOTES TO DRAFT PROMPT

Read every note file in the folder I have granted you. Produce one new document named Draft_[Topic] that organizes the material into: a one-paragraph summary, the three main themes with supporting points under each, and a list of open questions. Quote directly where the notes are specific. Do not change the original notes.

The draft will not be final, but it converts scattered notes into a structured starting point, which is the part that usually stalls.

Keeping Confidential Files Out of Reach

Folder access cuts both ways. The same design that lets Cowork build your expense sheet means you must be deliberate about what it can see. Two rules keep you safe.

First, never grant access to a folder that contains files the task does not need. Create a dedicated, single-purpose folder for each Cowork task and move only the relevant files into it. The agent cannot reach what is not in a granted folder.

Second, keep originals protected by always instructing Cowork to create new files rather than overwrite. Every prompt above includes a "do not modify originals" clause for this reason. Review the new output, and only then decide whether to replace anything yourself.

Because Cowork is still a research preview, treat its output the way you would treat a capable new hire's first week of work: useful, fast, and worth reviewing before it goes anywhere important.

Action Steps Summary

• Enable Cowork on the right plan: Open Claude on macOS with a Pro, Team, or Enterprise account and turn on the Cowork research preview. Team and Enterprise access went live January 23.
• Create a single-purpose folder: Make one folder per task and move only the files that task needs into it. This is your safety boundary.
• Grant access and run a bounded prompt: Use the receipts-to-spreadsheet pattern: name the folder boundary, define one new output file, and forbid changes to originals.
• Review before you trust: Check the new file the agent created against a few source files before relying on it. Treat the first run as a draft.
• Turn the best task into a weekly habit: Once a task is reliable, run it on a fixed schedule. That is where the 2 to 4 hours per week of savings comes from.