Permissions & settings.json
Claude Code can create, edit and delete files, so by default it asks before doing anything significant — and you can pre-approve the safe stuff.
Because Claude Code can genuinely modify your machine, it asks for approval before significant actions by default. Approving every single action in a long session kills your flow, so the video's advice still holds: start cautious while you learn what Claude Code actually does, then pre-approve specific safe actions once you trust the pattern.
Pre-approvals live in a settings.json file (editable directly, or via /permissions), as an allow-list of specific actions. Anything not on the list still needs your approval — it's not all-or-nothing. A sensible starting allow-list: reading files, running the dev server, running tests, and routine git operations. Keep gated: installing new packages, deleting files or folders, and anything that touches the network or sends data externally. You can also just ask Claude Code to propose and add a safe permission set for you, and review the diff before it saves.
Real-life use cases
A team-shared safe list
A small team checks their agreed settings.json allow-list into the project repo, so every teammate who clones the project gets the exact same pre-approved actions — no one accidentally works with looser permissions than the rest of the team.
Gating the risky 20%
A non-technical founder pre-approves file reads and test runs but deliberately leaves package installs and file deletion gated, so Claude Code can move fast on routine work while she still reviews anything that could break or leak something.
Source
- Source video: “Claude Code Explained” — 27 concepts in 27 minutes (YouTube)https://www.youtube.com/watch?v=ZlDnsf_DOzg
- Settings files and precedencehttps://code.claude.com/docs/en/settings