Use this page to check whether a workflow is in the build you installed. "Included" means the build contains the command or code. It does not mean that every path passed release acceptance; What has been checked and the known limits say what did.
Build identities
The beta has one version, 0.2.0b1, in two builds from one source commit.
| Build | Platform |
|---|---|
| Humble build | Ubuntu 22.04, ROS 2 Humble, Python 3.10, x86_64 |
| Jazzy build | Ubuntu 24.04, ROS 2 Jazzy, Python 3.12, x86_64 |
The install page lists each build's release name and archive SHA-256. flightops --version prints the version, release and source commit of your install. Install steps are in Installation; changes from the 9 October 2026 test builds are in the release notes.
Feature availability
Both builds include the same features.
| Workflow or controls | Beta builds |
|---|---|
| Attach, launch, results, and session reopen | Included |
Terminal: views rail with Health first, graph checks, : palette, 256-colour fallback | Included |
Terminal live data: sampled received rates, readiness min_hz/max_hz, per-node use_sim_time, launch process exits, recording lanes, Playback seek | Included; seek was checked on Jazzy only |
Results viewer (flightops results --open, Ctrl K) and personal workspace page (flightops workspace) | Included |
Managed launch recording (flightops record), separate collector (flightops record collector), retention (flightops retention) | Included |
| History, knowledge, handoff, sources and evidence commands | Included |
Bounded checks and probes (checks, rank-checks, run-check) | Included |
| Optional AI: API key providers, local OpenAI-compatible servers, ChatGPT account route (preview) | Included; off by default |
Jev evidence priority (flightops ai jev, --jev) | Included; off by default |
License and usage metrics (flightops license, flightops telemetry) | Included; required for the beta |
Scene Workbench (flightops workbench): Replay and Compare of recordings | Included |
| Scene Workbench simulation actions and the reviewed change flow | Source checkout with the developer image only; installed builds refuse them with a reason |
onscope, splashdown, lcc and launchcommit, highbay on PATH | Included |
flightops-mcp, flightops-results, flightops-tui, flightops-service on PATH | Included |
flightschool and its 14 skills | Included |
flightlead coordinator | Included (preview) |
flightops-gym-smoke | Included (research preview); Gym payload campaigns are not |
Offline documentation (flightops docs) and two Nav2 sample recordings | Included |
Lidar and IMU live recipe checks (flightops-tui recipes check), bundled simulation demos (demo/) | Source checkout only |
| Teams publication | Not included |
Check flightops --help and flightops COMMAND --help on your own install before you use an advanced command.
What has been checked
Before release, each beta build is installed in a clean container on the development PC and checked: the installer and flightops --verify, license activation against a local beta service, the installed commands, and the Scene Workbench under a software renderer. The exact checks and results are kept for each build; ask beta@flightops.dev for them. The known limits list what has not been checked, such as first use by an independent person on another machine.