Authors: Kangrui Wang, Qineng Wang, Changhe Chen, Pingyue Zhang, Chi Gui, Feishi Wang, Canyu Chen, Wenli Xiao, Xiaoyu Huang, Tonghe Zhang, Linjie Li, Zihan Wang, Minyeong Kim, Yiyou Sun, Mingkai Deng, Jinyu Hou, Qi Zhu, Han Liu, Eric P. Xing, Huaxiu Yao, Zhiwen Fan, Yuejiang Liu, Dawn Song, Pieter Abbeel, Li Fei-Fei, Jiajun Wu, Yuke Zhu, Guanya Shi, Ruohan Zhang, Manling Li
Organizations: Northwestern University · Carnegie Mellon University · UC Berkeley · University of Washington · Stanford University · UNC-Chapel Hill · Texas A&M University · UT Austin
Early successes on agentic robotics point to a potential paradigm shift toward using coding agents to control robots. Existing robotics benchmarks are built around visuomotor policy learning, leaving it open whether coding agents can reliably control diverse robots under physical-world constraints. We therefore introduce the Embodied First Exam, a unified, comprehensive, and agent-native evaluation framework where coding agents can choose their own control approach: direct control, code to control, or train a policy to control. We hope it serves as a first exam for coding agents before they enter the physical world, with 1,156 tasks in 35 suites on 47 robots, including 9 new suites that go beyond pick-and-place to spatial puzzles, dexterous manipulation, multi-robot interaction, dynamic whole-body control, and sim-to-sim engineering. Each task can be run in up to three evaluation settings. The Standard Setting mimics the real world: the agent receives only sensor observations and, by default, cannot reset the environment. Its Realtime variant keeps the environment running while the agent reasons. The Privileged Setting gives the agent access to the full simulator state and unlimited resets, allowing it to search for an oracle solution for training purposes. Success rates in this setting serve as an approximate upper bound. On the 456 core tasks, the strongest of eight agents, GPT-6 Astra in Codex, achieves a success rate of 34% in the Standard Setting, leaving much room for improvement. To see where agents fail, we label the stage at which failed attempts go wrong and compare failures across agents, settings, and stage categories.
Figures & tables
Figure 1: Examples of the control approaches, each with an excerpt of the agent’s commands or code. Dark tabs mark the approaches used ( model is direct control), and the framed line is a policy.
Figure 2: The EFE framework and evaluation protocol. (a) Our unified framework supports different models, harnesses, control approaches, and simulators. (b) In Privileged , the agent and simulator share a container, and the verifier replays the submitted answer separately. In Standard and Realtime , the simulator and verifier are separated from the agent and grade the live episode.
Figure 3: Resource constraints across the exam. The large number and the tick give the median over tests (for GPU memory, over the tests that reserve a GPU), the line spans the range, and the dark box spans the middle half of the tests.
Figure 4: The tasks of the exam: the 9 suites built for the exam, each with a frame and its number of tasks, in the three groups of Section 2.3 , and a frame from each of the 26 adapted suites, ordered by their main robot embodiment, from single arms to aerial robots.
Figure 5: The core tasks by the stage categories of their task graphs, with an example task of each category. Each seat is one task in one category, and the angle of a category is proportional to its number of tasks. A task counts once in each category its task graph contains. The centre counts all 456 core tasks, and the seats cover the 427 with a task graph; no task graph has a Safety or Information stage, since the graphs of Embodied Safety Exam give its safety rules as conditions of their stages ( Section H.1 ).
Figure 6: Task graph and progress maps of carrying in groceries (BEHAVIOR-1K). Panel (a) gives the stages, the order in which they must be met, and the type and contact of each stage. Panel (b) gives the share of the stages whose conditions hold at each moment of the graded episode, for three attempts. Red lines mark failure stages and their failure phenomena ( Section H.6 ).
Figure 7: Success rate of each agent on the core set, with solved tests in parentheses. The harness dsh is DeepSeek Harness, DeepSeek’s own harness.
Figure 8: Every attempt on the core Privileged and Standard tests, with the agents in the order of Figure 7 .
Figure 9: Success rates by suite, for suites with at least five core tests in the setting. Dots give the success rate of each of the three strongest agents, and bars the share of tests that none of them solves. The IKEA assembly tasks of RoboARC count as their own suite.
Figure 10: The 391 core tasks that have both a Privileged and a Standard test, split for each agent by the settings in which it solves them.
Figure 11: (a) Success rate of GPT-6 Astra in Codex on the 391 core tasks that have both settings, as features of the Privileged Setting are added to the Standard interface. (b) Failure rate of each stage type compared in at least two suites, eight agents. (c) Share of GPT-6 Astra’s failures at precise and coarse stages that each run solves.
Figure 12: Claude Opus 5.5 installing the front guard of a fan (DexHandExam) in the Privileged and the Standard Setting. Red marks where the Standard attempt goes wrong. Times are seconds on the replay of the Standard episode.
Figure 13: (a) Concentration of failure stages, mean over tests, and share of tasks with the same most common failure stage in both settings, without the tasks where it is the first stage in both. Gray bars: random failure stages; black lines: 95% intervals. (b) Failure rate of a stage once reached, by category, both settings pooled ( Table 18 ).
Figure 14: Catching a ball twice (RoboDynamicExam): the stages that the attempt of each agent reached and the stage at which it failed, in each setting, and Standard replay frames at three failures at stage 2.
Figure 15: (a) Failure profile of each agent; zero progress means that the attempt reached no stage. (b) Share of the row agent’s solved Standard tests (first column) that the column agent also solves; the last column uses any agent above it in Figure 7 . (c) Success rate by model and harness on the 456 core tests of the Standard Setting; hatched bars mark other harnesses.
Figure 16: Preparing a lunch box (BEHAVIOR-1K, Standard Setting): a head-camera frame of four failed attempts, with the failure circled.
Figure 17: (a) Share of each approach by setting in 1,489 sampled attempts. Mixed attempts switched approach midway or used two approaches equally. (b) Soccer attempts in the Standard and Realtime settings that trained a policy, scored or won.
Figure 18: GPT-6 Astra in Codex on the two soccer versions in the Standard Setting. Each row gives the approach and result, two replay frames and the goals over match time.
Appendix figures & tables34 assets
Supplementary material from the paper’s appendix.
Appendix
Item
Count
Suites (new)
35 (9)
Robots
47
Tasks
1,156
Tests
2,288
Tasks with a full / partial reference solution
686 / 78
Core tasks
456
Appendix
Table 1: Size of the exam. Rows list the number of suites (with the number built for the exam in parentheses), robots, tasks, tests, tasks with a full or partial reference solution, core tasks and core tests.
Suite
Simulation backend
Kind
Robots
Tasks
Tests
Core
DexHandExam
MuJoCo
hand
3
30
60
23
Embodied Olympics - Fun
MuJoCo
humanoid
2
79
179
56
Embodied Olympics - Match
MuJoCo
arm, humanoid, mobile manip.
5
14
41
13
Embodied Safety Exam
MuJoCo
arm, two arms, mobile manip.
4
72
76
50
iSpatialGym
OmniGibson (Isaac Sim)
mobile manip.
1
12
24
8
RoboARC
MuJoCo
arm, two arms
3
106
212
58
Appendix
Table 2: The suites of the exam. The 9 suites that we built come first, followed by the 26 suites adapted from existing benchmarks, which Section A.2 cites. The Kind column gives the kinds of robot body in the suite, nine over the exam (mobile manip. = mobile manipulator; car = wheeled car). The Robots column counts distinct robot models, the Tests column counts tests over all tasks, and the Core column counts tasks in the core set.
Figure 19: Success rate of each agent on the core set. Each bar gives the share of the core tests of one setting that one agent solves.
Figure 20: Success rate of each agent against the mean list-price cost of its attempts.
Figure 21: Share of the core tasks of each type whose Standard test each agent solves, with a gray line joining the three strongest agents. The number of core tasks of the type is in parentheses, and a task can have several types.
Figure 22: Share of the Privileged tests solved by the row agent that the column agent also solves, as in Figure 15 , with the agents in the order of Figure 7 .
Standard
Privileged
Suite
Tests
Claude Opus 5.5
Gemini 4 Argon
Weaker
Tests
Claude Opus 5.5
Gemini 4 Argon
Weaker
Embodied Safety Exam
50
8
5
0
–
–
–
–
RoboARC
50
8
2
1
50
5
1
0
Embodied Olympics - Fun
56
5
1
0
56
1
0
0
ManiGuard
7
4
0
0
7
0
0
0
RoboDojo
12
0
2
1
12
0
0
0
Appendix
Table 3: Tests that break the order of Figure 7 , by suite and setting. “Tests” gives the number of tests of the suite in the setting. Each test that breaks the order is counted in the column of the highest agent in Figure 7 that solves it, and “Weaker” sums the five weaker agents. The six suites with the most such Standard tests and BEHAVIOR-1K, which has the most such Privileged tests, are listed, and “Other suites” sums the rest. RoboARC excludes its IKEA assembly tasks, which are counted under Other suites.
Figure 23: First and last frames of the graded episodes of two Standard tests that break the order of Figure 7 . Gemini 3.8 Flash folds a blanket in RoboARC, and Gemini 4 Argon opens a jam jar in DexHandExam.
Figure 24: Core tests of each setting, grouped by which of the three strongest agents solve them.
Setting
Version
Attempts
Trained with RL
Played with it
Scored a goal
Won
Standard
GPU
12
10
9
7
3
CPUs only
12
0
0
3
0
Realtime
GPU
8
7
5
2
1
CPUs only
8
0
0
0
0
Privileged
GPU
8
5
0
–
2
CPUs only
8
0
0
–
3
Appendix
Table 4: Attempts of the agents on the two versions of the soccer task, in their own harness and in the harness comparison. “Played with it” counts the attempts that played the match with the policy they trained. The Privileged Setting does not record goals.
Run
Standard
Realtime
Standard (baseline)
28
30
+ object-state query
45
38
+ unlimited resets and save/load states
53
64
+ both
68
80
Privileged
77
84
No success signal
31
26
Appendix
Table 5: Success rate (%) of GPT-6 Astra in Codex in the controlled runs, on the 391 core tasks that have both a Privileged and a Standard test, and in the Realtime column on the 50 Realtime tests of these tasks. The Standard column includes the Realtime tests. The Privileged row uses the Privileged tests of the same tasks.
Model (tests)
Codex
Claude Code
Antigravity CLI
GPT-6 Astra (456)
34 / 26 ∗
22 / 18
–
Claude Opus 5.5 (456)
26 / 21
25 / 21 ∗
–
Gemini 4 Argon (456)
29 / 25
25 / 24
24 / 21 ∗
Appendix
Table 6: Success rate (%) of each model in each harness, on the 456 core tests of the Standard Setting. The first number counts the final result, and the second counts first-episode success. The model’s own harness is marked with an asterisk.
Category
Stage types
Relation
place, put in, take out, gather, stack, insert, assemble, disassemble, screw/unscrew, thread/hang, connect, hand over
navigate, traverse, jump, perform acrobatics, hang and swing, maintain balance, maintain pose
Appendix
Table 7: Stage types, by category. Competition stages (score, defend, win) are counted by category only.
Who
Fingers/gripper
one hand or gripper touches the object directly, also when the pose of a held tool is graded
Bimanual
two hands or arms act on the stage together
Tool
the robot acts through a held or mounted tool
Legs/torso
feet, legs, head, torso or landing gear on a support surface
Mobile base
wheels or a wheeled base, while moving
No contact
no contact to label, as when flying, observing or reporting
Appendix
Table 8: Contact of a stage: who touches and how.
Category
Phenomenon
Meaning
Contact
Failed to make contact
the contact the stage needs never existed, as in a missed grasp or fingers that never closed on the object
Lost hold
held and then lost: slipped or dropped while held or carried
Abnormal contact force
visible or sensed wrong force, such as a part not fully inserted or a latch not engaged
Failed to release
the object stays in the hand or tool when the stage needs it to leave
Unstable after release
after a planned release the object falls over, rolls away or bounces
Drags the base
manipulating a part moves the body that should stay still
Appendix
Table 9: Failure phenomena: what visibly went wrong at the failure stage, up to two per attempt.
Category
Root cause
Meaning
Cognition
Task understanding
the behavior shows the task was misread
Reasoning/planning
wrong goal, stage order or overall strategy
Perception
the robot acted on a wrong estimate of where or what something is
Safety judgment
records show a hazard was not recognized or misjudged
False completion belief
a false belief that the task was done affected stopping or decisions
Control
Grasp and contact design
the contact geometry or load layout does not suit the stage
Appendix
Table 10: Root causes: why the failure happened, up to two per attempt, each with its evidence.
Agent
Setting
Failed
Filter cutoffs
with failure stage
Missing trajectory
Excluded
Gemini 4 Argon
P
221
108
9
134
163
S
326
36
22
0
36
R
47
9
3
0
9
Kimi 3.1 Pro
P
238
0
0
49
49
Gemini 3.8 Flash
P
291
4
1
97
98
S
400
3
2
0
3
Appendix
Table 11: Failed attempts excluded from the failure analysis, by agent and setting. P, S and R stand for the Privileged , Standard and Realtime settings. The column “with failure stage” counts filter cutoffs whose labels also give a failure stage with a physical phenomenon. The column “Excluded” counts filter cutoffs and missing trajectories, and an attempt in both groups counts once. GPT-6 Astra, Claude Opus 5.5 and DeepSeek V4.1 Flash are not listed: they have no filter cutoffs and 1, 2 and 4 missing trajectories in the Privileged Setting.
Figure 25: Failures by suite. Each cell gives the share (%) of the suite’s analyzed failures in the column, with the three settings pooled, and n is the number of failures. A failure can have up to two phenomena and up to two root causes, so these two blocks can add up to more than 100%.
Figure 26: Failures by robot body, agent and setting, in the same format as Figure 25 . Here too, the phenomena and the root causes can add up to more than 100%.
Stage type
Suites
Weight
P
S
S − P
Clean
2
68
33
84
+51
Fold
1
35
38
89
+51
Assemble
2
56
34
80
+46
Strike
2
221
11
55
+44
Perform acrobatics
1
29
28
71
+43
Flatten
1
36
42
84
+42
Appendix
Table 12: Failure rate of each stage type in percent, compared within suites: the types compared in at least two suites, as in Figure 11(b) , and the types of one suite with a weight of at least 25. P is the Privileged and S the Standard Setting. The Suites column gives the number of suites compared, and the Weight column the sum of the smaller counts. Types compared in only one suite are less reliable. Close includes stages that already hold at the start, such as a closed fridge, which count as reached even when the attempt never acts on them.
Value
Suites
Weight
P
S
S − P
Who
Legs/torso
6
844
27
64
+37
Bimanual
10
741
39
71
+32
Tool
12
910
24
55
+31
Fingers/gripper
26
3,420
24
46
+22
Mobile base
6
1,169
26
43
+18
No contact
3
173
11
24
+13
Appendix
Table 13: Failure rate by contact in percent, compared within suites as in Table 12 . Bimanual stages are the hardest in both settings, and among the values of how, the failure rates of in-hand adjustment and of cradling or scooping rise the most.
Run
Precise (91)
Coarse (97)
Material (36)
Other (32)
No success signal
19 (11–26)
14 (8–22)
28 (14–42)
16 (3–28)
+ object-state query
21 (13–30)
34 (25–43)
42 (25–58)
28 (13–44)
+ unlimited resets and save/load states
36 (26–46)
44 (35–54)
47 (31–64)
31 (16–47)
+ both
47 (37–58)
67 (58–76)
69 (56–83)
41 (22–56)
Privileged
73 (64–81)
60 (51–69)
83 (69–94)
72 (56–88)
Appendix
Table 14: Share (%) of GPT-6 Astra’s labeled failures in the Standard Setting that each controlled run solves, by type of failure stage, with 95% intervals over failures. Material stages include drawing, pouring and cleaning. The Privileged row uses the Privileged test of the same task.
Suite
Task
Stages
Shared stage
Type
Failed here
BEHAVIOR-1K
clean up branches and twigs
5
first branch into the bin
put in
8/8
Embodied Safety Exam
three spice jars onto a tray
3
second jar onto the tray
place
8/8
RoboARC
thread a fiber bundle through rings around a post
18
first fiber through its ring
thread/hang
7/8
RoboCasa365
defrost meat in the microwave
4
container into the microwave
put in
7/7
DexHandExam
install the front guard of a fan
5
seat the front guard
assemble
6/7
RoboDynamicExam
catch, return through a slot, deliver to a moving cart
3
recatch after the rebound
catch
7/8
Appendix
Table 15: Examples of shared failure stages in the Standard Setting, one per suite. The Stages column gives the number of stages of the task. The column “Failed here” gives the failed attempts that failed at this stage over all failed attempts with a located failure stage, without the attempts excluded in Section H.3 .
Naming rule
All
Two or more stage types
Stage-type rates, other tasks
73
67
Stage-type rates, same suite
75
71
Always the first stage
65
56
Appendix
Table 16: Stage types and the common failure stage, in percent: how often a rule names the most common failure stage of a Standard test, over the 264 Standard tests that have one and over those among them whose tasks have at least two types of stages, and the concentration of failure stages, observed and expected if each agent failed independently at the given rates.
Privileged
Standard
Passed the test, all attempts covered
30
10
Passed the test, attempts past the common stage
64
33
Passed the test, past a common stage that is not the first
76
41
Failed exactly at the common stage, attempts that never met it
77
83
Appendix
Table 17: Getting past the common failure stage, in percent. For each attempt, the common stage is the most common failure stage of the other agents on the same test. The table covers the 1,235 Privileged and 1,874 Standard attempts that have such a stage and a readable status at it.
Category
Stage type
Suites
Privileged
Standard
Both
Mechanism
all
18
14 (124/856)
27 (220/825)
20 (344/1,681)
Press
6
2 (3/179)
6 (7/114)
3 (10/293)
Close
9
5 (15/287)
8 (25/305)
7 (40/592)
Switch on/off
4
11 (5/44)
24 (8/33)
17 (13/77)
Open
12
29 (92/321)
47 (164/350)
38 (256/671)
Pose
all
16
16 (253/1,592)
51 (389/763)
27 (642/2,355)
Appendix
Table 18: Failure rate (%) of each stage category and of the stage types found in at least three suites, in the Privileged Setting, in the Standard Setting and in both together, with the stages at which attempts failed over the stages that attempts reached. The Suites column gives the number of suites with the stage type.
Figure 27: Failure rate of a stage once reached, by stage category and by the robot part that makes contact, with the Privileged and Standard settings pooled ( Table 18 ). Each cell gives the rate, the stages failed over the stages reached, and a bar on a scale from 0 to 100%. The rows are those of Figure 13 , at the same heights.
Astra
Opus
Argon
Kimi
G-3.8 Flash
Qwen
DeepSeek
GLM
Failed attempts
316
372
328
432
449
433
467
472
Zero progress, Standard
27
36
32
44
47
64
59
59
Failed to make contact
9.8
7.3
10.1
16.7
18.7
20.3
21.2
24.2
Lost hold
17.4
12.6
10.1
12.5
10.5
7.2
9.4
10.8
Inaccurate pose
20.9
20.4
23.5
25.2
21.2
11.1
12.8
14.2
Obstruction/collision
17.1
15.1
8.2
6.5
10.0
11.5
18.8
12.9
Appendix
Table 19: Failure profile of each agent, given as the share in percent of its failed attempts in the Standard and Realtime settings with each label. Zero progress, an attempt that met no stage of the task, counts only Standard attempts on tasks with at least two stages whose progress shows whether they met a stage. Of each agent’s failed Standard attempts on such tasks, 3 to 33% have no readable progress and are left out, the most for Qwen3.8 Max. The highest value of each row is in bold. The rows from “Failed to make contact” to “Not attempted” are phenomena, that row gives the position of the failure stage, and the two rows after it are root causes. The two rows “per stage reached” divide by stages instead of failed attempts: among the reached stages that need contact (or a grasp), the share at which the attempt failed without contact (or with a lost hold). The last two rows compare each agent with GPT-6 Astra on the tests with at least three stages that both failed, excluding ties: the share of these tests on which GPT-6 Astra reached more stages, and their number.
Figure 28: Task graph of a DexHandExam task, installing the front guard of a fan, and the stages that three attempts met over time. A bar shows when a stage’s condition held, and a cross marks the failure stage.
Figure 29: Progress maps of the eight agents on preparing a lunch box (BEHAVIOR-1K, Standard Setting). Crosses mark the failure stages.
Figure 30: Standard Setting. (a) RoboARC, threading a rope . (b) RoboCasa365, fetching cereal and a bowl ; the column of stage 4 shows the end of the episode.
Figure 31: BEHAVIOR-1K, disposing of batteries , Standard Setting: the task graph and the stages of each agent, where the wastebasket on the floor holds from the start, and head-camera frames as the robot tips over.
Figure 32: Privileged and Standard settings. (a) RoboTwin 2.0, hanging a mug : progress maps of GPT-6 Astra. (b) Embodied Olympics - Fun, heading a ball ten times : the headers of each agent in the Privileged (P) and Standard (S) settings.
Figure 33: Buzz wire game on a physical robot arm. (a) Four frames in time order of one trial of GPT-6 Astra and one of Claude Opus 5.5, with a close-up of the light and the buzzer and the command being executed. In the last frame of Claude Opus 5.5’s trial, the loop has touched the wire and the light is on. (b) The plot gives the progress score of each agent in each of its eight trials.
Coding agents are beginning to move beyond purely digital tasks to tackle physical-world challenges, particularly in robotics. Existing robotics benchmarks, however, primarily focus on the performance of individual artifacts, such as policies or controllers, offering limited coverage of coding agents' broader engineering capabilities. Real-world robotics extends beyond control: agents must build, integrate, diagnose, and improve heterogeneous artifacts under resource constraints and reason from multimodal feedback. To evaluate these broader capabilities, we introduce RLE-Bench, a benchmark of robot-learning tasks spanning four representative robotics development workflows: interactive control, policy learning, perception and estimation, and mechanical design. We use diverse task-specific metrics to evaluate the artifacts submitted by the coding agents, from the success rate the agents achieved to the policy agents trained, the harness agent built, and the mechanical structures the agent designed. We aggregate these metrics into an overall RLE Index and report workflow-specific capability profiles, enabling systematic comparison of coding agents' capabilities across multiple capability dimensions. Beyond performance ranks, we also conduct in-depth case studies examining agent behavior on representative tasks, highlighting both current capabilities and limitations, and pointing to the opportunities robotics tasks have to offer for future agent training.
Haitong Ma, Chenxiao Gao, Rushi Qiang +2
Harvard University · Georgia Institute of Technology
How well can general-purpose multimodal models turn visual understanding and reasoning into embodied manipulation via executable code? We introduce CodeActionBench, a benchmark of 25 manipulation tasks that evaluates this capability through agentic Code-as-Policy. Without task-specific fine-tuning, demonstrations, external specialist perception or grasp modules, privileged scene state, or predefined task policies, agents should select visual evidence, form task-relevant 3D estimates, construct manipulation targets, and iteratively execute and revise their policies. A shared robot API provides RGB observations, calibrated geometric operations, robot feedback, and bounded motion, leaving task-dependent decisions to the evaluated agent. Fixed task instances, resource budgets, and a hidden physical-outcome verifier support controlled comparisons across models and harness configurations. Extensive evaluations across nine configurations and 675 attempts achieve success rates ranging from 2.7% to 73.3%. The strongest configuration, GPT-6 Astra with Codex CLI, solves 22 of 25 tasks at least once in three attempts, demonstrating the best performance while still leaving substantial room for improvement. Trajectory analyses reveal difficulties in spatial alignment, object retention, and completion judgment, including task failures despite successfully completed motions. CodeActionBench provides a controlled testbed for measuring how general-purpose models translate their capabilities into manipulation behavior and for examining typical failure scenarios in that process.
Improvements in multi-modal capabilities have enabled agents to act directly as robot policies, a setting we refer to as agentic robot control (ARC). We introduce RoboARCade, a benchmark of long-horizon manipulation tasks across three embodiments designed to test in-context adaptation, memory, and reasoning for precise control. The tasks build on existing open-source benchmarks, which we make harder by widening the range of initial conditions. RoboARCade is easy to use and extend: all tasks run on a single simulation backend, MuJoCo, each task is a self-contained data pack, and agents connect through interchangeable interfaces, so new tasks, agents, and interfaces can be added independently. The benchmark separates leading agents: GPT-6 Astra achieves 49.8% compared with 43.6% for Claude Fable 5.1, leaving substantial room for improvement. Comparing two interfaces, we find that a richer visual interface adds only 1.5 to 6.8 points at 1.7 to 2.3 times the cost. Failures stem mostly from choosing a poor manipulation strategy or executing a good one imprecisely, rarely from misunderstanding the scene, and agents incorrectly claim success on 24% to 39% of attempted subtasks. Agents can also improve without human input: one successful demonstration in context raises Astra's score from 53.5% to 73.0% on a five-task subset, and a prompt the agent writes and revises itself reaches 72.0%. Code, videos and full traces are available at roboarcade.org.