Take over at any point
AI edits the same project you do. The tables, Actionflows, pages and permissions it creates are exactly the same kind of thing you would have created by hand — there is no “the AI’s copy” and “the one you can edit”.
That means:
- No handoff. Wherever AI stops, you carry on from there. Nothing to export, convert, or move into another project.
- No code to finish the job. Changing a field’s type, reordering nodes, rebinding a component — all of it is done by clicking in the editor, the same way you would build normally.
- Not just the last stretch. Anything is editable, including the core structure AI has just finished.
How to take over
Change one detail — edit it in the relevant editor. You do not need to tell AI first.
AI is working and heading the wrong way — click Stop at the bottom right of the composer, or press Esc while the cursor is in it. Stopping discards any queued messages it has not picked up yet; messages it already picked up stay in the conversation. Once it stops, look at what the turn actually created (see Read what AI built) before deciding whether to edit by hand or describe it again.
Carry on after editing — just send another message. You do not need a new session.
After the data model, Actionflows, APIs, permissions, secrets, or AI Agents change, the backend has to be synced before what runs online is the new schema. AI Copilot can sync it itself, in sessions whose editable scope is Project.
When doing it yourself is faster
AI is good at laying out structure in one go — planning a set of tables, orchestrating a business process into an Actionflow, building a page skeleton from a description. These are usually quicker by hand:
- changing one specific value: a font size, a color, a field’s default;
- nudging spacing and position;
- editing one parameter on a node you are already looking at.
Describing it means explaining where it is, and you are already looking at it.
What it cannot change
A session is bound to the one app you have open, and what it can change depends on whether that app carries an editable server schema. A client app in a multi-client project, or a session with app-level access only, can build the frontend but cannot change backend configuration. See The limits of a session.