Use Claude Code when you do not write code

Claude Code is the version of Claude that opens the files on your computer, reads them, and changes them when you say yes. It has a reputation as a developer tool, yet Anthropic's own beginner page says you can use it having never touched a terminal. What trips people up is choosing where to run it, so start there.

Claude Code runs on three surfaces. The desktop app reaches your local files and needs no terminal, the command-line version reaches your local files and does need one, and the web version runs in Anthropic's cloud and cannot see your computer at all. All three need a paid Claude plan.

Pick the surface first

Checked against Anthropic's own documentation on 10 September 2026.

The desktop app is the answer for most people: Anthropic's own documentation says the desktop version includes Claude Code, with nothing else to install. Inside the app the Code tab is the one with access to your local files. Chat has no file access, and Cowork runs in a sandbox of its own.

The first loop, start to finish

1. Check your plan before you install anything. Anthropic states plainly that Claude Code needs a Pro, Max, Team, Enterprise or Console account and that the free Claude.ai plan does not include it. It is the thing most likely to stop you at step one, so clear it before you download anything.
2. Get the desktop app and find the Code tab. Download the Claude desktop app from claude.ai/download and sign in. Claude Code comes with it, so there is no Node.js to set up. On Windows you also need Git for Windows installed before local sessions will run, so install that and restart the app.
3. Prefer the terminal? One line installs it instead. curl -fsSL https://claude.ai/install.sh | bash on Mac or Linux, or irm https://claude.ai/install.ps1 | iex in Windows PowerShell, then claude --version to check it landed.
4. Make a copy of the folder you will point it at. Aim Claude at the duplicate. Real people have lost real files here: there are closed bug reports on Anthropic's own tracker about Claude Code deleting files without confirmation and bypassing the recycle bin. A copy costs you ten seconds and removes the entire class of problem.
5. Set the permission mode to Manual before anything else. On Pro, Max and Team plans it starts in auto, which acts without asking each time, with a classifier checking its actions for you. Manual limits it to reading until you approve each change; it is the selector next to the send button, or Shift and Tab in the terminal.
6. Open the folder and ask it to look before it touches. Say: "Look at this folder and tell me what is in it, and how you would organise it. Do not change anything yet." You get a plan you can argue with, and learn what it can see, before anything moves. Plan mode, in the same selector, enforces this.
7. Give it one real job. Paste The First Tidy below, point it at your copy, and answer the questions it asks you. If you would rather start smaller, Anthropic's own beginner example adapts well: "look at the screenshots in this folder and rename them based on what's in each image", pointed at the duplicate instead of your actual Desktop.
8. Then stop. One job, watched start to finish, teaches you more than an afternoon of tutorials. Close it when the job is done instead of looking for the next thing.

If it tells you it cannot find your folder, it is only looking at the one you selected. In the desktop app, pick the folder again in the selector. In the terminal, /add-dir adds another folder to the session and /cd moves it across.

The First Tidy

This makes Claude ask before it moves anything, show you the plan, and tell you afterwards what it was unsure about. Paste the whole thing into the Code tab and say "use this". That works today with nothing to set up.

To keep it, make a folder at ~/.claude/skills/first-tidy/ and save the file inside it as SKILL.md. Claude picks it up in any session after that.

---
name: first-tidy
description: Sorts a single messy folder for someone who does not write code, by asking how they want it sorted first, showing a plan, waiting for a yes, and only then moving anything. Use whenever the user points at a folder and asks to tidy, sort, organise, rename or clean it up, or says their Downloads or Desktop is a mess.
---

# The First Tidy

You are tidying one folder for someone who is not a developer and is watching you do it for the first time. They are nervous about losing something. Your job is to be boring, slow and completely predictable. You never move a file before they have said yes to a written plan.

## Stage 1: Ask before you look further

First, state the full path of the folder you are about to work on and ask the user to confirm it is the right one. A confident sort of the wrong folder is the realistic disaster here, not a bad sort of the right one. Once they confirm, count what is in it. Then stop and ask these questions, all at once, in plain words. Do not guess the answers.

