Beta Free while in beta

Disco: your AI-powered dispatch copilot. Built for humans and AI agents.

Disco lets AI teammates like Grok Bot take action on your flights in plain English. If you already have Grok, Claude Code, or Codex, keep that harness — Disco installs into it. OpenClaw is last; it’s the hardest to get going.

Disco is in beta and free while it is. We’ll charge later — not today, and not without telling you first.

via Grok Bot
Hey Disco, create a flight from KSBA to TNCM tomorrow 9am in N26DS.
Disco
On it — CJ3 won’t make it nonstop. Two fuel stops:
KSBA → KABI → KPIE → TNCM
3 legs · ETD 09:00 PDT · N26DS · filed in Dispatch.
Reschedule that to Tuesday at 10.
Disco
Done. All three legs shifted to Tuesday — first ETD 10:00 PDT at KSBA. Trip sheet updated.

Let's Disco.

$curl -fsSL https://disco.aeronautic.ai/install.sh | bash
Install Disco
Get Started
Teach your bots to Disco — or run it raw from Terminal.
Grok Bot is the host we prefer if you’re starting fresh. Already on Grok, Claude Code, or Codex? Same one-liner — don’t stand up a new stack. Terminal if you want no agent. OpenClaw is last; it’s the hardest to get going.

Grok Bot is the AI teammate we’d rather fly with. It has its own computer, stays signed in, and can install Disco for you. Grab your ForeFlight Dispatch API key at dispatch.foreflight.com/tools/console/keys first — Grok will not take the key in chat. It opens an editor instead.

1

Install Grok Bot and create a Disco teammate

Download the desktop app from the Grok Bot access page (macOS or Windows). It’s also on iOS. Sign in, then create a Bot — name it Disco if you want — and give it one job: flight dispatch.

Grok Bot needs SuperGrok Heavy or Cursor Ultra. Setup takes a few minutes; the official walkthrough is at docs.x.ai/grok-bot/get-started.

2

Send Grok Bot this message

In the Bot conversation, paste this one-liner and approve computer / terminal use when it asks:

> Read https://disco.aeronautic.ai/install.md and install Disco for me. Let's Disco.

Already using Grok in the terminal? Same line works as a one-shot:

$ grok "Read https://disco.aeronautic.ai/install.md and install Disco for me. Let's Disco."
3

Paste the key in the editor Grok opens

Grok will not ask for the Dispatch key in chat. It runs disco setup --editor, which opens a file. Paste the key there, save, and close. In Grok Bot, open Agent Computer if you need to finish the editor. Then ask Grok to save Disco as a skill.

4

Let's Disco

Ask Grok Bot anything flight-related:

> Plan a trip to St. Martin on April 15 in N555DC with Alex

Already living in Grok (local CLI), Claude Code, or Codex? Keep it. The installer drops disco on your PATH and links the skill into ~/.grok/skills, ~/.claude/skills, and ~/.codex/skills. Grab your ForeFlight Dispatch API key at dispatch.foreflight.com/tools/console/keys first.

1

Send your existing teammate this message

Paste this into Grok, Claude Code, or Codex and approve terminal use if it asks:

> Read https://disco.aeronautic.ai/install.md and install Disco for me. Let's Disco.

Local Grok one-shot:

$ grok "Read https://disco.aeronautic.ai/install.md and install Disco for me. Let's Disco."
2

Save the Dispatch key the way that host allows

Grok: do not paste the key in chat. It runs disco setup --editor — paste into the file, save, close. Claude Code / Codex: they may take the key in chat, then run disco setup --api-key. Don’t use interactive disco setup in a PTY.

3

Let's Disco

Ask the same teammate anything flight-related:

> Plan a trip to St. Martin on April 15 in N555DC with Alex

Last option. OpenClaw is the hardest to get going (gateway, WhatsApp or Telegram, JSON wrangling). Use this only if you already live there. Otherwise pick Grok Bot or an existing harness. If you are on OpenClaw, grab your ForeFlight Dispatch API key at dispatch.foreflight.com/tools/console/keys first.

1

Send OpenClaw this message

In an active OpenClaw session, send this one-liner:

> Read https://disco.aeronautic.ai/install.md and install Disco for me. Let's Disco.

Need a teammate first? Don’t start with OpenClaw. Use the Grok Bot tab, or the Existing tab if you already have Grok / Claude Code / Codex.

2

Hand OpenClaw your API key when it asks

OpenClaw will ask for your ForeFlight Dispatch API key in chat, then save it non-interactively via disco setup --api-key. No terminal-paste corruption.

3

Let's Disco

Start a new session and ask OpenClaw anything flight-related:

> Plan a trip to St. Martin on April 15 in N555DC with Alex

