Have you ever switched vibe-coding tools mid-project? What actually pushed you over the edge?

by

Everyone talks about which tool they're using right now. Fewer people talk about the tool they left and why.

I switched from Bolt to Cursor halfway through a project a few months ago, not because of a big feature gap, but because of something small: Bolt kept losing context after a few file edits and I'd have to re-explain the whole architecture every session. It wasn't a benchmark loss, it was a patience loss.

That's the kind of thing that never shows up in comparison posts. Nobody writes "Tool A has 12% worse long-context memory," they just quietly open a new tab and start using Tool B.

So, curious about real switches, not hypotheticals:

  • Have you switched vibe-coding tools mid-project? What was the actual trigger (a bug, a missing feature, a vibe, a price change)?

  • Was the switch worth the setup/relearning cost, or did you regret it later?

  • Is there a tool you want to switch to but haven't, purely because of switching friction?

11 views

Add a comment

Replies

Be the first to comment