Credentials. The Planner endpoint needs its own API access settings, so keep those keys out of logs and shared session files.
Who it is forA developer testing a new OpenAI-compatible Planner model who needs a quick end-to-end check of the perception and action loop.
The problemTesting a Planner against a physical or simulated task usually means wiring many services together before seeing any behavior.
The outcomeThe agent runs one task for up to a set number of turns, and the developer can see how the loop behaves on that scene.
What you need first
- Python 3.10 or newer and uv installed
- An OpenAI-compatible Planner LLM or VLM endpoint for any run that reasons over a task
- One simulator backend installed through scripts/setup_envs.sh, such as libero
Steps
- Run
uv sync --extra devin the Open ETA repository folder. - Run
bash scripts/setup_envs.sh liberoto install the LIBERO simulator backend. - Run
uv run python -m sim.mcp_serverand keep it running. - Run
uv run openeta --once "inspect the current scene" --max-turns 8after configuring the Planner with/providerin the TUI if needed.
Prompt for your agent
In the OpenETA repo, run `uv run openeta --once "<task text>" --max-turns 8` with the LIBERO simulator MCP service running. Report the final status and whether the environment reports task completion, and do not treat a finished process as task success.
Caveat. The README says a finished process does not imply task success, so check the trusted environment receipt or checker output rather than the exit alone.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for OpenMOSS/OpenETA and "Run one bounded task through a Planner and the simulator"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer