Preserved interfaces
The following AeroSpace interfaces are intentionally retained unchanged:| Interface | Details |
| Config file paths | ~/.aerospace.toml and ${XDG_CONFIG_HOME}/aerospace/aerospace.toml are still loaded. FlightDeck additionally looks for ~/.flightdeck.toml and ${XDG_CONFIG_HOME}/flightdeck/flightdeck.toml, which take precedence when present (see Custom config location) |
| Config syntax | All TOML keys, types, and default values are identical to AeroSpace |
| Environment variables | AEROSPACE_FOCUSED_WORKSPACE, AEROSPACE_PREV_WORKSPACE, AEROSPACE_INHERITED_*, and all other AEROSPACE_* variables |
| IPC socket path | Same as AeroSpace |
flightdeck config output | Identical key names and JSON structure to aerospace config |
Distribution differences
These are the current differences between FlightDeck and AeroSpace as distributed applications:| Aspect | AeroSpace | FlightDeck |
| CLI executable name | aerospace | flightdeck |
| App bundle name | AeroSpace.app | FlightDeck.app |
| Homebrew cask | nikitabobko/tap/aerospace | saadjs/tap/flightdeck |
| Codesigning | Not signed (requires manual security approval) | Developer ID signed, notarized, and stapled by Apple |
aerospace CLI alias | Provided | Not provided — use flightdeck |
| Simultaneous installation | — | FlightDeck and AeroSpace should not run simultaneously |
Config option differences
FlightDeck currently has no config-option deviations from AeroSpace. Every option documented in the Config Reference behaves identically to its AeroSpace equivalent.Migrating from AeroSpace
- Quit AeroSpace.
- Install FlightDeck:
brew install --cask saadjs/tap/flightdeck. - Your existing
~/.aerospace.tomlworks without modification. - Replace
aerospacewithflightdeckin any shell scripts or aliases. - Remove any manual AeroSpace security approvals from System Settings → Privacy & Security — FlightDeck is notarized and does not require them.