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:
- ๐ญ OpenAI's own agent broke out of its sandbox to win a coding contest, then explained how
- ๐ง NVIDIA's SIGGRAPH slate pairs agentic tools with real-time physical-AI sim, Azure leans on AMD
- ๐ฌ Trimming agent bloat, sycophancy's hidden address, breaking reasoning loops
- ๐๏ธ Brussels spells out the AI Act's transparency duties, twelve days before they bite
- ๐ ๏ธ Stress-test your own agent against the failure modes OpenAI just admitted to
- ๐ Glasswing's critical-infrastructure expansion, Anthropic's rare-disease grants, GitHub's $100M milestone
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
- NVIDIA used SIGGRAPH to pair agentic dev tools (an Agent Toolkit for local DGX agents with MCP support, NemoClaw for packaging your own domain-specific agent) with physical-AI sim: Cosmos-Dreams spins up a full driving world from a single frame on one RTX PRO 6000 GPU. SIGGRAPH recap
- NVIDIA also cut Cosmos 3 Edge loose, a 4B-parameter world model small enough for Jetson and RTX PRO hardware. It hits real-time control at 15 Hz on Jetson Thor and tops VANTAGE-Bench for its size class, the kind of spec that matters when you want vision reasoning running on the robot itself, not round-tripping to a server. Cosmos 3 Edge
- Microsoft is threading AMD into Azure's AI buildout: HDv2 for data prep and agent coordination, HXv2 for chip-design simulation, and an ND MI455X v7 inference line running on AMD's Helios rackscale gear. Read it as a hedge against Nvidia dependence as much as a capacity add. Azure/AMD announcement
๐ฌ RESEARCH HIGHLIGHTS
- TRIM Coding agents leave a mess behind: speculative edits, abandoned hypotheses, scaffolding that never gets cleaned up before the final diff. This paper names it "CodeSlop" and trims it by pruning the agent's search trajectory itself rather than post-editing the output. Builder read: worth wiring into any coding-agent pipeline where diff size matters for review. link
- Sycophancy has an address Slip a model a casual hint, a mislabeled few-shot example, or a fake prior answer, and it'll often flip a correct answer to match. Researchers traced the effect across multiple model families and found the bug isn't in pretraining. Base models barely have it. Alignment tuning installs it, as a single decodable direction in the hidden states for each type of bias, and nudging that direction recovers the right answer across every family tested. Watch, don't act: it's a diagnostic tool for now, not a shipped fix. link
- SOPHIA Long reasoning chains sometimes get stuck circling the same dead end until the token budget runs out. This method detects that kind of loop mid-trace and steers the model back out before it burns through the budget. Reports gains in both accuracy and token efficiency. link
๐๏ธ POLICY & REGULATION
- European Commission published its guidelines on Article 50 transparency duties under the AI Act, and the timing tells you something: obligations kick in August 2, 2026, twelve days out. The guidance spells out who has to disclose what: providers of chatbots and content-generation tools flag that users are talking to a machine, deployers running emotion-recognition or biometric-categorization systems tell the people being scanned, synthetic and manipulated media gets marked. Builder read: if your EU-facing product does any of that and doesn't have a disclosure flag wired in yet, you have less than two weeks.
๐ ๏ธ 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
- Grabette (Pollen Robotics) A handheld rig for recording your own robot-manipulation demos by hand and turning them into LeRobot-ready training data. No robot needed for the capture step, just cameras, an IMU, and a Raspberry Pi. huggingface.co/blog/grabette
๐ QUICK LINKS
- Anthropic expanded Project Glasswing, its AI-assisted vulnerability-hunting program, from roughly 50 partners to about 150 new organizations across 15+ countries, pulling in critical-infrastructure operators in power, water, healthcare, and comms for the first time. Early partners had already found over 10,000 high- or critical-severity flaws. Anthropic
- Anthropic opened its AI for Science rare-disease grants: up to $50K in Claude API credits over six months, for researchers and early-stage biotechs working on the roughly 7,000 conditions that affect 400 million people worldwide. Applications close August 2. Anthropic
- GitHub Sponsors has now paid out $100M to open source maintainers since 2019. The first $10M took two years; the most recent $10M took five months. GitHub
See you tomorrow.
Pradeep Perugu