GUIDES
6 Claude Code Settings Power Users Change On Day One 📚
Claude Code is powerful out of the box, but the settings that actually save you time and money are switched off by default. Here are the 6 I turn on first.
Most people install Claude Code, start typing, and never open a single setting. It works, so why touch it? Because the defaults are built to be safe for everyone, not fast for you. The minute you change a few things, it stops feeling like a clever chatbot in your terminal and starts feeling like a teammate who knows your project.
These are the 6 I change on day one, every single time. None of them are hard. Most are one file or one command. At the bottom I give you my whole settings.json to copy and paste.
One Thing To Know First
Claude Code reads its settings from a hidden folder called .claude that lives inside your project. Files in there (like settings.json, or a commands and agents folder) only apply to that project, so you can give every project its own setup. New to this? Everything below tells you the exact file and where it goes.
Undo Anything Claude Did
Claude went rogue and rewrote half your files? Do not panic and do not start manually fixing things. Press Esc twice (or type /rewind) and Claude opens a list of checkpoints from this session. Pick a point and it rolls back both your code AND the conversation to exactly how they were then. It is a time machine for the whole session, not just an undo for the last edit.
This is the single setting that makes people brave enough to actually let Claude work. You stop hovering, because you know any mess is one keystroke away from being erased.
Build Your Own Slash Command
That prompt you paste five times a day? Stop pasting it. Make a folder called .claude/commands in your project, drop in a plain text file like review.md, and put your prompt inside. Now typing /review runs it instantly. The file name becomes the command name.
Here is a real one I would actually use. Save this as .claude/commands/review.md and you get a /review command forever.
Give Claude A Code Reviewer
A subagent is a second Claude that your main Claude can hand work to. The magic is that it runs in its own clean context, a fresh mind that has not been staring at the same code for an hour. So when it reviews, the review stays honest and your main chat stays focused on building.
Make a folder called .claude/agents and drop in this file. Now your main Claude can send its work to a dedicated reviewer whenever you (or it) wants a second pair of eyes.
One Model Per Project
Running your most expensive model on everything? You are burning through your usage way faster than you need to. A project that is mostly scraping, renaming, and editing docs does not need a genius on every keystroke. A project full of hard architecture decisions does.
Set a default model per project by adding one line to that project's .claude/settings.json. The light, repetitive projects get Haiku (fast and cheap). The hard, high-stakes builds get Opus or Fable. You can always switch on the fly with the /model command, but setting a smart default per project means you stop paying premium prices for grunt work without thinking about it.
Build A Deny List
Before you let Claude move fast, give it a hard line it can never step over. In your .claude/settings.json, a permissions.deny list names the things Claude is flat-out not allowed to do, no matter what. Deny rules beat everything, even the "just do it" mode from setting 6. A deny rule is a guardrail, not a suggestion.
The essentials to block: the command that can wipe folders, anything run as the all-powerful admin user, and reading your secret files.
· Bash(rm -rf:*) blocks the wipe-a-folder command
· Bash(sudo:*) blocks running anything as admin
· Read(.env) blocks reading your secret keys
· Read(./secrets/**) blocks your whole secrets folder
Then add one lock the operating system itself enforces, so even a rogue process cannot read your keys: chmod 600 .env (run that once in your terminal, it makes the file readable only by you).
Stop Clicking Approve All Day
If you sit there approving every single edit, you lose the whole point of having a teammate. You are not building, you are babysitting. Set Claude's default mode so it applies its own edits to files without stopping to ask each time:
"permissions": { "defaultMode": "acceptEdits" }
This is safe precisely because you did setting 5 first. Claude can now edit freely, but it still asks before running commands, and your deny list means the dangerous ones are blocked no matter what. You get the speed of letting it run, with the guardrails holding underneath.
My Ready-To-Paste settings.json
Here is the whole thing in one file. It sets your model, turns on accept-edits, allows the safe everyday commands, and blocks the dangerous ones. Settings 4, 5, and 6 are all in here. Paste it, tweak it, and your project is set up like a power user's.
Save as .claude/settings.json in your project
What To Do With This
In your project, open the .claude folder (or make one), create a file called settings.json inside it, and paste this in. Change "opus" to "haiku" for light projects or "claude-fable-5" for your hardest ones. Add your own safe commands to the allow list as you notice yourself approving the same thing over and over. The deny list is your floor, keep it strict. Then run chmod 600 .env once in your terminal for the OS-level lock.
The Real Win
Twenty minutes of setup and Claude Code stops being a careful assistant you have to supervise and becomes a fast teammate you can trust. It can undo anything, runs your favorite prompts as commands, reviews its own work, uses the right model for the job, and moves at full speed inside guardrails it can never cross. That is the difference between people who play with Claude Code and people who build with it.
The real unlock of AI agents is not full autonomy, but human-in-the-loop systems design. Structure your agent inputs with explicit constraints, negative prompts, and automated test checkpoints. When building tools, keep token consumption lean by caching system prompts and isolating tasks into specialized sub-agents.