Online documentation for FlightOps 0.2.0b1. An installed build has the same pages offline: flightops docs --open.
Flightops helps you inspect ROS 2 systems, recordings and saved evidence. Flightops is in beta (0.2.0b1) for invited ROS 2 teams. Start with installation and first steps, then choose a task. Use a laptop or desktop terminal at least 120 columns by 36 rows.
Start here
- The beta: what is included, known limits, and where to send feedback.
- Install Flightops for your Ubuntu version, then activate this device.
- First steps: observe a demo node in two terminals.
- User guide: follow everyday tasks and recover from common errors.
Release notes · Beta terms · Privacy notice · Feedback: beta@flightops.dev
Other starting points
- Try a recording without ROS: use the bundled sample.
- Open recordings in the Scene Workbench: replay a run or compare two.
- Test your installation: run the manual checklist and record results.
- Fresh Ubuntu demo: install ROS 2, create a package, and showcase Flightops with TurtleBot3.
Tutorials
Work through a tutorial to complete one task.
- Attach to running nodes.
- Launch a system.
- Diagnose Nav2, Panda, and Go2 faults (offline HTML).
- Connect optional AI.
- View saved results.
- Capture a talker and open a report: record, query, save, and reopen one bounded demo.
- Read the screens: real captures with numbered explanations.
Use the user guide for a complete everyday workflow.
Scene Workbench
- Scene Workbench guide: open recordings, replay, compare, keys and limits.
AI assistance
- AI overview: available connections and how requests work.
- Connect a provider.
- Use the assistant: attach evidence, ask, and review.
- Connections and credentials: manage keys and troubleshoot.
- Jev evidence priority: optionally prioritize a receipt before an assistant request.
How-to guides
| Task | Guide |
|---|---|
| Check topic delivery or lifecycle state after launch | Launch readiness |
| Read and search a launch log in the terminal | Launch log summary and recall |
| Connect a project to live observations and local checks | Development workspace |
| Investigate a failure | Investigation workflows |
| Follow screenshot-supported ROS 2 fault examples | ROS 2 troubleshooting examples |
| Query a recording | Evidence queries |
| Prepare a recording for replay | Replay readiness |
| Gate a change in a project | Project intake and launchcommit |
| Compare retained runs | Proof comparison |
| Reproduce a run elsewhere | Reproduction packages |
| Run the bundled simulation (source checkout) | Simulation demo |
Advanced guides use the component commands where needed. The advanced user guide covers the component workflows.
Component tools
| Tool | Guide |
|---|---|
onscope: ROS 2 graph and runtime diagnosis | onscope |
splashdown: recording analysis | splashdown |
lcc: the launch gate | launchcommit |
highbay: warm build containers | highbay |
flightops-mcp: MCP server for coding agents | integrations |
flightschool: ROS 2 skills for coding agents | flightschool |
flightlead (preview): coordinator for coding agents | flightlead |
flightops-gym-smoke (research preview) | Gym |
Reference
- Command reference: every
flightopscommand, the other installed commands and their reference pages. - License and usage metrics: activation, renewal, devices and what is sent.
- Reference pages by topic: recording, history, checks and workspace.
- Build features: what the beta build includes.
- Glossary: short definitions of the terms used here.
- Terminal controls.
- Troubleshooting.
- Supported ROS and Gazebo environments.
- Scenario format.
- Security and execution boundaries.
Read offline
Open the HTML edition locally; an installed build has its own copy (flightops docs --open). Tutorials and maintained guides have navigation and copyable commands. Use Search the docs to find a command, term, or error across the offline guides. Every search word must match a section; results link to that section. Search runs locally, including when pages open from file://.