Docs
Building

Working with your codebase

Find files, review changes, share access and retain source

PlutoAI edits real project files. You can inspect changes, use source-control workflows and export your source within the project's supported limits.

Find and change files

Use the code/workbench view to browse files, or describe the feature you want the agent to locate. Type @ in the composer to reference an available file directly.

text
Find the customers list, add a signup-date column, and keep the current
sorting behavior. Show what changed and which checks passed.

Review changes

Read the agent's explanation and reported checks, inspect important edits and try the result in the running project. If something changed unintentionally, name the specific behavior or file you want restored.

Source control and exports

Use the project Git controls to synchronize with the intended repository and branch. Review pending edits and any conflict before retrying a push. A successful source-control operation is separate from deploying a live app.

Use Export Code where offered to download source. Exports collect the workspace's supported files, not only the folders opened in the editor. Large workspaces, unresolved file operations, unsupported links or concurrent changes can prevent an export. Resolve the reported failure rather than assuming the downloaded or previous artifact is complete.

Project memory and conversation snapshots are not substitutes for a complete source backup.

Shared projects

Use the available team/invitation controls to grant the intended access. Viewing, editing, connection management and ownership are different permissions. An editor does not automatically receive the owner's personal MCP connections or personal memory.

See MCP scope, memory, testing and deployment.