# Bolt.new Problems & Issues 2026 - Tokens Burn, Error Loops

Source: https://www.tryorbye.com/products/bolt-new
Last analyzed: 2026-11-15
Try or Bye score: 52/100

## Verdict: Try with caution

Bolt.new works for some teams, but users report recurring problems (score 52/100). Most reported issues: Bolt.new tokens burn fast on larger projects; Error-fix loops waste tokens; Tokens spent on planning and thinking with no code change. Not a good fit for: Teams building production SaaS; Anyone needing refunds or guaranteed support. Users most often switch to Lovable, Replit, Cursor.

## What it is

Bolt.new is StackBlitz's AI app builder. You describe an app in chat and it writes, runs and publishes it in the browser, with built-in hosting, databases and Netlify or GitHub integration. It suits founders and developers who want fast prototypes, but usage is metered in tokens that can drain quickly on larger projects.

## Common errors & fixes

### How to Cancel Bolt.new Subscription

Open the sidebar, click your account name, Subscription, then Cancel subscription under Billing details. It takes effect next billing period; subscriptions are non-refundable per the Terms.

1. **Cancel in Bolt** — Open the sidebar and click your account or workspace name Click Subscription On Billing & usage, under Billing details click Cancel subscription and confirm
2. **Keep tokens until the end** — Your plan and unused tokens stay active until the next billing period Tokens, including rollover, are lost when the cycle ends; resubscribing before they expire restores them
3. **Undo a cancellation** — Click Resume subscription on the same page before it takes effect
4. **Refunds** — Terms say subscriptions are non-refundable Email support@bolt.new from your account email for specific problems

Full guide: https://www.tryorbye.com/products/bolt-new/issues/cancel

### Bolt.new Error Loop

Bolt error loops come from repeating automatic fixes. Stop clicking Attempt fix, switch to Plan mode, ask for logging and error handling, or revert in Version History.

1. **Stop clicking Attempt fix** — Each attempt consumes tokens Research the error and step in manually
2. **Ask for logging and error handling** — Prompt Bolt to add detailed logging around the problem area Use the logs for a more precise next prompt
3. **Use Plan mode** — Ask focused questions and agree a plan before the next fix
4. **Revert** — Open Version History and restore the last working version

Full guide: https://www.tryorbye.com/products/bolt-new/issues/error-loop

### Bolt.new GitHub Sync Not Working

Reauthorize the GitHub app from the Bolt homepage. If one GitHub account is linked to two Bolt accounts, remove the link from the old account first.

1. **Reauthorize the GitHub app** — Bolt homepage > GitHub below the chatbox Click Configure the GitHub App Select your account > Install & Authorize
2. **Fix account conflict** — In the original account reset password and log out Log back in, Settings > Credentials > GitHub > Delete Connect from the new account

Full guide: https://www.tryorbye.com/products/bolt-new/issues/github-sync-not-working

### Bolt.new Missing Secrets and CORS Errors

API calls from server functions fail when secrets are missing or CORS headers are wrong. Add secrets via the database icon and check Access-Control headers.

1. **Add missing secrets** — Database icon > Secrets Name exactly as code expects, e.g. OPENAI_API_KEY Save; no redeploy needed
2. **Check CORS** — Open DevTools Network tab Verify Access-Control-Allow-Origin, -Methods and -Headers in your function
3. **Webhooks** — Ask Bolt to turn off JWT verification for the webhook function Add your own signature check

Full guide: https://www.tryorbye.com/products/bolt-new/issues/missing-secrets-and-cors-errors

### Bolt.new Netlify Publish Failed

If Bolt fails to publish to Netlify, run the build, download the project and deploy it manually via Netlify drag and drop. Check status.bolt.new first.

1. **Check status page** — Open status.bolt.new and look for incidents
2. **Manual deploy** — Run the build command (usually npm run build) Download the project Follow Netlify manual drag-and-drop deploy
3. **After forking** — Reconnect Netlify using the integration guide Point custom domains to the new site

Full guide: https://www.tryorbye.com/products/bolt-new/issues/netlify-publish-failed

### Bolt.new Project Too Large to Deploy

This error means project files exceed 100MB, usually from images or videos. Delete unused media, then move the rest to external storage and use URLs.

1. **Check size and delete unused media** — Download the project and check folder size Back up, then ask Bolt to find and delete unused images and videos
2. **Move media to external storage** — Use Supabase Storage, Cloudflare R2, AWS S3, Google Cloud Storage or Cloudinary Ask Bolt to reference the external URLs Delete local media files

Full guide: https://www.tryorbye.com/products/bolt-new/issues/project-too-large

### Bolt.new Ran Out of Tokens

When Bolt tokens run out, free users can still edit in Code view, paid users can upgrade or reload. Free tokens reset daily and monthly; paid tokens on renewal.

1. **Free plan: edit code directly** — Use Code view, which costs no tokens Wait for the daily reset or upgrade
2. **Upgrade your plan** — Billing & usage > Upgrade plan Higher tiers give a better price per token
3. **Reload tokens if eligible** — Reload is available on the highest monthly Pro tier or any annual Pro plan Reloaded tokens do not expire
4. **Check rollover** — Paid tokens roll over for two months; older tokens are used first

