THE CREW
Coding agents can write ROS 2 code, but they cannot see the running robot. FlightOps gives them, and you, the record: what the graph did, why it broke, and whether the change works.
Stack Overflow Developer Survey 2026
66%of developers who use AI already work in coding agents.
93%say trusting AI output requires source attribution.
In robotics, the source is the recording. Read the survey
THE WORKFLOW
Eight steps between an idea and a robot. Your agents do the typing, FlightOps supplies the evidence, and you make the calls.
BEFORE MERGE · CHECKLISTFO-1
Set the goala prompt or a bug report
YOUWrite the changenodes, launch files, parameters
AGENTObserve the runflightops launch
FLIGHTOPSDiagnoseonscope doctor --json
FLIGHTOPSTriage the recordingsplashdown triage
FLIGHTOPSGuard it with a testsplashdown fixture
AGENTVerifylcc run · build, test, replay, simulate
FLIGHTOPSRead the evidence, give the GOthe evidence bundle, not just the diff
YOUAGENT KIT
Agents break middleware contracts that only show up at runtime. FlightOps gives them the same bounded evidence and the same verdict it gives you.
DECLARATION · OPTIONAL AIFORM AI-1
Ask questions about up to eight evidence files in plain language. Before anything is sent to a model, FlightOps lists every item it would send. Nothing leaves your machine until you approve. Off until you turn it on.
Read-only MCP toolsSourcing, recording stats, asserts and bounded queries, confined to a root you choose.
ROS 2 skillsQoS, Nav2, ros2_control, launch files, Jetson and more.
Coordinator agentFlightlead reads your AGENTS.md and runs crewmates side by side.
JSON on every checkBounded output that fits a context window.
NEXT DRAWER