Proactive Agent Research Environment: Simulating Active Users to Evaluate Proactive Assistants
This paper introduces Proactive Agent Research Environment (Pare), a framework that models applications as finite state machines to enable realistic active user simulation, along with Pare-Bench, a comprehensive benchmark of 143 tasks designed to evaluate proactive agents' abilities in context observation, goal inference, timing, and multi-app orchestration.
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 digital assistant that doesn't just wait for you to ask, "Hey, can you buy milk?" but actually notices you're out of milk, sees a text from your roommate saying they need soap, and quietly adds both to your shopping list before you even think about it. That is the dream of a Proactive Agent.
But here's the problem: How do you test if these assistants are actually good at guessing what you need without annoying you or making mistakes? You can't just ask a real human to pretend to be a user for hours; they get tired, they get bored, and they aren't consistent.
This paper introduces Pare (Proactive Agent Research Environment), a new "playground" for testing these smart assistants. Here is the breakdown in simple terms:
1. The Core Problem: The "Flat" vs. "Labyrinth" Gap
Think of most current AI testing like a video game cheat code.
- The Old Way: The AI (the assistant) has a "God Mode" cheat. It can instantly teleport to any menu, click any button, and change any setting with a single command. It doesn't have to "walk" through the app.
- The Real World: You, the human, have to actually open the app, scroll through the menu, tap the right button, type in the password, and navigate the screens.
The paper argues that if you test an AI that has "God Mode" against a human who has to navigate a labyrinth, you aren't testing the AI's ability to be helpful; you're just testing if it can read a manual. The AI needs to understand that you have to walk through the maze, even if the AI can fly.
2. The Solution: The "Pare" Playground
The authors built Pare, a simulation environment that fixes this gap using two main ideas:
A. The "Stateful" Maze (Finite State Machines)
Imagine a video game where you can't just jump to the boss level. You have to walk through the castle, open the door, go up the stairs, and unlock the chest.
- In Pare, the apps (like Email, Calendar, or Shopping) are built like these mazes.
- The Simulated User is a robot programmed to act like a real human. It must open the app, find the search bar, type the name, and click "send." It cannot just whisper "send message" to the universe.
- This forces the AI to watch the user navigate the maze and understand where the user is stuck or what they are trying to do.
B. The "Asymmetric" View (The Spy vs. The Tourist)
This is the most clever part. The paper creates an unfair (but realistic) information gap:
- The User (Tourist): Can only see what's on their screen. If a new email arrives, they get a tiny notification: "New message from Mom: Hey..." (truncated). They have to open the app to read the rest.
- The Assistant (Spy): Can see everything. It sees the full email, the full calendar, and the full shopping list instantly.
Why does this matter?
A good proactive assistant shouldn't just shout, "I see your email!" (because the user doesn't know that yet). It needs to wait until the user looks at the notification, realizes they might need to act, and then gently suggest, "Hey, I saw Mom's email about the party. Want me to add it to your calendar?"
3. The "Observe-Then-Execute" Dance
The paper introduces a specific way for the AI to behave, like a dance with two steps:
- Observe Mode: The AI watches the user. It's like a butler standing in the corner, watching you look at your phone. It gathers clues but doesn't touch anything yet.
- Propose: If the AI thinks it knows what you want, it asks: "I noticed you're looking at flight prices. Should I book the ticket?"
- Execute Mode: Only if you say "Yes," the AI jumps into action and does the work.
This prevents the AI from being a "pushy" robot that does things without permission.
4. The "Pare-Bench" Test
The authors created a massive test called Pare-Bench with 143 different scenarios.
- The Test: They simulated 143 different days in a user's life (shopping, scheduling, texting).
- The Goal: They tested 7 different AI models (like GPT-5, Claude, Gemini) to see which one could best guess the user's needs without being annoying.
The Results:
- Even the smartest AI models only got about 42% of the tasks right.
- The biggest failure wasn't guessing the goal; it was execution. The AI would guess correctly ("You need to buy milk") but then fail to actually navigate the shopping app to buy it.
- Smaller AI models were even worse, often getting confused by the "maze" of the app.
5. Why This Matters
This paper is a wake-up call. It says, "Stop testing AI assistants in a vacuum where they have superpowers."
- Privacy: By simulating users this way, we can test AI without needing real people to upload their private data to the cloud.
- Realism: It forces AI to learn how to be helpful in a world where humans have to click buttons and scroll screens, not just whisper commands.
- Trust: It ensures that future assistants ask for permission before acting, keeping humans in control.
In a nutshell:
The authors built a realistic video game where a "smart butler" AI tries to help a "human-like robot" navigate a digital world. They found that even the best butlers are still clumsy, often guessing the right thing but failing to actually do the job. This new playground helps us teach them how to be better, more respectful, and more useful helpers.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.