Skip to main content

​
Overview

For complex changes that span multiple files, Plan Mode keeps you in control. Parsaa analyzes the work, proposes a step-by-step plan, and executes only after you approve. Nothing runs without your explicit consent.
During the planning phase the agent works read-only — it gathers context but does not modify your project until the plan is approved.

​
How It Works

1

Analyze

Parsaa reads the relevant parts of your project to understand the architecture, files, and relationships involved in your request.
2

Design

Parsaa proposes a plan: the specific steps it will take, which files change, and in what order.
3

Approve

You review the plan before anything runs. Approve it, ask for changes (revise), or reject it.
4

Execute

Once approved, Parsaa runs the steps one at a time. Exactly one step is in progress at a time, and you can stop execution at any point.

​
Plan & Step Status

A plan moves through these states, surfaced in the activity tray:
Plan statusMeaning
Awaiting ApprovalPlan proposed; waiting for your review
ApprovedYou approved the plan
ExecutingSteps are running
CompletedAll steps finished or skipped
RejectedYou rejected the plan or requested changes
CancelledYou stopped execution mid-run
FailedAn unrecoverable error occurred
Each step is tracked individually: pending → in progress → completed (or failed / skipped).

​
When to Use Plan Mode

Multi-file Refactors

Rename a protocol and update all conforming types, or restructure how data flows between layers.

New Features

Add a feature touching models, views, view models, and networking — Plan Mode maps out every change.

Architectural Changes

Introduce a coordinator pattern, restructure module boundaries, or adopt a new framework.

Pattern Migration

Convert delegate-based APIs to async/await, or replace singletons with dependency injection.

​
Safety

Every plan requires explicit approval before Parsaa writes any code. You see what will change and where.
During execution you can cancel. Already-applied steps stay in place for you to review.
Code changes surface as diffs in an approval card before they’re applied, so you confirm each edit.
For single-file, scoped edits, capture the Xcode selection and ask directly — see Capture Code & Context. Use Plan Mode when a change touches multiple files or needs coordinated edits.