Skip to main content

Review preview and visual editing tools

Builder keeps the live app close to the conversation so you can move from prompt to verification without switching tools.

Preview panel modes

The right-side Builder panel includes several review modes:

ModeBest for
PreviewRun and inspect the live app
AnnotateMark up the preview visually before changes
CodeReview source output for the active app
ProblemsCheck build, runtime, or lint-style issues
SecurityReview security-focused findings
ConfigureAdjust app-level configuration from the preview workspace
CloudOperate Builder Cloud for the active app
Auto ImproveConfigure how Builder should prepare future product improvements from connected app, chat, and session signals
PublishConnect GitHub and Vercel, then prepare deployment

Builder also keeps a System messages area at the bottom so you can inspect recent runtime and app activity.

Use Preview as the default verification step

After a generation finishes:

  1. Open Preview.
  2. Click through the main user flow.
  3. Confirm the page loads cleanly.
  4. Open Problems if anything looks broken.

This should happen after every meaningful product change, not just before publishing.

Edit one component at a time

When the preview is healthy, Builder exposes targeted visual-editing tools in the preview toolbar:

  • Edit component to target a single element
  • Select components to collect multiple components for context

Use these controls when the change is visual or copy-focused and you do not want to re-prompt the whole app.

Common visual editing workflow

  1. Wait until preview is fully loaded.
  2. Click Edit component or Select components.
  3. Pick the relevant element in the live preview.
  4. Use inline controls such as Edit Text or Swap Image when available.
  5. Review the draft in preview immediately.
  6. Choose Save Changes or Discard.

Builder keeps pending visual edits visible until you decide what to do with them.

Use Annotate when the feedback is visual first

Annotate is useful when you want to mark the preview before asking for a change, especially for layout and hierarchy feedback.

It is a good fit for:

  • spacing issues
  • content grouping problems
  • visual bugs that are easier to point at than describe

Know when to use Preview vs Chat

  • Use Preview when you need to verify behavior or make targeted component changes.
  • Use AI Chat when the change is structural, multi-screen, or requires reasoning across files.

In practice, teams move back and forth between the two.

Plan and entitlement notes

Preview inspection is the standard Builder workflow. Some save actions for advanced visual editing depend on your Builder plan and workspace capabilities.

If editing controls appear locked, first confirm:

  • the preview is running
  • the correct app is selected
  • your workspace plan includes the feature you are trying to use

Use Auto Improve when Builder should learn from product signals

Auto Improve is a preview-panel mode for teams that want Builder to stay ready for more autonomous product improvement work over time.

Use it to:

  • connect the active app to richer product signals through OXVO and OXVO Sessions
  • choose whether Builder should stop for review first or move through approved improvement cycles with Full Access
  • keep the feature enabled while Builder waits for stronger usage, support, replay, traffic, and bug data

Two operating modes are available:

  • Review Mode: Builder prepares the next improvement cycle, then waits for Continue or Cancel
  • Full Access: Builder is allowed to move through approved improvement cycles without another manual confirmation step

Auto Improve is designed to become more useful as real usage builds up. A waiting state is normal early on, especially before enough OXVO and Sessions data is connected.

Auto Improve is also plan-gated. Free workspaces can review the setup, but only paid Builder workspaces can enable it.

Publishing and Cloud live in the same review loop

Once preview is stable, continue directly into:

That keeps shipping and backend setup connected to the actual app state you just verified.