Working with your codebase
See and find your files, understand what changed, and keep control of your AI-built project
PlutoAI writes standard source code organized into normal project files and folders. You describe the outcome you want, the agent handles the files, and you can always see and understand what it did. This page covers how to see your code, find the right file, understand changes, and stay in control.
Seeing your files
The agent creates and edits real project files, and you can see the files it works with. Nothing is hidden inside a format only PlutoAI can read. Because it is standard source code, you can export the full source as a zip anytime and save it to GitHub. See Deploy your app for both.
Finding the right file
You do not need to know the file layout to make a change. Describe the feature or the screen, and the agent locates the relevant code.
Find the page that shows the list of customers and add a column for the signup date.
If you already know the file, name it directly.
In the pricing page, change the annual discount from 10% to 20%.
Understanding project structure
A project usually contains source files, which hold the code for your pages and features, and configuration files, which control how the project builds and runs. To understand how your project is organized, ask the agent to explain it in plain language rather than reading the files yourself.
Understanding what changed
When the agent makes changes, it explains what it changed and why in the conversation, and it shows the files it touched as it goes. The live preview updates at the same time, so you can read the explanation and check the result together. See Preview and test.
If you are not sure what a change did, ask. The agent can walk you through the part of the project it just edited in plain language, without you needing to read the code yourself.
Keeping control
At decision points the agent pauses and asks you before continuing, so consequential steps do not happen behind your back. See Agent permissions.
A few habits keep you firmly in control as the project grows:
- Change one thing at a time so each result is easy to check.
- Name what should stay the same, not just what should change.
- Confirm each change in the preview before you ask for the next one.
If a change touched more than you expected, tell the agent what should not have changed and ask it to restore that part. If a change broke something that worked before, ask it to fix or undo the last change. See Troubleshooting.
Your code goes with you
Because every project is standard source code, you are never locked in. Save it to GitHub to keep a full history, or export the source as a zip and host it anywhere. See Deploy your app.