Get Started
Use AI properly

Mission 10 of 11

Use Claude Code on your own files, with no coding at all.

Tidy a messy folder, turn a spreadsheet and scruffy notes into a report, and build a web page, by telling Claude Code what you want in plain English. You read, you decide, it does the typing.

46 minBeginnerClaude Pro, $20 a month, or $17 a month billed yearlyFree mission

What you'll do

Install it and meet the terminal

Open a terminal for the first time, paste one line to install Claude Code, and check that it worked.

Tidy a folder with a backup

Copy first, ask for a plan, approve the moves and check the result on a real messy folder.

Build a report and a web page

Turn rows and notes into a printable report with mistakes flagged, then make a personal page on your computer.

  • The skill that keeps you safe: knowing when to say No
  • A backup and checking habit you can use on any job
Before you start
  • A Windows 10 or 11 PC or a Mac on macOS 13 or later. These steps also work on Linux
  • A paid Claude plan. Pro is the cheapest that includes Claude Code
  • About 45 minutes, and a messy folder you'd love to sort out
  • No coding, and no experience with the terminal. Step 1 starts from nothing
Your progress0/7
● What you'll have in 46 minutes
Preview
Animation of the job you'll do in step 4: a plan first, then a messy folder sorted, with nothing deleted.
01/07Open the terminal and install Claude Code0 done
STEP 01 of 07~6 min

Open the terminal and install Claude Code

Meet the terminal, which is far friendlier than it looks, and get Claude Code onto your computer with one pasted line.

Everything in this lesson starts with Claude Code installed on your computer, and it lives in the terminal. This step gets you there: a plan check, a first look at the terminal and one pasted line.

Check your plan

  1. Open claude.com/pricing ↗ and find the Pro card.

    If you're on Free, upgrade to Pro before you carry on.

    A screenshot of the pricing page, November 2026, with prices listed in US dollars.

Open the terminal

  1. Press Win + X and choose Terminal or Windows PowerShell, not the one marked Admin.

  2. Press Cmd + Space, type Terminal and press Enter.

    How every terminal conversation goes.
Tip
It's a text chat with your computer. You type a line, press Enter, it replies. Before Windows and Macs had icons, this was the whole computer. Nothing happens until you press Enter, so you can't break anything by looking around.

Say your first word to it

  1. Type pwd and press Enter.

    It means "where am I?" and it's completely harmless.

    Terminal
    pwd
    Output
    Path
    ----
    C:\Users\user
    Tip
    You just did the hard part. That's the real output from a Windows machine. Yours will show your own name, and a Mac prints a single line. That location is your home folder, and it's where you'll work next.

Paste the installer

  1. Copy the line for your computer, paste it into the terminal and press Enter.

    Windows PowerShell
    irm https://claude.ai/install.ps1 | iex
    Mac or Linux Terminal
    curl -fsSL https://claude.ai/install.sh | bash

    Paste with Ctrl + V on Windows.

    Paste with Cmd + V on a Mac.

    A screenshot of Anthropic's official terminal guide. 1 is the Windows command, and 2 is the message you're waiting for.
    Tip
    It goes quiet, and that's normal. The installer shows no progress while it downloads. Leave the window alone until you see Claude Code successfully installed!
    Tip
    A rule for life. Only paste commands from a source you trust. These two come straight from Anthropic's terminal guide ↗, so check them against it any time you like.

Prove it worked

  1. Close the terminal window, open a new one, then type this and press Enter.

    Terminal
    claude --version
    Output
    2.1.258 (Claude Code)
    Tip
    Your number will be different. It updates itself in the background, so expect a higher one. Any number followed by (Claude Code) means you're in.
Checkpoint
claude --version prints a version number followed by (Claude Code).
If it breaksIt says 'irm' is not recognized + 3 more
It says 'irm' is not recognized
You're in the older Command Prompt rather than PowerShell. Close it, press Win + X, choose Terminal or Windows PowerShell, and paste again. PowerShell lines start with PS.
It says 'claude' is not recognized, or command not found
Open a brand new terminal window first, because the old one hasn't heard about the install. Still stuck? The troubleshooting section of the official guide ↗ has the exact fix for Windows and Mac.
Pasting does nothing
On Windows, right-click inside the window, which also pastes. Then press Enter.
I'd really rather not use a terminal at all
There's a Claude desktop app ↗ that runs Claude Code without one. The screens differ from this course, but the habits in steps 3 and 4 carry straight over.
Still stuck? Ask the community
STEP 02 of 07~4 min

Give it its first job in a practice folder

Sign in and watch it make real files on your computer, somewhere it's safe to mess around.

Claude Code is installed, so now you'll start it for the first time. You'll do it inside a practice folder, somewhere it's safe to mess around.

Make a practice folder

  1. Type this and press Enter. On Windows a small table appears, which just confirms it worked.

    Terminal
    mkdir claude-practice
  2. Step inside it. cd means "change directory", and directory is an old word for folder.

    Terminal
    cd claude-practice

Start Claude Code

  1. Type this exact line and press Enter.

    Terminal
    claude --permission-mode manual
    Tip
    Why the extra words? Newer versions can start in Auto mode, where a background check approves actions instead of you. Manual mode asks you first, and that's where you want to be while you learn. Use this same line whenever you start it during this course.

Answer the setup questions

  1. The first question asks you to choose a text style. Press Enter to accept the highlighted one.

  2. Choose how to log in. Keep option 1 highlighted and press Enter.

    Where to press on the login menu. If you chose a light or dark text style, your colours may differ.
    Warning
    Stick with option 1. Option 2 is billed by usage on a separate Console account, so it won't use the Pro plan you just paid for.
  3. Sign in. Your browser opens, so sign in with your Claude account and follow the prompts.

    Then come back to the terminal. If another short setup screen appears, read it and press Enter to carry on.

  4. Trust your practice folder. The highlight starts on No, exit, so press the Down arrow once to move it to Yes, I trust this folder, then press Enter.

    Where to press on the folder check. You'll see your own folder name.
  5. Check the bottom line. Under the box you type in, look for manual mode on. If it says something else, press Shift + Tab until it does.

    The four modes, and what each one lets it do without asking.

    Manual mode is the one that asks you first.

Give it a job

  1. Paste this into the box and press Enter.

    Paste into Claude Code
    Make me a practice mess. In this folder, create 15 small fake text files with realistic messy names: receipts, holiday notes, a CV, meeting notes, shopping lists, and a couple of near-duplicates like final and final FINAL. Put a line or two of made-up text in each.
  2. Approve the first file. When it asks permission, read what it wants to do, then press Enter on Yes.

    If it offers an option that allows edits for the rest of the session, take it: these files are fake, and it saves you pressing Enter 15 times.

  3. When it finishes, ask it what it sees. Paste this.

    Paste into Claude Code
    What's in this folder? Group the files in plain English and tell me which ones look like duplicates. Don't change anything.

See it with your own eyes

  1. On Windows, press Win + R, type %USERPROFILE%\claude-practice and press Enter. On a Mac, click the desktop, press Cmd + Shift + H, then open claude-practice.

    Tip
    This is the moment it clicks. A chatbot gives you words to copy somewhere. This made real files on your real computer, and then read them back. Everything else today is that same trick pointed at something you care about.
    Tip
    Two keys to remember. Esc stops it mid-task. /exit leaves Claude Code and takes you back to the plain terminal.
Checkpoint
You can open claude-practice in a normal window and see about 15 fake files, and Claude Code has described them to you in groups. You now have a safe mess to practise on.
If it breaksIt says 'Login expired' or 'Not logged in' + 3 more
It says 'Login expired' or 'Not logged in'
Type /login in the box, press Enter and sign in again in your browser.
It says my account doesn't have access
Claude Code doesn't come with the free plan. Upgrade to Pro at claude.com/pricing ↗, then type /login again.
I pressed Enter on No, exit and it closed
No harm done. Type the start line again, and this time press the Down arrow before Enter.
My Mac asks whether Terminal can access a folder
That's macOS checking with you. Allow it for folders you're happy for Claude Code to work in.
Still stuck? Ask the community
STEP 03 of 07~7 min

Learn to read what it asks permission for

This is the one real skill in the course. Once you can read a prompt, you're the boss and it's the very fast assistant.

In the last step you approved the first file on fake files. Now you'll learn to read what it asks permission for, so you can do it properly when the files are real.

Watch how a prompt reads

  1. Watch the animation.

    Every permission prompt has the same three parts: what it says it's doing, the exact command, and your answer.

    Demo
    Animation: how to read a permission prompt, top to bottom. Layout based on the example in Anthropic's docs.
    Tip
    Think of a contractor in your house. Before they knock down a wall, they tell you what they're about to do. The sentence is their summary, and the command is the sledgehammer in their hand. Always look at the sledgehammer.