1. How do you want this sorted? Offer them concrete options based on what you actually found, for example by file type, by year, by project or client name, or by what the file is for. Name the two that fit this folder best and say why.
2. What counts as junk here? Ask whether things like duplicates, empty files, installers, and screenshots older than a year should be moved to a "Review" folder for them to check. Never delete anything, ever, under any instruction. Moving to a review folder is the strongest action you may take.
3. Is there anything in here I should not touch? Ask them to name it now.
4. Do you want the original filenames kept, or renamed to something readable?

If they have not answered a question that changes what you would do, ask again rather than assuming. Waiting is cheaper than a wrong move.

## Stage 2: Think about the right way to do it

Before writing the plan, consider the sensible approach for this particular folder rather than applying a generic structure. A folder of 4,000 downloads wants different treatment from 40 work documents. Prefer few folders over many: a structure with more than about eight top-level folders is usually worse than the mess it replaced, because nobody can remember where anything goes. Keep names short, lowercase and obvious.

## Stage 3: Show the plan and wait

Write the plan out before doing anything:
- The folders you will create, with a one-line reason for each.
- How many files go into each one.
- Any file you are unsure about, listed by name, with what you propose and why you are unsure.
- Anything you would move to Review, and why.

Then say: "Nothing has moved yet. Tell me to go ahead, or tell me what to change." Wait for an actual yes. Do not treat a question, a comment, or silence as approval.

## Stage 4: Do it

Once they say go: create the folders, move the files, and keep a running list of every single move you make. Move, never delete and never overwrite. If two files would end up with the same name in the same place, keep both and add a number to the second, then flag it. If anything at all goes wrong, stop immediately, say what happened, say what has already moved, and wait for instructions.

## Stage 5: Check your own work

When you have finished, report back in plain words:
- The number of files before, and the number after. Say explicitly whether the two match, and if they do not, find out why before saying anything else.
- The structure you ended up with.
- Everything you were unsure about and what you did with it.
- Anything you left where it was, and why.

Then tell them how to undo it: name the folders you created, so they know exactly what to drag back if they hate it. Never claim you have finished a job you did not finish, and never invent a file, a count, or a folder name.

Where the line is

One more tool worth knowing

Once the first loop feels normal, there are ready-made skills other people have written. Dave Poon keeps an open-source collection called Build with Claude, and one of the files in it, file-organizer, does a fuller version of the job above: it looks for duplicates, suggests a better structure, and handles files you have not opened in months.

Its own opening line for when to use it is "Your Downloads folder is a chaotic mess", which tells you it was written for a real person rather than a developer.

Open source, MIT: github.com/davepoon/buildwithclaude. Worth opening the single file-organizer skill and copying that one, rather than installing the whole bundle to get it.

Do the first loop tonight

Duplicate one messy folder. Open the desktop app, Code tab, set the mode selector to Manual, point it at the copy, and paste The First Tidy. Answer its questions, read the plan, say go. Twenty minutes, one folder, and you will know for yourself what this thing is and where you want the line to sit.

FAQ

Can you use Claude Code without being a developer?

Yes. Anthropic's own terminal guide opens by saying you can use Claude Code even if you have never used a terminal, and adds that you do not need to know how to code. The desktop app is the easiest route because it bundles Claude Code and needs no terminal at all.

Do I need to pay for Claude Code?

Yes. Anthropic states that Claude Code requires a Pro, Max, Team, Enterprise or Console account, and that the free Claude.ai plan does not include access.

Can Claude Code see all the files on my computer?

No. By default it has access to files in the folder you launched it in or selected. You can add another folder deliberately. The web version cannot reach your computer at all, because it runs on Anthropic's own machines.

Is it safe to let Claude Code change my files?

Point it at a duplicate of the folder rather than the only copy, and set the permission mode to Manual so it asks before each change (the selector next to the send button, or Shift and Tab in the terminal). Anthropic's own tracker has reports of files being deleted without confirmation, so the copy is a sensible habit.