LIBERO-PeRM is a robot manipulation benchmark that asks a simple question: can a policy do the task the way you want it done? Released on arXiv on October 15, 2026 (paper, project page) and listed as a NeurIPS 2026 Evaluations and Datasets Track paper, it separates two things most robot benchmarks blend together: finishing the task and respecting a user's preference. The short answer from its first round of experiments, as of October 2026, is that today's vision-language-action (VLA) models usually finish the task and ignore the preference unless they are fine-tuned for it.

What LIBERO-PeRM measures

Picture a household robot asked to put a mug on a shelf. One person wants it moved slowly. Another wants the arm to stay clear of a knife on the counter. A third always wants the red mug used first. The goal is identical, but the acceptable execution is not. The authors call this personalized robotic manipulation (PeRM) and argue it is essential if general-purpose robots are going to be practical at home. Their point is that the field lacked a controlled benchmark that could tell task completion and preference satisfaction apart.

The benchmark was built by ten researchers from UC Riverside, Yale, Georgia Tech, the University of Michigan and the University of Toronto. Code, datasets and demos are public.

A preference changes the how, not the what

In LIBERO-PeRM, a preference is not a second goal. It is a conditioning signal that biases execution while the task goal stays fixed. The scope is deliberately narrow: preferences must be expressible in language, instantiable in LIBERO without changing the goal, scored automatically and reusable across tasks. The policy receives one prompt in the form "Task: … Preference: …" plus images from a third-person camera and a wrist camera.

Three preference levels

All three levels map to the same four-step label (0, 1/4, 3/4, 1), so results are comparable. User-profile preferences are the hardest because they change which object is the target, for example by adding a red twin of an item and phrasing the task so that one sentence covers both behaviors.

How it differs from the original LIBERO robot manipulation benchmark

The original LIBERO, released in 2023, targets lifelong robot learning: four task suites with 130 tasks and human-teleoperated demonstrations, used to study how knowledge transfers as a robot learns new tasks over time. LIBERO-PeRM reuses its simulator and layouts but changes the question.

How the data is generated

1. 1

   Minimal layout edits

   A vision-language model makes the smallest scene change needed for a preference to be acted on. Motion and skill preferences leave layout and task language untouched.

2. 2

   Paired plans and trajectories

   The VLM writes a plan without the preference and a plan with it. A skill library, each skill built from one human demo plus a motion planner, turns both into trajectories. The project page says more than 72% of skills needed no per-task offset tuning.

3. 3

   Explicit metrics

   Each preference gets its own scoring rule, so evaluation runs without a human judge.

The five suites and how to read SR and SA

• LIBERO-SinglePref (100 tasks): learning and executing one preference at a time.
• LIBERO-PrefScale (100 tasks): how learning scales with more demonstrations, tasks and layouts.
• LIBERO-PrefConflict (48 tasks): two preferences that cannot both hold, or a preference that argues against the task.
• LIBERO-PrefCompose (64 tasks): no preference, preference A, preference B and A + B on matched layouts.
• LIBERO-ComprePref: no new tasks; it rewrites prompts from the other suites, including implicit cues that suggest a preference without naming it.

Key results: task done, preference ignored

All figures below come from the project page and describe simulated evaluation.

Training trade-offs

Training on LIBERO first and preferences second dropped no-preference success to 52.3%. Mixing both in one run kept it at 91.0% and held up better on rewritten prompts (72.8 / 70.1 on ComprePref versus 44.0 / 42.6 for preference-only training). The cost showed up on motion preferences, where success fell from 90.0% to 66.9%, so mixing is not a free win. At a fixed budget of 2.25K demonstrations, spreading them across more layouts helped more than adding demonstrations per layout.

Composition, decomposition and conflict

• Trained on A and B separately, the policy combined A + B with 25.0% SR and SA.
• Asked to recover B alone after training on A + B and A, it reached 37.5% SR but 0.0% SA.
• With two conflicting preferences, SR / SA fell from 73.0 / 63.4 to 66.0 / 47.8, and neither preference clearly won.
• When the preference argued against the task, the robot followed the task 33.3% of the time, the preference 29.2%, and neither 37.5%.

Limits to keep in mind

It would be a stretch to read this as proof that robots cannot personalize. Everything runs in simulation, without real lighting, clutter or sensor noise. Only language-expressible, auto-scorable preferences are covered, so subjective requests like "make it look tidy" are out of scope. Fine-tuning results come from a single base model, π0.5. And the paper is a v1 preprint as of October 2026, so cite the version if you quote numbers, because they may change in later revisions.

Robotics papers often get amplified into bigger claims as they spread. If you want to see how a topic like this is being discussed, theddari's AI Telegram channel tracker and blog trends page show where the conversation is happening.

Page Reference

Trendstheddari.com›TrendsTelegram · AILive posts from AI channels

Page Reference

Trendstheddari.com›TrendsBlog PostsSummarized Naver blog posts

Checklist for reading personalized robotics research

1. Look for task success and preference satisfaction reported separately; a high success rate alone says nothing about doing it your way.
2. Check whether a number is zero-shot or after fine-tuning.
3. Look for results on unseen layouts and tasks, not just in-domain scores.
4. Confirm whether the setup is simulated or on real hardware, and note the paper version and date.