Full guide: https://www.tryorbye.com/products/bolt-new/issues/ran-out-of-tokens

### Bolt.new Site Shows 404 After Publishing

Static hosting needs HTML output and an SPA redirect rule. Ask Bolt to build static or prerendered output and add a redirect so refreshing non-home routes works.

1. **Build as static HTML** — Ask Bolt to use SPA mode or prerendering Publish again
2. **Add a redirect rule** — Ask Bolt to add /* /index.html 200 in a _redirects file (or netlify.toml) Publish, then Update Refresh a non-home page to confirm
3. **Build output directory not found** — Paste the error in chat and ask Bolt to fix the build Publish again; contact support if it persists

Full guide: https://www.tryorbye.com/products/bolt-new/issues/site-shows-404-after-publish

### Bolt.new Supabase Connection Not Working

Check status.bolt.new, then confirm the Supabase URL and keys match the intended project and fix RLS. Re-add environment secrets on the host if you exported.

1. **Check status and project keys** — Open status.bolt.new Confirm the Supabase URL and anon key belong to the project you intend
2. **Reset RLS** — Ask Bolt to remove all RLS rules from the table Ask it to add the correct rule, describing the behavior Confirm RLS is enabled in Supabase
3. **Use secrets for server calls** — Click the database icon > Secrets Add the exact name the code expects and save
4. **Under load** — Use Supabase's pooled connection string

Full guide: https://www.tryorbye.com/products/bolt-new/issues/supabase-connection-issue

### Bolt.new Tokens Burning Fast

Bolt spends tokens on every prompt and on its full project context, so big projects and fix loops drain allowances. Use Plan mode, specific prompts, Version History and clear context.

1. **Switch to Plan mode for discussion** — Use Plan mode to troubleshoot or decide before changing code It uses fewer tokens because it writes no code
2. **Be specific and build incrementally** — Name the exact file or function Add one feature at a time and test after each
3. **Use buttons, not prompts** — Use Publish to publish Use Version History to revert instead of prompting a fix
4. **Reduce project size and context** — Remove unused files and split large ones Clear context when no longer needed Turn on connectors only when needed
5. **Pick the right agent** — Standard for average tasks Max only for complex tasks

Full guide: https://www.tryorbye.com/products/bolt-new/issues/tokens-burning-fast

## Common problems

- **Bolt.new tokens burn fast on larger projects** (pricing): Because the project context is sent with each prompt, token use per request grows with project size. Users report monthly allowances being used up in a small number of prompts on bigger apps. Typical for projects past the prototype stage.
- **Error-fix loops waste tokens** (reliability): Clicking Attempt fix repeatedly can spend tokens without solving the problem, and Bolt's own docs warn against repeating it. Users describe millions of tokens lost chasing one bug, often authentication or setup.
- **Tokens spent on planning and thinking with no code change** (pricing): Reviewers on Trustpilot report tokens consumed on plans or processing that never produced the requested change, with no automatic restoration.
- **No refunds: Bolt subscriptions are non-refundable** (pricing): The Terms of Service say subscriptions are non-refundable. Users who lost tokens to errors or crashes report difficulty getting restored tokens or money back.
- **Prototype ceiling: complex apps get brittle** (usability): Reviews say Bolt is great for first versions but the AI rewrites large files for small fixes and breaks working features as the app grows.
- **Sessions crash or stall near completion** (reliability): Trustpilot reviewers describe sessions ending abruptly or failing near the end of a build, losing work and tokens.
- **Supabase connection and credentials problems** (integrations): Users report Supabase credentials reverting to the wrong database, RLS rules that expose or hide data, and connection errors after export and re-import.
- **Project too large to publish (100MB limit)** (performance): Publishing fails when project files exceed 100MB, usually due to images and videos stored in the project. Media must move to external storage.
- **Netlify publish fails or breaks after forking** (integrations): Publishing can fail at the Netlify step, and forking a project creates a new Netlify site so the old connection and custom domains are lost.
- **Slow or unhelpful support, reply to few complaints** (support): Trustpilot shows 78% 1-star ratings (2.0/5 from 217 reviews) and Bolt replying to about 12% of negative reviews. Some users do praise support.
- **Generated apps ship with weak security by default** (security): AI-generated Supabase apps can have disabled RLS or missing policies, exposing data until fixed.
- **Tokens vanish when you cancel** (pricing): Allocated and rollover tokens are lost when the billing cycle ends after cancelling. Rollover tokens also expire after two months.
- **Token reloads only for the highest Pro tier or annual plans** (pricing): Buying extra tokens is restricted, so people on lower monthly tiers must upgrade instead of topping up.
- **Setup and npm install failures in new projects** (onboarding): Some users burn tokens just getting a basic project running, with npm install failures a common trigger.

## What users like

- **Fast prompt-to-app prototypes**: Users report working prototypes in hours or days with no setup.
- **Built-in hosting, databases and publishing**: Publish to a bolt.host URL, custom domain on Pro, unlimited databases, no separate infrastructure.
- **GitHub, Netlify, Supabase, Stripe via server functions**: Common services connect through integrations and secrets without leaving the editor.
- **Plan mode and Version History**: Plan mode discusses without changing code and costs fewer tokens; history lets you revert without prompting.
- **Free plan with 1M tokens per month**: Free tier lets you test before paying, though a 300K daily cap applies.
- **Mobile app support**: Builds are not limited to web apps; mobile projects are supported via Expo.

## Pricing

- **Free**: $0.00 (free) — hidden costs: Bolt branding on published sites; unused tokens do not roll over; the daily cap resets and does not carry over.
- **Pro**: $25.00 (monthly) — hidden costs: Tokens can drain fast on large projects; token reloads only on the highest monthly Pro tier or annual Pro plans; no refunds; tokens lost on cancel after the cycle ends.
- **Teams**: $30.00 (monthly) — hidden costs: Tokens are not shared between members and stay with the member who accrued them. Price is per member per month.
- **Enterprise**: usage_based — hidden costs: Custom quote

## Who should and shouldn't use it

- **Founders validating an idea** — Good fit: Fast prototype with hosting included.
- **Designers and PMs making demos** — Good fit: Quick clickable apps without code.
- **Hackathon and weekend builders** — Good fit: Free tier covers small projects.
- **Developers wanting real code control** — Depends: Code export and GitHub exist, but an IDE like Cursor offers more control.
- **Non-technical users on a tight budget** — Depends: Token burn from error loops can drain a plan with no recourse.
- **Teams building production SaaS** — Avoid: Brittleness, token cost and security defaults make it risky at scale.
- **Anyone needing refunds or guaranteed support** — Avoid: Subscriptions are non-refundable and support feedback is mixed.

## Alternatives

- **Lovable** (https://www.tryorbye.com/products/lovable): Similar prompt-to-app flow aimed at non-technical founders. Trade-off: also credit-metered with its own error loops.
- **Replit** (https://www.tryorbye.com/products/replit): Agent with terminal, database and hosting; more stacks and easier debugging. Trade-off: usage-based charges.
- **Cursor** (https://www.tryorbye.com/products/cursor): IDE with full code control for developers who outgrow prompt builders. Trade-off: requires coding knowledge.
- **Bubble** (https://www.tryorbye.com/products/bubble): Visual no-code builder with fixed structure and mature hosting. Trade-off: lock-in and a learning curve.
- **GitHub Copilot** (https://www.tryorbye.com/products/github-copilot): Assistant inside your existing editor and repo, no token metering per app. Trade-off: no one-click hosting.

## FAQ

### Is Bolt.new worth it?

For quick prototypes and demos, yes. For production apps the token cost, error loops and no-refund policy make it risky. Start on the free plan (1M tokens a month, 300K per day) to test your project size first.

### Why does Bolt.new use so many tokens?

Bolt reads your prompts and project files each time, so larger projects cost more per request. Repeated Attempt fix clicks and Max agent on simple tasks add to it.

### How much does Bolt.new cost in 2026?

Free is $0 (1M tokens per month, 300K per day). Pro starts at $25 per month with 10M tokens. Teams is $30 per member per month. Enterprise is custom. Yearly billing saves up to 28%.

### Does Bolt.new offer refunds?

No. Bolt's help center says subscriptions are non-refundable under the Terms of Service. You can email support@bolt.new from your account address to ask about a specific problem.

### How do I cancel Bolt.new?

Open the sidebar, click your account name, then Subscription, then Cancel subscription under Billing details. Cancellation takes effect at the next billing period and you keep tokens until then.

### Do Bolt.new tokens roll over?

On paid plans unused tokens roll over and stay valid for two months from the start of the billing cycle they came from. Free plan tokens do not roll over.

### What happens to tokens when I cancel Bolt.new?

You lose access to your allocation and rollover tokens when the billing cycle ends. If you resubscribe before the rollover tokens expire, you regain them.

### Why is Bolt.new stuck in an error loop?

Automatic fixes often repeat the same change. Stop clicking Attempt fix, switch to Plan mode, ask for detailed logging, or revert in Version History.

### What is the Bolt.new project size limit?

Published projects must be under 100MB of combined files. Large images and videos are the usual cause; move them to external storage like Supabase Storage or Cloudflare R2.

### What are the best Bolt.new alternatives?

Lovable for non-technical founders, Replit for debugging and hosting, Cursor for code control, Bubble for visual no-code.

### Is Bolt.new free?

There is a free plan with 1M tokens per month and a 300K daily limit. Published sites carry Bolt branding.

### Is Bolt.new good for production apps?

It is best for prototypes. For production, review security (Supabase RLS), move code to GitHub and consider an IDE for ongoing work.

---
Try or Bye aggregates problem patterns from user reviews, forums, and app stores. Methodology: https://www.tryorbye.com/methodology