Check your Claude Code settings
Last checked . Checked against code.claude.com 1, Permission modes.md, code.claude.com 2, code.claude.com 3, Scheduled tasks.md, code.claude.com 4.
In short. Make a short CLAUDE.md file with your rules, start in Plan or Manual mode, deny the files Claude must not read, and run claude doctor. This takes about 15 minutes, once.
Before you start
Finish Install Claude Code. Open a terminal in the folder you will work in. Claude Code reads files there and sends them to Claude, so read the safe use notes first.
Set these once
Step 1. Write a first CLAUDE.md
A CLAUDE.md file holds standing rules that load at the start of every session. Read What is a CLAUDE.md file. In your project folder, start claude and type /init. Claude drafts a file from what it finds. If one exists, it suggests improvements. Then edit it. Keep it under about 200 lines, because long files get followed less well. You can also keep personal rules for every project in ~/.claude/CLAUDE.md.
A short start for a quote folder:
# Quote folder rules
- Files here are supplier quotes for Mesquite Ridge Manufacturing.
- Never change the original files. Write results to a new folder named out.
- If a value is missing, write "not stated". Do not guess.
- Keep part numbers exactly as written.
These rules are advice, not locks. For a rule that must never break, use a hook.
Step 2. Pick a permission mode
Press Shift+Tab inside a session to cycle modes. Read What is plan mode.
- Manual (setting name
default) asks before it edits files or runs commands. Use it for sensitive work. - Plan only reads and proposes. Use it first on any new job.
- Accept edits lets it change files without asking, but still asks for most commands.
- Auto lets a second AI check each action in the background. On version 2.1.283 or newer, it is the starting mode in the terminal. Switch to Manual or Plan with Shift+Tab until you trust a job.
You can also start one session with claude --permission-mode plan.
Step 3. Allow and deny actions
Settings files hold rules. A deny rule blocks an action. An allow rule skips the question. Create ~/.claude/settings.json (on Windows, .claude inside your user folder) and add:
{
"permissions": {
"deny": ["Read(./.env)", "Read(./.env.*)"]
}
}
The file must be strict JSON, with no comments or trailing commas.
Step 4. Know where settings live
~/.claude/settings.jsonholds your personal settings for every project..claude/settings.jsonin a project is shared with the team..claude/settings.local.jsonis yours alone for one project.- A company can also push managed settings that you cannot override.
Run /status inside Claude Code to see which files loaded. Run /config for a short menu of personal options such as theme. /config works in the terminal, not in every app.
Step 5. Check your version and updates
Native installs update themselves. Run claude update to update now. Homebrew and WinGet installs do not update themselves.
Step 6. Set up a scheduled task
A scheduled task is a prompt that Claude Code runs on its own at a set time. There are three kinds.
- Cloud scheduled task (formerly called a routine). Open claude.ai/code/routines and click New task, or type
/schedulein Claude Code. It runs in the cloud, so your computer can be off. It starts from a fresh copy of your repository, so it cannot see local files. It is a research preview, so names and limits may change. Pro, Max, Ultra, Team, and Enterprise plans have it. The shortest gap is one hour. - Desktop scheduled task. It runs on your own machine, so your files are there, but the machine must be on.
- /loop. Type
/loop 30m check the buildin a session. It runs only while that session is open, and a repeating loop ends after seven days.
Here is a sample for a cloud task:
Every Monday at 7 am, list open POs past due from the attached export and draft one chase email per supplier. Do not send anything.
For a cloud task, open its page to Run now, use the on/off switch at the top to pause or resume it, or open the menu by its name for Edit and Delete. Past runs open as full sessions you can read. For a loop, ask Claude "what scheduled tasks do I have?" and "cancel the build check."
Safety habit. Start with drafts only. Say "do not send" in the prompt. Read the first few runs before you trust it. A cloud task connects to everything you have linked, so remove connectors it does not need. Read How to schedule AI tasks and What triggers an AI agent before you rely on one.
Check it worked
Run these:
claude --version
claude doctor
claude doctor prints install health and any settings errors. Then start claude and type /memory. Your CLAUDE.md should be in the list.
If something goes wrong
- Claude ignores a rule in CLAUDE.md. Make it shorter and more specific, or turn it into a hook.
- A setting does not apply. Run
/status. A higher file, or your company, may set it. Auto and bypass modes do not work from a project settings file. Put them in~/.claude/settings.json. - A Settings Error appears at start. The JSON has a typo. Let Claude help fix it, or run
claude doctor. - You cannot use
/config. It is a terminal feature. In VS Code or the desktop app, edit the settings file or use the app's own settings.