What --dangerously-skip-permissions Actually Does in Claude Code (And Why Builders Turn It On)

By Jonah, Founder of FindClout — July 2026

The first time you set up Claude Code, you'll run into an alias that half the internet swears by and the other half clutches its pearls over:

alias cc="claude --dangerously-skip-permissions"

The word dangerously is right there in the flag name, in the command you're about to run all day, every day. Naturally people ask: am I about to blow up my laptop? Is this reckless? Why does the tool ship with a flag that sounds like a warning label?

I run this flag on my machine constantly and I've built most of FindClout's internal tooling with it turned on. I'm also not going to pretend the "dangerously" is marketing. It's an honest name for an honest trade-off, and if you understand exactly what it does and where the boundaries are, it's the difference between Claude Code feeling like an autonomous employee and feeling like a nervous intern who asks permission to breathe. Let's break it down properly.

First, the permission system it's turning off

By default, Claude Code has guardrails. Before it runs a terminal command, edits certain files, or takes an action it judges to be potentially consequential, it stops and asks you: "I'd like to run this command — is that okay?" You approve, it proceeds. You decline, it doesn't.

This is a genuinely good default. Claude Code is an agent with real access to your machine — it can create and delete files, install packages, run scripts, hit the network. The permission prompts are a human checkpoint sitting between "the agent decides to do something" and "the something actually happens." For an experienced engineer who can read each proposed command and catch a mistake before it runs, that checkpoint is a safety net worth having.

If you haven't installed Claude Code yet, start with my zero-to-running install guide — this post assumes you already have the terminal saying hi.

What the flag actually does — and doesn't do

Here's the part people get wrong. --dangerously-skip-permissions does not give Claude Code new powers. It does not unlock some hidden god-mode capability. The agent can already do everything it does. What the flag removes is the approval prompt in front of each action.

So the honest one-sentence version: the flag doesn't make Claude Code stronger, it makes it less interrupted. You're taking the training wheels off a bike you already know how to ride — not bolting on a bigger engine. The capability was always sitting there. You're just changing how often you're asked to sign off on it.

Why builders turn it on: the interruption tax

Picture building a tool with an assistant who, every thirty seconds, taps you on the shoulder and says "may I do this thing you literally just asked me to do?" For an hour. That is the default experience, and for a certain user it's exactly right. For a non-technical builder, it's death by a thousand papercuts.

Two things happen when you're prompted constantly:

• Your flow is shredded. The entire promise of an autonomous agent is that you describe the outcome and go get coffee while it works. Approving every step means you never leave the driver's seat — you've just traded typing code for clicking "yes," which is barely an upgrade.
• The prompts add anxiety without adding safety — for you specifically. This is the uncomfortable truth. A permission prompt only protects you if you can actually evaluate the command it's asking about. If you're a marketer who can't tell a safe command from a dangerous one, hitting "yes" a hundred times isn't safety — it's a ritual. You're not reviewing anything; you're just clicking. The prompt gives the feeling of control without the substance of it.

That's the real reason velocity-focused and non-technical builders turn the flag on. The checkpoint is valuable in proportion to your ability to use it. If you can't meaningfully review each action anyway, the friction is pure cost. Turn it off, let the agent run in long uninterrupted stretches, and get the autonomous experience the tool was actually designed to deliver. This mindset — trading a checkpoint you can't use for velocity you can — is a big part of what separates a growth engineer from someone still copy-pasting snippets out of a chat window.

The honest risk section (read this part twice)

I'm not going to soft-pedal this, because pretending there's no trade-off is exactly how people get burned. With the flag on, Claude Code can run any command it decides to run, without asking. The overwhelming majority of the time that's mundane — creating a file, installing a package, running your project. But "any command" genuinely means any command, and the agent, brilliant as it is, can misunderstand you, misjudge a situation, or make a mistake. When it does, there's no longer a human checkpoint to catch it before it executes.

