How to use Codex to build a robot mission simulation

Varianyk Danil used Codex to turn an existing Windows-oriented repository into NEXUS, a repeatable robot-mission simulation on macOS and Docker. The work joined a FastAPI control plane, PostgreSQL memory and audit data, a browser console, and a C++ navigation component.

Three virtual robots moved through a shared metric building model. Codex helped implement sequenced WebSocket telemetry, route checks, mission stages, and the interface that showed why a robot was assigned to a job. The team exercised the final browser experience and checked route geometry so movement did not simply cut through walls.

The owner selected a clear physical boundary. A Spot integration could inspect identity, battery, and cameras, but could not acquire motor authority. The deterministic demo worked without a model API key, and simulated telemetry was not presented as a measurement from a real fleet.

The reported result was a running, tested simulation with visible jobs, memory, paths, and audit evidence. That is distinct from a deployed robot controller. Physical pilots were still future work, dependent on further authentication, grants, watchdogs, and safety review. The account shows Codex implementing an inspectable simulation while the human retained product and physical-operation decisions.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Devpost · Varianyk Danil