Skip to main content

Claude Code Basics Lesson 21 of 46

The Modes: How Much Leash You Give It

In short
  • Modes are a single dial that shifts the overall behavior, not one rule at a time.
  • They're a scale: from "touches nothing" all the way to "never asks".
  • By default you're on Manual: it asks before touching anything.
  • The last step should never be used on the computer that holds your work.

Rule and mode: two different things

In the last lesson you learned to decide one thing at a time: this one always yes, that one never. The mode is the other tool, and it's bigger: it shifts the overall behavior of the session.

You use them together, and the two don't cancel each other out: denials stay in force in every mode. The mode decides how much it bothers you about everything else.

The scale, from most cautious to most relaxed

  • Plan — what everyone calls Plan mode — touches nothing. It reads, looks around, explores, and tells you what it would do. Zero changes to your files. It's useful enough to get a lesson all to itself, the next one.

  • Manual — the default mode: before changing a file or running a command, it asks. In the desktop app this is the one you've already seen, with the proposed change and buttons to accept or reject.

  • Accept edits — file edits go through on their own, commands still stop for confirmation. This is the right step once you've already agreed on what to do and just need it done.

  • Auto — approves on its own, with safety checks that verify what it's doing matches what you asked for.

  • Bypass permissions — never asks anything anymore. We'll cover this below, and not in the way you're hoping.

In the desktop app you pick the mode from the control in the bottom left, next to the text box; from the terminal there's a keyboard shortcut that cycles through the modes, and you can also set one as the default.

Looping animation: the cursor clicks the «Manual» button in the bottom left and the Modes menu opens with its five entries — Manual (checked), Accept edits, Plan, Auto, Bypass permissions.
The button in the bottom left always tells you which mode you're in: click it and this menu opens. One thing to note though — the order of the entries isn't the order of the scale above: the menu lists them by how often they're used, we've lined them up here by how cautious they are.

How you move up, in practice

The sensible path is always the same, and it's gradual:

  • At the start stay on Manual and watch what it asks you. This is how you learn what it actually does, before giving it more rope.

  • When you notice you're repeating the same yes, don't switch modes: write a rule. It's more precise and doesn't widen anything else.

  • When you're working in a burst on something you've already agreed on, bump up to "accept edits" for that session, then drop back down.

The mode is a choice per session, not a lifelong decision. Raising it for twenty minutes and lowering it back down is the normal way to use it.

Now what

I left you hanging on the first step of the scale. It's the most interesting one of all, because it's not there to protect you: it's there to help you work better. In the next lesson, Plan mode.

Did you get it?

Two minutes, no grade. Trying to answer — even getting it wrong — cements the concepts far more than rereading. Not in the mood? Skip it: the lesson still counts as complete.

What's the difference between a permission rule and a mode?

You're making repetitive edits you've already agreed on, and it asks you to confirm every two minutes. What do you do?

When does the mode that never asks anything make sense?

Course Claude Code Basics
  1. Chapter 1 Introduction

    1. 1 The Claude Ecosystem and Where Claude Code Fits
    2. 2 What Claude Code Is: The Collaborator Who Walks Into Your Studio
    3. 3 How an Agent Works: The Loop
  2. Chapter 2 What's Underneath

    1. 4 Claude Code in Action: The Loop, for Real
    2. 5 The Model Has No Memory: It Starts Over Every Time
    3. 6 The Harness: The Engine and the Gear Around It
    4. 7 The Map: Four Buckets
  3. Chapter 3 You Choose the Engine

    1. 8 There's No Single Claude: The Model Lineup
    2. 9 Which Model for Which Job
    3. 10 Effort: How Hard It Should Think
    4. 11 Model or Effort? The Question That Trips Everyone Up
    5. 12 The Bill: Why Saving Money Can Cost You More
  4. Chapter 4 First Time at the Controls

    1. 13 Where to Run It: Four Doors In
    2. 14 What You Need Before You Start
    3. 15 Installing Claude Code
    4. 16 The Folder: Where You Open It Decides What It Works On
    5. 17 Choosing the Engine, in Practice
    6. 18 Your First Task: Small, Yours, and It Works
  5. Chapter 5 What You Let It Touch

    1. 19 Why It Asks for Permission
    2. 20 The Rules: Always Yes, Ask Me, Never
    3. 21 The Modes: How Much Leash You Give It
    4. 22 Plan Mode: Get the Plan Before the Work
    5. 23 Verification in the Loop: Give It a Yardstick
    6. 24 Example: Putting the Bucket Together
  6. Chapter 6 What It Knows About You

    1. 25 CLAUDE.md: The Notes It Reads the Moment It Walks In
    2. 26 How to Write a CLAUDE.md That Actually Works
    3. 27 The Context Window: How Much It Can Hold at Once
    4. 28 Cleaning Up: Compact and Clear
    5. 29 Automatic Memory
    6. 30 Example: From Repeating Yourself to Never Again
  7. Chapter 7 Skills

    1. 31 What a Skill Is: A Procedure Written Once
    2. 32 Creating Your First Skill
    3. 33 The Description Decides Whether It Gets Used
    4. 34 Example: A Skill That Saves You the Week
  8. Chapter 8 How Many You Put to Work

    1. 35 The Subagent: A Helper With Its Own Desk
    2. 36 When a Helper Is Worth It (and What It Costs)
    3. 37 Teams: When Agents Talk to Each Other
    4. 38 Example: Searching Without Cluttering the Desk
  9. Chapter 9 What It's Connected To

    1. 39 MCP: The Standard Plug Into Your Tools
    2. 40 Plugins: Packaging Up and Borrowing
    3. 41 Example: When You Stop Copying and Pasting
  10. Chapter 10 Automating the Setup

    1. 42 Hooks: The Thing That Always Happens
    2. 43 Where It Fires and What It Can Do
    3. 44 When You Actually Need One (and When It's Too Much)
  11. Chapter 11 Wrap-Up

    1. 45 The Project: Your Expense Tracker
    2. 46 Wrap-Up: What You're Taking Home
From a Confusing Brief to a Complete UX/UI A vague brief becomes a navigable app. Product Ad From a Single Photo A photo becomes an animated ad, no code required. Get Claude to Watch Your Videos Claude watches your videos and turns them into text. Higgsfield Inside Claude Code Generate images and video while you code in Claude Code. Turn a Loom Recording Into a Web Page A screen recording becomes a web page, no code. Vertical Shorts With NotebookLM Your sources become a vertical short. Luxury Landing Pages on Lovable A luxury landing page from a single prompt. Excalidraw Running Locally Excalidraw free on your computer, no code. Mistral OCR in Your Workflow Extract text from documents with Mistral OCR. Claude SEO in the Terminal 25 free SEO skills inside Claude Code. Google Search Console inside Claude Code Search Console data inside your terminal. Claude Code Routines Claude working on its own, computer off. Clone a Landing Page in React With v0 Clone a real landing page into React code. Context Economy With Claude Work light and don't burn through Claude's limits. From Prompt to Self-Improving Skill Claude skills that learn from your mistakes. From NotebookLM to Canva: Presentations NotebookLM slides, finally editable in Canva. The Map for Understanding Every AI Tool 12 categories for placing any AI tool. Transparent PNGs With ChatGPT Real transparency, not a fake checkerboard. Animated Infographics With Gemini Infographics that loop, animated with Gemini. Market Research With Deep Research Deep Research as your market analyst. Get Cited by AI Search Engines (AEO) Become a source that ChatGPT and Perplexity cite.