Claude Code Settings & Permissions Builder

Build a settings.json for Claude Code: decide which commands run without asking, which are blocked, add hooks that run automatically, and set environment variables — no JSON hand-editing.

1. Where will this file live?

.claude/settings.json — Checked into git and shared with your whole team.

2. Permissions

Quick-add rule packs (click again to remove):

ToolSpecifierList

Rule: Bash

allow 0

Runs without asking

No rules yet.

ask 0

Always asks for confirmation

No rules yet.

deny 0

Blocked entirely (wins over allow)

No rules yet.

Default mode

Additional directories

Extra folders Claude may read and edit outside the project root.

3. Hooks

Hooks are shell commands Claude Code runs at lifecycle events. They receive the event as JSON on stdin (e.g. .tool_input.file_path). In PreToolUse, exit code 2 blocks the tool call and sends stderr back to Claude.

Recipes:

No hooks yet — pick a recipe above.

4. Environment & other settings

ModelCo-authored-by in commitsTranscript cleanup (days)

Import existing settings.json

.claude/settings.json

✓ No issues found.

{
  "$schema": "https://json.schemastore.org/claude-code-settings.json"
}

Precedence: managed policy → command-line flags → local project → shared project → user settings. Check what is active with /permissions and /hooks inside Claude Code.