Home / Choosing the right way in
Cowork, the default mode for a non technical user
On an account that has not yet moved to the new unified experience, Cowork acts directly on connected folders and is best split into small passes rather than one giant job; once the account has moved, the same actions happen from the same conversation as the chat, with a single approval setting for the whole conversation.
Cowork is Anthropic's desktop agent. As of the 2 September 2026 survey, it opens from the desktop app on all paid plans, and from the web or mobile on Pro, Max and Team plans, with an Enterprise account getting it wherever an administrator has switched it on. Access to a local folder requires the desktop app to stay open and connected: the web and mobile alone are not enough for this kind of access. You describe a result, Claude reads and writes the files in the folders you have connected to it, plans several steps, then hands back 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 done, then read through Claude's approach before letting it run. This last step is not decorative. A wrong assumption spotted before execution costs nothing more than a sentence read, while the same mistake spotted afterwards may mean undoing work already done. Before authorising anything, also choose a verification level: a first mode pauses before actions and lets you allow or refuse, a second lets Claude check the safety of each action itself and block what it judges dangerous, a third checks nothing automatically. This setting can be changed at any time, it does not commit the whole session. One thing does not change from one mode to the next: as of the 2 September 2026 survey, the documentation states that Claude asks for confirmation before any permanent file deletion, even in the most permissive mode. That does not make this mode a safe one, it lets everything that is not a deletion through unchecked, starting with the rewriting of a file. Keep 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 a whole one
The documented strengths of Cowork are specific: 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, Cowork itself splits a complex job into subtasks and coordinates several streams in parallel, a documented capability that is not a promise of speed. Aiming at a specific subset is still the safest way to begin a first task. A vague instruction such as tidy or fix, launched on a whole folder, forces Claude to guess your filing preferences, and the disappointment that follows almost always comes from that fuzzy brief, not from a real limit of the tool.
Instruction given to Cowork:
Invoices 2026 folder, sort the files into subfolders by month,
year-month format, without deleting anything.Brief this first task as you would brief a colleague who is new to 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 period.
On an account that has moved to the new experience
Since 16 September 2026, an account that has moved to the new unified experience no longer asks you to select Cowork rather than the chat: the same conversation handles both the question and the action, and Claude decides for itself whether to answer or to act on the connected folders. The choice between the three verification levels described above then becomes a single setting, Auto or Manual, valid for the whole conversation rather than for each task taken separately. The four-step sequence described here keeps its value for any account that the switch has not yet reached, and the lesson on the merger details this change.
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 tidy this up. Claude presents him with the plan it intends to follow. The employee skims the plan, then lets the run 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 filing 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 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 that the instruction was two words long, saying nothing about the folder it applied to.
- Beside the point It establishes that the plan Claude proposed described the expected filing, since the employee let it run.
- Cowork reads and writes the files in connected folders directly, with no manual upload or download.
- A first task always follows the same four steps on an account that has not yet moved, open Claude, choose Cowork, describe a precise result, then read the plan before running it.
- Three verification levels exist before an action takes place on that same account, a systematic pause, an automatic check, or no check at all; once the account has moved to the new experience, a single setting, Auto or Manual, applies to the whole conversation.
- Targeting a specific subfolder avoids the disappointment of a task that was too broad, handed over on a vague verb.
- Cowork itself splits a complex job into subtasks and coordinates several streams in parallel, a documented capability that does not replace a reasonable starting scope.
Open a Cowork session, choose the approval mode that pauses before every action, and launch it on a subfolder of a few files rather than on a whole folder.
Every datable claim in this lesson links here to the public text behind it. A source that does not open proves nothing.
- Anthropic, get started with Claude Cowork, surfaces and plans consultée le 2026-09-02
- Anthropic, use Claude Cowork safely, confirmation before permanent deletion consultée le 2026-09-02
- Anthropic Help Center, Claude Cowork and chat are one Claude, release note of 16 September 2026 consultée le 2026-09-28