Flightops is in beta (0.2.0b1) for invited ROS 2 teams. This page says what the beta includes, how to get access, what it asks of you, its known limits and where to send feedback. The release notes list what changed.
What is in the beta
Two archives, one per platform, each with every tool below:
- Ubuntu 22.04 with ROS 2 Humble (Python 3.10), x86_64
- Ubuntu 24.04 with ROS 2 Jazzy (Python 3.12), x86_64
| Tool | Status | Guide |
|---|---|---|
flightops: terminal, launch, doctor, results, recording, history, retention, optional AI | beta | user guide |
flightops workbench: Scene Workbench desktop app (Replay, Compare) | beta | Scene Workbench |
onscope, splashdown, lcc, highbay | beta | component tools |
flightops-mcp, flightops-results, flightops-tui, flightops-service | beta | command reference |
flightschool: 14 ROS 2 skills for coding agents | beta | flightschool (source repository) |
flightlead: coordinator directory for coding agents | preview | flightlead (source repository) |
flightops-gym-smoke: one local Gym task in a KVM guest | research preview | Gym (source repository) |
Offline documentation (flightops docs --open) and sample recordings | beta | documentation |
Teams publication is not part of the beta.
Get access
- Register at beta.flightops.dev/register.
- Open the confirmation link in the first email within 48 hours.
- The second email holds your license key and the install link.
- Install the archive for your Ubuntu version.
- Activate this device with
flightops license activate.
One key works on 3 devices. A device is one user account on one machine.
What the beta asks of you
- Usage metrics are required. Installed builds send which tools and subcommands run, their outcome and duration, license events, and the Flightops, Ubuntu, Python and ROS 2 versions. They never send arguments, paths, ROS names, recordings, evidence, logs, AI content or code.
flightops telemetry showprints exactly what is queued. Details: privacy notice. - An internet connection now and then. Activation needs the internet once. The license renews in the background and stops working 37 days after its last renewal.
- Feedback. Tell us what failed, what was unclear and what you expected instead.
Known limits
Platforms and access:
- Only Ubuntu 22.04/Humble and Ubuntu 24.04/Jazzy on x86_64. No ARM64 archive, no PyPI packages.
- Activation needs the internet; offline activation is not supported. Every beta license ends on 31 March 2027.
- The beta archives were installed and checked in clean containers on the development PC. A first use by an independent person on another physical machine has not happened yet.
Hardware and simulation:
- Real-hardware execution stays blocked. The HIL GO/NO-GO ritual always refuses motion.
- Cross-architecture builds are blocked. The Jetson compatibility table of
onscope doctor targetis not verified on hardware. - Replay is open-loop: it checks responses to recorded inputs, not how a changed robot would move afterwards.
- The behaviour workflows have no clearance or latency extractors yet.
Scene Workbench:
- The scene is 2D and draws no map layer.
flightops workbenchopens recordings read-only (Replay and Compare). Imported recordings are labellednot_judged, and Live is not available for them.- Simulation actions and the reviewed change flow need a source checkout and the developer image; installed builds refuse them with a reason.
- Tested on an X11 desktop with an NVIDIA RTX 3080 and under Xvfb with Mesa. Wayland, integrated graphics and screen readers are untested.
Terminal and recording:
- Playback seek was checked on Jazzy, not yet on Humble.
- Declared launch-readiness checks passed fixture and container tests; a trial on a native Humble or Jazzy host is still open.
- Recording limits (bytes, duration, reserve) are polled, not kernel-enforced quotas, and have not been accepted under sustained high-rate load.
AI, agents and research tools:
- Live exchanges through the ChatGPT account route (preview), the OpenAI API and the Jev provider were not accepted for this beta.
- flightlead (preview): full headless completion through a coding-agent harness is implemented but not yet validated.
- Gym (research preview): a local smoke run only. Payload campaigns are not included, and Gym makes no claim of isolation between hostile tenants.
Feedback and support
Write to beta@flightops.dev. Include:
- the exact command and what you expected,
- the error text or a screenshot,
flightops --version, your Ubuntu version and ROS 2 distribution.
Do not send license keys, credentials or customer recordings. Report security problems as described in security (source repository).
When the beta ends
Every beta license ends on 31 March 2027. After that date installed beta builds refuse to run commands. Data on the beta service is kept and deleted as the privacy notice says.