{"slug":"work-with-the-assistant","title":"Work with the assistant","summary":"Send requests with images or files attached, answer the assistant's questions, stop or undo a turn, and keep several conversations on one project.","body":"The chat is where most of the building happens. Each message you send starts a turn. The assistant reads the project, writes files, checks its work in the preview, and reports what it changed.\n\n## Send a request\n\nType in the message box and send. Be specific about the screen and the outcome. See [Write better prompts](/docs/writing-prompts).\n\n## Attach context\n\n| Attachment | How | Limits |\n| --- | --- | --- |\n| Images | Paste, drag and drop, or use the image button. PNG, JPEG, WebP, or GIF. | Up to 4 per message |\n| Files | Use the file button to attach source or config files. | Up to 6 files, 512 KB in total |\n| Code selection | Highlight lines in **Code** and send them with your request. | The selected lines |\n| Figma | **Import from Figma** in the message box. | See [Import from Figma](/docs/figma) |\n\nScreenshots are the fastest way to show a layout you like or a bug you see.\n\n## When the assistant asks a question\n\nSometimes the assistant stops to ask before it continues: when a requirement is unclear, when two requests conflict, or when a choice is risky. The question appears in the chat with options, and sometimes a text field.\n\nAnswer while the turn is running. Once the turn has ended, the question expires and the controls are disabled. Send a new message instead.\n\n## Stop a turn\n\nPress **Stop** in the message box. Edits that already landed are kept, and the preview returns to you. Send a follow-up to continue or change direction.\n\n## Undo\n\nThe most recent turn that wrote files shows an **Undo** button next to its list of changed files. Undo restores the project to the revision before that turn. You can undo several turns, one at a time. See [Revisions and undo](/docs/revisions).\n\n## Next-step suggestions\n\nAfter a turn, the chat may offer chips for work that is still open, such as connecting a backend. Picking a chip fills in the message box. Review it, add the details it needs, and send.\n\n## Conversations\n\nA project can hold several conversations. Use them to keep separate topics apart, such as design polish in one and payments in another.\n\n- Start a new conversation with **New chat** (the + button) in the chat header.\n- Double-click a conversation to rename it. Press Enter to save or Escape to cancel.\n- Delete a conversation with its trash button. The project's source is not affected.\n\nThe plan limits how many conversations can run at the same time in the organization. When two run together, their changes merge. See [Revisions and undo](/docs/revisions).\n\n> [!WARNING]\n> Do not paste API keys, tokens, or passwords into chat, even as placeholders. Add them under [Connections](/docs/connections). The assistant will ask you to add a missing credential there.","sectionSlug":"build","sectionTitle":"Build your app","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"the-workspace","title":"Tour the workspace"},"next":{"slug":"writing-prompts","title":"Write better prompts"}}