For pilots and dispatchers who want Disco directly from the command line. The REPL and one-shot CLI give you faster control than any web UI — and no agent in the loop.

1

Install the CLI

$ curl -fsSL https://disco.aeronautic.ai/install.sh | bash

Drops disco into ~/.local/bin. macOS or any Unix-like terminal.

2

Configure your ForeFlight Dispatch key

Opens the ForeFlight key page in your browser and prompts for paste:

$ disco setup
3

Set a default aircraft (optional)

$ disco aircraft default N555DC
4

Launch the REPL or run one-shot commands

Open the interactive TUI:

$ disco

Or fire one-shots from your shell:

$ disco flights +from tomorrow

Integrates with ForeFlight Dispatch

Full read-write access to your ForeFlight Dispatch account — without opening a browser. List flights by date range, create new flights, update routes and crew, manage passengers and cargo, and release flights for filing.

  • List, create, update, and delete flights
  • Assign PIC, SIC, and cabin crew with weights
  • Manage passenger manifests and cargo loads
  • Release flights for filing (editable or read-only)
  • Fetch performance data, navlogs, and flight documents
  • Multi-leg trip chaining and templates
$ disco flights +from tomorrow +limit 5 # Lists your next 5 flights with crew, aircraft, FBO info $ disco flight release +id abc123 # Releases flight for filing // Or just ask Grok Bot: > What flights do I have tomorrow? > Release tomorrow’s flights for filing. > Show me the manifest for the Aspen flight.

Plan, Update, and Reschedule Flights

One surface for the whole flight lifecycle. Plan a new flight, change a route or aircraft mid-stream, or shift the whole chain when plans change — ETDs cascade across every connected leg and Dispatch stays in sync.

  • Plan a single flight or a multi-leg trip with one command
  • Update any field on existing flights — route, ETD, altitude, tail, callsign, tags
  • Move a single flight to a new ETD with /resched
  • Shift an entire chain — ETDs cascade with the original turn times
  • Override the turn time at any leg (overnight stops, longer ground time)
  • Dry-run mode shows the new schedule before anything is committed
$ disco flight create --from KHOU --to KAPF --etd "7am tomorrow" --tail N123AB # Plans a new flight in Dispatch $ disco flight update abc123 --route "KASE..PUB.J80.TUL..KRVS" # Updates route on existing flight $ disco chain shift abc123 --etd "May 7 9am" --turn-hours 2 # Cascades ETDs across the whole chain // Or just ask Grok Bot: > Plan a flight from Houston to Naples at 7am tomorrow on N123AB. > Change tomorrow’s route to go via PUB and TUL. > Move tomorrow’s flights to start at 11am. > Push the whole Aspen trip back a day.

Door to door planning

Tell Disco where you’re leaving from and where you’re going — addresses, cities, or landmarks, not ICAO codes. Disco picks the right airports for your aircraft, inserts fuel stops, and accounts for ground transportation so you see the full door-to-door time, not just block.

  • Address → airport selection — runway length, customs availability, and FBO options factored in
  • Automatic fuel stops sized to your aircraft, route, and payload
  • Ground legs included — departure drive + arrival drive in the trip total
  • Multi-stop itineraries: "Aspen to Tulsa to Kissimmee to Marathon Key"
  • One natural-language prompt: "Plan a trip from my house in Aspen to the Four Seasons in Nevis next Thursday for two passengers on N555DC"
// What the user says: "Get me from Aspen to Sint Maarten Thursday morning. Two passengers. N555DC." // What Disco builds: Drive 15 min Home → KASE Leg 1 2:45 KASE → KFLL (fuel stop) Ground 0:45 Fuel + customs Leg 2 2:30 KFLL → TNCM Drive 20 min TNCM → Hotel Total 7:15 door to door

Route and Stop Planning

Get real route options between any two airports and let Disco figure out where to stop for fuel. Preferred routes, historically filed routes, airway suggestions, and automatic fuel-stop planning so you don't hand-pick intermediate airports from memory.

  • Preferred and historically filed routes between any pair
  • Airway-based routing suggestions
  • Automatic fuel-stop planning for out-of-range legs
  • Per-segment wind analysis at cruise altitude
  • Fuel burn, block time, and distance from Dispatch performance
$ disco routes +from KDEN +to KJFK # Preferred, filed, and suggested routes $ disco winds +route "KDEN..DBL.J80.JHW..KJFK" +alt FL350 # Wind component per segment, GS, time, fuel // Or just ask Grok Bot: > What’s the best route from KDEN to KJFK in a CJ3? > Pick a fuel stop between Aspen and Sint Maarten. > Compare FL370 and FL410 winds for this trip.

Weather and NOTAM Lookup

