Benchmarks for Trajectory Safety Evaluation and Diagnosis in OpenClaw and Codex: ATBench-Claw and ATBench-CodeX
This paper introduces ATBench-Claw and ATBench-CodeX, two domain-specific extensions of the ATBench framework that utilize a customized three-dimensional safety taxonomy to evaluate and diagnose trajectory-level safety risks in OpenClaw and OpenAI Codex execution environments.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are building a self-driving car. You have a safety manual (the benchmark) that teaches the car how to handle traffic, pedestrians, and road signs. But what happens when you take that same car off the highway and put it into a construction zone? Or a nursing home? The rules change. The dangers change. A "stop sign" in a construction zone might mean something totally different than on a highway.
This paper is about updating the safety manual for two very specific, new "construction zones" where AI agents (smart computer programs) are starting to work.
Here is the breakdown in simple terms:
1. The Problem: Old Maps Don't Fit New Territories
AI agents are getting smarter. They aren't just chatting anymore; they are actually doing things.
- Old AI: "What's the weather?" -> Answers.
- New AI: "Order me a pizza, then delete the file on my desktop, and email the receipt to my boss." -> Does it.
The researchers realized that the old safety tests (benchmarks) were like checking if a car can stop at a red light. But now, we need to check if the car can handle a construction site (where it might accidentally knock over a crane) or a surgery room (where it might pick up the wrong scalpel).
2. The Solution: The "Universal Safety Kit" (ATBench)
The team created a flexible safety system called ATBench. Think of this as a Lego-based safety kit.
- Instead of building a brand-new safety car for every new job, they built a chassis that stays the same.
- The only thing they change is the instruction manual (the "Taxonomy") attached to it.
- This manual lists: Where does the danger come from? How does the robot fail? What is the real-world damage?
3. The Two New "Construction Zones"
The paper introduces two specific versions of this kit for two different types of AI jobs:
🛠️ ATBench-Claw: The "Swiss Army Knife" Agent
- The Setting: Imagine an AI assistant that has a giant toolbox. It can talk to people, send emails, open files, and control other apps.
- The Danger: The risk here is like a chaotic office. The AI might confuse "Send to Boss" with "Send to Spam," or it might accidentally delete a file because it thought it was a temporary note.
- The Fix: The researchers updated the safety manual to focus on identity confusion (who is talking?), session state (what was the AI doing 10 minutes ago?), and approval chains (did the human say "yes" before the AI clicked "send"?).
💻 ATBench-CodeX: The "Code Monkey" Agent
- The Setting: Imagine an AI that writes code, fixes bugs, and manages software projects. It lives inside a digital workshop full of code repositories and servers.
- The Danger: The risk here is like a sabotaged factory. The AI might install a virus disguised as a helpful tool, delete the entire factory floor (workspace), or leak secret blueprints (passwords).
- The Fix: The safety manual was tweaked to focus on code injection (tricking the AI with bad code), dependency chains (installing a tool that breaks everything else), and destructive mutations (accidentally deleting the whole project).
4. The Magic Trick: "Customize the Rules, Keep the Engine"
The coolest part of this paper is their philosophy.
- Before: If you wanted to test a new type of AI, you had to build a whole new testing lab from scratch.
- Now: You just rewrite the rulebook for that specific job, but you keep using the same testing engine.
It's like having a driving test.
- For a Taxi Driver, the rulebook says: "Watch out for pedestrians and traffic lights."
- For a Race Car Driver, the rulebook says: "Watch out for tire wear and aerodynamics."
- The car (the AI framework) and the test track (the data generator) are the same. You just change the rules to fit the driver.
5. The Results: Who Passed the Test?
The researchers tested several AI models on these new, harder safety tests.
- The "Guard" Models: These are AI models specifically trained to be safety police. They did okay, but they struggled a bit with the new, complex rules.
- The "General" Models: These are smart, general-purpose AIs. They did surprisingly well, showing that if you teach them the right rules, they can be very safe.
- The Winner: The team's own system, AgentDoG, which uses a smart "guardrail" approach, scored the highest. It was the best at spotting the subtle, dangerous mistakes in both the "Swiss Army Knife" and "Code Monkey" scenarios.
The Big Takeaway
As AI starts doing more dangerous and complex tasks, we can't just use the same safety tests we used for chatbots. We need to adapt our safety rules to the specific environment the AI is working in.
This paper proves that we don't need to reinvent the wheel every time. We just need a flexible rulebook that can be customized for the job, ensuring our AI agents don't accidentally burn down the house while trying to cook dinner.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.