TL;DR
We introduce uni-robot-agent, a unified and modular harness for robot use without privileged inputs. Designed for generalizable agentic training. It unifies interaction records across environments and supports efficient experience collection for open models.
On RoboDojo1, Qwen3.8-Flash-Next2 reaches 31.39 Score and 25.00% success rate; GPT-6 Astra3 reaches 51.90 Score. On physical robots, Qwen achieves a zero-shot Score of 53.50, compared with 47.75 for fine-tuned π₀.₅4. With Astra, the harness reaches 80.50 zero-shot. These results support a reusable foundation for effective robot use with open models.
Models call shared tools; environment adapters execute actions and return evidence for the next decision.
RoboDojo
Simulation · direct control · Score (0–100)
1. Introduction
Frontier models such as GPT-6 Astra have shown surprising zero-shot robot manipulation capabilities, as demonstrated by RoboProbe. These robot-use agents bring general problem-solving abilities—task decomposition, planning, and failure recovery—to physical interaction. Such abilities are valuable for robotics, yet difficult to learn from limited robot data alone.
But proprietary models constrain how researchers can develop this approach. Without access to their weights, we cannot directly train them to become better robot-use agents. API dependence also makes large-scale interaction costly and limits model-level optimizations, such as efficient caching, even though inference speed is a major bottleneck.
Open-weight models offer a path forward, but often fall short in spatial understanding and agentic capabilities. One response is to supply simulator ground truth, oracle success feedback, or task-specific skills. Before attributing failures to the models themselves, however, we need to establish what they can already do with an effective, generalizable harness. That gives us a stronger foundation for deciding how future robot-specific training should improve them.
We built uni-robot-agent to provide that foundation: competitive robot use with open models today, and infrastructure for future training. Unified tool interfaces and feedback formats span models, robots, tasks, and environments, making simulation and real-world experience easier to combine for training. Efficiency makes large-scale interaction more practical; modularity lets researchers change models, tools, and robot backends as their methods evolve.
Our central finding is that well-structured information and reliable tools with informative feedback can be enough for effective robot use. With camera calibration and robot descriptions, Qwen3.8-Flash-Next reaches 31.39 Score on RoboDojo without privileged inputs, surpassing the published Astra–RoboProbe result of 28.97. Across 19 physical-robot tasks, Qwen reaches 53.50, outperforming zero-shot Dream-1 (43.50) and performing comparably to fine-tuned π₀.₅ (47.75). In this real-world comparison, our agents use sensor depth; the two baselines use RGB only.
With this foundation in place, we ask what makes robot use work. Comparisons across model generations, families, and sizes reveal four recurring bottlenecks: visual understanding, spatial grounding, geometric coding, and embodied reasoning. These point to complementary targets for future training. We then examine the effects of privileged information and skills, followed by the cost and speed of interaction.
2. A Unified and Modular Harness
2.1 Modular Architecture
A tool call passes through five layers. The agent layer manages model interaction and context; orchestration schedules and dispatches requests. Shared operations in the tool layer access environment, perception, and action-model capabilities through services, which manage runtime resources. Concrete simulator, robot, and model implementations sit in the backend layer. Results return through these interfaces to the agent, completing the loop.
System architecture
2.2 Unified Interaction Interface
Shared motion, perception, skill, and episode tools use common arguments, units, and feedback. Environment descriptions identify available arms, cameras, and optional capabilities; adapters translate shared operations into native control. Adding an environment requires an adapter rather than reimplementing every tool, and the common interaction format lets us combine experience for subsequent training.
A shared interface is also a foundation for agentic training. AgentGym8 collects trajectories across diverse environments in a common interaction format and uses filtered demonstrations for supervised fine-tuning. Agent Lightning9 addresses a complementary layer: structured invocation records separate execution from training, with LLM inputs, outputs, and rewards extracted for policy optimization.
For robot-use agents, this motivates preserving the link between observations, tool calls, and feedback while keeping operation semantics consistent across environments. Such records make experience easier to combine and prepare for training open models. Data selection, learning objectives, and reward design remain separate questions; training on the collected experience is future work.
Why does a unified tool interface enable generalizable agentic training?
From an LLM’s perspective, search and coding tasks across different environments can be learned through the same set of tools. This shared interface can more effectively promote cross-environment generalization.
Stack the red block on the blue block.
- Locate both blocks
- Grasp & align
- Stack & release
Pass an object from the left arm to the right.
- Present the object
- Secure second grasp
- Transfer & release
Insert a peg while stabilizing the socket.
- Stabilize socket
- Align the peg
- Insert & verify
One tool interface across environments and embodiments.
2.3 Efficient Execution
Waiting for every robot movement to finish also holds up reasoning that could proceed independently. A background tool call returns a job handle—a reference the agent can use to retrieve its result later—so the agent can continue reasoning while the tool runs. An immediate call waits for completion. Decisions that need a result still wait.
Tool execution follows resource constraints. Calls controlling the same robot arm enter a queue and run in submission order: a second movement waits for the first to finish, even as the agent prepares later steps. Independent operations, such as reading an existing snapshot, can overlap movement. This forms a two-stage pipeline between reasoning and execution. If new feedback changes the plan, flush_queue cancels calls that have not yet started for the specified resource, allowing the agent to submit revised actions.
Agent–tool pipelining
2.4 Interaction Without Privileged Inputs
Depth measurements can vary or be missing even in a static physical scene, and simulator task-verifier feedback is unavailable on real robots. We therefore test whether agents can infer spatial relationships and assess progress from more limited observations.
Our main simulation setting provides RGB images, camera calibration, robot proprioception and descriptions, and task instructions. It excludes depth measurements, supplied object CAD assets, hidden scene annotations, task-verifier feedback, and external web access. These restrictions also apply to tool computations: localization must derive coordinates from permitted observations, such as through multi-view triangulation. Tools return measured robot poses and execution outcomes; task-verifier results are used only for evaluation.
Task instructions. Within these input constraints, agents still need a clear task specification. Some RoboDojo instructions omit or ambiguously describe task requirements. We add brief clarifications: each red button’s prescribed press count must be confirmed with the blue button, and tower building requires a specified arrangement of blocks and boards. These additions clarify task rules without providing scoring rubrics or verifier logic. We also manually check that models do not access prohibited information.
2.5 Key Design Choices
Physical interaction can leave the agent with stale images, uncertain action status, or incomplete evidence of success. These six choices keep its next decision tied to what was observed and what actually ran.
Physical consistency
Keep observations and execution records tied to the physical state.
Use the same snapshot
If the robot moves after an image is captured, a newer camera pose can misinterpret the selected pixel. We bind images, calibration, and robot state to one immutable snapshot, so localization uses the state that produced the image.
Check before repeating
A missing reply may hide an action that already ran. Request identities and execution records reject duplicates. When completion is uncertain, further actions are blocked while the session recovers the record; unresolved requests stay explicitly uncertain.
Action precision
Coordinate control and respond to measured progress.
Move and grip together
Separate movement and gripper commands cannot adjust the opening during a movement. The move tool accepts a target pose and an optional gripper opening together, allowing the arm and gripper to act simultaneously.
Stop based on progress
A fixed step count can stop too early or waste motion on an unreachable target. The tool generates intermediate targets from measured poses and checks progress after each step, stopping on arrival or returning control when motion stalls or reaches an execution limit.
Context management
Interpret outcomes and retain the evidence needed for the next decision.
Inspect action outcomes
Reaching a pose does not prove that an object was grasped. Pose errors and stopping reasons distinguish small residual errors from rejected or stalled motion; outcome images reveal the effect on the object. Together, they guide motion refinement or a change of strategy.
Keep useful context
Old images become text placeholders in batches, preserving recent views and a stable prompt prefix for cache reuse. If more space is needed, we remove older complete interactions, keeping calls paired with results and protecting essential instructions and pending calls.
3. Evaluation
3.1 Simulation Evaluation on RoboDojo
Benchmark and protocol. We use RoboDojo to test open-weight models and compare harnesses across 42 tasks in five dimensions: generalization, precision, long-horizon execution, memory, and open-vocabulary instruction following. Our main configurations use three seeds and two layouts per seed, giving 252 episodes each. The 12 generalization tasks pair standard and randomized layouts. Score credits partial progress; success rate (SR) counts fully successful episodes. We average within each task, then within each dimension, and weight the five dimensions equally. Each episode has a three-hour wall-clock limit: in four-hour runs, aggregate performance largely plateaued by the third hour.
Baselines. With Qwen3.8-Flash-Next as the planner, we compare against GAP (Hybrid)10, which incorporates π0.5, plus RoboProbe and RPent11 in their default configurations. Published Astra–RoboProbe results and VLA / WAM entries from the RoboDojo leaderboard provide broader context.
Results. Qwen with uni-robot-agent reaches 31.39 Score / 25.00% SR, compared with 21.01 / 16.11% for GAP (Hybrid), the strongest Qwen baseline. DeepSeek reaches 27.11 / 21.39%, extending the result to another open-weight model; Astra reaches 51.90 / 46.67%.
Different capability profiles. Qwen and DeepSeek perform better on memory and open-vocabulary tasks than on precision and long-horizon execution. Conversely, Xiaomi-Robotics-112 and OpenWAM-α13 score 38.39 and 34.93 on long-horizon tasks, but 7.81 and 10.41 on memory. These configurations have complementary strengths; precise manipulation and long-horizon planning remain challenges for current foundation models.
| Model | Harness | Gen. | Prec. | Long- | Mem. | Open | Avg.↑ |
|---|---|---|---|---|---|---|---|
VLA & WAM | |||||||
| π0.5 | – | 8.17/13.38 | 5.50/12.40 | 14.67/23.54 | 4.67/5.89 | 1.67/1.98 | 6.93/11.44 |
| Hy-Embodied-0.5-VLA14 | – | 8.39/11.78 | 8.00/13.81 | 14.92/25.74 | 12.11/13.37 | 0.58/0.65 | 8.80/13.07 |
| OpenWAM-α | – | 14.83/20.71 | 9.25/18.45 | 25.33/34.93 | 9.11/10.41 | 1.08/1.41 | 11.92/17.18 |
| Xiaomi-Robotics-1 | – | 17.00/23.54 | 18.83/26.69 | 23.67/38.39 | 6.56/7.81 | 3.58/3.94 | 13.93/20.07 |
Agent | |||||||
| GPT-6 Astra | RoboProbe | 30.50/33.36 | 4.00/12.65 | 8.25/21.45 | 38.67/43.04 | 31.00/34.36 | 22.48/28.97 |
| GPT-6 Astra | uni-robot-agent | 31.94/37.15 | 20.83/28.75 | 39.58/50.31 | 80.56/80.56 | 60.42/62.71 | 46.67/51.90 |
| GPT-6 Astra | uni-robot-agent + depth | 43.06/47.85 | 29.17/36.04 | 52.08/60.31 | 75.00/75.42 | 62.50/64.17 | 52.36/56.76 |
| Qwen3.8-Flash-Next | RoboProbe | 0.00/0.35 | 0.00/0.83 | 0.00/3.75 | 0.00/0.00 | 4.17/4.58 | 0.83/1.90 |
| Qwen3.8-Flash-Next | RPent | 5.56/9.24 | 4.17/8.02 | 4.17/12.40 | 5.56/5.56 | 2.08/3.54 | 4.31/7.75 |
| Qwen3.8-Flash-Next | GAP (Hybrid)† | 13.89/19.31 | 8.33/16.46 | 18.75/28.85 | 16.67/16.67 | 22.92/23.75 | 16.11/21.01 |
| DeepSeek-V4.1-Flash | uni-robot-agent | 16.67/20.35 | 6.25/16.25 | 4.17/14.79 | 36.11/38.33 | 43.75/45.83 | 21.39/27.11 |
| DeepSeek-V4.1-Flash | uni-robot-agent + depth | 18.06/21.88 | 12.50/19.79 | 10.42/25.31 | 41.67/45.56 | 37.50/38.54 | 24.03/30.22 |
| Qwen3.8-Flash-Next | uni-robot-agent | 18.06/21.60 | 2.08/10.21 | 6.25/23.75 | 52.78/54.72 | 45.83/46.67 | 25.00/31.39 |
| Qwen3.8-Flash-Next | uni-robot-agent + depth | 22.22/25.28 | 18.75/26.35 | 14.58/29.69 | 52.78/56.25 | 39.58/41.88 | 29.58/35.89 |
How stable are the scores?Rollout-count sensitivity
We examine sampling variability in a separate depth-enabled Qwen3.8-Flash-Next evaluation: 50 rollouts for each of 54 task variants, or 2,700 episodes. The variants include standard and randomized versions of the 12 generalization tasks, plus the other 30 tasks. The full-pool Score is 34.59.
With six rollouts per variant, the mean sampled Score is 34.59, with a central 95% range of 30.65–38.51. Taking the first six recorded rollouts, ordered by pass and layout identifiers, instead gives 36.55—an upward difference of 1.96 points. A small sample can recover the aggregate Score on average while individual subsets still vary by several points.
How to read this check. At each sample size, episodes are sampled independently without replacement within each variant, with the five capability dimensions weighted equally. Six rollouts per variant here gives 324 episodes. This is a separate depth-enabled pool, not the main no-depth, three-seed/two-layout evaluation. The band describes variation within the observed pool, not a confidence interval for the main Score of 31.39 or a bias correction to it; it collapses at 50 by construction. Read the sampling values.
3.2 Real-World Evaluation on Real-World Benchmark
Benchmark and protocol. Real Eval tests tabletop manipulation on a physical dual-arm robot through 19 evaluation entries. Five dimensions—spatial understanding, object generalization, instruction following, compositional generalization, and unseen tasks—contribute 20 points each. Task-specific criteria award credit for completed objectives and, where specified, intermediate progress such as grasping before placement.
Insert test tubes into rack


