Claude Code for Non-Coders: Your First Day, Install to Undo
Install Claude Code with one command, sign in with a paid Claude plan (Pro, Max, Team or Enterprise) or a Console account, and switch to Manual mode with Shift+Tab for your first day so Claude asks before every change. Undo with /rewind (or Esc twice), but know its blind spot: it restores files Claude edited, not files it moved, renamed or deleted with terminal commands. Ask for a log and an undo file before any bulk move.
Most "Claude Code for beginners" guides jump straight to building an app. This one stops earlier, at the part that decides whether you trust the tool: what the permission prompts are asking you, which answer to pick, and how to get back to where you were when something goes wrong. You finish with three small jobs done on your own files, and you know exactly which of them you could undo.
Should you be here, or in Cowork?
Be honest about the job first. If you want to hand Claude a research task, a report or a spreadsheet and never see a terminal, Claude Cowork is the better fit, and our Claude Cowork vs Claude Code comparison explains why. Claude Code earns the extra setup when you want Claude working directly on files and folders on your computer, want to see every command before it runs, or plan to automate things later.
If you like the idea of Claude Code but not the terminal, the Claude Desktop app has a Code tab that runs Claude Code with the same permission modes and no command line. Everything below about prompts and undo applies there too; only the install step differs.
Let Claude guide your first session
Paste this as your very first message once Claude Code is installed and running. Claude then acts as a tutor: it asks which task you want, explains each permission prompt before it appears, and sets up a way back before it touches anything.
Paste into a fresh Claude Code session, started in the folder you want to work on. Claude explains each step and each permission prompt before asking you to approve it.
- Checks which permission mode you are in and suggests Manual for day one
- Asks which first task you want: tidy a folder, clean a CSV, or check your site's links
- Shows a dry-run plan and creates an undo file before changing anything
- Walks you through /rewind and what it can and cannot restore
I am new to Claude Code and I am not a developer. Be my guide for this first session.
Rules for the whole session:
- One step at a time. After each step, stop and wait for me.
- Use plain language. No jargon without a one-line explanation.
- Before any action that will show me a permission prompt, tell me in one or two sentences what the prompt will say, what each option means (Yes / Yes, and don't ask again / No), and which one you recommend for a beginner. Recommend plain "Yes" unless there is a clear reason not to.
- Never delete anything. Never touch files outside the folder I started you in unless I name the path.
- Before moving or renaming more than a few files, first show me a dry-run table (old name -> new name), then write a log file called claude-moves.csv and an undo script next to it, and only then do the moves.
- For spreadsheets and CSVs, always write the cleaned version to a NEW file and leave the original untouched.
Start like this:
1. Ask me to look at the status line under the prompt box and tell you which mode it shows (for example "auto mode on" or "manual mode on"). If it is not manual, explain that pressing Shift+Tab once switches to Manual mode, and why that is safer on day one.
2. Ask me which first task I want:
a) Tidy the folder I am in (for example Downloads): sort files into subfolders by type and give them readable names.
b) Clean a CSV export: fix dates, trim spaces, remove duplicate rows, save as a new file.
c) Check the links on my website and list the broken ones.
3. For the task I pick, show me your plan first and wait for my OK.
4. For task c: if an Apify tool is available in this session, propose the broken link checker Actor khadinakbar/broken-link-checker with maxLinksToCheck set to 100 or less, tell me the cost estimate first (about $0.001 per link checked), and wait for my OK. If no Apify tool is available, offer to check up to 10 pages yourself instead, or explain how to install the Apify plugin.
5. When the task is done, explain how /rewind works (also opened by pressing Esc twice on an empty prompt), and tell me exactly which of today's changes /rewind could restore and which only the undo script could.
Claude asks before each change it makes. Read each step before you approve it.
The rest of this guide is the same session done by hand, so you know what Claude is doing on your behalf.
Step 1: Install and sign in
You need a paid Claude plan (Pro, Max, Team or Enterprise) or a Claude Console account with API credits. The free plan does not include Claude Code.
Open a terminal (on a Mac: Cmd + Space, type Terminal, press Enter) and paste the command for your system:
| System | Install command |
|---|---|
| macOS, Linux, WSL | curl -fsSL https://claude.ai/install.sh | bash |
| Windows PowerShell | irm https://claude.ai/install.ps1 | iex |
| Windows CMD | curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd |
The installer shows no progress bar, so leave the window alone until it finishes. Then open a new terminal window and run claude --version. A version number followed by (Claude Code) means it worked. If you get command not found: claude, the installer printed a one-line fix under Setup notes; run that and open a fresh window. On Windows, Anthropic recommends installing Git for Windows too; without it, Claude Code falls back to PowerShell for commands.
Now go to the folder you want to work in and start Claude:
cd ~/Downloads
claude
On Windows PowerShell the first line is cd $HOME\Downloads. A browser window opens for you to sign in once; after that, your login is remembered.
Three keys to know before anything else: Esc stops Claude mid-task, exit (or Ctrl + D twice) leaves Claude Code, and /help lists the commands.
Step 2: Pick your permission mode before your first request
This is the step most guides skip, and it matters more now than it did a year ago. Recent versions of Claude Code start in auto mode. In auto mode a second model, a safety classifier, reviews actions in the background instead of asking you. That is convenient once you know the tool. On day one it means you never see what Claude is about to do.
Look at the line under the prompt box. If it says ⏵⏵ auto mode on, press Shift+Tab once. It changes to ⏸ manual mode on. Pressing Shift+Tab again cycles through the other modes:
| Mode (status line) | What Claude does without asking | Use it when |
|---|---|---|
Manual (⏸ manual mode on) | Only reads files in your folder | Day one, and any folder you care about |
Accept edits (⏵⏵ accept edits on) | Edits files, plus mkdir, touch, rm, rmdir, mv, cp, sed inside the folder | You trust the task and review the result afterwards |
Plan (⏸ plan mode on) | Explores and writes a plan, edits nothing until you approve it | You want to see the approach before anything changes |
Auto (⏵⏵ auto mode on) | Everything, with background safety checks | Long tasks, once you know what "normal" looks like |
Notice that Accept edits auto-approves rm and mv. It sounds like the mild option, but it lets Claude delete and move files inside your folder without asking. Stay in Manual until you have watched a few tasks.
To start in Manual every time, launch with claude --permission-mode manual.
Step 3: Read a permission prompt
In Manual mode, each command Claude wants to run shows a box like this:
Bash command
mv "IMG_2041.png" "Screenshots/2026-10-02 invoice screenshot.png"
Move the screenshot into the Screenshots folder
Do you want to proceed?
❯ 1. Yes
2. Yes, and don't ask again for: mv *
3. Yes, and switch to auto mode
4. No
Illustrative example. The layout follows Anthropic's documented Bash prompt; the exact wording of option 2 depends on the command.
What each answer does:
- Yes: runs this one command. The right default on day one.
- Yes, and don't ask again: for a terminal command, this saves a permanent rule, so future sessions will run that command without asking. For a file edit, it only lasts until you close the session. Don't pick this for
mvorrmuntil you are sure. - Yes, and switch to auto mode: approves and hands the rest of the session to the classifier.
- No (or
Esc): Claude stops and asks what to do instead. You can also pressTabto add a note, for example "use a subfolder called Old instead".
Read the command line itself, not just Claude's one-line summary. The summary is Claude's description; the command is what actually runs.
Step 4: Three first tasks
Each task below is safe for a first session if you follow the one rule that comes with it.
Tidy your Downloads folder
Ask: "Sort the files in this folder into subfolders by type (PDFs, images, installers, spreadsheets, other) and rename screenshots to something readable. Show me a dry-run table first."
The rule: ask for a log file and an undo script before the moves. Renaming and moving happen through terminal commands, and /rewind cannot undo those (see the next section). A claude-moves.csv with old and new paths is your way back.
Clean a CSV export
Start Claude in the folder that holds the file, then ask: "Open contacts-export.csv. Trim extra spaces, make all dates YYYY-MM-DD, remove exact duplicate rows, and save the result as contacts-clean.csv. Tell me how many rows changed and why."
The rule: always a new file. Claude may write a short script to do the cleaning; that's fine, because the original stays untouched and you can compare the two.
Check every link on your site
For a handful of pages, Claude can fetch them itself. It will ask permission for each new website domain the first time. For a whole site, a crawler is faster and cheaper than Claude reading every page. The Apify plugin for Claude Code connects Claude to ready-made scrapers called Actors, including a Broken Link Checker that crawls your site and reports the dead links.
To add it, type these inside Claude Code, one at a time:
/plugin marketplace add apify/apify-claude-code-plugin
/plugin install apify@apify
/reload-plugins
Then run /mcp, open plugin:apify:apify, choose Enable, then Authenticate, and sign in to Apify in the browser that opens. Apify's own docs warn that the sign-in page shows a "registered dynamically and wasn't verified" notice for this plugin; that is expected for the current release.
Then ask: "Use the Apify broken link checker on https://example.com with maxLinksToCheck 100. Tell me the cost estimate before you run it."
We ran it on a public crawler test page with a 40-link cap. It took 4 seconds and cost $0.04: 40 links checked at $0.001 subject to change · verified 2026-10-21 per link, plus a start fee of $0.00005. One row of the result, trimmed:
{
"url": "https://crawler-test.com/links/not_found/foo1",
"status": 404,
"statusText": "Not Found",
"classification": "broken",
"sourceUrl": "https://crawler-test.com/links/broken_links_internal",
"anchorText": "Broken Internal Link 1"
}
Real output from a test run on 2026-10-21. The sourceUrl and anchorText fields are the useful part: they tell you which page holds the broken link and what the link text says, so you can find and fix it.
The rule: set maxLinksToCheck. The Actor charges per link checked, and its default cap is 500, so an uncapped run on a big site costs more than you expect.
Undo: what /rewind restores, and what it doesn't
Claude Code saves a checkpoint each time you send a message. Type /rewind, or press Esc twice on an empty prompt, to open the list of your messages. Pick the point you want to go back to, then choose:
- Restore code and conversation: files and chat both go back to that point.
- Restore conversation: the chat rewinds, your files stay as they are now.
- Restore code: files go back, the chat stays.
Checkpoints are saved with the conversation, so you can reopen a session later with /resume and still rewind. Anthropic keeps the file snapshots for about 30 days by default.
The limits are the part that matters for non-coders:
| Change | Can /rewind undo it? |
|---|---|
| Claude edited or created a file with its editing tool | Yes |
Claude moved, renamed, copied or deleted files with a terminal command (mv, cp, rm) | No |
| A script Claude wrote and ran changed files | No |
| You changed a file yourself outside Claude Code | No |
So the folder-tidying task, the one that feels the most harmless, is the one /rewind can't undo. That's why the setup prompt above insists on a move log and an undo script, and on writing cleaned CSVs to a new file. Anthropic says the same: checkpoints are for quick recovery within a session, not a replacement for proper backups or version control.
When to move on
After a few sessions you will notice the same prompts again and again. That's the point to try Accept edits for folders you trust, or Plan mode for bigger jobs, so you approve one plan instead of twenty commands. When your tasks turn into things like weekly reports or research digests, compare your options: Cowork can run Apify scrapers and fill a spreadsheet with no terminal, and our Claude Code business workflows guide covers the jobs where Claude Code pulls ahead. When you are ready for live web data, the Claude Code web research setup gives you a ready-made workspace, and Claude prompts that use live web data has copy-paste prompts by role.
FAQ
No. Claude Code needs a paid Claude plan (Pro, Max, Team or Enterprise), a Claude Console account with prepaid API credits, or access through a supported cloud provider. The free Claude plan does not include it.
No. You describe what you want in plain English and Claude writes and runs any code needed. What you do need is the habit of reading permission prompts before approving them, which is why this guide starts in Manual mode.
Yes, if you approve it, and Accept edits mode approves rm inside your folder without asking. In Manual mode every delete shows a prompt first. Deletes on critical system paths are never auto-approved in any mode. Deleted files cannot be restored with /rewind, so ask Claude to move files to a folder instead of deleting them.
Type /rewind or press Esc twice on an empty prompt, choose the message to go back to, then pick Restore code. This only restores files Claude changed with its file editing tool. Moves, renames and deletes done with terminal commands are not tracked, so ask for a log file and an undo script before bulk moves.
For delegating research, reports and spreadsheets with no terminal, Cowork is the simpler choice. Claude Code fits when you want Claude working directly on files and folders on your computer, want to approve each command, or plan to automate tasks later.