Skip to main content

Build with AI Chat

Home is where you start quickly. AI Chat is where you keep building once an app exists.

Each chat belongs to a specific Builder app, so follow-up prompts stay grounded in the app's current files, preview, and project state.

How chat fits into Builder​

Use Builder chat to:

  • create the first version of an app
  • make targeted product or UI changes
  • fix build and runtime issues
  • add integrations and deployment prep
  • continue work over multiple conversations on the same app

Home vs AI Chat​

  • Home is best for new-app prompts and fast ideation.
  • AI Chat is best when the app already exists and you want ongoing iteration, preview review, approvals, and follow-up edits.

Model selection and workspace-managed access​

In hosted Builder, model access is managed at the workspace level.

That means:

  • the visible model list depends on providers enabled by your OXVO administrator
  • each model can show its Builder credit cost
  • personal model-provider API key entry is not the normal hosted workflow

If no managed models are enabled, Builder shows a notice and points you back to the workspace owner or OXVO workspace settings.

Write better Builder prompts​

Builder works best when prompts describe the product outcome, not just a UI fragment.

Include:

  • the user or team the app is for
  • the main workflow to support
  • the pages or states that matter most
  • the desired visual tone
  • any hard constraints such as auth, database, or publishing needs

Example:

Refine this onboarding dashboard for customer success teams. Keep the existing structure, but make the checklist easier to scan, add a healthier empty state, and tighten the page spacing so it feels more operational.

Work iteratively instead of rewriting the whole app​

After the first build, switch to focused follow-up prompts:

  • "Make the left navigation more compact."
  • "Add a billing status badge and overdue state."
  • "Keep the layout, but rewrite the copy for enterprise users."
  • "Fix the broken preview and then clean up the loading state."

This usually produces a cleaner result than repeatedly asking Builder to regenerate everything.

Approvals and controlled actions​

Some Builder runs generate explicit proposals before changes are applied.

Use that flow when you want to review:

  • code changes
  • file edits
  • potentially destructive actions

Teams that trust the workflow can also tune approval behavior from Settings.

Attachments and context​

You can attach reference material to the prompt flow when you need Builder to work from something concrete, such as:

  • screenshots
  • copy drafts
  • specs
  • assets

Use attachments when the change depends on exact visual or product context, not just general direction.

When chat should move into Builder Cloud​

If the request needs real backend work, Builder should stop treating it as frontend-only.

Turn on Builder Cloud before asking for:

  • auth and sign-in flows
  • database tables and records
  • secrets
  • file uploads
  • server APIs
  • scheduled jobs or webhooks

Continue: Use Builder Cloud for backend features

Useful chat habits for teams​

  • Start a fresh chat when the task changes significantly.
  • Keep one chat focused on one app outcome.
  • Save reusable instructions to Library instead of rewriting them every time.
  • Review Problems and Preview between major prompts.