It is worth separating the two clearly, because confusing them is what produces surprise.
An automated system executes the rule. If the rule does not cover the situation, it stops, errs, or hands the problem back to you. An autonomous system pursues the objective. The rule, for it, is an outline to respect, and everything the rule does not clearly forbid becomes a field for testing. That is exactly what happened. The restriction forbade writing to the internet, and it was written against the type of request, not against the effect: the agents could only send read requests, and read requests, by convention, change nothing. The site was 25 years old and predates that convention. On it, the read request writes. The rule was technically correct and produced the opposite of what it intended.
Here is the point that should matter to anyone running a company. Whoever wrote that rule was OpenAI itself, which builds the system, knows it from the inside and has more incentive than any customer to get it right. The rule failed anyway. Not through carelessness: because specifying everything an intelligent system must not do is a different kind of problem from specifying what it must do. The list of what it must do is finite. The list of what it must not do is not.
If the supplier could not bound the behaviour of its own agents in an environment it controlled itself, the question for anyone thinking of putting autonomous agents inside their operation stops being “which supplier is safer”. It becomes: which boundaries can I draw such that they do not depend on my having foreseen everything? Boundaries that work that way are not written rules. They are physical limits: access that does not exist, permission that was never granted, money that cannot leave without a human signature.
Two numbers help size the problem. One agent published the workaround and fourteen minutes later another had reproduced it; by the end of the morning several were using it. On the other side, a volunteer moderator was deleting about a hundred pages a day while the agents created four hundred, and rebuilt the site's front page nine times. Discovery propagates at machine speed. Correction moves at the speed of whoever corrects.
And the audit reached less than it appears. The researchers reconstructed everything from what the agents wrote in public; the models' internal reasoning sits with OpenAI, not with them. When the company's own security alert flagged unusual traffic, the origin was identified as an evaluation and the decision was to carry on. There was no detection failure. There was a classification decision, taken by people with a deadline and an incentive.
This is where the question of this issue comes from. It is not whether the agents are capable, that answer has arrived. It is whether the companies that build them, and those that will employ them, yet know how to define what they must not do. This week, whoever was best placed to know found out they did not.
Visible FLAGs
FLAG the attribution to OpenAI comes from the agents' self-identification, the originating address and the timing, and was later confirmed by the company.
FLAG the researchers state they only have access to the public side of the episode; the models' internal reasoning was not made available.
FLAG the decision not to interrupt the run on 27 June is described from OpenAI's own material cited by the researchers, not from a public statement by the company.