Docs

Reference

Every term NeoBuild uses, and a symptom-to-page index for when something goes wrong.

Chapter 01

Glossary

Agent mode: The default composer mode. Writes files, creates a version and builds a preview. See Start Here.
Ask mode: Read-only questions and answers about your project. Explains, reviews and diagnoses; never changes anything and never drafts a plan.
Plan mode: Read-only. Drafts an implementation plan for approval; Approve & Build runs it in Agent mode. Nothing changes until you approve.
Auto-fix: Silent build repair on the current version, normally up to three attempts. Does not create a new version.
Fix all: Manual repair that creates a new version carrying the Issues context, so you can compare it with the broken one.
Issues: The view that appears when a build fails and auto-fix could not resolve it.
Version: A build of your project. v0 is the first generation; each file-changing prompt creates the next. Rollback selects an earlier one.
Preview: The build inside the editor, rebuilt as you prompt. Not the public site — see Deployment.
Publish: The deliberate step that makes a selected version the live production site.
Edge function: A Supabase-hosted server-side function, for work that needs a secret or must not run in the browser. See Integrations & Ownership.
Server features: The edge functions of a project, published together as one step.
SQL review: The approval step before NeoBuild applies a generated database script. Nothing runs against your database without it.
Customer Supabase: Your own Supabase project — you own the data, billing, users, storage and backups.
RLS: Row-level security: Supabase rules deciding which rows a given user may read or write. The usual cause of permission errors.
Remix: Cloning a public project template into your own workspace. Not the Remix.run framework.
Token: The unit of AI work. 1 Million free to start, then $1 (₹100) per 100,000 tokens — see Plans & Billing.
Build History: The record of preview builds, SQL applies and edge publishes for a project. The first place to look when something did not ship.

Chapter 02

Where to look when something goes wrong

The build failed: Issues, then Fix all, then roll back — Troubleshooting.
The preview is blank or out of date: Rebuild first, then check Issues — Troubleshooting.
A database call is refused: Almost always RLS — Database and RLS errors.
A server function returns 404: It was probably never published; check Build History — Edge function errors.
My fix is not live: Preview is not production; publish the version — Deployment.
My domain is not resolving: Check the CNAME and that you have published — Custom domain.
Tokens are going faster than expected: Check Tools → Token Usage — Plans & Billing.
Still stuck: Support — include the project name and what you last prompted.