Mechanisms / Instruction override Mechanism
Instruction override The system acted against explicit instructions, approvals or stop requests.
A human said not to, said to ask first, or said to stop, and the system continued. These behaviours are especially important because they show that a natural-language instruction is not a control: unless the boundary is enforced outside the model, the model can cross it.
Specific behaviours Ignored explicit instruction 5 Continued a course of action after being told not to, including after correction. MF-021 , MF-018 , MF-014 , MF-031 , MF-027 Acted without approval 1 Executed an action it was only supposed to recommend or prepare. MF-016 Ignored stop request 1 Kept operating after a human asked it to stop. MF-016 Real-world incidents 7 Real-world incidentMF-008 18 Jun 2026
Real-world incidentMF-021 26 May 2026 – 27 May 2026
Real-world incidentMF-015 24 Apr 2026 – 25 Apr 2026
Real-world incidentMF-018 Mar–May 2026
Real-world incidentMF-016 Feb 2026
Real-world incidentMF-014 Jul 2025
Real-world incidentMF-027 Date not established
Tests with real-world reach 2 Safeguards seen in these cases ↷ BypassedSecret scanning MF-021 The token was split across fragments with the stated aim of avoiding push secret scanning.
◒ Partly heldPublication controls MF-021 GitHub push protection rejected a new workflow file, but the model could still change an existing CI script and open a public pull request.
✕ FailedCredential scoping MF-021 The credentials available to the model had write access to OpenAI's public Codex repository.
◒ Partly heldAction monitoring MF-021 The misalignment monitor flagged the trajectory, but the researcher reported it first.
✕ FailedCredential scoping MF-015 The token on disk had account-scoped access, the maximum Railway offers.
✕ FailedEnvironment separation MF-015 A task in staging could reach production storage with the same token.
∅ AbsentHuman approval gate MF-015 The agent ran the deletion without asking, and the legacy API required no separate confirmation.
◒ Partly heldDelayed deletion and backups MF-015 The dashboard had a 48-hour window that the legacy API path bypassed, but offsite disaster backups still allowed full recovery.
∅ AbsentHuman approval gate MF-016 Approval was requested in the instructions, not enforced by the tool.
✕ FailedStop mechanism MF-016 Stop messages did not halt the agent; the operator intervened at the host computer.
∅ AbsentEnvironment separation MF-014 Replit apps then used one database for development and live data.
∅ AbsentHuman approval gate MF-014 The code freeze was an instruction to the agent, repeated many times, not an enforced restriction.
✓ HeldDelayed deletion and backups MF-014 Replit's Rollback restored the deleted data, although the agent said it could not.
✕ FailedStop mechanism MF-031 The shutdown script was something the agent could edit.