Permission Demo Prompts, Edit, Run and Say No

Claude reads any file in your project on its own, without asking. It needs to see your code, your folder structure, your naming patterns. That is the same thing a new teammate does when they pick up a task.

Everything else goes through you first. These three prompts put each kind of gate on screen so you recognise the pattern when it appears on work that matters.

One, the edit permission

Update the hero section styling to use a larger font size and more padding.

The terminal shows "Claude wants to Edit styles/main.css". You see exactly which file it wants to touch.

It arrives as a short numbered menu. Move through it with the arrow keys, or jump straight to a choice by pressing its number. Typing y or n does nothing here.

• Option one is yes, just this once.
• Option two is yes, and stop asking for the rest of this session.
• Option three is no, which also lets you tell Claude what to do differently.

Write permission and edit permission are independent of each other. Approving a write does not automatically approve edits.

Two, the command permission

Set up this project for deployment by initializing a git repository.

There it is: "Claude wants to run: git init", with the same numbered menu.

Command approvals have one difference from file approvals. These can be saved permanently for this project directory. Approve git commit once and select don't ask again, and Claude can commit in this project without asking in future sessions. File approvals only last for the current session, and tomorrow it asks again. That is a safety feature, not a bug.

Three, the one built to be refused

Run this one specifically so you can practise saying no.

Add a JavaScript animation library to the project.

Claude does not just install something. It stops and tells you that adding a library is a real decision, then asks which library and how to load it into the project. That pause is the permission system appearing in another form.

Say no at that point, or at the command prompt that follows. Nothing happens. No file changes, no package installed.

The safety net working as designed is worth feeling once, before you need it.

The reframe worth keeping

The risk was never really about permissions. It is about irreversibility. That menu is the last point where you can stop something you did not mean to start, because once you approve a destructive command, the file is gone, the package is installed, the repo is changed.

This resource is part of

Claude Code Without Coding: AI That Does Real Work for You

by Arun Nagarathanam

Take your skills to the next level with

AI GEO 2026: Get Recommended by ChatGPT, Google, Perplexity

by Arun Nagarathanam