Learn the words that matter

You don't need to speak the language, only recognise these. On Windows the title may say PowerShell instead of Bash, and the longer names appear.

  • rm, rmdir, del, Remove-Item: deletes. Slow down.
  • -r, -rf, -Recurse, -Force: "and everything inside, without asking". Slow right down.
  • mv, Move-Item, Rename-Item: moves or renames.
  • cp, Copy-Item: copies, which is usually safe.
  • mkdir, New-Item: makes something new, which is usually safe.
  • curl, wget, irm, Invoke-WebRequest: talks to the internet. Ask why.
  • ls, dir, cat, Get-Content: only looks.

Refuse a delete

  1. Paste this request, which you're going to refuse.

    Paste into Claude Code
    Delete every file in this folder with final in its name.
  2. Read the prompt. Find the line with the exact command, and spot the word from the list above.

    Where to look on a permission prompt. Layout based on Anthropic's docs, with our own example command. Yours will name the files it wants to delete.
  3. Refuse it, with a reason. Press the Down arrow until No is highlighted, then press Tab. Type the line below and press Enter.

    Type into the comment box
    Don't delete anything. Move those files into a folder called Maybe instead.
    Tip
    Stuck? Look at the very bottom of the prompt for the key hints. If the comment box doesn't open, press Esc to cancel, then simply send that line as a normal message.
  4. Read the new prompt. It should now say a move command and a folder called Maybe. If it does, press Enter on Yes.

    Tip
    The sentence you just learned. No plus a reason turns it around on the spot. You'll get better work from one quick correction than from starting again.

Know the risky answers

Tip
Watch out for option 2. "Yes, and don't ask again" means it won't ask about that command again in this folder, even next time. It's fine for looking at things. Never use it on anything that deletes.
Tip
Going outside the folder. It works in the folder you started it in. If it asks to read or change something elsewhere and you didn't ask for that, choose No. Same if it suddenly wants something unrelated to your request, since text inside a file can try to steer it.
Warning
You'll see people online recommend --dangerously-skip-permissions. It turns off the prompts, including for deletes. Anthropic says to use it only in an isolated environment such as a container or virtual machine. Never run it on your own files.
Checkpoint
You refused a delete, gave a reason, and your final files are now in a Maybe folder, all still there. That's the whole skill: read it, then say yes or no.
If it breaksIt didn't ask me anything before acting + 2 more
It didn't ask me anything before acting
Check the bottom line. If it doesn't say manual mode on, press Shift + Tab until it does, then try again.
The arrow keys do nothing
Click inside the terminal window first. You can't click the options themselves, so the keyboard does the choosing.
I pressed Yes by accident on the delete
This is why we practise on fake files. Ask it to recreate them, or start the folder again. Step 4 shows how to make sure a slip like that can't hurt you on real files.
Still stuck? Ask the community
STEP 04 of 07~10 min

Tidy a messy folder, backup first

Do a real job on real files with a safety net, using a pattern that works for any big change: copy, plan, approve, check.

You can now read a prompt. Next you'll put that to work on a messy folder, with a backup made first.

Understand what can go wrong

Claude Code has an undo called /rewind, but moving files is exactly what it can't always reverse.

Why the backup comes first.
Warning
Claude Code can change and delete your files. When a terminal command deletes something, it skips the Recycle Bin or Trash, so there's nothing to fish back out. Make a copy every time, before it touches anything you care about.

Make your backup

  1. Do it by hand. Open your home folder: Win + R, type %USERPROFILE% and press Enter, or Cmd + Shift + H in a Mac's Finder.

  2. Click claude-practice once. On Windows press Ctrl + C then Ctrl + V. On a Mac press Cmd + D.

    Tip
    Why do it yourself? A copy you made and can see is one you can trust. It also sits outside the folder Claude Code is working in, so it stays out of the way. You should now see a second folder with Copy or copy in its name.

