Work with the assistant
Send requests with images, files or picked elements, plan big changes first, answer questions, and stop, continue or rewind a turn.
Updated Oct 18, 2026
Steps
- Pick the agent from the menu at the top of the chat, or keep Designer.
- Name the screen and the outcome; attach images, files, code lines or preview elements.
- For a bigger change, pick Plan and approve its steps and credit range (about 20–60 credits on Standard for a plan that changes one file), or Revise.
- Answer its questions while the turn runs; a question expires when the turn ends.
- Stop keeps the edits that landed, Continue picks up the rest, Rewind undoes the latest turn.
Agents
| Agent | For | Plans |
|---|---|---|
| Designer (default) | Screens, features and the look | Every plan |
| Build | Builds, build errors and store review | Every plan |
| Growth | Launch plans, push campaigns, listing copy, video ads and metrics; usually 3–15 credits a message | Pro and up; one free turn per app on Creator |
Manage App's Growth plan shows on every plan, with no credits: your app's own facts, Apps like yours, Growth loops (Add briefs Designer on one not found yet) and Moments ahead. Growth writes the plan and the Launch kit; Campaign links start on Creator.
Attach context
| What | Limit |
|---|---|
| Images (PNG, JPEG, WebP, GIF): paste, drop or the image button | 4 per message |
| Files: the file button | 6 files, 512 KB in total |
| Code: highlight lines in Code | The selection |
| Preview elements: the pick button, Shift-click for more | 5 per message |
| A Figma design: Import from Figma (the dashboard's + menu, or the Figma button in an app's chat), with the plugin | 12 screens per import on Free, 60 on paid plans. See Build from a Figma design |
Good to know
- Big requests keep a checklist, one line an item: tap an item to see how it is checked. A done item's mark says what proves it (hover it to read, for example, that the assistant tried it in the preview); the line under the list names what only a phone shows (open the share link on it; notifications, the share sheet and haptics need an installed build); open items say why, once in the heading when they share a reason (Not checked yet, Paused for credits).
- Checks the assistant left failing are never yours to supply: the card reads Not finished: checks still fail, and Fix it starts a turn that fixes them.
- A chip to connect a backend or RevenueCat opens Server on its form, never a paid turn. A control the assistant points you to, such as Server, keeps an Open button under its reply.
- Credits a rewound turn used are not refunded. New chat (+) keeps topics apart; the plan sets how many run at once (1 on Free, 2 on Creator, 4 on Pro, 10 on Business), and when two change the same lines the later one asks which to keep.
- The floating assistant (⌘J) answers and opens pages but never edits code: it hands changes to the coding agent once you approve its card.
Related
Did this page help?