METARs, TAFs, area forecast discussions, PIREPs, AIRMETs, SIGMETs, a 7-day hourly outlook, and time-filtered NOTAMs — in one CLI surface. Time-aware queries return the right TAF period or active NOTAM set for the moment you actually care about.

  • METAR / TAF / brief / forecast at any airport
  • PIREPs — turbulence, icing, ride reports along your route
  • Area Forecast Discussions — the human-written synopsis
  • NOTAMs filtered by airport, route, and active-at-time window
  • Time-aware: “weather at KASE at 9am tomorrow” returns the TAF period covering 9am
$ disco weather brief KDEN # METAR + TAF + 7-day forecast in one call $ disco notams KASE KDEN --at "tomorrow 9am" # NOTAMs active at 9am tomorrow at both airports // Or just ask Grok Bot: > What’s the weather at KASE at 9am tomorrow? > Brief me on weather for tomorrow’s flight. > Any NOTAMs at KJFK that affect my arrival? > PIREPs for icing on the route to Naples?

Manage Crew and Passengers

Assign crew, build a reusable passenger roster with passports and addresses, and keep manifests in sync with Dispatch. Perfect for Part 91 operators flying the same people over and over.

  • List and assign crew members (PIC, SIC, cabin crew)
  • Persistent passenger roster with DOB, weight, passport, and address data
  • Per-flight weight-and-balance manifest for one-off weights
  • Passenger readiness check — domestic or international
  • FBO / handler lookup with services, hours, and fuel info
$ disco passenger add --first Alex --last Reed --weight 200 # Adds Alex to the roster, returns slug 'alex-reed' $ disco passenger check alex-reed --intl # Verifies passport, address, DOB for international travel // Or just ask Grok Bot: > Add Alex Reed as a passenger, 200 lbs, DOB Mar 15 1985. > Save Alex’s passport: X12345678, US, expires Jun 2030. > Is Alex ready for an international trip? > Set Smith as PIC and Jones as SIC on tomorrow’s flight.

Trip Checklists and Sheets

Disco keeps a trip sheet for every flight — a living document that ties together the flight legs, passengers, crew, and all the logistics that need to happen before wheels up. Each trip also gets a checklist that guides the AI (and you) through what's left to coordinate, so nothing falls through the cracks.

  • Auto-generated trip sheet for every flight or multi-leg itinerary
  • Checklists tailored by trip type — domestic, charter 135, or international
  • AI reads the checklist to know what to work on next (passports, eAPIS, customs handler, gen dec)
  • disco trip check runs the checklist and reports OK / WARN / FAIL / PENDING for every item
  • Exportable as .md, .html, and .pdf for sharing with crew, passengers, or your ops team
  • Scheduled monitoring runs trip check every 15 minutes until departure and alerts you if anything regresses
$ disco trip check 20260415-ie8a Trip Check: FAIL OK: 3 | Warn: 0 | Fail: 1 | Pending: 7 ✓ Flights in Dispatch — 2 legs ✓ Passenger manifest — 2 passengers ✓ Alex Reed — passport ✗ Alex Reed — abroad address … eAPIS filing — Not filed … Customs handler — Not arranged // Or just ask Grok Bot: > What’s the status of the St. Martin trip? > What’s left to do on trip 20260415? > Watch this trip and alert me if anything regresses. > Send me the trip sheet as a PDF.
Capabilities
Helpful tools for planning flights and logistics.
A unified aviation data layer that works for pilots, dispatchers, and AI agents.

Talks straight to ForeFlight Dispatch

Disco creates, edits, releases, and reshapes flights in your operator account — the way a dispatcher would, but agent-friendly and JSON-first.

✈️

Create & edit flights

disco flight create / disco flight update. Set route, ETD, altitude, tail, callsign, tags. JSON-first so agents can parse the result; --text when a human is reading.

🔁

Reschedule entire chains

/chain shift and /resched. Move a multi-leg trip to a new ETD; turn times cascade through every leg and the table re-renders with the new times in context.

📄

Trip sheets, end-to-end

disco trip plan builds the legs, the sheet, and the paperwork checklist in one call. disco trip check rolls flights, passengers, eAPIS, gen dec, and customs handler into a single pass/fail.

👤

Crew & passengers

Assign PIC/SIC and cabin crew, manage per-flight manifests for weight-and-balance, or build a reusable passenger roster (passport, address, DOB) for international filings.

🧩

Reshape & reuse

Copy a span to a new date with /flights copy, split one trip into two with /flights split, save and re-apply trip recipes with /templates. Recurring trips become boring.

📊

Performance, release, files

Live performance numbers from Dispatch on every edit, one-call flight release, and /files to attach customs decals or gen dec scans directly to the flight.