Ask for a plan, then say go

  1. Ask for a plan. Back in the terminal, paste this. It won't move anything yet.

    Paste into Claude Code
    Tidy this folder. First, read the file names and show me a plan: the folders you'd create and which file goes where. Rules: never delete anything, ask me about anything you're unsure of, and don't touch anything outside this folder. Don't move a single file until I say go.

    Why is this prompt better than a bare "Tidy this folder"? Compare the two:

    • Weak: "Tidy this folder." It has to guess what you mean, what's safe and when to stop.
    • Better: the prompt above. It asks for a plan first, bans deleting, tells it to ask when unsure, and fences it inside the folder.
    • Why it works: a plan costs nothing to throw away. You catch a bad idea before it becomes 40 moved files.
  2. Correct the plan in plain English. Read where each file is going.

    If something's off, just say so, for example: "Put the CVs in a folder called Job hunting."

  3. Say go. Once the plan looks right, paste this.

    Paste into Claude Code
    Go ahead with the plan. Move files only, delete nothing. When you're done, write every move into a file called moved-files.txt, so I can see what went where.
  4. Read each command as you approve it.

    You're looking for moves and new folders. If you see a delete word from step 3, choose No.

  5. Check the result. Open claude-practice in a normal window, click through the folders and open moved-files.txt.

Do it for real

  1. Choose one small messy folder of yours, such as a corner of Downloads.

    Type /exit, make a backup of that folder the same way, then come back to the terminal.

    Warning
    What it reads gets sent to Anthropic to work on, so leave out passwords, bank statements, ID scans and other people's private files. You can choose whether your chats help train future models at claude.ai/settings/data-privacy-controls ↗. If the folder syncs through OneDrive, iCloud or Dropbox, the tidy will sync too.
  2. Go to your folder. Type cd and a space, drag the folder from its window onto the terminal, and press Enter.

    Terminal (type this, then drag your folder in)
    cd 
    Tip
    Stuck? Dragging should paste the folder's full address after cd , and the space matters. Your terminal line should now end with your folder's name. On Windows 11 you can also right-click the folder and look for Open in Terminal.
  3. Run the same pattern. Start Claude Code with the line from step 2, trust the folder, then paste the plan prompt from above.

    Approve the plan and the moves as you just practised.

    Tip
    Keep the copy for a week. Give yourself time to notice anything you can't find. Once you're happy, delete the backup yourself.
Checkpoint
Your real folder is sorted, a moved-files.txt lists every move, and an untouched backup sits alongside it. That's the copy, plan, approve, check pattern working end to end.
If it breaksIt wants to put things in a way I don't like, halfway through + 3 more
It wants to put things in a way I don't like, halfway through
Press Esc to stop it. Tell it what you want instead, and ask it to use what it's done so far as a starting point.
I want it all put back
Ask: "Use moved-files.txt to put every file back where it was." If that's not clean enough, close Claude Code with /exit, delete the tidied folder yourself and rename your backup to the original name.
It says it can't see my files
You probably started it in the wrong folder. Type /exit, repeat the cd and drag move, and check the last part of the terminal line is your folder's name.
What does /rewind actually do, then?
Type /rewind, or press Esc twice on an empty box, to get a list of your earlier messages and go back to one. It restores files it edited with its own tools. You'll try it in step 6.
Still stuck? Ask the community
STEP 05 of 07~9 min

Turn a spreadsheet and scruffy notes into a report

Hand it the raw material, get back a page you could actually send, and learn how to check the numbers before you trust them.

Tidying moved files around. This step has Claude Code read your files and write something new.

See where you're heading

You're going to take rows and scribbles and get a clean page out, with the odd things flagged.

  1. Look at the idea in the picture.

    Illustration of the idea, using a tiny made-up example. Yours will be longer.

Get back to your practice folder

  1. Leave your real folder. Type this in Claude Code and press Enter.

    Type into Claude Code
    /exit
  2. Go back to your practice folder. The ~ is shorthand for your home folder.

    Terminal
    cd ~/claude-practice
  3. Start Claude Code again.

    Terminal
    claude --permission-mode manual

Make practice data, with traps in it

  1. Paste this and approve the new files.

    Paste into Claude Code
    In a new folder called report-practice, create spending.csv with 40 rows of made-up household spending from January to March (date, shop, amount), and notes.txt with ten scruffy lines of my thoughts about that spending. Hide two mistakes in spending.csv: one duplicated row and one amount that's ten times too big. Don't tell me where they are.
  2. Wipe its memory. Type this and press Enter.

    Type into Claude Code
    /clear

    It starts a fresh conversation, so now it doesn't know where it hid the mistakes.

