ora interactive lets you pick a prepared benchmark task, watch ORA work on
it, and send it a message while it runs, the way you would talk to a coding
agent. ora local (see Run ORA on your computer)
opens the same interface for its local task.
./scripts/ora interactive --spec path/to/run-spec.yaml --confirm-launchRepeat --spec to offer several tasks. Each must be a Native RunSpec for
LIBERO, RoboTwin or RoboDojo. The selected task keeps its benchmark
instruction, official evaluator, seed or layout, provider, resources and
policy; a typed message never replaces the task. Selecting a task and passing
--confirm-launch are both required before the normal preflight and launch.
The header names the model, reasoning effort and protocol that the offered
RunSpecs' Provider profile binds (several values when the specs differ).
Preflight prints one line per check, [PASS] name or [FAIL] name: detail;
the full record of every check is kept under the run workspace's preflight/.
| Key | Effect |
|---|---|
| ↑/↓, Enter in the picker | Select and start a task |
| Enter in the editor | Steer the active run: the message reaches the model before its next call |
| Alt+Enter | Queue a follow-up for the next task you start |
| Tab | Switch between the picker and the editor when no run is active |
| Esc | Stop the active run through the normal stop path |
| Ctrl-C / Ctrl-D | Leave the interface; the run keeps going |
Queued, delivered and rejected messages are shown above the editor. A message is delivered at a model-call boundary: it never interrupts a request in flight or moves the robot directly.
A run that received a message is human-assisted. Its official verdict is
kept, but it is marked human_intervention: true with an
operator_message_count, excluded from autonomous success rates, and not used
for automatic learning or SFT export. A stopped run ends incomplete with
the operator as termination authority. Use ora watch RUN_ID to inspect any
run without being able to send input.
After the environment ends the episode, ORA writes metrics, evaluates, seals
and releases the run's resources. The status line shows Landing… until
that is done. Keep the terminal (and, on a cluster, the job step that runs
ORA) open until the run is reported finished: closing it earlier can stop
the landing midway.