Recent public rollout question this answers
Public operator discussions continue to ask whether Claude Code git writes can be bounded by permissions instead of prompt-only instructions. Treat commits, pushes, and force-pushes as explicit rollout controls, not as a vibe-check.
- HN: question about preventing Claude Code from committing to git
- HN: settings.json and hooks as harness-enforced controls
Fast path: run the editable Claude Code rollout check, verify branch/worktree isolation, commit/push scope, secret access, shell approval, and mandatory review, then save a receipt before wider rollout.