Set Up Claude Cowork and Run Your First Task
Last updated: July 2026
Claude Cowork is the version of Claude built for people who do not write code. In the next hour you will install it, point it at a messy folder on your own computer, hand it a real task, and set that task to run again every week without you. By the end you will have one annoying job off your plate and a repeatable pattern for taking off ten more.
What you need before starting
- A paid Claude plan (Cowork is included on Pro, which is 20 dollars a month, and up)
- The Claude desktop app installed on your computer
- One real folder that is genuinely messy: downloads, screenshots, receipts, anything
- About an hour, and nothing open that you are precious about
Step 1: Open Cowork in the desktop app
Cowork lives in the Claude desktop app, not the browser. Install the app, sign in with your paid account, and find the Cowork area. It looks different from the chat box you are used to, because it is allowed to reach into the files on your computer, not just talk.
Checkpoint: You see a Cowork workspace that can act on your files, not just a chat window.
Step 2: Point Cowork at a real folder
Do not start by asking it to change anything. Start by asking it to look. Type a plain instruction naming the folder you want it to work in:
Look at my Downloads folder and tell me what is in it. Do not change
anything yet. Just summarize what you find and how you would group it.
Cowork will scan the folder and come back with a summary, usually grouped by file type. This step matters because it shows you the model understands your folder before it touches it.
Checkpoint: Cowork lists the kinds of files it found and proposes groupings, and it has not moved a single thing yet.
Step 3: Write the task the way that actually works
This is the step that decides whether you are impressed or annoyed. A vague instruction gives a vague result. Here is the version most people type first:
Organize my Downloads folder.
And here is the version that actually works:
Organize my Downloads folder into subfolders by type: Images, PDFs,
Spreadsheets, Installers, and Other. Keep the original file names.
Move the files, do not copy them. When you are done, write a short
list of what went where into a file called sorted.txt.
The first time my students run the vague version, they go from images cluttering the desktop to folders cluttering the desktop. The fix is never a better tool, it is a more specific instruction. Tell Cowork the outcome you want, the rules it must follow, and what "done" looks like.
Checkpoint: Cowork asks you a clarifying question or two (how to handle duplicates, what counts as "Other") before it touches anything. That hesitation is the sign you gave it enough to work with.
Step 4: Let it run, and answer its questions
Approve the plan and let it go. Cowork works in multiple steps, sometimes running several sub-tasks at once, and it will pause to ask permission before it does anything it cannot undo. Answer its questions and let it finish.
Checkpoint: Your folder is organized into the subfolders you named, and sorted.txt exists with a plain rundown of what moved where.
Step 5: Put it on a schedule
A one-time cleanup is nice. The real value is never doing it again. Tell Cowork to repeat the task:
Run this same task every Friday at 5pm: sort any new files in Downloads
using the same rules as before, and add what you did to sorted.txt.
Checkpoint: A scheduled task now shows in Cowork. One thing to know: your computer has to be on and the app running at that time for it to fire.
Step 6: Give Cowork your standing instructions
The last upgrade is the one that makes every future task sharper. In Cowork's settings you can set instructions that apply to everything it does: your tone, your rules, how you like results delivered. It is the same idea as a CLAUDE.md file for developers, just kept in settings instead of a file at your project root.
Checkpoint: Open a brand new task and confirm Cowork already follows your standing instruction without you repeating it.
Where this breaks
The usage meter moves faster than you expect. Cowork counts all of your Claude use that day, not just this one task. If you have been chatting all morning, the meter is already partway up before you start. Check Settings, then usage, so the number does not surprise you.
Scheduled tasks need the machine awake. A weekly task only runs if your computer is on and the app is open when it is due. For anything that matters, do not assume it fired. Glance at the output file.
Big images get downsized. When Cowork analyzes large images it often converts them to smaller JPEGs to save usage. That is fine for sorting and filing, worth knowing if you need the originals left untouched.
It asks before deleting, on purpose. If a permission prompt appears about removing a file, read it. Usually it is clearing a temporary file it created, not your data, but the prompt is there so you stay in control.
What to build next
Once one task runs on a schedule, the same pattern fits anything repetitive: a weekly summary of a folder of reports, renaming and filing receipts, turning a pile of notes into one clean document. The two upgrades that make all of it better are good standing instructions, which you set in Step 6, and knowing when to reach for Claude at work versus a quick chat. If you do write code, there is a more technical sibling worth knowing, Claude Code, but most professionals never need it.
If you want to set this up on your own files with someone watching your screen and catching the fiddly parts in real time, that is exactly what my sessions are. Book a free Discovery Call and bring the most annoying repetitive job you have.
These tutorials come from the actual curriculum I teach 1-on-1. Every step here I have run myself before publishing it.
Related articles
Keep reading on related topics.
Enjoyed this article?
You can master this and more with a dedicated 1-on-1 tutor.
Book a Free Discovery Call