Know what the planning model will see.

Bad plans usually start with the wrong context. ProPR shows the files, summaries, screenshots, attachments, and reference repositories that will shape the plan before generation starts, so the team can adjust the input before code changes expose the mistake.

The context preview with eleven selected implementation files, relevance scores, and context controls.
The context preview names every selected file before plan generation.

Feature overview

Start from the prompt

The preview uses the chosen branch, prompt, attachments, manual file choices, exclusions, and any file references named in the prompt.

Find likely files

ProPR suggests files that appear relevant; you review and adjust the selection before planning.

Fit the useful context

If the repository is large, ProPR prioritizes the most useful files and warns when the prompt is getting too big for the selected model.

Add supporting material

Add repository summaries, screenshots, attachments, and reference repositories when they help the model understand the task.

Refresh or export

Refresh the preview when inputs change, or export it to inspect exactly what will be sent into planning.

Controls

Change selected files, excluded files, attachments, supporting repositories, and model choice before generation.

Signals

The UI shows included files, warnings, size estimates, cost estimates, and whether the preview needs a refresh.

Large repositories

When a repository is too large to include everything, ProPR keeps the priority paths and leaves lower-value files out.

Reference repositories

Include additional repositories as examples or background without making them the target of the implementation.

Reuse

When the prompt, branch, files, and attachments have not changed, ProPR reuses the existing preview.

Why it matters

Planning errors usually start with wrong context. ProPR makes the context boundary visible in the planning workspace before implementation begins.