Claude Code for Non-Engineers • Part 1 • About 13 min
Using Claude Code Without Coding: Your First Automation, Organizing a Messy Downloads Folder
Contents
Version at time of writing: Claude Code 2.1.x (tested on 2.1.311) / October 2026. Claude Code updates quickly, so on-screen text, defaults, and command names may change. If what you see differs from this article, please refer to the official documentation. If you find a mismatch, please let us know.
What This Article Will Help You Do
By the end, you'll complete a real chore on your own computer: automatically sort a folder with dozens of files into subfolders for Documents, Images, Spreadsheets & Slides, Archives, and Other, and generate a cleanup list.
You won't write a single line of code. You only need to do two things: tell it what you want in plain language, and click "Allow" before it takes action.
What you'll need:
- A Windows or Mac computer (this article focuses on Windows 11, with Mac differences noted)
- A paid Claude subscription (Pro, Max, Team, or Enterprise), or a Claude Console account
- About 30 minutes, including 5 minutes for installation
First, understand one thing: how this differs from "pasting files into a chat box"
With ChatGPT or the Claude web version, the flow is: upload a file, it answers, and then you do the work yourself. It can only "say," not "do."
Claude Code is different. It's a program that runs on your computer. It can read files, write files, rename them, and run commands. If you say "move all the images into the images subfolder," it will actually move them. Even though the name includes "Code," it isn't limited to programming. The closest way to think of it is "an assistant that can operate the files on your computer."
This is what makes it useful, and also what makes it risky. That's why this article spends a lot of space on "brakes": how to limit permissions, how to review its plan before it acts, and how to recover from mistakes. Please don't skip Steps 4 through 7.
Step 1: Install (5 minutes)
Claude Code mainly runs in a "terminal." On Windows, that means PowerShell.
- Press the Windows key, type
PowerShell, and click "Windows PowerShell" to open it. - The black window starts with
PS C:\Users\YourName>. ThePSmatters. The prompt withoutPSis the "Command Prompt (CMD)," which uses different commands. - Paste this line and press Enter:
irm https://claude.ai/install.ps1 | iex
The installation won't show a progress bar. It may look stuck, which is normal.
Confirm the Installation
When it finishes, close the window and open a new PowerShell, then type:
claude --version
It should print a version number followed by (Claude Code), for example 2.1.311 (Claude Code). That means the installation succeeded.
Common error messages:
| Message You See | Meaning | What to Do |
|---|---|---|
'irm' is not recognized as an internal or external command |
You opened CMD instead of PowerShell | Close it and reopen PowerShell |
The token '&&' is not a valid statement separator |
You pasted the CMD version of the command into PowerShell | Paste the PowerShell line above instead |
It says it can't find the claude command |
The install location hasn't been added to the system PATH yet | Try closing and reopening the window first. If that doesn't work, see the official Installation Troubleshooting guide. |
The official docs also recommend that Windows users install Git for Windows. With it installed, Claude Code can use the Bash tool. Without it, Claude Code uses PowerShell instead. Both work. The "native installation" above updates automatically in the background, so you don't need to manage versions.
Mac, Linux, or WSL users: In Step 3 above, replace the command with this line in your terminal. All other steps are the same:
curl -fsSL https://claude.ai/install.sh | bash
(Mac commands follow the official documentation and have not been tested for this article.)
Step 2: Create a "Practice Sandbox." Don't Work Directly in Your Real Downloads Folder
Paste these two lines into PowerShell, one at a time, pressing Enter after each:
New-Item -ItemType Directory -Force "$env:USERPROFILE\Claude練習"
explorer "$env:USERPROFILE\Claude練習"
The first line creates a "Claude Practice" folder. The second line opens it in File Explorer.
Next, manually copy (don't cut) 20–50 files from your Downloads folder into it. Include a variety of types: PDF, images, Word, Excel, and ZIP. These are copies, so if something goes wrong, it's no big deal.
Mac users: In Terminal, use mkdir -p ~/Claude練習 && open ~/Claude練習 (Mac commands follow the official documentation and have not been tested for this article).
Step 3: First Launch and Login
In PowerShell, switch to the practice folder, then launch Claude Code:
cd "$env:USERPROFILE\Claude練習"
claude
cd means "change to this folder." This step is critical. Claude Code's default scope is the folder you launch it from. Launching it inside the practice folder gives it a smaller space to work in.
On first launch, it will guide you to log in through your browser. Sign in with your Claude Pro, Max, Team, or Enterprise account. Your credentials will be saved, so you won't need to log in again.
If your computer has
ANTHROPIC_API_KEYset, Claude Code will ask whether you want to use that key. Most users should choose No, or usage will be billed by usage instead of through your subscription.
After logging in, you'll see the input prompt. The top shows the version, model, and working directory. First, type /help to see the available commands.
Step 4: Essential security settings for first-time use (don't skip this)
Claude Code has "permission modes" that determine whether it asks for your approval before taking an action. In version 2.1.283 or later, the default starting mode in the interactive terminal is "Auto (automatic mode)", meaning another model reviews actions in the background instead of asking you at every step.
This is convenient for experienced users, but you're using it for the first time, and we're letting it modify your files. Switch to the most conservative Manual mode first. It stops to ask you before most file edits, command executions, and network actions.
To switch, press Shift+Tab during the conversation to cycle through modes. The cycle order is Auto → Manual → acceptEdits → Plan → Auto. Pressing Shift+Tab once from the default Auto mode takes you to Manual, and the status bar will show ⏸ manual mode on.
(On Windows, if Shift+Tab doesn't respond, press Alt+M instead.)
You can also set the mode at startup:
claude --permission-mode manual
(In the settings file, this mode is named default. The CLI also accepts the alias manual. They are the same thing.)
Differences between the modes (Claude Code has 6 permission modes. Only the ones you'll see in the Shift+Tab cycle are listed here):
| Mode (display label) | What it can do without asking | When to use it |
|---|---|---|
Manual(⏸ manual mode on) |
Read-only | First-time use, or when touching important files |
acceptEdits(⏵⏵ accept edits on) |
Reading, editing files, and common file commands such as mkdir, mv, and cp |
Rules are confirmed and you want it to edit a batch of files continuously |
| Plan (plan mode) | Reading. Blocks file edits until you approve the plan (but commands may still be reviewed by a classifier and executed) | You want to see its intended approach first |
| Auto (automatic mode) | Almost all actions, with background safety checks | Once you're familiar with it, for long-running routine tasks |
If you accidentally press past the mode you want and see accept edits on, don't panic. Press again a few times and it will cycle back.
Step 5: Let it "look" first, not "act"
Don't give it a command in your first message. Ask for a report first. Just type in Chinese in the input box:
請先不要修改任何檔案。看一下這個資料夾裡有哪些檔案、各有幾個、分別是什麼類型,列一張表給我。
It will read the folder and report back. This step confirms that it can actually see the correct folder.
To see its intended approach first, switch to Plan mode (also with Shift+Tab). It reads the files and writes a plan for you to review, and it won't use editing tools to change files until you approve the plan. However, in Plan mode, "commands" (such as file-moving commands) may be reviewed by a background classifier and run directly when auto mode is available. So Plan mode means "review the plan first," not "will never touch files." To approve every step yourself, stay in Manual mode.
A common pitfall for beginners: when it shows you the plan and asks whether to proceed, don't select the first option, "Yes, and use auto mode." That switches the whole session to auto mode, and your earlier switch to Manual is wasted. Select "Yes, approve edits manually" so it keeps asking you step by step.
Step 6: Give the first real command
Once everything checks out, state clearly what you want. The key is to be specific. Don't say "help me tidy this up." Explain the rules, scope, and exceptions:
請把這個資料夾裡的檔案依類型分類到子資料夾:
- 文件(.pdf .docx .doc .txt)放到「文件」
- 圖片(.jpg .jpeg .png .gif .webp)放到「圖片」
- 試算表與簡報(.xlsx .xls .csv .pptx)放到「試算表與簡報」
- 壓縮檔(.zip .rar .7z)放到「壓縮檔」
- 其他類型放到「其他」
規則:
1. 不要刪除任何檔案,只能搬移。
2. 如果目標資料夾已有同名檔案,不要覆蓋,在檔名後面加上 -1、-2。
3. 搬完後,在資料夾裡寫一個「整理清單.md」,記錄每個檔案從哪裡搬到哪裡。
4. 動手前先把你要做的事列出來給我確認。
Next, it will propose a plan and then request permission step by step. Each time it asks, review the action before you approve it. If you don't understand it, ask "What does this command mean?" The whole process takes from tens of seconds to a few minutes. To stop partway through, press Esc.
The permission dialog has two options that disable the safety brakes. Don't select them during your first practice runs:
- If you see "Yes, and switch to auto mode," don't select it. Afterward, actions won't ask for your approval.
- Don't press Shift+Tab in the permission dialog. That means "allow for the entire session."
Just press plain Yes.
Step 7: Verify results, and how to recover from mistakes
Open File Explorer to check the results, and compare them with the "整理清單.md" (tidy list) it generated.
If you're not satisfied with the results, you have two options:
Option A: Ask it to undo the changes directly. This is the simplest and most reliable method: "Please move all the files you just moved to the 'Other' folder back to their original locations." It has the earlier record and can do this.
Route B: Rewind with /rewind. Type /rewind, or press Esc twice while the input box is empty, and a rewind menu appears listing every message you've sent in this conversation. Pick a point in time, then choose one of: "Restore code and conversation," "Restore conversation," or "Restore code." The menu also has "Summarize from here," "Summarize up to here," and "Never mind."
If that point in time has no tracked file changes, the menu only offers restoring the conversation. "Restore code" won't appear at all. This is the case when you moved files with commands.
There's a trap that non-engineers often fall into. Please remember this:
/rewindfile snapshots only track files that Claude changed using its file editing tools. Files moved or renamed purely by commands (Bash/PowerShell) aren't tracked, so/rewindwon't restore them.
Moving files and renaming them is often done with commands. That's why Step 2 has you copy files to a practice folder, and why you must make your own backup first before working on real folders. /rewind is a handy small restore point, not a backup system.
Step 8: Make it remember your rules next time
You probably don't want to retype your sorting rules every time. Each time Claude Code starts working, it reads a plain-text file named CLAUDE.md in the working folder and treats its contents as long-term instructions. The simplest approach is to ask it to write the file for you:
請在這個資料夾建立一個 CLAUDE.md,把我剛才說的分類規則寫進去,
另外加上兩條:(1)所有回覆用繁體中文;(2)刪除檔案前一定要先問我。
The next time you start Claude Code in this folder, the rules apply automatically. You only need to say "tidy up according to the rules." To check that it read the file, enter /context and look for your CLAUDE.md under Memory files. To view or edit it, use /memory.
The writing principles are the same as for a handover note: specific, verifiable, and consistent. Keep it under 200 lines. (Part 3 covers this in detail, with templates for administrative, social media, and freelance work.)
Step 9: Wrap up and come back later
- To exit, use
/exit, or press Ctrl+D twice. - To continue the previous conversation, run
claude -cin the same folder, or use/resumeafter launching to choose an old conversation. - To clear the current conversation and start over, use
/clear. - Shortcuts:
/lists all commands, ↑ recalls the previous message, and Tab autocompletes.
Three "don'ts"
- Don't work on important folders the first time. Leave the Desktop, cloud-synced folders (Google Drive, OneDrive), and shared company drives alone. Mass moves in cloud folders cause sync conflicts that are hard to resolve.
- Don't approve anything you don't understand. If you're unsure, ask "What is this line doing?"
- Don't use "skip all permissions" modes. Those are meant for isolated containers or virtual machines, not personal computers.
Next episode preview
Part 2: "100 files named 'final version(2)': Batch-rename with Claude Code, and recover if you make a mistake"
The focus is on how to describe naming rules in Chinese, how to have it first produce a "rename mapping table" for you to check before executing, and the recovery process if something goes wrong.
Want copy-ready rule templates?
References (all official documentation, accessed 2026-10)
- Quickstart: https://code.claude.com/docs/zh-TW/quickstart
- Choose a permission mode: https://code.claude.com/docs/zh-TW/permission-modes
- Checkpointing (
/rewindand its limitations): https://code.claude.com/docs/zh-TW/checkpointing - Remember your project (CLAUDE.md): https://code.claude.com/docs/zh-TW/memory
- Installation troubleshooting: https://code.claude.com/docs/zh-TW/troubleshoot-install
- Interactive mode (Shift+Tab / Alt+M): https://code.claude.com/docs/zh-TW/interactive-mode
- Documentation home: https://code.claude.com/docs/zh-TW
- Free course, Claude Code 101: https://academy.claude.com/courses/claude-code-101
Error message reference table for Step 1, compiled from the official quick start and installation troubleshooting guides.
The author tested the steps on Windows 11 with Claude Code 2.1.311. Mac commands follow the official documentation and have not been tested.
Related Series Reading
- Teach It Your Habits: How Non-Engineers Write a CLAUDE.md
- Turn Your Weekly Tasks into a Skill Card: An Introduction to Agent Skills (Meeting Notes and Invoice Filing)
`← Back to article listNext: 100 "Final(2)" Filenames: Batch-Rename with Claude Code, and Recover from Mistakes →`