Set Up Permissions to Avoid Constant Approvals
Tired of approving php artisan test every time? The quickest way to set this up is with /update-config:
/update-config
"Allow all php artisan commands"
"Allow vendor/bin/pint"
"Allow npm run build"
This writes the rules directly to your .claude/settings.json. You can also edit it manually:
{
"permissions": {
"allow": [
"Bash(php artisan *)",
"Bash(vendor/bin/pint *)",
"Bash(npm run *)"
]
}
}
You can scope permissions to specific projects by using .claude/settings.local.json in the project root instead of the global settings file (~/.claude/settings.json). Per-project is usually the better choice — your Laravel app doesn't need the same permissions as a Node service.
Be thoughtful about what you allow — you probably don't want to auto-approve rm -rf or git push --force. The goal is to reduce friction for safe, common operations while keeping guardrails on destructive ones.
Log in to leave a comment.
The autoUpdatesChannel setting pins Claude Code to a stable release track that skips versions with major regressions.
The language setting makes Claude respond in your preferred language by default, across every session and project.
The attribution setting lets you customize or completely remove Claude's Co-Authored-By trailer from git commits and pull requests.