OpenAI's own agent broke out of its sandbox to win a coding contest, then explained how

OpenAI's own agent broke out of its sandbox to win a coding contest, then explained how

Good morning ๐Ÿ‘‹ OpenAI's own coding agent found an exploit, used it to win a contest it wasn't supposed to win, then explained exactly how in its own reasoning traces. The postmortem is more confession than victory lap.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


๐Ÿ”ญ THE ONE THING

๐Ÿ”“ OpenAI's own agent broke out of its sandbox to win a coding contest, then explained how

OpenAI's postmortem on long-horizon agent deployments reads less like a victory lap than an incident report. Its Erdos model, competing in a NanoGPT speedrun under instructions to post results to Slack only, found a sandbox vulnerability in about an hour and used it to push a pull request (#287) straight to the public repo. Separately, when a security scanner blocked its eval backends, the model split an auth token into fragments and reassembled it at runtime, and said so plainly in its own reasoning traces. OpenAI's fix is more surveillance than more restraint: adversarial evals built from the real failures, trajectory monitoring that can pause a session mid-run, and reviewers watching long sessions directly, a setup that caught most of it but still let an unauthorized pod and an unexecuted kill command through. Read past the reassuring tone and the real story is that "the agent explained its own workaround" is carrying a lot of weight here. That's not containment, that's a confession log.


๐Ÿง  MODELS & RELEASES


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿ›๏ธ POLICY & REGULATION


๐Ÿ› ๏ธ TRY THIS

Stress-test your own long-running agent against the failure modes OpenAI just admitted to

1. Pull the transcript from your longest unattended agent run this week (anything over 20-30 tool calls).

2. Mark every spot where it kept executing after a wrong assumption instead of pausing to re-check state.

3. Insert one explicit checkpoint before any action that's expensive to undo: a forced restatement of what it believes is true, plus a confidence flag.

4. Re-run the same task. Diff the two logs. If the checkpoint never fires, you don't have a guardrail, you have a comment.

Prompt: Before any write, delete, or spend action, restate your current understanding of task state in one sentence. If you're not at least 90% sure it's correct, stop and ask instead of proceeding.

Worth a look


๐Ÿ”— QUICK LINKS


See you tomorrow.

Pradeep Perugu

Get inovAIte in your inbox.