How it works with folders and files
The workspace and why it matters
A working folder gives Claude access to selected local files. It is one source of context alongside attachments, project knowledge, and any tools you enable. Choose a small practice folder so you can see exactly what the task reads and changes.
How you start it, in practice
You do not install anything separate. Open the Claude Desktop app (macOS or Windows) and point Claude at the folder you want to work in — that becomes the working folder for the session. For this course, use two explicit instructions:
- Inputs: put copies in the connected folder and name the files Claude should read. In cloud tasks, the app can fetch those files for processing; folder access does not mean offline processing.
- Outputs: say "save the result in output/ inside this connected folder and tell me the path." Open that path in Finder or File Explorer. If the result is a session attachment, download it to the folder and open it before using it.
The working folder = its workspace
When you start a session, Claude "sits" in a folder. It can read the connected folder and its subfolders; attachments and other enabled tools can provide additional context. Connecting one folder does not grant access to your whole computer. That means two things:
- Safety: if you want it to work on only one project, put that project's files in a folder and start there.
- Clarity: when you say "the document with the offer," it looks in the current folder, not across everything you own.
Quarterly-Report-Project/ — and put all the relevant files inside. That way the assistant has clean context and you always know where the results are.
What types of files it "sees"
Almost any office file: text, Word (.docx), Excel (.xlsx), CSV, PDF, images, notes. A plain text file it simply reads; an Excel sheet or a scanned PDF it opens with the right tool behind the scenes (for a spreadsheet it may even run a few lines of code to total a column). You never pick the tool yourself — you tell it what you want, and it chooses the method.
How to point it at a file
You can refer to a file in plain language:
- "Read offer-supplier-A.pdf"
- "Take all the files in the invoices/ folder"
- "The Excel document with the budget"
If it is unsure — say, two files could match — it asks you. When you want to be precise, give the exact name.
Tell it where to save new files
Ask for an exact local destination, such as output/report.docx, and check that it exists. A file offered in the session is also a real deliverable, but you may need to download it. Check both the path and the contents; a message saying "done" is not proof that the local file was saved.
Is it safe? How permissions work
The most common worry: "what if it breaks or deletes my files?" Short answer: you choose the working folder, and that folder is the normal boundary. Choosing it grants Claude read/write access there, so it can inspect files and create new ones. Anything beyond that boundary, and anything hard to undo, deserves a deliberate approval.
| Safety net | What it means for you |
|---|---|
| The folder is explicit | Claude reads and writes in the working folder you selected. It does not silently roam across your whole computer. |
| Approval depends on the mode | Auto is the default on Pro, Max, Ultra, and Team; Manual is the default on Enterprise. Auto can proceed after automated safety checks. Select Manual for first runs to see approval requests for new tools or sites; do not assume every outside action will pause. |
| Deletion is special | Permanent deletion still requires explicit confirmation. For first runs, ask for copies or backups before bulk moves, renames, or overwrites. |
| You stay in control | You can ask for a plan first, watch what it did, stop a run, and review outputs before you use them. |
Set up a project, step by step
A project is the durable form of a working folder: a folder you keep coming back to, where Claude remembers its instructions, files, and context from one session to the next. Here is the full setup, click by click.
-
Go to Projects. In Claude Desktop (pick Cowork first if your message box offers the choice), choose Projects in the left rail, then click New project (top-right).
Projects → New project. Each card is one project: a folder plus everything Claude should remember about it. -
Name it and say what it's for. The Create a project dialog asks what you're working on (the project's name) and what you're trying to achieve — a sentence or two that Claude keeps as standing context.
A name, a goal, and optional uploaded context. Link the local working folder from the project screen after creating the project. -
Create the project, then link your working folder. Click Create project. On the project screen, use Context → Add → Link local folder, select your practice folder, and review the permission request for that exact folder. Confirm that Context shows a linked folder. In the tested desktop layout, Add context in the creation dialog uploads files; the Add folder chip beneath a message adds session context. Use the project's Link local folder control for a folder you want to keep with the project. Labels can vary by version.
-
You are in the project. The workspace opens with a message box ('New session in …'), the working-folder chip beneath it, and a right-hand panel with Instructions, Context, Folder, Memory and Scheduled. If the app offers Keep folder linked, that keeps the original folder local; it does not make a new Pro/Max/Ultra task run locally. Cloud project storage and linked local folders are different choices. From here, you simply describe the work.
The open project: one message box, the folder as context, and panels for instructions, schedules, and a memory that persist across sessions.
Three things you can set per project
A project is more than a folder. Down the right-hand side of the project screen are three panels that shape how Claude works here — and, unlike a one-off chat, they stay put from one session to the next.
| Panel | What it is for |
|---|---|
| Instructions | Standing rules for the project — tone, formatting, and how Claude should work here. Set them once and they apply to every task in the project, so you never repeat the same guidance. |
| Scheduled | Recurring tasks that run on a timer — a weekly digest, a Monday report. Set one up and the project carries it out on schedule, even when you are not watching. |
| Context, Folder & Memory | What the project knows: the files and folders you linked (Context), the working folder it reads and writes in (Folder, here colearn), and a Memory where you can ask Claude to remember facts it should carry across chats. |
You can ignore all three at the start — a project works fine with just a folder. Add them as your workflow takes shape: Instructions when you catch yourself repeating the same guidance, Scheduled when a task recurs, Memory when there is something Claude should always know.
That is the whole setup. From now on, "start Claude in a folder" simply means opening this project — and the mini-exercise below is your first run.
Mini-exercise (3 minutes)
- Create a new folder on your desktop called
Test-Claude. - Put a fictional test document or an approved, redacted copy inside. Local-folder access does not mean the document stays off Anthropic's servers.
- Start Claude in that folder and ask: "Tell me what files are here and, briefly, what each one contains."
Watch how it responds — that shows you exactly what it "sees."