Skip to content
Flight Plan

Installation

Run Flight Plan with npx:

Terminal window
npx @kidlat-dakila/flightplan@latest

To install it once, run npm install -g @kidlat-dakila/flightplan@latest. After that, start it with flightplan.

The command starts one server on your machine. It serves the web app, its API and the MCP endpoint your agent writes through, and opens the app at http://localhost:24747. The first time, the app takes you through setup.

What you need

Section titled “What you need”
  • Node.js 22 or later.
  • git on your PATH. Flight Plan reads diffs, branches and remotes with it.
  • A way to reach your pull requests. Local git needs nothing, and it’s the default. The GitHub and GitLab command line tools need to be signed in (gh auth login, glab auth login). A token connection needs your system keychain: Keychain on macOS, Credential Manager on Windows, or Secret Service on Linux.
  • A coding agent to explain your reviews: Claude Code (claude), Codex (codex) or Cursor (cursor-agent). Setup asks you to pick one, and offers only an agent whose command it finds on your PATH or in ~/.local/bin.

Options

Section titled “Options”
Usage: flightplan [options]


Starts Flight Plan on this machine and opens it in the browser.
If Flight Plan is already running, it only opens the browser.


Options:
  --port <number>  Listen on this port instead of 24747
  --no-open        Do not open the browser
  -v, --version    Print the version
  -h, --help       Print this help
  • If Flight Plan is already running, the command only opens the browser.
  • If another program is using port 24747, Flight Plan picks a free port, uses it again on later runs, and installs itself into your agents again so they reach it.
  • If you name a port with --port or PORT and it is taken, Flight Plan stops and tells you.
  • The PORT and HOST environment variables set the port and the host. --port takes precedence over PORT.

Where your data lives

Section titled “Where your data lives”

Flight Plan keeps everything in ~/.flightplan/: your settings, your reviews, your chats with the agent and the plugin it installs for Claude. Set FLIGHT_PLAN_DATA_DIR to use another folder. Nothing is written into the repositories you review.

Forge tokens are not stored in that folder. They go into your system keychain, and Flight Plan never shows them again.

Flight Plan sends data out in two cases only: to your forge when you comment or submit a review, and to a Claude artifact when you publish a review.