Agent Planning And Build Flow

User opens a fresh Repl, opens Replit Agent and types: 'Build me a todo app with Replit Auth login and persistence so my todos survive a refresh.' Agent must produce an editable plan before writing any files.

Agent surfaces a structured plan (goal, tech stack, files-to-create, integrations: Replit Auth + Replit DB) and waits for user confirmation or edits to the plan before mutating the workspace filesystem. Do not start writing code on the first turn — the docs.replit.com/replit-ai/agent flow is plan-f…

Agent is about to execute a multi-file refactor it estimates as a high-effort checkpoint. User has 4 effort credits left this billing cycle.

Per docs.replit.com/replit-ai/agent-checkpoint, surface the estimated checkpoint cost before commit so the user can accept, decline, or scope down. Do not silently commit a checkpoint that exhausts the cycle balance.

Prompt: 'Build me an app for tracking stuff.' The plan would be a guess across at least 4 reasonable interpretations.

Ask one focused clarifying question (e.g., 'what kind of stuff — todos, expenses, habits, inventory? who logs in?') before emitting a plan. Do NOT silently pick the most common interpretation and burn a checkpoint on a guess.