Bolt burned through 4 million tokens on one TypeScript error, is this normal??

It's normal in the sense that every Attempt fix sends a big chunk of your project as context, so each loop costs a lot. The error itself is a one-liner, which is the painful part.

string | undefined → string means line 42 passes a value that might be empty into something that requires text. Two honest fixes:

// if an empty value is fine
name={form.name ?? ""}

// if it should never be empty, stop before rendering
if (!form.name) return null;

Rule I give everyone: if the second Attempt fix doesn't solve it, stop. Open the file, read the exact line from the error, and either fix it by hand or paste only that function + the error into a free chat model. Then come back to Bolt.

Also worth doing: a .bolt/ignore file for big folders (assets, generated data), smaller context per message.

Practical thing: enable 'diffs' mode in settings if you don't have it on. Bolt then sends changed parts instead of rewriting whole files, noticeably cheaper when it does go in circles.

Cheap insurance: connect GitHub and let every session start from a clean commit. When Attempt fix goes in circles, you roll back to that commit instead of paying for the way out.

Maybe the real lesson is to learn TypeScript instead of paying a chatbot to guess. This is what happens when people who can't code build apps.