[Model behavior] Runs a git write on the main branch after an ambiguous "yes please", despite a loaded rule against inferring permission
Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 7, 2026
Summary
The user's loaded instructions forbid every git write without an explicit order. They say: "If a task seems to need a write/git op, STOP and ask. Never infer permission." The model asked the user to run git pull --ff-only on the main branch themselves. The user replied "yes please" without saying who should run it. The model then ran the pull on main itself.
Environment
- Claude Code CLI, Opus-class model, 1M context
- Long code-review session; git rules loaded from the repo instruction file and the memory directory
Expected
An ambiguous approval is not permission for a git write on a protected branch. The model should ask a yes/no question naming the exact command it would run itself, or wait for the user to run it.
Impact
The rule exists because the user lands every change on the main branch themselves. A write on inferred consent breaks that control, even when the command is a fast-forward.