Claude Code's --dangerously-skip-permissions: What It Actually Risks

October 26, 2026 · Dirk

Claude Code's --dangerously-skip-permissions flag is the same as --permission-mode bypassPermissions: the agent stops asking before it acts. Here is what that turns off, what still applies, where Anthropic says it belongs, and how to see what the agent did when nobody was asked.

What it turns off, and what still applies

In the words of Claude Code's permission modes documentation, the mode "disables permission prompts and safety checks so tool calls execute immediately, including writes to protected paths." In practice:

Anthropic is direct about where it belongs:

"Only use this mode in isolated environments like containers, VMs, or dev containers without internet access, where Claude Code cannot damage your host system."

And: it "offers no protection against prompt injection or unintended actions."

What it actually puts at risk

And sometimes nothing in between catches anything at all. From one developer who runs it constantly:

"I run claude code --dangerously-skip-permissions all the time … Well, the worst finally happend claude issued a command to delete all files on my C: directory."

Nothing of value was lost in that case, because it was a gaming and build machine. That is the point: the mode is only as safe as the machine it runs on.

Why people run it anyway

Because the prompts interrupt real work. An agent that stops every few minutes to ask about npm test is hard to use for anything long. That is a real cost, and the answer is not to tell people to stop; it is to give the agent a machine where saying yes to everything is acceptable, and a record of what it did.

Getting the speed more safely

Seeing what it did

In this mode nobody reviews the actions as they happen, so the record afterward is the only review there is. kaimon gives you that record for AI coding agents on Linux:

Stated plainly: kaimon does not tell you that the mode was on. It shows what happened while it was. It observes and never blocks, records from the moment it is installed, and runs on Linux, including a Linux dev box or VM you work on from macOS or Windows over VS Code Remote-SSH.

Get the VS Code Extension

Always free and 100% local: nothing leaves your machine. See how it works, or read what to check when an agent deleted your files.

FAQ

Does --dangerously-skip-permissions disable deny rules?

No. Deny rules block in every mode, including this one. Allow rules have no effect, and explicit ask rules still prompt. Deny rules match commands, though, so the same effect reached another way is not blocked.

Is auto mode a safe replacement?

It blocks far more than skip-permissions, because a classifier reviews actions before they run. Its documentation says it reduces prompts but does not guarantee safety.

Can kaimon tell whether an agent ran with --dangerously-skip-permissions?

Not today. It records what the agent did to files, attributed and risk-rated, which is what matters most in a mode where nobody reviewed the actions.

Is it safe to use in a container?

That is what Claude Code's documentation recommends: a container, VM or dev container without internet access, run as a non-root user, where the agent cannot damage the host.

Ready to Align Your AI Agents?

Two minutes to install. From then on, every file change your agents make is on record.

Get the Free VS Code Extension

Linux, local or over Remote-SSH · Nothing leaves your machine

Running a team? Get notified about kaimon for Teams