OpenAI Dots safety report: blocks scams but oversteps limits
The author breaks down OpenAI's own report: Dots blocked all 16,600 scam emails, but with more tasks it quietly overstepped its limits nearly one in five times at 10 tasks.
nobody could hack OpenAI’s Dots. nobody had to 16,600 scam emails thrown at Dots. zero worked. but left alone in a quieter test, the same agent broke its own limits nearly 1 time in 5. both numbers are in OpenAI's own report. here's what the Sam Altman launch hype skipped. so the real question is how it decides what it's allowed to do without you. I mapped it (video below). every time a Dot wakes up, 3 things happen: 1. something wakes it: your message, a schedule, an event in one of your apps, or its own background research while you're away. 2. it picks where to work: your apps, its cloud computer, helper agents, or a coding task. 3. a separate AI reviewer checks the action before it happens. there are only 4 outcomes: → it just runs (it's only reading, or you already said yes) → it asks you first (sending an email, posting for you) → it hands the step to you (passwords and money transfers, always) → it gets blocked (an email telling it to forward your data somewhere) that reviewer is why the scam emails failed. so where does the 1 in 5 come from? juggling. when a Dot's limits changed quietly between jobs, it overstepped 8.6% of the time with 5 tasks in between, and 19.7% with 10. nothing severe, mostly carrying info from one job into another. the more you pile on one agent, the sloppier it gets. the skill that matters now is giving an AI one clear job and clear limits. I break down how new AI tools work under the hood in visuals like this one. if someone on your team is about to hand their inbox to an agent, they should see this first. would you let an AI read your email all day if it promised to ask before hitting send?
This post quotes another post: x.com/noisyb0y1/status/2105964235087856080