Skip to main content
Fabricate no longer has a separate Build Mode — you build your app by chatting. Every message you send is handled by Fabricate’s AI agent, which reads the parts of your code it needs, makes the changes, and deploys them to the live preview.
Every message uses credits, based on the work Fabricate does to handle it — including messages that only ask a question. See Plans & Credits.

​
How Building Works

1

You send a message

Type what you want to change, add, or fix. The more specific you are, the better the result.
2

Fabricate reads your code

The AI agent opens and searches the files it needs to understand your request — components, API routes, and the code that stores your data.
3

Code is written

Fabricate edits the affected files and adds new ones where needed.
4

Fabricate deploys and checks the preview

The agent deploys the change to your live preview and checks it in a browser for errors, fixing what it finds before it finishes.

​
What You Can Do in the Chat

​
Add New Features

​
Modify Existing UI

​
Fix Bugs

​
Database Changes

​
Style Changes

​
Tips for Building Effectively

Be specific about scope. “Fix the button” is harder to action than “Fix the submit button on the contact form — it’s not showing a loading state while the form is submitting.”
One change at a time. For complex features, break them into smaller steps. This gives you more control and uses credits more efficiently.
Ask before you build. If you’re not sure how to approach something, ask in the chat and say you only want an explanation for now. Questions use credits too, but a clear plan can save you from rebuilding.

​
Understanding Credit Usage

The cost of a message depends on:
  • Your app’s current size — larger apps have more code for the AI to read
  • The complexity of your request — touching many files costs more
  • The length of the generated code — more new code = more output tokens
Targeted, specific requests on smaller apps are the most credit-efficient.

​
Frequently Asked Questions

Yes. Select Go back to this point under an earlier message, or open the history in the chat header, then choose Restore and redeploy. Going back restores your app’s code, not the data stored in it. Some older versions can’t be restored; for those, ask in the chat to undo the change.
Describe the issue in a follow-up message. The AI can read your current code and check the preview in its own browser for errors, so it can often fix issues in a subsequent message.
On Pro and Scale, you can edit a file in the Code view and save it. On the Free plan, the Code view is read-only. Changes made outside Fabricate — for example, in a repository you pushed to GitHub — aren’t brought back into your project.
Yes. A message you send during a build waits in line and runs after the current build finishes.
Not all at once. For each request, the AI agent opens and searches the files it needs, and it keeps your earlier conversation as context.