Flightops is in beta (0.2.0b1) for invited ROS 2 teams. Read the beta first, then install and follow first steps. Use the user guide for everyday workflows with expected results and troubleshooting. Use the task guides below for a specific result.
The beta
Tutorials
AI assistance
Task guides
| Task | Guide |
|---|
| Check topic delivery or lifecycle state after launch | Launch readiness |
| Trace a map, lidar, planner, joint, or control-topic fault | ROS 2 troubleshooting examples |
| Investigate a ROS project from source to live observations | Development workspace (source repository) |
| Compare parameters and inspect message-time transforms | Development tools (source repository) |
| Plan and retain a development experiment | Development experiments (source repository) |
| Save and reopen project settings | Project profiles |
| Resolve a selected launch file and its declarations | Launch resolution |
| Set up the launch gate for a project | Project intake |
| Inspect parameter provenance, timelines, or change impact | Investigation workflows |
| Inspect laser, IMU, or depth inputs | Device recipes |
| Run repeated seeded simulation experiments | Simulation experiments |
| Test a depth-camera pipeline | Depth camera |
| Run an agent development experiment | Developer test lab (source repository) |
| Compare simulation runs or inject a bounded fault | Behavior and fault workflows |
| Prepare a recording for replay | Replay readiness |
| Compare two saved proof records | Proof comparison |
| Package evidence for another machine | Reproduction packages |
| Deliver to a remote development container | Remote development (source repository) |
| Run local Docker and KVM acceptance checks | Local VM testing (source repository) |
Reference
| Reference | Use it for |
|---|
| Command line | Public commands and common options |
| Build features | What the beta build includes |
| License and usage metrics | Activation, renewal, devices and metrics |
| Glossary | Plain-language definitions and term links |
| Terminal workspace (source repository) | Views and keyboard controls |
| Integrations (source repository) | MCP setup, results reports, and source builds |
| Scene Workbench protocol (source repository) | The local service protocol behind the Scene Workbench |
| Bounded evidence queries | MCAP query clocks, limits, and result meaning |
| TF history | Session TF collection, clocks, and bounds |
| Troubleshooting | Common setup and launch problems |
| Supported ROS and Gazebo environments (source repository) | Supported development images |
| Scenario format (source repository) | Versioned scenario fields and semantics |
| Security boundaries (source repository) | Execution, evidence, and hardware limits |
Reference pages by topic
Each page describes one command family or data format. The command reference maps every flightops command to its page.
| Tool | Guide |
|---|
| Live graph and topic inspection | onscope (source repository) |
| Recording analysis and replay fixtures | splashdown (source repository) |
| Build, test, and simulation gates | launchcommit (source repository) |
| Reusable build workspaces | highbay (source repository) |
| ROS skills for coding agents | flightschool (source repository) |
| Coordinator directory for coding agents (preview) | flightlead (source repository) |
| MCP server and results reports | integrations (source repository) |
| Desktop app for recordings | Scene Workbench and its build notes (source repository) |
| Local KVM smoke task (research preview) | Gym (source repository) |
| Shared data and evidence library | axikit (source repository) |
| Recording-to-regression workflow | Recorded failures (source repository) |
Project and contributor guides
- Contributing (source repository) explains how to work in this repository.
- Demo project (source repository) explains the bundled ROS example.
- Safety model (source repository) holds the safety requirements that outrank every other design choice.
- Known limits lists what the beta does not do and what has not been checked.
For a short overview of the component workflows, use the advanced guide.