PIES Studio 1.9 · Documentation
Build with AI turns one description, such as a CRM with contacts, companies, teams and tasks, into a complete application: its tables, its functions, its screens, a home page and a menu. This page covers what happens during such a build, what you see while it runs, and how long to expect it to take. For a single screen or a single change, ask PIES AI in the chat instead; see How PIES AI works. To build screens from a Figma design, see Import a Figma design.
PIES AI first plans the application from your description, then builds it in phases, each phase finishing before the next one starts:
Inside a phase, several units run side by side.
Each generated screen goes through the same design path as a screen you ask for in the chat. A table's list, form and detail screens start from a working layout bound to the table, and are then designed: a header, the content grouped into labelled sections and cards, the form's Save and Cancel buttons kept with their events unchanged, and the app's own theme colours. The design is then judged against the same design standard the chat uses, and a screen that falls short is repaired before the build moves on. The home page and the menu are built the same way, from the application's data model.
What you asked for is kept. When your description asks for a filter on a screen, such as an approval queue filtered by status, the screen gets a filter bar. The same holds when you change a screen in the chat: asking for a search box and status filter above the task list on a screen that already has that table adds a search box and a status filter to the table, not a data-entry form with a Save button. When it asks for an Add button, such as a button to add a customer, the button opens a form for adding that record, and the build creates that form if it would not otherwise exist. Detail screens are built before their list, so selecting a row opens its detail screen.
So a screen from a whole-app build should look like a screen you asked for one at a time. If one does not, select it and ask PIES AI to redesign it; it changes only that screen.
The built-in user and role tables belong to PIES Studio, so a build never adds your own columns to them. When your description asks for details about each user, such as a job title, phone number or avatar, PIES AI creates a separate profile table linked to the user (for example user_profiles, with a user_id that points to the user) and puts those fields there. Your screens then read and save the profile through that table.
Your screens can still show the built-in tables. A chart PIES AI builds on them, such as roles by name, plots their rows like a chart on any of your own tables.
Which model builds each unit is decided by your organisation's AI governance policies, and an application can carry its own policy; see Governance policies.
Type delete or remove followed by the name, for example delete zudio_test or delete screen Thematic. PIES AI deletes the screen with exactly that name, or, if there is no such screen, the table with that name; capitals do not matter and names with underscores or other characters work the same way. If nothing has that name, PIES AI replies that it couldn't find a screen or table called that, and nothing is changed. Requests such as delete it or delete everything are not treated as a delete of a named screen or table.
A whole application is a large build, and its time grows with the number of tables. As a guide from our own test builds, a CRM-sized application of around ten tables plans well over a hundred units and takes an hour or more on a cloud model, and several hours on a private model.
You can keep working in Studio while it runs. If the PIES Studio server restarts during a build, the build stops with Interrupted — the server restarted while this loop was running. Everything finished before the restart is kept; start the build again to finish the rest.