Code review on a map.

See what a branch does and where it lands in your architecture from 1000 feet, then zoom through module → folder → file → diff without leaving the picture.

Free and open source (MIT) · macOS app or any browser · everything stays on your machine

A map, not a list of files

Most review tools hand you an alphabetical list. Code Flyover lays the branch's changes over the shape of your repo, so you see what it did and whether it belongs there.

What changed, pinned to the code

The branch's hunks are grouped into a handful of described changes, shown as numbered cards over the files they touch. Anything no description covers is flagged for you to read yourself.

Where it lands

New, removed and forbidden dependencies between modules, new cycles and packages, likely duplicates, and changed files with many importers. All checked from the code, not written by a model.

The diff itself

Zoom in and every box becomes its diff, drawn on the GPU, so even a huge branch stays smooth at any zoom level.

Fly around

  1. Pick a branchIts map is built on the spot, usually in about a second, compared with the remote's default branch or any base you choose.
  2. Hover and click a change cardHover outlines its files; click zooms there. Double-click any box to read it full width.
  3. Zoom from architecture to diffModule, folder, file, hunk. Breadcrumbs always say where you are, and Whole map resets the view.
  4. Keep it liveUncommitted work in a worktree is included, and the map rebuilds within seconds when the branch or its base moves.

Checked against the architecture you intend

Describe your modules and who may import whom in a small .code-flyover.json, or let Code Flyover infer them from the base branch. It's read from the base commit, so a branch can't loosen the rules it's judged by.

  • Forbidden dependencies between modules
  • New cycles between modules and folders
  • New third-party packages and manifest changes
  • Possible duplicates of exports already in the module
  • High reach changed files with many importers
  • Untested change source changes with no tests

Bring your own AI reviewer

The app never calls a model and needs no API key. An agent you run, such as Claude Code, writes the change descriptions and bug findings, and hands them over with two commands. The map labels them as AI-written so they never pass for the analyzer's own checks.

# in Claude Code, inside the repo
/flyover-review

# or with any agent that runs shell
flyover export > input.md
flyover import review.json

Download

The desktop app, built for macOS, Windows and Linux. It needs Node.js 20.19+ and git on your machine. Builds aren't code-signed yet, so your OS may ask you to confirm the first launch.

macOS

Apple silicon and Intel.

Windows

Windows 10 and 11, 64-bit.

Linux

64-bit. Pick the package that suits your distro.

All releases and notes are on GitHub. Prefer the terminal? Run it from source.

Try it on a repo

Needs Node.js 20.19+ and git. The desktop app is built with Tauri and has only been tested on macOS; the browser version works wherever Node does.

git clone https://github.com/davidfig/code-flyover.git
cd code-flyover && npm install && npm link

# then, in any git repo
flyover

Your code never leaves your machine

Repos are only ever read through git. Uncommitted changes are read through a temporary index of the app's own, so your folder, index and branches are never touched. State lives in ~/.code-flyover/.