Introduction to RPent#

RPent (Recursive Physical Agent) is a framework for embodied agents. A language model selects tools from task instructions and visual observations, then controls the robot through action models or scripted motions. Results return to the planner to inform its next action.

RPent planning, perception, memory, and execution architecture

How a Task Runs#

  1. The planner reads the task, observations, and available task experience.

  2. It locates targets with visual tools and selects a VLA or scripted action.

  3. The environment executes the action and returns state and camera views.

  4. The planner continues, adjusts its strategy, or finishes.

Exploration supports repeated attempts and local memory generation. Evaluation reads existing memory and uses the environment’s success criterion. See Architecture and Execution for implementation details.

Leaderboard#

Compare success rates on LIBERO, LIBERO-PRO, RoboCasa365 Target50, and RoboTwin C2R. Rankings apply to the methods and evaluation coverage shown; see RPent Leaderboard for detailed results, configurations, and sources.

RPent Leaderboard RPent Leaderboard

Choose a Platform#

Platform

Documentation

LIBERO

Pi0.5, SAM3, and LIBERO / LIBERO-PRO runs and reproduction.

RoboCasa365

RLDX-1, kitchen tasks, and Target50 reproduction.

RoboTwin

LingBot-VLA, dual-arm simulation tasks, and C2R reproduction.

Single-Arm Franka

Hardware preparation, calibration, motion checks, and operation.

Dual-Arm Franka

Two-node deployment, operation, and exploration with an operator.

YAM

Task demo available; installation and usage documentation is coming soon.

SO-101

Coming soon.

Choose api, claude_code, or codex for online planning. LIBERO also supports Flash Mode for executing stored plans. See Planners and Model Services for model-service configuration.

Start with Quick Start. See RPent Leaderboard for reported results and resource costs, and Harness VLA for the research background.

DreamZero, Cosmos Policy, and RoboDojo are also listed in the project roadmap; their usage documentation is pending.