Dangerously-skip-permissions is the only safe mode
The article discusses the safety implications of using the --dangerously-skip-permissions flag in Claude Code. It argues that the default permissions mode can lead to approval fatigue, making it less secure than the alternative. By using --dangerously-skip-permissions, users are encouraged to implement a proper authorization system instead of relying on constant approvals.
- ▪The default permissions mode in Claude Code can lead to approval fatigue.
- ▪Using --dangerously-skip-permissions allows the agent to operate without constant human approval.
- ▪Implementing an authorization system is suggested as a safer alternative to the default mode.
Opening excerpt (first ~120 words) tap to expand
--dangerously-skip-permissions is the only safe modeJim FisherMay 11Claude Code has a flag called --dangerously-skip-permissions. Despite the name, I'm more nervous about engineers who don't use it. If you run the default "permissions" mode, your Claude setup is probably unsafe. --dangerously-skip-permissions lets the agent do anything it wants on your machine. Sounds dangerous. Claude could do real damage with the DATABASE_URL in your env files. By default, Claude asks permission before it acts: run a script, delete a file, make a network request. Sounds sensible. The human stays in the loop. Now watch what happens after a few minutes. Claude asks to write a script. Writing files is safe. Approve. Claude asks to run the script. The script looks safe. Approve. The script has a bug.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Granola.
Discussion
0 commentsMore from Granola
