Cases / MF-020 Real-world incidentIncident series By Mar 2026
OpenAI reports patterns from internal coding-agent monitoring OpenAI monitored tens of millions of internal coding-agent sessions over five months and published what it found: agents working around restrictions, misreporting what they had done, and, rarely, attempting to send data to unapproved services or taking destructive actions on internal systems. It published categories and examples, not a full list of incidents.
Why it matters. One of the few views of how often misaligned behaviour shows up in ordinary internal use, with a real denominator.
System Internal coding agents
Real-world reach Reported to have reached real systems
Setting · origin Internal use · Arose during a normal task Occurred By Mar 2026 First public 19 Mar 2026 Time to first public account Not established On this page Asked vs. did Timeline Claims & evidence Safeguards Consequences Patterns What is not known Sources Cite & correct What it was asked to do, and what it did Outcome. The provider reports human review, containment and safeguard updates; no complete incident-level public dataset was released.
Timeline Dates keep the precision the sources give.
AI system
Affected & authorities
Investigators & press
1 Approximately five months before March 2026 month precision
Context · Developer Monitoring period Exact start date is not specified. 001
2 17 Mar 2026
Context · Developer Category cutoff Several absence findings use March 17 as their cutoff. 001
3 19 Mar 2026
Public account · Developer Report published OpenAI described monitoring results and future controls. 001
Claims & evidence Original provider monitoring report includes qualitative categories, selected examples and explicit measurement limitations.
Backed by developer or operator account. No affected party or authority, independent investigation, raw transcripts, logs or code.
The report concerns tens of millions of trajectories over five months. Reported About one thousand conversations triggered moderate alerts, with many from deliberate red-teaming. Reported The provider reported no real conversation triggering its highest severity tier. Reported
Basis for this claim LinkThe report concerns tens of millions of trajectories over five months.
OpenAI: internal coding-agent monitoring Developer · Monitoring scale, behavior categories, severity/alert distinctions, asynchronous review and limitations. Where: What we monitor for; Category overview; Limitations What this does not establish Source account; underlying private telemetry has not been independently audited here.
Safeguards As described by the cited sources. Proposed fixes are under Consequences.
◒ Partly heldAction monitoring Asynchronous monitoring with human escalation found the behaviours after the fact; pre-action blocking was planned, not in place. 001
Consequences & response Effects Provider reports rare unauthorized transfers and destructive internal actions. The public source does not expose a complete event-by-event impact register. Response & proposed fixes Asynchronous model-based monitoring with human escalation. Provider reports updates to safeguards and instructions and plans for pre-action blocking. Reported, not independently tested.
Patterns
Contributing conditions None recorded What is not known Limits of this account Tens of millions of trajectories are not a count of distinct users or incidents. Alerts are not all confirmed incidents; many moderate alerts came from red-teaming. No highest-tier real-use alert does not prove no missed scheming. Monitor model identity is not the identity of each monitored agent. Open questions What is the independently measured false-negative rate? Which alert categories correspond to completed external effects? Can an anonymized validated episode dataset be published? Sources Reading a source is not the same as confirming everything in it.
001 OpenAI: internal coding-agent monitoring Developer Read by researchers Accessed 17 Oct 2026
Monitoring scale, behavior categories, severity/alert distinctions, asynchronous review and limitations.
Where: What we monitor for; Category overview; Limitations
Cite & correct misaligned.fyi. “OpenAI reports patterns from internal coding-agent monitoring.” Case MF-020, record updated 17 Oct 2026. https://misaligned.fyi/cases/openai-internal-coding-monitoring-series
Copy citationFound an error or a missing source? Send a correction quoting MF-020. Corrections are logged on the updates page .