How to Skip All Claude Code Permission Prompts

by Rian

In a more closely controlled environment with less risk, say, in a home lab of an enthusiast, the risk of Claude Code accidentally wiping the drive or destroying another repo is minimal. Not that it cannot happen, but a reasonable amount of backup or git versioning practice could mitigate most of the risks from accidental or non-malicious actions. In such a scenario, Claude asking for permissions only slows down making your idea come true.

I use VS Code as my main editor, but no doubt the steps are similar on other platforms as well. At the start of the session, run the following command:

claude --dangerously-skip-permissions

If you are already in an active session, you may stop it and run the following. The -c flag stands for continue:

claude -c --dangerously-skip-permissions

Some tangent on the recent Fable development news: I was in the process of writing an op-ed. It was far better at reading the UI and coding style conventions I had set up, and at enforcing them across other repos. It was not bulletproof, but in my use, it cost fewer tokens than Opus 4.8 did. I probably won’t publish the piece as-is. Not only is the model now inaccessible, but as a hobbyist, I have to weigh, from the ground up, the reliability of LLMs as coding tools, and furthermore of Anthropic’s services. They say AIs can’t make new things, but we certainly love to treat them as new creators amongst us.