NeuralCodeDOCS
Core workflow

Preflight checks

When several workspaces are finished, the hard part isn't each change on its own — it's whether they still work once they're all merged. Preflight ✈ answers that before you touch your base branch.

NeuralCode
Preflight3 workspaces ready to merge Re-run
fix-test-bug
Merges clean. 42 tests pass.
Merge
add-dark-mode
Merges, but 2 tests fail afterward.
Fix with agent
refactor-auth
Conflicts with fix-test-bug in src/auth.ts.
Review overlap
Combined run — all three together
Fine alone; together checkout.spec.ts fails. Catches “breaks together”.
running…
Preflight: a streaming traffic-light verdict per branch, plus a combined run, with one-click actions.

When it appears#

Preflight shows up in the sidebar automatically when two or more workspaces are done. Open it and it runs a safety pass over every ready branch without disturbing your working worktrees.

What it checks#

Each ready branch is merged into an isolated copy of the base branch — never your real one — so Preflight can answer three questions safely:

CheckWhat it tells you
ConflictsWhether the branch merges cleanly, or collides with another ready branch.
TestsWhether your project's tests still pass after the merge.
Combined runWhether all the branches together still pass — catching changes that are “fine alone, broken together.”

Plain-English verdicts#

Results stream in live as traffic lights, so you never wonder what a raw git error means:

VerdictMeaning
🟢 ReadyMerges clean and tests pass — safe to merge.
🟡 CautionMerges, but tests fail afterward.
🔴 BlockedConflicts with the base branch or another ready branch.

One-click actions#

For each result, Preflight offers the obvious next step:

ActionWhat it does
MergeMerges a green branch into the base — same path as Commit, push & merge.
Fix with agentStarts an agent in that workspace, pre-filled with the failing output so it can get straight to the fix.
Review overlapShows the two branches that collide so you can decide how to reconcile them.
Run it before a merge train
Preflight is most useful right before you merge a batch of finished work. The combined run is the one that saves you: two changes can each be perfect and still break the suite when they land together.
Note
Preflight only ever merges into throwaway copies. Your branches and base branch are untouched until you explicitly click Merge.