Tube / rack alignment
Move the test tubes to the other rack.
Bimanual bottle handover


New container geometry
Place the mug on the wooden block.
Pick and place (assorted objects)


Object and destination
Put the toy car into the basket.
Stack upward-facing cups


Upright cup configuration
Stack the upward-facing paper cups together.
Tower of Hanoi


Ring / peg alignment
Move the disks to build a three-layer Tower of Hanoi.
One representative task per dimension, from the paper. The outlined region is enlarged alongside each scene; photographs illustrate task setups, not complete trial outcomes.
Baselines. We evaluate uni-robot-agent zero-shot with Astra and Qwen, alongside π0.5 fine-tuned on demonstrations from the same platform and Dream-1 evaluated zero-shot through its public API. Our agents additionally use depth from Intel RealSense D405 cameras, while π0.5 and Dream-1 use RGB only. The five dimensions describe variation relative to the π0.5 training catalogue; our agents receive no task-specific training on these entries.
Results. Astra reaches 80.50 / 100 and Qwen 53.50, compared with 47.75 for fine-tuned π0.5 and 43.50 for Dream-1. These results extend the simulation findings to physical robots with both frontier and open-weight models. Astra scores 20 / 20 on compositional generalization, while unseen tasks remain difficult: both agents score 8 / 20.
| VLA | WAM | uni-robot-agent | ||
|---|---|---|---|---|
| Capability | π₀.₅ | Dream-1 | Astra | Qwen |
| Spatial understanding | 11.25 | 6.50 | 17.00 | 9.00 |
| Object generalization | 12.50 | 13.50 | 17.50 | 10.00 |
| Instruction following | 14.00 | 9.50 | 18.00 | 13.50 |
| Compositional generalization | 6.00 | 10.00 | 20.00 | 13.00 |
| Unseen tasks | 4.00 | 4.00 | 8.00 | 8.00 |
| Total | 47.75 | 43.50 | 80.50 | 53.50 |
Per-task scores · 19 evaluation entries
| ID | Task | Max | π₀.₅ | Dream-1 | Astra | Qwen |
|---|---|---|---|---|---|---|
| 1 | Pick and place (fruits) | 5 | 2 | 3 | 5 | 3 |
| 2 | Fold rag | 3 | 1.75 | 1.5 | 3 | 1 |
| 3 | Bimanual plate pull-out | 4 | 3 | 0 | 2 | 1 |
| 4 | Insert test tubes into rack | 4 | 2 | 1 | 3 | 2 |
| 5 | Hang mug | 4 | 2.5 | 1 | 4 | 2 |
| 6 | Bimanual bottle handover | 10 | 2.5 | 5.5 | 10 | 4 |
| 7 | Stack bowls (new objects) | 10 | 10 | 8 | 7.5 | 6 |
| 8 | Stack cups (color order) | 10 | 6 | 1 | 8 | 5 |
| 9 | Pick and place (assorted objects) | 6.5 | 6 | 6.5 | 6.5 | 6.5 |
| 10 | Stack bowls (given direction) | 3.5 | 2 | 2 | 3.5 | 2 |
| 11 | Pull out tissue and discard | 4 | 0 | 4 | 4 | 1 |
| 12 | Stack upward-facing cups | 4 | 4 | 0 | 4 | 0 |
| 13 | Wipe whiteboard | 4 | 2 | 4 | 4 | 4 |
| 14 | Arrange cubes (color order) | 8 | 0 | 2 | 8 | 8 |
| 15 | Close microwave door | 4 | 4 | 4 | 4 | 4 |
| 16 | Take bowl from microwave | 4 | 0 | 0 | 0 | 0 |
| 17 | Unfold rag | 4 | 0 | 0 | 0 | 0 |
| 18 | Stack books | 4 | 0 | 0 | 2 | 4 |
| 19 | Tower of Hanoi | 4 | 0 | 0 | 2 | 0 |
| Total | 100 | 47.75 | 43.50 | 80.50 | 53.50 |
4. What Capabilities Enable Robot-Use Agents?
The evaluation shows that open models can use robots with the harness. To guide future training, we next ask which capabilities make this possible and where they fall short. We compare generations, families, and model sizes, then connect their failure modes to general-purpose benchmarks.
Performance Across Generations, Families, and Sizes
We evaluate additional models on RoboDojo’s 42 tasks and reuse the main 252-episode results for Qwen3.8-Flash-Next, DeepSeek-V4.1-Flash, and GPT-6 Astra. Most additional models use one seed and one layout per task; Qwen3.8-27B uses three layouts. SR and Score equally weight the five capability dimensions. These are exploratory comparisons, without a claim of statistical significance.
Robot use across thirteen models
SR & ScoreRead the data
† GLM Score is set to zero in the manuscript; native-score records are unavailable. Its evaluation includes depth.
| Model | Episodes | SR (%) | Score |
|---|---|---|---|
| Qwen3.5 Flash | 42 | 0.00 | 0.00 |
| Qwen3.5-122B-A10B | 42 | 0.00 | 0.00 |
| Qwen3.6 Flash | 42 | 0.00 | 0.00 |
| Qwen3.6 Plus | 42 | 0.00 | 0.38 |
| Qwen3.7 Flash | 42 | 0.00 | 0.00 |
| Qwen3.7 Plus | 42 | 0.00 | 0.00 |
| Qwen3.8-27B | 126 | 8.06 | 9.61 |
| Qwen3.8 Flash | 252 | 25.00 | 31.39 |
| DeepSeek-V4.1-Flash | 252 | 21.39 | 27.11 |
| GLM-5.3-Flash (+ depth) | 42 | 0.00 | 0.00 † |
| GPT-5.6 Sol | 42 | 19.17 | 24.04 |
| GPT-6.1 Sol | 42 | 37.50 | 45.63 |
| GPT-6 Astra | 252 | 46.67 | 51.90 |
Robot use predates the latest generation. GPT-5.6 Sol reaches 19.17% SR / 24.04 Score; GPT-6.1 Sol improves to 37.50% / 45.63. The latest generation improves performance substantially, but the ability was already present in earlier GPT models.
The pattern differs across families. Qwen3.5–3.7 Flash, Qwen3.6–3.7 Plus, and Qwen3.5-122B record zero SR. Qwen3.8-27B and Flash-Next reach 8.06% and 25.00%, respectively. Yet a recent generation alone is not sufficient: GLM-5.3 Flash also records zero SR.
Larger is not always more capable. Within Qwen3.8, Flash-Next (125B) outperforms 27B. Across generations, however, 27B completes tasks while earlier 122B and >150B models do not. This motivates the paper’s hypothesis that changes in training distribution matter beyond parameter count.
Four Major Failure Modes
Trajectory inspection reveals four recurring difficulties: interpreting the scene, locating corresponding features across views, computing poses correctly, and choosing physically appropriate interactions. The analysis spans thirteen models, with available measurements shown for each failure type.
Where robot interactions break down
Trajectory analysisRead the data
| Model | Failure type | Errors / reviewed | Rate (%) |
|---|---|---|---|
| Qwen3.5 Flash | Visual understanding | 5 / 41 | 12.20 |
| Qwen3.5 122B-A10B | Visual understanding | 2 / 40 | 5.00 |
| Qwen3.6 Flash | Visual understanding | 10 / 42 | 23.81 |
| Qwen3.6 Plus | Visual understanding | 9 / 42 | 21.43 |
| Qwen3.7 Flash | Visual understanding | 8 / 42 | 19.05 |
| Qwen3.7 Plus | Visual understanding | 9 / 41 | 21.95 |
| Qwen3.8 27B | Visual understanding | 4 / 125 | 3.20 |
| Qwen3.8 Flash 125B | Visual understanding | 0 / 42 | 0.00 |
| DeepSeek V4.1 Flash | Visual understanding | None / 0 | N/A |
| GLM-5.3 Flash | Visual understanding | None / 0 | N/A |
| GPT-5.6 Sol | Visual understanding | 0 / 42 | 0.00 |
| GPT-6.1 Sol | Visual understanding | 0 / 42 | 0.00 |
| GPT-6 Astra | Visual understanding | N/A | N/A |
| Qwen3.5 Flash | Spatial grounding | 2 / 2 | 100.00 |
| Qwen3.5 122B-A10B | Spatial grounding | 14 / 16 | 87.50 |
| Qwen3.6 Flash | Spatial grounding | 15 / 18 | 83.33 |
| Qwen3.6 Plus | Spatial grounding | 16 / 31 | 51.61 |
| Qwen3.7 Flash | Spatial grounding | 5 / 6 | 83.33 |
| Qwen3.7 Plus | Spatial grounding | 17 / 18 | 94.44 |
| Qwen3.8 27B | Spatial grounding | 536 / 834 | 64.27 |
| Qwen3.8 Flash 125B | Spatial grounding | 58 / 112 | 51.79 |
| DeepSeek V4.1 Flash | Spatial grounding | 109 / 179 | 60.89 |
| GLM-5.3 Flash | Spatial grounding | 0 / 0 | N/A |
| GPT-5.6 Sol | Spatial grounding | 342 / 589 | 58.06 |
| GPT-6.1 Sol | Spatial grounding | 359 / 1138 | 31.55 |
| GPT-6 Astra | Spatial grounding | N/A | 34.10 |
| Qwen3.5 Flash | Geometry code | 9 / 11 | 81.82 |
| Qwen3.5 122B-A10B | Geometry code | 2 / 4 | 50.00 |
| Qwen3.6 Flash | Geometry code | 8 / 10 | 80.00 |
| Qwen3.6 Plus | Geometry code | 26 / 55 | 47.27 |
| Qwen3.7 Flash | Geometry code | 21 / 34 | 61.76 |
| Qwen3.7 Plus | Geometry code | 20 / 39 | 51.28 |
| Qwen3.8 27B | Geometry code | 110 / 218 | 50.46 |
| Qwen3.8 Flash 125B | Geometry code | 169 / 2069 | 8.17 |
| DeepSeek V4.1 Flash | Geometry code | 30 / 1972 | 1.52 |
| GLM-5.3 Flash | Geometry code | 20 / 172 | 11.63 |
| GPT-5.6 Sol | Geometry code | 3 / 427 | 0.70 |
| GPT-6.1 Sol | Geometry code | 0 / 259 | 0.00 |
| GPT-6 Astra | Geometry code | N/A | 0.00 |
| Qwen3.5 Flash | Embodied reasoning | 9 / 41 | 21.95 |
| Qwen3.5 122B-A10B | Embodied reasoning | 3 / 40 | 7.50 |
| Qwen3.6 Flash | Embodied reasoning | 10 / 42 | 23.81 |
| Qwen3.6 Plus | Embodied reasoning | 4 / 42 | 9.52 |
| Qwen3.7 Flash | Embodied reasoning | 3 / 42 | 7.14 |
| Qwen3.7 Plus | Embodied reasoning | 1 / 41 | 2.44 |
| Qwen3.8 27B | Embodied reasoning | 1 / 124 | 0.81 |
| Qwen3.8 Flash 125B | Embodied reasoning | 0 / 42 | 0.00 |
| DeepSeek V4.1 Flash | Embodied reasoning | 3 / 42 | 7.14 |
| GLM-5.3 Flash | Embodied reasoning | 11 / 42 | 26.19 |
| GPT-5.6 Sol | Embodied reasoning | 1 / 42 | 2.38 |
| GPT-6.1 Sol | Embodied reasoning | 0 / 42 | 0.00 |
| GPT-6 Astra | Embodied reasoning | 0 / 42 | 0.00 |
General vision. Earlier Flash and Plus models mistake objects and action outcomes—for example, reading zero as nine or treating an inverted cup as upright. These errors affect 12.2–23.8% of reviewed trials, compared with 3.2% for Qwen3.8-27B and none of the reviewed trials for Qwen3.8-Flash or GPT-5.6 Sol.
Spatial grounding. Inconsistent image points produce large reprojection errors, so triangulation rejects the result. Lower rejection rates tend to accompany higher task performance. GPT-6.1 Sol has the lowest rate in this comparison, but 31.5% of its triangulation calls still fail these checks—precise grounding remains a substantial challenge.
Geometry code. Earlier Flash and Plus models reverse coordinate transforms or mix quaternion conventions; confirmed errors affect 47.3–81.8% of their executed calculations. The rates fall to 8.2% for Qwen3.8-Flash, 1.5% for DeepSeek, 0.7% for GPT-5.6 Sol, and zero observed errors for GPT-6.1 Sol. Reliable robot-specific computation is another promising target for improvement.
Embodied reasoning. A correctly computed pose can still be a poor way to grasp an object. We focus on pick-and-place tasks and use GPT-6 Astra to assess whether proposed grasp poses are physically reasonable. GLM leaves inappropriate grasp proposals uncorrected in 26.2% of reviewed tasks, repeatedly failing to reorient its wrist. These errors are less frequent in newer Qwen and GPT models. This is one narrow test of embodied reasoning: Astra still struggles with more complex interactions, including bimanual coordination.
Relationship to General Model Capabilities
Four benchmarks probe complementary parts of this loop: ERQA for embodied reasoning, MMMU-Pro for multimodal understanding, ScreenSpot-Pro for visual grounding, and LiveCodeBench v6 for coding.
General capabilities and robot-use performance
Six-model comparisonRead the data
| Model | Episodes | Benchmark | Benchmark (%) | RoboDojo Score |
|---|---|---|---|---|
| Qwen3.5 Flash | 42 | ERQA | 53.75 | 0.00 |
| Qwen3.6 Flash | 42 | ERQA | 56.75 | 0.00 |
| Qwen3.7 Flash | 42 | ERQA | 57.25 | 0.00 |
| Qwen3.8 Flash | 252 | ERQA | 66.75 | 31.39 |
| DeepSeek V4.1 Flash 1017 | 252 | ERQA | 65.0 | 27.11 |
| GPT-6 Astra | 252 | ERQA | 81.0 | 51.90 |
| Qwen3.5 Flash | 42 | MMMU-Pro | 76.07 | 0.00 |
| Qwen3.6 Flash | 42 | MMMU-Pro | 72.63 | 0.00 |
| Qwen3.7 Flash | 42 | MMMU-Pro | 76.88 | 0.00 |
| Qwen3.8 Flash | 252 | MMMU-Pro | 79.71 | 31.39 |
| DeepSeek V4.1 Flash 1017 | 252 | MMMU-Pro | 80.76 | 27.11 |
| GPT-6 Astra | 252 | MMMU-Pro | 85.09 | 51.90 |
| Qwen3.5 Flash | 42 | ScreenSpot-Pro | 50.73 | 0.00 |
| Qwen3.6 Flash | 42 | ScreenSpot-Pro | 36.81 | 0.00 |
| Qwen3.7 Flash | 42 | ScreenSpot-Pro | 41.24 | 0.00 |
| Qwen3.8 Flash | 252 | ScreenSpot-Pro | 68.44 | 31.39 |
| DeepSeek V4.1 Flash 1017 | 252 | ScreenSpot-Pro | 24.73 | 27.11 |
| GPT-6 Astra | 252 | ScreenSpot-Pro | 92.7 | 51.90 |
| Qwen3.5 Flash | 42 | LiveCodeBench v6 | 74.81 | 0.00 |
| Qwen3.6 Flash | 42 | LiveCodeBench v6 | 77.1 | 0.00 |
| Qwen3.7 Flash | 42 | LiveCodeBench v6 | 78.63 | 0.00 |
| Qwen3.8 Flash | 252 | LiveCodeBench v6 | 86.82 | 31.39 |
| DeepSeek V4.1 Flash 1017 | 252 | LiveCodeBench v6 | 87.79 | 27.11 |
| GPT-6 Astra | 252 | LiveCodeBench v6 | 83.21 | 51.90 |
All four associations are positive: Pearson r = 0.97 for ERQA, 0.93 for MMMU-Pro, 0.69 for ScreenSpot-Pro, and 0.75 for LiveCodeBench. The pattern is consistent with robot use drawing on several abilities together: interpreting observations, identifying targets, reasoning about consequences, and expressing decisions as code.
The strongest associations are with embodied reasoning and multimodal understanding. ScreenSpot-Pro has a weaker relationship, possibly because its 2D screen grounding differs from the 3D geometry of manipulation. These associations do not isolate the contribution of any one capability. Together with the failure analysis, they suggest that future training should jointly improve visual understanding, spatial grounding, geometric coding, and embodied reasoning—for example, by constructing training tasks from robot experience that target each capability.
5. Analysis of Privileged Information
Model capabilities explain part of the picture; the information and tools available to an agent also matter. We next examine how performance changes without depth or camera calibration, and whether it depends on predefined skills. These comparisons test the support a harness needs to provide under realistic conditions.
RQ1: How Does Depth Affect Spatial Understanding for Robot Use?
Recognizing an object in an image does not tell the agent where to move the robot. We compare three information levels: RGB with depth and calibration, RGB with calibration only, and RGB alone. Depth and calibration allow direct pixel-to-world localization. Calibration alone supports multi-view triangulation, but the agent must find corresponding image points. Without either, it must infer spatial relationships from images and adjust movements using action feedback. Robot proprioception remains available throughout.
We evaluate both models on the same 42 benchmark tasks with skills enabled. We use three seeds and two layouts per task for Qwen (252 episodes), and one seed and one layout per task for Astra (42 episodes) to limit evaluation costs. The Astra geometry comparison is separate from its 252-episode main result.
With calibration retained, agents can move the camera and triangulate corresponding points across views. Astra’s Score changes from 55.83 to 55.04 without depth, retaining 98.6%; Qwen falls from 35.89 to 31.39, retaining 87.5%. This contrast suggests that Astra is more effective at recovering spatial information when direct depth measurements are unavailable.
Progress with less geometric information
Read the data
| Model / condition | Episodes | Score |
|---|---|---|
| Astra / depth + calibration | 42 | 55.83 |
| Astra / calibration only | 42 | 55.04 |
| Astra / RGB only | 42 | 31.29 |
| Qwen / depth + calibration | 252 | 35.89 |
| Qwen / calibration only | 252 | 31.39 |
| Qwen / RGB only | 252 | 9.13 |
How much does calibration still matter?
Read the data
| Model / condition | Episodes | Score |
|---|---|---|
| Astra / depth + calibration | 42 | 55.83 |
| Astra / calibration only | 42 | 55.04 |
| Astra / RGB only | 42 | 31.29 |
| Qwen / depth + calibration | 252 | 35.89 |
| Qwen / calibration only | 252 | 31.39 |
| Qwen / RGB only | 252 | 9.13 |
Removing calibration too lowers Astra to 31.29 Score and Qwen to 9.13. With RGB-only input, Astra completes 10 of 42 tasks. Astra’s higher Score and wider task coverage suggest stronger spatial perception from visual observations alone, although both models lose substantial performance.
The paper’s appendix examines two successful Qwen episodes without depth or predefined skills. The agent writes and executes its own geometry code, triangulating tube positions across views in one case and testing candidate table heights against image evidence in another. Both cases connect RGB-based localization to successful manipulation.
RQ2: How Important Is the Skill Library?
A reusable harness should support varied tasks through shared tools, without depending on a handcrafted procedure for each task. We test whether the results mainly reflect benchmark-specific skill guidance by removing Qwen’s access to both the robot skill library and skill writing. Task instructions, environment descriptions, and standard tools remain available.
Without skills, Qwen reaches 30.31 Score / 24.58% SR, compared with 31.39 / 25.00% with skills. It retains 96.6% of the Score, with an SR gap of only 0.42 percentage points. This small aggregate gap suggests that effective task execution is not simply a consequence of the predefined skill library.
Skills help, but are not a prerequisite
Read the data
| Condition | Capability | Score | SR (%) |
|---|---|---|---|
| With skills | Overall | 31.39 | 25.00 |
| With skills | Generalization | 21.60 | 18.06 |
| With skills | Memory | 54.72 | 52.78 |
| With skills | Precision | 10.21 | 2.08 |
| With skills | Long-horizon | 23.75 | 6.25 |
| With skills | Open-vocabulary | 46.67 | 45.83 |
| Without skills | Overall | 30.31 | 24.58 |
| Without skills | Generalization | 23.26 | 20.83 |
| Without skills | Memory | 47.78 | 41.67 |
| Without skills | Precision | 16.88 | 8.33 |
| Without skills | Long-horizon | 26.77 | 16.67 |
| Without skills | Open-vocabulary | 36.88 | 35.42 |
For VLA and WAM policies, demonstrations can communicate requirements that are difficult to specify through text alone. Language-capable agents can also interpret explicit textual rules. Removing predefined skills does not remove the need for a clear task specification—a distinction that matters when designing benchmarks and interpreting generalization.
6. Speed and Efficiency
A harness intended for future training must also make repeated interaction practical. Final scores alone do not tell us how much interaction an agent needs or what it costs. We relate progress to tokens, API price, and elapsed time, then compare serial and pipelined execution.
RQ1: How Does Robot-Use Performance Relate to Token Usage and API Cost?
An agent can spend many interactions locating an object, testing a grasp, or recovering from an unsuccessful action. We analyze the same 252-episode cohorts as the main results to compare the resources spent with the progress achieved.
Astra reaches 51.90 Score with the fewest tokens, but costs $21.29 per episode. Qwen reaches 31.39 at $1.09, outperforming DeepSeek with fewer tokens at a slightly higher API cost. The substantial price gap highlights the value of open models for affordable robot use. Costs use reference API rates from OpenAI15, Alibaba Cloud16, and DeepSeek17.
Score versus tokens and API cost
Read the data
| Model | Episodes | Score | Mean tokens (M) | Mean cost (USD) |
|---|---|---|---|---|
| Qwen3.8-Flash-Next | 252 | 31.39 | 37.668227 | 1.090718 |
| DeepSeek-V4.1-Flash | 252 | 27.11 | 48.761635 | 0.942606 |
| GPT-6 Astra | 252 | 51.90 | 16.778868 | 21.292319 |
Final Score hides when useful progress occurs. The recorded curves first reach Score 25 at approximately 7.4M tokens for Astra, 23.5M for Qwen, and 49.9M for DeepSeek. Qwen reaches that level with less than half DeepSeek’s token usage.
When does interaction turn into progress?
Read the data
| Model | Episodes | Final Score | Tokens to Score ≥ 25 (M) | Time to Score ≥ 25 (min) |
|---|---|---|---|---|
| Qwen3.8-Flash-Next | 252 | 31.39 | 23.5 | 95.5 |
| DeepSeek-V4.1-Flash | 252 | 27.11 | 49.9 | 99.2 |
| GPT-6 Astra | 252 | 51.90 | 7.4 | 42.6 |
The time axis tells a different story. Astra first reaches Score 25 at 42.6 minutes, Qwen at 95.5, and DeepSeek at 99.2. Qwen’s substantially lower token usage yields little elapsed-time advantage at this progress level. Token efficiency alone does not imply faster robot execution.
RQ2: How Does Pipelining Affect Execution Efficiency?
Pipelining helps when the agent can prepare independent work while an action runs. We compare five selected tasks using Astra with medium reasoning effort, one episode per configuration, and matching seeds and layouts. Episode duration excludes simulator initialization.
The pipelined runs are shorter on all five tasks, with observed reductions of 4.8% to 73.7%. Swapping T blocks takes 12.5 versus 34.7 minutes; pressing buttons by number takes 13.7 versus 25.0 minutes.
Episode duration with and without pipelining
Read the data
| Task | Pipelined (min) | Serial (min) |
|---|---|---|
| Swap T blocks | 12.48 | 34.73 |
| Press by number | 13.66 | 24.95 |
| Conveyor pickup | 15.72 | 59.73 |
| Align blocks | 20.18 | 30.17 |
| Solve equation | 22.01 | 23.11 |
API latency, resource sharing, and different action sequences also affect duration. The comparison shows shorter observed runs, but does not attribute the entire reduction to scheduling alone.
7. Conclusion
uni-robot-agent combines shared interfaces, replaceable components, efficient execution, and structured feedback for robot use. Astra achieves strong results in simulation and on physical robots. With the open-weight Qwen3.8-Flash-Next, the harness reaches 31.39 Score on RoboDojo, exceeding the published Astra–RoboProbe result of 28.97.
Precise manipulation and reliable long-horizon execution remain challenges. These results motivate further work on open-weight models that can run locally and learn from robot experience. The harness provides a common foundation for collecting that experience across environments, developing training methods, and evaluating their effects on agent behavior and task performance.
Citation
@article{yuan2026democratizing,
title={Democratizing Robot-Use Agents: A Unified Harness with Open Models},
author={Yuan, Jiarui and Zuo, Yuxin and Huang, Xiaoyu and Zhang, Wenbo and Park, Kwanyoung and Yang, Junlin and Zhang, Tianxiang and Chen, Ruoqu and Ouyang, Yutao and He, Bingxiang and others},
journal={arXiv preprint arXiv:2611.01560},
year={2026}
}
References
- Chen et al. (2026). RoboDojo: A Unified Sim-and-Real Benchmark for Comprehensive Evaluation of Generalist Robot Manipulation Policies.
- Qwen Team (2026). Qwen3.8-Flash-Next: A New Architecture, Towards Ultimate Cost-Efficiency.
- OpenAI (2026). GPT-6 Astra: A New Generation of Intelligence.
- Physical Intelligence (2025). π₀.₅: A Vision-Language-Action Model with Open-World Generalization.
- Zhang et al. (2026). An Unexpected Robot Policy: Early Evaluations of GPT-6 Astra on RoboDojo and Beyond.
- Dream Labs (2026). Zero-Shot to New Robots: Introducing Dream-1.
- RoboDojo Team (2026). RoboDojo Simulation Leaderboard.
- Xi et al. (ACL 2025). AgentGym: Evaluating and Training Large Language Model-based Agents across Diverse Environments.
- Luo et al. (2025). Agent Lightning: Train ANY AI Agents with Reinforcement Learning.
- Su et al. (2026). GPT 6 Astra as an Embodied Policy.
- Zhang et al. (2026). Harness VLA: Steering Frozen VLAs into Reliable Manipulation Primitives via Memory-Guided Agents.
- Xiaomi Robotics Team (2026). Xiaomi-Robotics-1: Scaling Vision-Language-Action Models with over 100K Hours of Real-World Trajectories.
- Wang et al. (2026). OpenWAM: An Open, Modular Exploration Towards Systematic World-Action Model Pretraining.
- Zhang et al. (2026). Hy-Embodied-0.5-VLA: From Vision-Language-Action Models to a Real-World Robot Learning Stack.
- OpenAI. GPT-6 Astra API pricing.
- Alibaba Cloud. Qwen3.8-Flash model information and pricing.
- DeepSeek. Models and pricing.
Evaluating robot-use agents
Evaluation protocols for resource budgets, episode termination, and task-specific knowledge.
Explore the evaluation