Claude Code settings.json Generator
Pick permission rules, hook presets, env vars, and a model override one step at a time, then copy or download the finished settings.json.
Step 1 of 5
What can Claude do without asking?
Claude normally stops and asks before running commands. Tick the ones you are happy for it to just do - the first one is on because it is completely safe.
5 quick steps - free, no sign-up, nothing you configure here leaves your browser
FAQ
What is settings.json in Claude Code?
The configuration file that controls permissions (what Claude can run without asking, what it must never touch), hooks (shell commands that fire automatically on lifecycle events like a file edit or session start), environment variables, and model selection. It lives at ~/.claude/settings.json for your whole machine, or .claude/settings.json to share with your team on one project.
Where do I put the generated settings.json?
~/.claude/settings.json applies to every project on your machine and is not shared. .claude/settings.json applies to one project and is meant to be committed, so your team gets the same rules. .claude/settings.local.json is project-scoped but gitignored, for personal overrides. If a file already exists at that path, merge the new rules in rather than replacing it - the generator's paste prompt does this for you.
Do the hooks in this generator run automatically?
Not until you paste the output into your settings.json and save it. Turning on a preset here only adds it to the JSON preview - nothing executes in your browser. Once saved, a hook fires every time its event happens, which is why every preset is off by default and worth reading before you turn it on.
What is the difference between allow, deny, and hooks?
Allow and deny are permission rules: allow skips the confirmation prompt for a command, deny blocks it outright with no override. Hooks are different - they do not gate a decision, they run a real shell command when an event fires, whether or not you would have approved that specific action. Use deny for hard limits and hooks for automation.
Is this settings.json generator free?
Yes - free, no sign-up, and nothing you toggle leaves your browser; the JSON is assembled locally. ClockedCode separately sells a complete done-for-you Claude Code setup, but the generator itself is not gated.
This is a visual builder for Claude Code's settings.json - the file that controls what Claude can run without asking, what it can never touch, which shell commands fire automatically on lifecycle events, and which model a project starts with. It walks you through one section at a time and ends on the full JSON preview, so you see exactly what you are about to paste before you paste it.
The permission rules are curated, not exhaustive. Reading git status, diff, and log is checked by default because those are read-only and Claude asks about them constantly. Blocking .env reads, force-pushes, and recursive deletes is also checked by default, because those three cover most of the damage a wrong command can do. Everything else starts off - you turn on what you actually want, using the exact `Bash()` and `Read()` matcher syntax Claude Code's permissions system expects.
Hooks are the part people get wrong most often, because the schema nests three levels deep: an event name, an optional matcher, then the handler array. This builder ships four tested presets - format-on-edit, lint-on-save, a terminal-bell notification, and a session-start context printer - and every one of them is off until you turn it on, since a hook runs a real shell command on your machine every time its event fires. Nothing here executes anything; it only writes the JSON.
The recommended path is the paste prompt, not the raw file: it tells Claude Code to check whether you already have a settings.json, merge this draft into it instead of overwriting your existing rules, and verify the format-on-edit and lint-on-save hooks actually match what is installed in your project before keeping them. That merge step is the part a static generator cannot do and a copy-pasted gist actively gets wrong.
The hook presets pair naturally with the complete Claude Code hooks guide, which documents every lifecycle event those presets hook into and when each one earns its place. And once the rules file is set, the CLAUDE.md generator builds the other half of a tuned setup - the instruction file that tells Claude how to behave inside the boundaries this one enforces.
I run Claude Code daily and this builder ships the same permission and hook conventions my own settings.json uses. If you want the finished version of the whole idea - a tuned settings.json, a tuned CLAUDE.md, and the full vetted tool stack, installed in one paste - that is what ClockedCode is. The link is at the bottom of this page.
By Neo Zino - builder of ClockedCodeOther free tools
CLAUDE.md Generator
Answer 7 quick questions, get a tuned CLAUDE.md for your project in 30 seconds.
Try toolTemplate libraryClaude Code Templates
A curated library of copy-paste Claude Code templates: subagents, hooks, slash commands, settings, and CLAUDE.md starters, each one explained and pulled from a setup that gets used every day.
Try toolToken scannerUsageCut
Scan your Claude Code setup in 30 seconds and see exactly what is burning your tokens - bloated context, heavy MCP servers, and settings quietly draining your usage limits.
Try tool