Docs
Quickstarts

How Pluto works

What happens when you send a request to the AI coding agent, in plain language

Here is what happens between the moment you send a request and the moment your app updates. Understanding the loop helps you know what to expect and when to step in.

The build loop

When you send a request, PlutoAI works in a loop:

  1. It reasons about the request

    The agent works out what you are asking for and what it needs to change, reading the relevant parts of your project first.

  2. It makes the changes

    It writes and edits code across your project's files and runs any commands the work needs.

  3. It checks its own work

    The agent selects checks for the project and the requested change. Review the reported results, including any checks that failed or could not run. A preview loading is only one part of verification.

You can follow along as it works, and the live preview updates so you can see the result.

What you see while it works

A build is not a black box. As the agent works, you see its plan, the files it writes and edits, and the commands it runs, along with a short explanation of what it changed and why. That record is what lets you review a change instead of taking it on faith. See Working with your codebase.

When it hits an error

If the agent hits an error, it uses the available evidence to investigate. Some operations can be retried; an uncertain external write may need its remote state checked first. A run can stop because of an error, a budget or runtime limit, or a missing decision. Review the reported outcome before continuing. See Troubleshooting.

Large builds

Large requests may need several runs. Give clear acceptance criteria, review intermediate results, and use a goal or automation when appropriate. Context, credits, runtime availability and execution limits still apply; an interrupted run is not a completed build.

You stay in control

At decision points the agent pauses and asks you before continuing, then resumes once you answer. See Agent approvals. It only uses a service once you have connected it, and it explains what it changed in the conversation, so you always know what happened.

Next steps