← Latest papers
🤖 machine learning

Reflective Prompted Policy Optimization: Trajectory-Grounded Revision and Salience Bias

This paper introduces Reflective Prompted Policy Optimization (R2PO), a two-stage LLM framework that enhances policy search by leveraging detailed trajectory-level evidence rather than scalar rewards to diagnose failures and guide revisions, while specifically addressing the "salience bias" failure mode to achieve faster, more stable, and near-optimal performance across diverse environments.

Original authors: Rahaf Abu Hara, Vaibbhav Murarri, Claudio Zito

Published 2026-05-12
📖 5 min read🧠 Deep dive

Original authors: Rahaf Abu Hara, Vaibbhav Murarri, Claudio Zito

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

The Big Problem: The "Scorecard" vs. The "Story"

Imagine you are teaching a robot to play a video game. In traditional methods, you only get a scorecard at the end of the game.

  • The Scorecard says: "You got 45 points."
  • The Robot thinks: "Okay, I need to do something different to get 46."

But the scorecard doesn't tell you why you lost. Did you fall in a hole on step 3? Did you get stuck in a loop? Did you play perfectly for 19 rounds but crash spectacularly on the 20th? Without the story, the robot has to guess, leading to a lot of trial-and-error.

Recent AI methods tried to fix this by using a "Smart Coach" (a Large Language Model) to look at the score and suggest changes. But even this coach was only looking at the scorecard. It knew the score was low, but it didn't know what the robot actually did wrong.

The Solution: R2PO (The Two-Coach System)

The authors propose R2PO, a new system that uses two AI coaches working together to teach the robot. They treat the robot's actual gameplay footage (the "trajectory") as the most important evidence, not just the final score.

Coach 1: The Scout (Search-LLM)

  • Role: The Scout looks at the history of scores from previous attempts.
  • Action: It says, "Okay, based on the scores, let's try changing the robot's settings slightly in this direction." It proposes a new set of instructions for the robot.
  • Analogy: Think of the Scout as a hiker looking at a map. They guess which direction might lead to the summit based on where they've been before.

The Environment: The Test Run

The robot tries out the Scout's new instructions. It plays the game 20 times (called "rollouts"). This generates a lot of data: where it went, what it did, and how it failed.

Coach 2: The Critic (Critic-LLM)

  • Role: The Critic is the detective. It doesn't just look at the score; it watches the video footage of the robot's 20 attempts.
  • Action: It analyzes the footage to find the specific mistake. "Ah, I see! In 19 of those runs, the robot was great. But in one run, it fell into a hole because it turned left too early."
  • The Fix: Instead of guessing, the Critic suggests a tiny, targeted tweak to the robot's instructions to fix that specific problem.

The Safety Net: The Selection Step

Before the Critic's new instructions are saved, a "Referee" checks them.

  • If the new instructions work better, they are kept.
  • If the new instructions make things worse (even if the Critic thought they were a good idea), the old instructions are kept.
  • Analogy: This is like a chef tasting a new soup. If the new spice makes it taste worse, they throw the new spice away and stick with the original recipe.

The Hidden Trap: "Salience Bias"

The researchers discovered a funny but dangerous habit in the Critic Coach. They call it Salience Bias.

Imagine the robot plays 20 games.

  • 19 games: It wins easily.
  • 1 game: It crashes into a wall in a very dramatic, messy way.

If you show the Critic Coach all 20 videos, the Coach gets obsessed with that one dramatic crash. It thinks, "Oh no! The robot is terrible at avoiding walls!" and it changes the robot's brain to fix the crash.

The Result: The robot was actually doing great in the other 19 games. By trying to fix the one weird crash, the Critic accidentally breaks the robot's ability to play the other 19 games. The robot gets worse.

How R2PO Fixes This:
The R2PO system is smart about which video it shows the Critic.

  1. The Median Video: Instead of showing the worst crash or the best win, it shows the "middle" video—the one that represents what the robot usually does.
  2. The Stats Sheet: It gives the Critic a summary sheet: "95% of the time, the robot wins. The crash was a 5% fluke."
  3. The "Don't Touch" Rule: If the robot is already doing really well (high score), the Critic is told: "Don't change anything unless you have a very, very good reason."

This stops the Critic from panicking over a single bad day and ruining a good strategy.

The Results: Faster, Smarter, and More Stable

The paper tested this system on 10 different environments (like balancing a pole, playing Pong, or navigating a maze).

  • Speed: R2PO learned much faster. For example, on the "CartPole" game (balancing a stick), it reached near-perfect scores in about 500 tries, while other methods needed 4,000 tries.
  • Stability: Other methods would find a great solution, then accidentally break it in the next step. R2PO found the solution and stayed there.
  • Efficiency: They used a relatively small, open-source AI model (20 billion parameters) to beat methods that used much larger, expensive, or proprietary models.

Summary

The paper argues that to teach AI effectively, you shouldn't just give it a score. You should show it the story of what happened. However, you have to be careful not to let the AI obsess over the one time it failed (Salience Bias). By showing the AI the "average" story and giving it a safety net, you can teach it to learn faster, fix specific problems, and avoid breaking what already works.

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 →