.claude/settings.json

{
  "permissions": {
    "ask": [
      "Skill(update-config)",
      "Skill(update-config:*)",
      "Bash(git commit)",
      "Bash(git commit *)",
      "Bash(git push)",
      "Bash(git push *)"
    ]
  },
  "sandbox": {
    "enabled": true,
    "failIfUnavailable": true,
    "autoAllowBashIfSandboxed": true
  }
}
chore(claude): add project settings with sandbox and ask rules Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> 2026-05-12 19:54:34 +02:00			`{`
			`"permissions": {`
			`"ask": [`
			`"Skill(update-config)",`
chore(claude): drop Bash() and require confirmation for commit and push The allow list in this file never took effect. Claude Code discards every `permissions.allow` entry from project settings while the workspace has not been trusted (hasTrustDialogAccepted is false for this repo), and it does so silently in interactive sessions. `Bash()` was therefore inert. Removing it rather than granting trust: the rule only ever bites on the unsandboxed path, where it would have meant "any command, outside the sandbox, without a prompt" for everyone who clones this repo. Sandboxed Bash is auto-allowed anyway, so the entry bought nothing safe. Add ask rules for git commit and git push instead. Unlike allow rules, ask and deny are not filtered by the trust gate, and the sandbox auto-allow path checks them before granting, so they apply to sandboxed and unsandboxed invocations alike. Both a bare and a wildcard form are listed because `git commit ` compiles to /^git commit .$/ and would not match the bare command. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> 2026-07-28 00:11:29 +02:00			`"Skill(update-config:*)",`
			`"Bash(git commit)",`
			`"Bash(git commit *)",`
			`"Bash(git push)",`
			`"Bash(git push *)"`
chore(claude): add project settings with sandbox and ask rules Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> 2026-05-12 19:54:34 +02:00			`]`
			`},`
			`"sandbox": {`
			`"enabled": true,`
chore(claude): expand permissions and require sandbox - Adds `Bash(*)` to the allow list so routine shell commands run without prompting. - Sets `sandbox.failIfUnavailable=true` so Claude Code aborts rather than silently running unsandboxed when the sandbox cannot initialize. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> 2026-05-12 22:18:54 +02:00			`"failIfUnavailable": true,`
chore(claude): add project settings with sandbox and ask rules Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> 2026-05-12 19:54:34 +02:00			`"autoAllowBashIfSandboxed": true`
			`}`
			`}`