Home / Choosing the right way in
Cowork, the default mode for a non technical user
Cowork acts directly on connected folders and breaks work into small passes rather than a single giant treatment.
Cowork is Anthropic's desktop agent. As recorded on 2 September 2026, it opens from the desktop application on all paid plans, and from the web or mobile on the Pro, Max and Team plans, with an Enterprise account gaining access wherever an administrator has switched it on. You describe a result, Claude reads and writes the files in the folders you have connected to it, plans several steps, then hands you the finished work, without ever opening a terminal.
Four steps for a first task
Launching a first task always follows the same sequence: open Claude on one of the three surfaces, select Cowork there rather than the chat, describe the task you want carried out, then review Claude's approach before letting it run. This last step is not decorative, a wrong assumption spotted before execution costs no more than a reread sentence, the same mistake spotted after execution can require undoing work already done. Before authorising anything, also choose a review level: one mode pauses before each action and lets you approve or refuse, a second lets Claude examine the safety of each action itself and block what it judges dangerous, a third checks nothing automatically. One thing does not change from one mode to another: as recorded on 2 September 2026, the documentation states that Claude asks for confirmation before any permanent file deletion, even in the most permissive mode. This does not make that mode a safe one, it lets through without check everything that is not a deletion, starting with overwriting a file. Reserve it for tasks that only read, and prefer the systematic pause the first time you try a new folder or a new type of task.
A reasonable folder, not an entire folder
Cowork's documented strengths are precise: turning scattered notes into a formatted document, building a real spreadsheet with formulas rather than a flat table, putting together a presentation from a transcript, organising hundreds of files into coherent subfolders. On a large folder, aiming at a precise subset remains the safest way to start a first task. A vague instruction such as sort or fix, launched on an entire folder, forces Claude to guess your sorting preferences, and the disappointment that follows almost always comes from this vague brief, not from a real limit of the tool.
Instruction donnee a Cowork :
Dossier Factures 2026, trier les fichiers en sous dossiers par mois,
format annee-mois, sans rien supprimer.Brief this first task as you would brief a colleague discovering it: a precise result, and an example or a note of rules if you have one. The next lesson covers the two computer settings to check before launching a task of this kind over a long stretch.
The four steps of a first Cowork task
An employee launches his first Cowork task by pointing it at his department's entire shared drive, with the instruction sort this. Claude presents the plan it intends to follow. The employee skims this plan, then lets execution start.
Write in one sentence what this situation establishes, and in one sentence what it does not establish.
What this establishes: It establishes that the targeted scope covers the entire drive and that the instruction given names an action without saying what sorting result to obtain at the end.
What this does not establish: It does not establish what Claude actually did with the files, nor what the plan the employee skimmed actually contained.
The three most common miscalibrations
- Too broad It establishes that pointing Cowork at an entire folder always fails, whatever its real size.
- Too narrow It establishes only a difference in wording between the two instructions, without saying anything about the scope targeted by each.
- Beside the point It establishes that the plan proposed by Claude described the expected sorting, since the employee let it run.
- Cowork reads and writes the files of connected folders directly, without going through a manual upload or download.
- A first task always follows the same four steps, open Claude, choose Cowork, describe a precise result, then review the plan before running it.
- Three review levels exist before an action happens, a systematic pause, an automatic check, or no check at all.
- Targeting a precise subfolder avoids the disappointment of a task that is too broad delivered on a single vague verb.
- Cowork's internal coordination on a large folder helps, it does not replace a reasonable starting scope.
Open a Cowork session, choose the approval mode that pauses before each action, and run it on a subfolder of a few files rather than an entire folder.
These points depend on an interface or a rule that may have changed since this was written. Check them on your own screen before relying on them.
- The exact wording of the menus used to create a Cowork project, such as the name of the Projects button or screen, comes from a June 2026 source and was not rechecked on 2026-09-01, the lesson therefore stays at the level of the four steps without citing a precise menu name.
- How Cowork splits work on a large folder, in a single pass or in several internal streams, is not established by any public source recorded on 2 September 2026. This course therefore draws no promise of speed from it.
Every datable claim in this lesson links here to the public text behind it. A source that does not open proves nothing.
- Anthropic, getting started with Claude Cowork, surfaces and plans consultée le 2026-09-02
- Anthropic, using Claude Cowork safely, confirmation before permanent deletion consultée le 2026-09-02