Bolt Lets Reviewers Click and Comment Directly on AI-Built Apps
Bolt.new adds in-preview commenting so you can click any element, drop a note, and send it straight to the AI agent as a build task.
- Bolt.new adds in-preview commenting: click an element, leave a note, send it to the agent
- Replaces the screenshot-to-Slack-to-prompt loop with direct, element-anchored feedback
- Builds on the existing Select tool that lets users target specific UI elements for the AI
- Comments carry both the instruction and the DOM context of what was clicked
- Useful for design review, QA passes, and non-technical stakeholder feedback
- Available now inside the Bolt editor at no additional cost
Bolt has added element-level comments to its browser-based AI app builder. Reviewers can click an interface element in a project preview, describe a problem or requested change, and route the comment to Bolt’s coding agent as a build instruction. The selected element gives the agent structural context that a screenshot, chat message, or standalone ticket may lack.
Bolt’s preview runs the application, allowing reviewers to navigate flows, submit forms, and test interactions during development. The new comment layer places feedback on that running application, connecting each note to the interface element under review.
From selected element to build task
Bolt already offered a Select tool for directing the agent to a specific interface element from the chat box. Builders can use it to revise text, colors, typography, formatting, and alignment, then inspect the result in the preview. Commenting extends that element-level workflow to reviews by teammates, designers, testers, and clients.
| Tool | Primary use | Result |
|---|---|---|
| Select | A builder targets an element while prompting the agent. | The agent receives a focused edit request. |
| Comments | A reviewer annotates an element in the preview. | The note becomes a contextual build task for the agent. |
The review loop in four steps
- Open the project preview in Bolt.
- Select the element that needs attention, such as a misaligned button, unclear label, or broken form control.
- Write a comment that states the expected behavior or change.
- Send the comment to Bolt’s agent for implementation.
Fewer details lost in handoff
Feedback often reaches a builder through Slack, Linear, shared documents, annotated screenshots, or recorded walkthroughs. The builder must then identify the relevant component, reconstruct the issue, and write another prompt for the agent. Element-level comments can remove much of that translation work by carrying the instruction and its interface target into the build process.
The feature is especially useful during design reviews, interface QA, copy edits, and accessibility passes. A product manager can flag a confusing label, a designer can identify spacing problems, and a tester can attach reproduction details to the control that triggered an error.
Some defects still require more context than an element can provide. Authentication failures, lost data, backend errors, and integration problems may need reproduction steps, console output, network traces, environment details, or production logs. Reviewers should include the expected result, the observed result, and the conditions that triggered the problem when those details matter.
Bolt says commenting is available now and included with existing plans. Teams can add it to their current preview workflow without moving feedback into a separate review system before sending changes to the agent.
Comments
