A Comprehensive Survey of Agents for Computer Use: Foundations, Challenges, and Future Directions
This survey presents a comprehensive taxonomy and analysis of 87 agents for computer use (ACUs) and 33 datasets to identify key research gaps and propose future directions for developing robust, general-purpose agents capable of executing complex tasks across digital platforms.
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 have a very smart, eager robot assistant. You tell it, "Please book a flight to Paris and email the confirmation to my boss." In a perfect world, this robot would open your browser, find the airline site, click the right buttons, fill in the forms, and hit send.
This paper is a massive survey of how close we are to building that perfect robot. The authors call these robots "Agents for Computer Use" (ACUs). They are software programs that don't just chat with you; they actually do things on your computer or phone, like clicking a mouse or tapping a screen.
Here is the breakdown of the paper, explained with some everyday analogies:
1. The Current State: The "Toddler" Phase
Right now, these AI agents are like smart toddlers. They can follow simple instructions, but if you ask them to do something complex or if the screen changes slightly (like a pop-up ad appearing), they often get confused, click the wrong thing, or give up.
The authors looked at 87 different research projects and 33 datasets (practice tests) to see what's working and what's broken. They found that while we are moving fast, these agents aren't ready for everyday office work yet.
2. The Three Ways to Look at the Problem
To understand why these robots struggle, the authors created a new "map" (a taxonomy) to organize all the research. They look at the problem from three angles:
- The Playground (Domain): Where is the robot working? Is it on a website (Web), a phone (Android), or a desktop computer?
- Analogy: It's like asking if the robot is learning to drive in a video game, on a real highway, or in a parking lot. The paper notes that most research is on websites and phones, but desktop computers (where most of us actually work) are being ignored.
- The Senses and Limbs (Interaction): How does the robot see and touch the screen?
- The Eyes (Observation): Does it look at a screenshot (like a human seeing the screen) or does it read the code behind the screen (like reading the blueprint of a building)?
- The Big Finding: Reading the code is fast but fragile. If the website changes its code slightly, the robot gets lost. Looking at screenshots is slower but much more robust, just like a human. The paper argues we should train robots to "see" like humans do.
- The Hands (Action): Does the robot click specific buttons by name, or does it move a mouse to exact coordinates?
- The Eyes (Observation): Does it look at a screenshot (like a human seeing the screen) or does it read the code behind the screen (like reading the blueprint of a building)?
- The Brain (Agent): How does the robot think and learn?
- Specialized Brains: These are custom-built for one specific job (like a calculator). They are fast but can't do anything else.
- Foundation Brains: These are the "super-smart" models (like the ones powering ChatGPT) that know a little bit about everything. They are becoming the new standard because they can reason better.
3. The Six Big Hurdles (The "Why We Can't Do It Yet" List)
The authors identified six major reasons why these agents aren't ready for prime time:
- Brittle Vision: Many robots rely on reading the "code" of a website. If the website updates its design, the robot breaks. They need to learn to look at the screen like a human does.
- Inefficient Learning: Teaching these robots is expensive and slow. It's like trying to teach a dog to fetch by throwing a ball 10,000 times. We need better ways to teach them faster.
- Short Attention Spans (Planning): These robots are terrible at long-term planning. They can do step 1, but they forget step 2 by the time they get to step 5. They struggle with complex tasks that require a "game plan."
- Fake Practice Tests: The current tests (benchmarks) are too easy. They use simplified websites that don't look like the messy, real internet. It's like training a pilot in a simulator with no wind or turbulence, then expecting them to fly a real plane in a storm.
- No Standard Scorecard: Everyone is grading their robots differently. One researcher says their robot is "90% good," while another says "80% good," but they are measuring different things. We need a standard test, like the SATs for AI.
- The Lab vs. Reality Gap: In the lab, the computer screen is static and quiet. In the real world, emails pop up, windows overlap, and apps crash. The robots aren't trained for this chaos.
4. The Roadmap: How to Fix It
The authors propose a clear path forward to build a truly useful robot assistant:
- Teach them to "See": Stop relying on code; train them on screenshots so they can handle any screen layout.
- Better Learning: Find cheaper, smarter ways to teach them without needing millions of human examples.
- Long-Horizon Thinking: Give them better "planning" skills so they can handle multi-step tasks without getting lost.
- Real-World Tests: Create harder, messier practice tests that look like real life.
- Standardize the Score: Agree on one main metric: Did the robot finish the whole job? (Success Rate), not just "Did it click the right button?"
- Safety First: Acknowledge that in the real world, robots need to know when to stop and ask a human for help, especially for dangerous actions like deleting files.
The Bottom Line
This paper is a call to action. It says, "We have made amazing progress, but we are still in the 'toy' phase." To get to the point where an AI can truly manage your computer for you, we need to stop building robots that only work in perfect, fake environments and start building ones that can handle the messy, unpredictable reality of our digital lives.
In short: We are building the engine, but we need to teach the car how to drive in traffic, not just on a straight, empty track.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.