Open-source project

Preflight Scout: focused checks before release.

It starts from the diff, finds the affected flows, and collects screenshots, traces, and browser errors. You review the plan before the browser runs.

Preflight Scout showing a failed browser check with its evidence

A CLI, a browser runner, and a report.

Preflight Scout installs from npm and works with Codex or Claude Code. The repository, website, and documentation are public.

It is still a public alpha. Use it on local, preview, or staging environments with test accounts and human review before release.

The diff is the starting point.

The analysis identifies affected routes, APIs, roles, and flows. Browser rules, credentials, and risky actions are not left to the model.

01

Focused analysis

Input
The diff between the base branch and the change being checked, plus a bounded repository index.
Output
An ordered list of affected areas, manual checks, and browser missions.
02

Approved browser checks

Before the run
Missions are reviewed, and risky actions require separate approval.
During the run
The browser stays on the approved origin. A blocked or failed check stays in the report.
03

Saved output

Files
Screenshots, traces, console and network errors, and final observations.
Report
Markdown, HTML, JSON, and optional PDF. A useful check can become a Playwright test.

What I built.

I handled product, architecture, implementation, documentation, and release.

  • Product and architectureConfiguration contract, change analysis, LLM providers, and the review flow.
  • CLI and integrationsInstallable commands, Codex and Claude Code skills, a GitHub Action, and MCP integration.
  • Browser and reportsPlaywright sessions, boundary checks, evidence handling, and Markdown, HTML, JSON, and PDF reports.
  • Open-source releaseVersioned npm packages, a public repository, documentation, licensing, and a dedicated website.

The website, source, and report are public.

The example report uses a synthetic app. It shows the output format, not a customer case.

The same approach applies to a feature or release in an existing codebase.

I can enter a codebase, understand what changes, and carry the work through release.

Tell me about the project