Skip to content
Lesson 1 of 119% of the course

Set up Claude Code's permissions, settings and hooks

Use Config Studio for Claude Code to choose what Claude Code may do, see exactly which file each setting goes in, and take the files or one install script away.

Nothing loads from YouTube until you press play. Then Google receives your IP address and may set its own storage. Narrated with an AI-generated voice. Privacy

Claude Code reads its setup from many files: settings in up to four places, CLAUDE.md, hooks, agents, skills, MCP servers and more. Config Studio for Claude Code puts all of them in one place, says what each option does, and shows the exact file it would write. Nothing touches your disk until you run what you take away.

The surfaces on the left, the one you are editing in the middle, the file it writes on the right.

Pick a surface

Open Config Studio for Claude Code. On the left is every surface Claude Code reads: Permissions, Settings, Memory (CLAUDE.md), Status line, Hooks, Agents, Skills, MCP servers and the rest. Click one to edit it. Tick its box to put it in your plan.

Start with Permissions: it decides which tool calls run on their own, which ask first and which are refused.

Start from something

The row above the editor has three shortcuts. This machine says what your computer has, so the plan warns about anything that will not run there. Read in a setup reads a .claude folder you already have into the editor, in your browser. Starter packs fill in several surfaces at once, from a safe seatbelt to fewer interruptions.

Set what you want

Every option says what it does in plain words. For permissions there are three lists: never, ask first, and allow without asking. Presets add common rules in one click, for example Secrets or Destructive shell to the never list, or Running the tests to the allow list.

Presets add common rules in one click.

See where it lives

Open Where it lives under the surface's title. It lists every file the surface can live in, highest precedence first: managed policy, local, project and user. If a setting you made seems ignored, this is where you find out which file overrides it.

Read the exact file

On the right is the file your choices produce, updated as you go and merged into what is already there. Copy it from here if that is all you need.

The exact file, merged with what is already there.

Try it, then take it away

Try it checks your rules and hooks against sample tool calls, so you see what would run, ask or be refused. When you are happy, open Changes to review the plan: every file it writes. Download the files, or take one install script that merges them into your setup and first copies what was there into a backup folder, so you can put it back.

Your progress stays in this browser only.
Contact