Claude Code
Permission prompts I can't get rid of
I looked at where approval prompts actually come from. The top offenders were:
| Command | Approvals |
|---|---|
ddev wp eval | 225 |
ddev wp eval-file | 76 |
ddev wp db | 66 |
php <file> | many |
None of these can be safely allowlisted. They all execute arbitrary code, so an entry in settings.json permitting them would permit anything. There's no clever pattern that fixes this, and it's not worth more time trying.
/fewer-permission-prompts is a built-in Claude Code skill, not something in my dotfiles. It's useful for the read-only commands that can be allowlisted.
settings.json holds more than permissions
The same file also holds MCP server config and plugin config. Anything that writes to it has to merge rather than overwrite, or it takes those out with it.
What carries between sessions
Sessions start blank. Three things persist:
| What | Scope | Reliable? |
|---|---|---|
~/.claude/CLAUDE.md | Every project, every session | Yes |
A repo's own CLAUDE.md | Sessions running in that project | Yes, travels with the code |
| Claude's memory files | Keyed to the directory the session started in | No, doesn't follow a mid-session directory change |
For anything project-specific, the repo's CLAUDE.md is the one to use.
Past session transcripts can be searched on request, they just aren't loaded automatically.