So you don't remove the safety net and just hope. You remove the per-action net and replace it with a structural one — you control the blast radius. Here's how, and these rules are non-negotiable:

• Run it inside a dedicated projects folder. Everything you build lives in one folder that contains nothing precious. If a build goes sideways, the worst case is "this scratch project got messed up, I start it over." That's a shrug, not a disaster. This is exactly why the install guide has you make that folder before anything else.
• Don't point it at sensitive stuff. Don't launch it in a folder full of financial records, legal documents, client data, or your entire home directory. The agent works in the folder you start it in — so start it somewhere boring on purpose.
• Understand what you're trading. You are trading a review step for speed. That's a real trade. Make it consciously, on a machine and in a folder where the trade is clearly worth it — not by accident on the wrong computer.

The rule of thumb I use: the flag is fine when the worst realistic outcome is "my scratch project broke and I redo it." It is not fine when the worst outcome is "I damaged something real and irreversible." Keep yourself permanently in the first category and you've handled the risk.

When NOT to use it

There are situations where turning this flag on is genuinely a bad idea, and I want to name them plainly so nobody hears "Jonah said run it everywhere." He did not.

• Shared machines. A laptop other people use, or one with a colleague's files and credentials on it, is not the place. The blast radius isn't yours alone to accept.
• Production servers you care about. Do not SSH into the live server running your business and fire up skip-permissions mode "to fix something quick." That's precisely the "real and irreversible" category. Build and test on your own machine; be deliberate about anything touching production.
• Folders with sensitive data. If the directory contains anything you'd panic about losing or exposing, either move your work to a clean folder first or leave the default prompts on for that session.
• When you're brand new and want to watch. Honestly, your first hour or two, leaving the prompts on can be a decent way to see what the agent chooses to do and build intuition. There's no shame in easing in. Flip to cc once the loop feels familiar.

The cc alias, and why the naming is Anthropic being honest

Once you've decided the trade is right for you, you don't want to type that long flag every time. So you alias it to two letters:

alias cc="claude --dangerously-skip-permissions"

Drop that into your shell config file (~/.zshrc on a modern Mac, ~/.bashrc on many Linux and WSL setups), reload it, and from then on you just open a terminal in your projects folder, type cc, and the agent boots straight into full-flow mode with no approval prompts. If you're not sure how to make an alias permanent, do the thing this whole workflow is built on: ask claude.ai in your browser to add it to your shell config, and paste in whatever line it gives you.

One last thing on the name itself, because I think it matters. Anthropic could have called this flag --auto-approve or --fast-mode or something friendly that hides the trade-off. They didn't. They called it dangerously-skip-permissions, which is them looking you in the eye and saying: this removes a safety mechanism, and we want you to know it before you do it. That's not a company being dramatic — that's a company being honest. Respect the name, understand the trade, put up your structural guardrails, and then go build at the speed the tool was actually designed for.

The bottom line

• --dangerously-skip-permissions turns off Claude Code's per-action approval prompts. It removes a checkpoint; it does not add capability.
• Builders turn it on because constant prompts destroy flow, and because those prompts only protect people who can actually evaluate each command.
• The real risk is that with no checkpoint, an agent mistake executes immediately — so you control the blast radius: dedicated projects folder, nothing sensitive nearby, understand the trade.
• Don't run it on shared machines, production servers, or folders full of sensitive data.
• The cc alias makes it a two-letter habit. The "dangerously" in the name is Anthropic being honest, and you should be too.

Used with a little discipline, this flag is what turns Claude Code from a tool that asks permission into an employee that just gets it done. That's the whole reason the fastest builders run it — and once you feel a two-hour build happen without a single interruption, you won't go back.

Jonah is the founder of FindClout, a curated creator distribution network that has generated 3.3B+ views for brands across sports, prediction markets, AI, and more. He builds most of FindClout's internal tooling himself, in a terminal, with zero formal coding background. Reach him at [email protected] or book a call.