Ask for the report

  1. Paste this.

    Paste into Claude Code
    Read report-practice/spending.csv and report-practice/notes.txt. Make report-practice/report.html: one clean page I could print, with the total, spending by category and by month, three things I should notice, and a section called Check this that lists anything in the data that looks wrong. Work out every number by running a calculation, not in your head. Don't change my original files.
    • Weak: "Summarise this." You get a paragraph of vague words and no way of checking them.
    • Better: the prompt above. It names the files, says what the page must contain and asks it to flag anything odd.
    • The key line: "by running a calculation, not in your head". Adding up is where a chat answer slips, and a calculation gives you a result you can rely on.
  2. Read the permission prompts. It may ask to run a small calculation.

    Check the command only reads your files and writes the report, then press Enter on Yes.

  3. Open your report. In a normal window, go into claude-practice, then report-practice, and double-click report.html.

    It opens in your browser. To make a PDF, use your browser's print option.

Check its homework

Did the Check this section catch both planted mistakes?

  1. Now pick three figures on the page and find them in spending.csv yourself.

    Tip
    Stuck? Open spending.csv by double-clicking it, and sort or filter by shop. If a figure doesn't match, tell it: "The March total looks wrong to me. Show me which rows you added up." You don't need to know why it's wrong. You only need to ask it to show its working.
    Warning
    It can get numbers wrong and sound completely sure of itself. Check any figure before it goes to a client, your accountant, your boss or a tax form.

Do it on your own stuff

In the folder holding your real notes or spreadsheet, swap your file names into the report prompt, and swap the list of contents for what you need.

Tip
Formats it likes. Text files, CSV and PDF are the easy ones. It won't open an Excel .xlsx directly with its reader, so in Excel use Save As and choose CSV first. Save a Word document as PDF or text the same way. That saves it the trouble of working around the format.
Checkpoint
You've got a report.html that opens in your browser, it flagged the planted mistakes, and you've checked three figures yourself.
If it breaksIt missed one of the planted mistakes + 2 more
It missed one of the planted mistakes
That's a useful thing to learn early. Ask: "Check every row of spending.csv for duplicates and any amount that's far larger than the usual for that shop, and list them." Specific checks work better than a general 'look for errors'.
cd ~/claude-practice doesn't work
You're probably still inside Claude Code. If you can see the manual mode on line, type /exit first, then try again.
It changed my original file
Try /rewind to go back, then repeat your request with "Don't change my original files." And keep the copy habit from step 4 for anything you can't replace.
Still stuck? Ask the community
STEP 06 of 07~8 min

Build your own personal web page

Finish with something you can show people, and practise the talk-to-it loop that gets a design from fine to yours.

For the last job, you'll build something with your name on it. You'll write a clear brief, look at the result, then change it by talking to it.

See why the brief matters

The more it knows about you, the less it falls back on bland filler.

  1. Compare the two pages in the picture.

    Illustration, with a fictional florist. A vague request invites a generic page, and a specific one gives it something to work with.

Write and send your brief

  1. Fill in the brief. Copy this into Notepad or TextEdit and replace everything in square brackets with your details.

    Paste into Notepad, fill in, then into Claude Code
    Make me a one-page personal website as a single file called index.html, in a new folder called my-page. No frameworks and nothing to install, so I can open it by double-clicking.
    
    Who I am: [your first name, and what you do or love in one line]
    Who it's for: [who you want reading it, such as clients, a new employer, or friends]
    What it should say: [three things you want people to know]
    The one thing I want them to do: [such as email me at name@example.com]
    The look: [three words, such as warm, calm, handmade] with one strong accent colour
    
    Make it look good on a phone. Write the words yourself from what I've told you, in plain language, and don't invent facts about me.

    Typing into the terminal is fiddly, so write it there first.

  2. Send it. In Claude Code, paste your filled-in brief, press Enter, and approve the file.

  3. Open your page. In a normal window, open claude-practice, then my-page, and double-click index.html.

    Tip
    It's only a file. A simple web page is a single text file that browsers know how to draw. There's no server and no account, and nobody else can see it while it's on your computer.

Make it yours

  1. Change two things by talking to it. Pick one thing about the words and one about the look.

    After each change, refresh your browser with F5, or Cmd + R on a Mac.

    Tip
    Stuck? Describe what you see and what you'd prefer, the way you'd tell a designer. "The heading feels shouty, make it calmer" works better than guessing at technical words.
  2. Try the undo. Ask for something silly, such as "Make the whole page lime green." Enjoy it, then type /rewind.

    Use the arrow keys to choose the message where you asked for it, press Enter, and pick Restore code. Refresh your browser.

    Tip
    That's rewind doing what it's best at. It wrote this page with its own file tools, so it can put it back. That's the difference from the file moves in step 4.

