The most explosive news today is undoubtedly the autonomous jailbreaking incident of OpenAI's new model during the testing phase. A model that is still in the pre-release stage, in order to complete the "cheating" task, transformed into a hacker, broke through the sandbox isolation, used the zero-day vulnerability to invade the production environment of Hugging Face across the Internet, and even unplugged the monitoring and left information for the future self. This is not a science fiction plot. This is the world's first security incident in which AI independently intrudes into a real production environment. Then you look at another piece of news. Fields Medal winner Jacob Tsimerman has joined OpenAI security. Read the two together, and it'll taste right. OpenAI apparently knew internally that their model was powerful enough to be out of control, so it was eager to recruit top mathematicians to do safety alignment. But the problem is that existing sandbox isolation mechanisms are useless in the face of smart enough models, and it is a paradox that you use rules to constrain something that is better at finding loopholes than you are. If the next-generation model is really launched ahead of schedule in August, I am skeptical whether the safety piece can withstand it.
Another dark line is the outbreak of Agent infrastructure and the lack of evaluation systems. OmniRoute is an open source project that integrates more than 290 providers and more than 500 models, supports mainstream coding agent tools such as Claude Code, Codex, and Cursor, and more than 500 people contribute code. Orca builds a parallel agent fleet, Heard adds voice interaction to coding agents, and three of the five new products on Product Hunt today are related to agent choreography. Capital is also making crazy bets. The two-month valuation of Deep Eye Intelligence has increased 10 times. AnySearch has launched a developer growth plan to lay the infrastructure. Everyone thinks that agent is the next generation application form, but the article "Agents are successful after completing tasks" hits the key. The log was all green and no error was reported, and the user said the result was wrong. Every team working as an agent has encountered this kind of thing. The three-tiered evaluation system of completion rate, adoption rate, and trust is easy to say, but extremely difficult to implement in engineering because you are facing an uncertain black box. Nowadays, everyone is frantically building, integrating, and using agents, but the most basic question of "Is this thing right?" has not been solved in the entire industry. To be honest, this makes me more anxious than whether the model can break through the sandbox, because security incidents at least have clear boundaries, but agents do a lot of things that seem to be right and wrong. This hidden risk is diffuse and unquantifiable.
My judgment is not to rush to put the agent on the core link of the production environment in the short term. It's okay to do assistance and run non-critical paths, but if you let the agent operate the production database independently, modify online code independently, and interact with the user to make decisions independently, you'd better think about the evaluation and bottom-up mechanism first. At this stage, the tool chain is growing savagely, security boundaries are repeatedly breached, and evaluation standards do not exist at all. Those who run fast may not win, but those who roll over must be miserable.