Know what the planning model will see.

Bad plans start with the wrong context. Before generation, ProPR shows every file, summary, screenshot, attachment, and reference repository that will shape the plan, so you fix the input before it becomes a bad commit.

The Define step's context panel: Scope at 60% and eight courier-app files ranked by relevance, led by the upload queue and the proof-of-delivery screen — The context preview names every selected file before plan generation.

Starting a plan on courier-app/main: the request in plain words, step 1 of 3

Start from the prompt

The preview starts from your branch, prompt, attachments and any files the prompt names.

Included Context (8 files): the courier-app files the planner will read, ranked by relevance, led by uploadQueue.ts and ProofOfDelivery.tsx

Find likely files

ProPR suggests the relevant files. Add or exclude any before planning.

Context Scope at 60%, between Focused, Expanded and Full Scan: a dependency-graph scan with a budget of up to 588k tokens

Fit the useful context

In a large repository, ProPR keeps the most useful files and warns before the prompt outgrows the model.

Two indexed repositories, orders-api and storefront-web, added to a plan as reference only: all implementation stays in the target repository

Add supporting material

Add repository summaries, screenshots, attachments, and reference repositories whose patterns the plan should follow.

The token bar after a context refresh: 94k of the 588k-token budget used (16.1%), with the estimate for generating the plan and a refresh button

Refresh or export

See size and cost estimates, refresh when inputs change, or export the preview to inspect exactly what planning receives.