FlightStack CLI — overview

CLI overview

The FlightStack CLI is the terminal-side surface for the whole product. It runs the same APIs the dashboard uses, plus a handful of agent-side commands that exist only on the CLI (installation, the upgrade flow, the doctor).

Installation

# macOS / Linux (Homebrew)
brew tap voostack/flightstack-cli-tap && brew install flightstack

# Linux / macOS (one-liner)
curl -fsSL https://get.flightstack.dev | bash

# Windows (PowerShell)
Invoke-WebRequest -Uri "https://github.com/voostack/flightstack-releases/releases/latest/download/flightstack-windows-x64.zip" -OutFile "flightstack.zip"

See the installation guide for verification and uninstall instructions.

Basic usage

flightstack <command> [subcommand] [options]

Getting help

flightstack --help              # all commands
flightstack agent --help        # subcommands of a command
flightstack agent start --help  # flags for a specific subcommand

Command groups

Auth & session

login · logout · config · doctor · update — see Authentication.

Build agents

flightstack agent <subcommand> — register, start, stop, status, install, doctor, upgrade. See Agent commands.

Repositories

flightstack repo --list · --available · --connect · --sync · --disconnect. See Repository commands.

Pipelines & runs

flightstack pipeline lint <file> · flightstack logs <run-id>. See Pipeline commands.

Full command reference

Command	What it does
`flightstack login`	OAuth login through your browser
`flightstack logout`	Sign out and clear local credentials
`flightstack config`	Show or change CLI configuration
`flightstack doctor`	Diagnose CLI environment issues (Flutter, Dart, Xcode, network)
`flightstack update`	Manually update the CLI binary
`flightstack status`	Quick status of your account, agents, and recent builds
`flightstack org`	List and inspect organizations you belong to
`flightstack repo [flags]`	List, connect, sync, or disconnect connected repositories
`flightstack workflow`	List and inspect workflows (legacy pipeline definitions)
`flightstack pipeline lint <file>`	Validate a pipeline YAML file against the FlightStack spec
`flightstack logs <run-id>`	Print or tail logs for a pipeline run
`flightstack build`	Inspect build history and individual build runs
`flightstack template`	Browse marketplace templates
`flightstack publisher`	Manage publisher profile (for those who ship marketplace steps)
`flightstack agent list`	List build agents on your account
`flightstack agent show <id>`	Show details for an agent
`flightstack agent register`	Register this machine as a build agent
`flightstack agent start`	Start the agent (foreground or daemon)
`flightstack agent stop`	Stop the running agent
`flightstack agent status`	Local agent status (PID, log path)
`flightstack agent install`	Install as a startup service (launchd / systemd)
`flightstack agent uninstall`	Remove the startup service
`flightstack agent update <id>`	Update an agent’s server-side settings (name, org)
`flightstack agent upgrade`	Upgrade the agent binary to the latest release
`flightstack agent delete <id>`	Delete / unregister an agent
`flightstack agent doctor`	Diagnose agent-side issues (service, binary, PID, API connectivity)

Global options

Flag	Description
`--help`, `-h`	Show help for the current command.
`--verbose`, `-v`	Enable verbose logging.
`--version`	Print the CLI version (no abbreviation).

Auto-update

CLI

The CLI checks for updates daily and self-installs when autoUpdate is enabled (default: enabled). Toggle:

flightstack config --auto-update true   # opt in
flightstack config --auto-update false  # opt out
flightstack update                      # manual check now

Agent

The build agent ships separately. Upgrade the agent binary explicitly with:

flightstack agent upgrade           # install latest
flightstack agent upgrade --check   # check only

If you registered the agent as a service, restart it after upgrade:

flightstack agent stop && flightstack agent start --daemon

Configuration files

All CLI state lives in ~/.flightstack/ (macOS / Linux) or %USERPROFILE%\.flightstack\ (Windows). See CLI configuration for the file layout, fields, and supported environment-variable overrides.

Next steps

Authentication — login, logout, config, doctor, update
Agent commands — register and run a build agent
Repository commands — connect a repo from the terminal
Pipeline commands — lint YAML, tail run logs
CLI configuration — what’s on disk and how to override it