Plans & approval

Generate a plan

A local plan lists resources and artifact counts, sizes, and digests without uploading source files or making network requests. It does not compare remote infrastructure state.

Pass the path to your infrastructure file, whether it lives at the project root or in a folder such as .ai/. Run it after changing the file, and use the output to understand the proposed changes.

Ask the right questions

Before approving, check which applications and resources are involved. Pay particular attention to changes that affect persistent data, secrets, or an existing application.

If the plan differs from what you intended, update the infrastructure and generate a new plan.

Make approval explicit

When working with an agent, give it a clear stopping point: explain the plan, then wait.

Approval should apply to the plan you have actually reviewed. If the configuration changes afterward, review it again before deployment.