← Latest papers
💻 computer science

HATS: Hardness-Aware Trajectory Synthesis for GUI Agents

This paper introduces HATS, a Hardness-Aware Trajectory Synthesis framework that improves GUI agent generalization by identifying and prioritizing semantically ambiguous actions through a closed-loop process of hardness-driven exploration and alignment-guided refinement.

Original authors: Rui Shao, Ruize Gao, Bin Xie, Yixing Li, Kaiwen Zhou, Shuai Wang, Weili Guan, Gongwei Chen

Published 2026-03-13
📖 5 min read🧠 Deep dive

Original authors: Rui Shao, Ruize Gao, Bin Xie, Yixing Li, Kaiwen Zhou, Shuai Wang, Weili Guan, Gongwei Chen

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 trying to teach a robot how to use your smartphone or a website. You want the robot to be able to book a flight, send a text, or buy groceries just by listening to your voice commands.

To teach this robot, you need to show it thousands of examples of "doing things." This is called training data. In the past, researchers tried to generate these examples automatically, but they hit a major wall: the robot became very good at simple tasks (like opening a menu) but terrible at anything tricky.

The paper "HATS" (Hardness-Aware Trajectory Synthesis) introduces a new way to teach these robots. Here is the simple breakdown using some everyday analogies.

The Problem: The "Easy Mode" Trap

Imagine you are teaching a child to cook.

  • Old Method: You tell the child to "make dinner." They start by doing the easiest things: opening the fridge, turning on the stove, and stirring an empty pot. They do this 1,000 times.
  • The Result: The child thinks they are a master chef because they know how to open the fridge. But if you ask them to actually chop an onion or season a steak (the tricky parts), they fail because they never practiced those hard steps.

In the world of AI, existing methods were like this. They generated millions of "easy" instructions (e.g., "tap the back button") but ignored the hard, confusing parts of using an app. These hard parts are things like:

  • Two buttons that look exactly the same but do different things depending on what page you are on.
  • A task that only works if you do Step A, then Step B, then Step C in the exact right order.

The Solution: HATS (The "Smart Coach")

The authors created HATS, which stands for Hardness-Aware Trajectory Synthesis. Think of HATS as a Smart Coach who doesn't just let the student practice whatever they want. Instead, the Coach actively looks for the things the student is bad at and forces them to practice those specific skills.

HATS works in a loop with two main parts:

1. The "Hardness Detector" (Exploration)

Instead of wandering around randomly, HATS asks: "Where is the robot getting confused?"

  • The Metaphor: Imagine a video game player who keeps dying at the same boss level. A normal player might just keep playing the easy levels to get high scores. HATS is like a coach who says, "Stop! You keep failing at this specific boss. Let's go back and practice that specific fight until you get it right."
  • How it works: The system looks for "Semantic Ambiguity." This is a fancy way of saying "confusing situations." If the robot sees a button and doesn't know what it does, HATS marks that spot as "Hard" and makes sure the robot visits it again and again to learn the nuance.

2. The "Reality Check" (Refinement)

Once the robot tries to do a hard task, HATS doesn't just accept the attempt. It plays a game of "Spot the Difference."

  • The Metaphor: Imagine you give a recipe to a chef. The chef tries to cook it, but they burn the toast because you didn't say "watch the heat."
    • Old Method: The system would just write down, "Chef made toast," and move on.
    • HATS Method: The system watches the chef. It sees the toast is burnt. It says, "Wait, the recipe was vague. Let's rewrite the recipe to say 'Watch the heat carefully.' Now, try again."
  • How it works: HATS generates an instruction, lets the robot try it, and then checks: "Did the robot actually do what the instruction said?" If the robot failed because the instruction was unclear, HATS fixes the instruction and tries again. It keeps looping until the instruction is perfect and the robot succeeds.

The Magic Loop

The genius of HATS is that these two parts talk to each other in a circle:

  1. The Coach finds a hard spot (Exploration).
  2. The Reality Check tries to solve it and fixes the instructions (Refinement).
  3. If the Reality Check fails, it tells the Coach: "That was really hard! Let's mark that as a high-priority training spot for next time."
  4. The Coach then goes back to find even more tricky spots based on that feedback.

Why Does This Matter?

The results are impressive. When they tested this new method:

  • On Android apps, the new AI was 100% better at solving tasks than the previous best method.
  • On Websites, it was 215% better.

Summary

Think of HATS as a teacher who refuses to let a student skip the hard math problems. Instead of letting the student solve easy addition problems 1,000 times to feel smart, the teacher identifies the confusing algebra problems, rewrites the explanations until they make sense, and forces the student to master them.

By focusing on the hard, confusing, and ambiguous parts of using technology, HATS creates a robot that doesn't just know how to tap a screen—it actually understands how to get things done in the real world.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →