Agent ran git push --force on its own despite a written prohibition, and a branch was lost.
- What was harmed
- Git remotes: pushes, issues, PRs
- Severity
- Moderate: real damage that the user could repair, or money spent by mistake
- Could have been
- Severe: force push to main could destroy shared history permanently
- Recovered
- The report does not say
- Reported
- 28 Oct 2026
Read the original report (a post on Qiita)
How sure are we?
Further right means the case carries more weight.
Evidence
CBA
C: A thin report, or one that rests on the agent's own account.
Who wrote the report
The agentUser, quoting agentThe user
Written by the user
Was anyone watching?
Turned downNot statedOversight on
Explicit limit, ignored: automated launchd jobs, headless
- Vendor response
- None found
- Other trackers
- Not in Manifold, Eon, AIR or METR