Put it online, if you want to

  1. Open app.netlify.com/drop ↗ in your browser and drag your index.html onto it.

    A screenshot of Netlify Drop. Drag the file onto the page.
    Tip
    The link has a password at first. Netlify's docs say you can publish with no account, but until you sign up and claim the site, the link is protected with a temporary password. Sign up when you want it open to everyone.
    Warning
    Once it's public, assume anyone can read it. Leave out your home address, your phone number and anything about other people they wouldn't want shared.
Checkpoint
Your page opens in your browser with your name on it, you've changed it twice by talking, and you've used /rewind once.
If it breaksDouble-clicking opens the code instead of the page + 2 more
Double-clicking opens the code instead of the page
Right-click index.html, choose to open it with your web browser.
My change doesn't show up
Refresh the browser. If it still looks the same, ask Claude Code which file it changed. It may have made a new copy rather than editing index.html.
It made up facts about me
Tell it which ones are wrong and give it the real version. The brief already says not to invent facts, but always read every line before you share.
Still stuck? Ask the community
STEP 07 of 07~2 min

Keep the habits, then go further

Lock in what kept you safe and pick your next move.

You've finished the jobs. What's left is the short list that made them safe, and a pointer to what comes next.

Keep these five habits

They're the whole method, and they work on any job you hand it.

  • Copy first. Anything you can't replace gets a backup before it starts.
  • Plan first. Ask to see the plan before it moves or changes a thing.
  • Read the command. The sentence is a summary. The command is what happens.
  • Check the work. Open the files, and test three numbers yourself.
  • Start fresh. Type /clear between unrelated jobs, so old details don't get in the way.

See how much you've used

  1. Type /usage.

    Type into Claude Code
    /usage

    Chat and Claude Code share one allowance on your plan, with a five-hour limit and a weekly one. If you reach a limit, the simplest fix is to wait for it to reset.

Go further

You've now run real jobs on your own files. If you'd like to see how the builders use it, Claude Code in your first hour picks up from here and takes you through reading a codebase and shipping a change.

Checkpoint
You can say the five habits without looking, and you've opened the next course.
Stuck? Ask the community

Your first wins

It works. Now do something with it.

Find your duplicates, safely

Start Claude Code in a folder you suspect is full of copies. This one only reports, so you stay in charge of what goes.

Prompt
Find files in this folder that look like duplicates or older versions of each other. List them in pairs with their dates and sizes, and tell me which you'd keep and why. Don't delete or move anything.

Rename a folder of badly named files

Make your backup first. Then let it give scanned or downloaded files names you can actually search for.

Prompt
Show me a plan to rename the files in this folder in the style YYYY-MM-DD description, based on what's in each file. Show me the old and new names as a list and wait for my go-ahead before renaming anything.

Plan a trip from a pile of bookings

Put your booking confirmations, as PDFs or text, in one folder. Check every time and date against the originals before you travel.

Prompt
Read every booking in this folder and make itinerary.html: one printable page with each day in order, the times, addresses and booking references, and a list of any gaps or clashes you spot.

Turn meeting notes into actions

Drop a month of scruffy notes into a folder and get one list you can act on.

Prompt
Read all the notes in this folder and make actions.html: every action with who owns it, the date it was mentioned and whether it looks done. Put anything unclear in a section called Ask about this. Don't change my notes.

Undo it cleanly

How to remove everything this mission installed.

Remove your practice workDelete the claude-practice folder and its copy from your home folder in the normal way, so they go to the Recycle Bin or Trash.

Undo a tidyDelete the tidied folder yourself, then rename your backup to the original name.

Uninstall Claude Code on WindowsRun these two lines in PowerShell.

Windows PowerShell
Remove-Item -Path "$env:USERPROFILE\.local\bin\claude.exe" -Force
Remove-Item -Path "$env:USERPROFILE\.local\share\claude" -Recurse -Force

Uninstall Claude Code on a Mac or LinuxRun these two lines in Terminal.

Mac or Linux Terminal
rm -f ~/.local/bin/claude
rm -rf ~/.local/share/claude

Clear its settings and history, if you want toThe official uninstall guide ↗ lists the commands, and warns that they remove your settings and session history.

Stop payingUninstalling doesn't cancel your plan. Cancel Pro in your account settings on claude.ai ↗.

Next mission · Use AI properlyFix your slow internet with Claude: find the real cause in 5 minutes
→