Set up optional AI · flightops

Flightops starts in Standard mode. You can use attach, launch, diagnostics, and saved results without an AI account or provider connection. AI setup is a separate action.

Prerequisites

Install Flightops. For OpenAI or Anthropic, have an API key. The wizard fetches the models available to that key. A local OpenAI-compatible endpoint does not need an API key.

1. Open setup

bash

flightops ai setup

Choose ChatGPT account (preview), OpenAI API, Anthropic API, or a local/custom model. The menu also has Continue without AI. You can open the same setup from the terminal app by pressing A, then C.

The ChatGPT account path uses the pinned official Codex runtime and needs Linux bubblewrap for isolated text turns. Install it with sudo apt install bubblewrap if Flightops reports it missing. The wizard can install the pinned Codex runtime and open browser sign-in. If you skip sign-in, run flightops ai login later. A saved account or successful login does not establish that the assistant works; run the connection test below. This preview path handles reviewed text and evidence only. It cannot run native Codex tools.

For OpenAI or Anthropic, enter the key at the masked prompt. Flightops makes a bounded request to that provider's model-list API, displays candidate assistant models, and asks for a model number. It saves the selected connection only after you choose a listed model. The model list confirms access to the list; the separate connection test checks an assistant response.

Flightops saves the key in the OS credential store when one is available. If there is no supported credential store, it keeps the key for this session and opens the app immediately. Press A, then m there to enable AI. The key disappears when that process exits. Local/custom and Gemini setup remain under the advanced menu, including an environment-variable reference option.

2. Check the connection

For a saved account, API, or local connection, run:

bash

flightops ai status
flightops ai test

status reads local configuration only. test makes one explicit provider request with a synthetic greeting. It may incur provider usage; it does not send project files. For ChatGPT, sign in before the test. A saved connection alone does not prove that a model is available. If you chose a session-only key, stay in the app that the wizard opened. That key is not available to a separate ai test process.

3. Use or disconnect it

For a saved account, API, or local connection, open Flightops with AI enabled:

bash

flightops --ai

In the app, press A for the assistant panel. If you used a session-only key, use the app opened by the setup wizard and press A, then m to enable AI in that session. Provider actions require their own review in the app.

To remove the selected connection:

bash

flightops ai disconnect

Optional evidence priority with Jev

Flightops can ask Jev to prioritize a supplied receipt before your assistant explains the evidence. Jev is separately configured and each provider request has its own disclosure review. Setup does not enable it for ordinary assistant requests, and the panel workflow does not call Jev.

Follow the Jev tutorial for flightops ai jev setup, select-evidence, and ask --jev.

Next steps

Follow using the assistant to attach evidence and ask your first question. The AI section covers connections, credentials, troubleshooting, and current limits.