Building your app
Build and refine your app round by round with the AI app builder
You build with PlutoAI by describing what you want in plain language. It plans the work, writes code across files, and shows a live preview. You try it, ask for the next change, and the app grows one round at a time.
The build-and-refine loop
Building is a loop, not a one-shot. The best results come from many small, reviewed rounds rather than one giant request.
- Describe what you want
Say what to build or change in plain language: a page, a feature, a fix.
- PlutoAI plans and builds
It breaks the work into steps, writes and edits the code, and runs what it needs to. You can follow along as it works.
- Review in the live preview
The preview updates as the build lands. Click through it and check the result.
- Ask for the next change
Request the next change in the same conversation. PlutoAI continues from your existing project. Workspace availability and recovery state can affect what is available after a long break; review any reconnect or recovery message.
How to structure a build
A reliable rhythm for a new project:
- Start broad. In your first prompt, describe the whole shape: the pages, the main content, and the look. This gives the agent a coherent starting point.
- Then go narrow. Once the shape is up, switch to one focused change per round so each result is easy to review.
- Connect services when you reach them. Add a database, payments, or other tools at the point your app needs them, not before.
What you see while it builds
A build is not a black box. While the agent works you see its progress and the live preview updating. It posts a plan, shows the files it writes and edits, and shows the commands it runs. It reports the checks performed for the requested change. Review those results and test your important user flows; missing or unavailable checks are not proof of success.
When it asks you a decision
The agent pauses and asks when it needs a decision from you, then continues once you answer. Giving more detail up front means fewer of these interruptions. See Agent approvals.
Using your connected tools
When a change needs one of your accounts, the agent uses it as part of the build. A connection gives access within its configured account, scopes and permissions. Describe the intended data or payment changes and review any required approval. Connect what you need first, then describe what you want. See Connecting your tools.
Get better results
Change one thing at a time. Describe the outcome you want, not the implementation. When something is wrong, say exactly what is wrong: "the save button does nothing after I edit a row" is faster to act on than "it's broken." See Prompting.