StackBlitz · Setup guide
How to set up Bolt
Prompt, run, edit, and publish a small web app in the browser on StackBlitz WebContainers. Review the preview and generated files before connecting GitHub, adding secrets, or treating a publish URL as production.
The “Open Bolt” link goes to the vendor site. It is not an affiliate-tracked link on this page — no commission is claimed for that click. Affiliate disclosure.
Before you begin
- A Chrome/Chromium browser according to the current quickstart, and a Bolt account (Google, GitHub or email).
- A small product brief with explicit boundaries for data, auth, and deployment.
- A GitHub account if you want an owned repository after the first preview works.
Authentication
Bolt.new account sign-in (Google, GitHub, or email) and optional GitHub OAuth for repo sync
Account: Bolt.new account; GitHub for repository export/sync
Review GitHub permission screens before connecting a repository. ACE has no publisher affiliate programme for Bolt.
Install or open it
1. Get the harness ready
These steps are written for beginners. On Mac, Terminal is the black/white text window where you type commands. On Windows, use PowerShell or Terminal. Use the OS tabs to hide steps that are not for your computer, then copy one command at a time.
- 01
Open Bolt in your browser
Open bolt.new in Chrome or another Chromium browser supported by the quickstart, then sign in with Google, GitHub or email. No credit card is required to start; the standard workflow needs no local install.
Bolt QuickStart - 02
Start from a constrained prompt
Describe one page or workflow, its acceptance criteria, and what should stay out of scope. Prefer a static or read-only first slice so Bolt does not spend tokens standing up auth and a database before the UI is right.
Bolt QuickStart - 03
Review the in-browser preview
Bolt runs the generated app in a StackBlitz WebContainer in the same tab. Exercise the preview yourself. Token use continues while you iterate — stop and edit files directly when the agent is looping on the same error.
Bolt.new README - 04
Publish only after the preview is correct
Use Bolt’s publish control for a shareable URL after the preview matches the brief. Treat auth, environment variables, and database rules as a first draft — verify them on the published URL, not only in the editor preview.
Bolt QuickStart
Repository or project
2. Start in the right place
Keep the first repository small, clean, and easy to roll back while you learn the harness’s permissions and context model.
- 01
Keep the first brief read-only
Ask for one page with an explicit acceptance checklist. Do not start with payments, secrets, or an existing production monorepo.
Bolt QuickStart - 02
Export or sync Git after the preview is right
Connect GitHub only after the in-browser preview matches the brief. Generated auth and env files are a starting point, not a production hand-off.
Bolt.new README
First run
Prototype a read-only page
Use this task to test the workflow before handing over a larger repository or production responsibility.
- 01Ask Bolt to build a static page with a small, explicit acceptance checklist.
- 02Review the generated files and test the in-tab preview at desktop and mobile widths.
- 03Publish a shareable URL only after the preview is correct, then connect Git if you need an owned repo.
Why this is safe: A read-only prototype exercises prompt-to-preview quality without introducing credentials, payments, or destructive data operations.
Stop and review if
- The generated app asks for secrets or payment credentials before the static slice works.
- The agent burns tokens retrying the same error instead of letting you edit the file.
- Git permissions are broader than the repository you intended to create.
The operating boundary
Privacy, data, and cost
The setup is incomplete until you know what the harness can see, what account pays for it, and who approves a risky action.
Privacy
The development preview runs in a browser WebContainer; AI processing still sends prompts, code and relevant files to providers. The September 22 policy schedules eligible Bolt model-development/dataset licensing from October 7 or the later account-terms date, with opt-out, regional and organization exclusions. Forge has separate affirmative-consent rules.
Training on code: tier dependent
EEA/UK/Swiss-account content is excluded from these model-development/dataset uses under the captured policy. Organization-managed and separately contracted accounts have distinct rules. Operational AI processing remains, and neither opt-out nor no-training establishes zero retention.
Sensitive repos: Start with non-sensitive briefs, review generated code and GitHub scopes, and inspect the account data-use controls. Ordinary opt-out stops new selections; previously completed training/dataset delivery is not undone. Stopping Forge alone does not withdraw its consent.
Pricing
Free includes public/private projects, 300K tokens/day and 1M/month. Pro starts at $25/month for 10M tokens without a daily cap; Teams starts at $30/member/month with tokens allocated individually. Paid unused tokens roll over for one additional month with an active subscription.
Model: usage based
Watch out: Both Free daily and monthly caps apply; a daily reset does not replenish exhausted monthly tokens. Included hosting, requests, uploads and database capacities have separate limits, and connected services can add costs. Plan mode uses project context and is not a zero-token interaction.
When setup goes wrong
The generated page looks right but the app does not work after refresh.
Test the preview as a new visitor, inspect runtime errors in the Bolt terminal, and ask for a reproduction-specific fix rather than a rewrite.
AI interactions stop with a token or plan limit.
Check whether the daily or monthly allowance is exhausted and its reset date. A daily reset does not fix a monthly limit; review any plan change before buying more usage. Stop repeated failing prompts and inspect the specific error.
Auth or data works in preview but fails after Publish.
Compare preview vs published env vars and backend rules; republish after fixing configuration rather than rewriting the UI.
The agent loops on the same compile or runtime error.
Stop the run, open the failing file, apply a minimal fix yourself, then ask Bolt to continue from the current tree.
Next steps
After the first successful run
Keep the pilot small, then compare surfaces and budget before a team rollout.
Setup details change quickly. The page was checked October 2, 2026; use the official source below before installing in a managed or production environment.