Robo Use

Supported

What Robo Use 0.1.1 supports.

Models#

ModelHarness
claude-sonnet-5claude-code
gpt-6-astracodex
zai-org/GLM-5.3 on Basetenclaude-code-glm, codex-glm, mini-swe-agent-glm
allenai/MolmoAct2-LIBERO-LeRobotmolmoact2

Harnesses#

Harness
oracle, noop
claude-code
codex
claude-code-glm, codex-glm, mini-swe-agent-glm
molmoact2

What each needs: Harnesses.

Simulators#

BackendSuitesTasksInstall
tabletop (MuJoCo)libero-style, arc-style, robo-use-families, safety, hard, part of vision95[sim]
Meta-World 3.1metaworld, part of vision74[sim,metaworld]
Gymnasium-Roboticsgymrobotics12[gymrobotics]
robosuite 1.5robosuite21[robosuite]
LIBEROlibero20by hand
MuJoCo Menageriemenagerie15[sim] + robouse fetch-assets
RoboHarm scenesroboharm80[sim] + robouse fetch-assets
Skydio X2 dronedrone10[sim] + robouse fetch-assets
DexJoCodexjoco14[sim] + DexJoCo, see Suites

Per-suite results: Suites.

Platforms#

PlatformStatus
macOS on Apple silicon, Python 3.11, 3.12, 3.13, MuJoCo 3.3.0supported
Python 3.14not supported: MuJoCo 3.3.0 and Meta-World have no build for it

Isolation#

BenchFlow is the environment framework whose task and trial formats Robo Use uses (Robo Use and BenchFlow). The released runner does not start BenchFlow; exported tasks run under bench eval run.

ModeStatus
Local runner, macOS: model harnesses under sandbox-exec, file access denied to ROBOUSE_SANDBOX_DENY pathssupported
Local runner, Linuxno sandbox
BenchFlow, Docker: agent and simulator in separate containersneeds a checkout

Output formats#

Output
Trial folder in BenchFlow's trial layout (config.json, result.json, verifier/reward.txt)
Agent trajectory in ATIF v1.7 (agent/trajectory.json)
Episode trace (episode/trace.jsonl) and video (artifacts/recording.mp4)
Task folders in BenchFlow's native format (task.md, schema 1.3)