I am making a fork of bolt.diy to work on -- new features!

hey guys! be warned, i am about to ramble for a sec. i am developing my own competitor to bolt.new and lovable. the scope is much larger, it’ll be much better and it will be at least 50% cheaper than both. over the past few hours, i have been reverse engineering no-code ai sites. i have used bolt.diy before, but never explored the codebase. i now have a really good understanding of how they work. i should’ve assumed because of bolt.diy, but really, all of these sites are just fancy API wrappers.

for a while, i thought lovable either had its own model or they were doing real fine tuning and codebase training because they were just so far ahead of the game. but, nope! it’s a claude sonnet 4 wrapper (they added that new model today, yay)! just a really well built fancy one. with some cyberpowers, i managed to figure out some of the secrets of how they built it tonight, so naturally, i want to make something even better and cheaper (companies like cursor and windsurf have my heart, AI should be accessable). $100 for 400 messages a month that don’t roll over where at least a quarter get spent on fixing a dumb bug; yeah, no thanks pal. they “optimize” their context window and spend, so no doubt they’re making bank.

anyways, i’ll cut to the chase! i figured i would fork bolt.diy and work on it as an open source endeavor; i want to add amazing improvements to it, maintain the fork and use it to refine my development skills on this sort of thing while i make my site. i’d like to master the art of building and improving these wrappers before i move on to a hybrid approach with v2 of my site which is real fine tuning, actual training and truly working on our own model.

below are some of the changes that i am scaffolding and planning, and i hope i can get to work soon on them as time permits. i will update the list as i come up with more ideas. please suggest additional changes in the comments that you would like to see, especially if it was posted before and went on deaf ears:

  • claude sonnet 4, claude opus 4 and google gemini latest support (i have had issues with them, some reasoning models don’t work well outside of those)

  • improved design functionality – replicates some reverse engineered lovable techniques; lovable always has made better looking stuff than bolt

  • FULL supabase support – been waiting on it forever with .diy

  • FULL stripe support – not yet listed on readme, very helpful tool

  • context7 mcp server or API support for easy integrations; with that and perplexity, i can integrate nearly anything even when fully vibe coding (and eventually, general mcp server support)

  • enhanced rules system – better global and project rule management

  • memory system (automatic and manual – memories will work as they do in Windsurf)

  • better codebase context

  • better previous chat context

  • perplexity ask (grabs context from perplexity using enhanced prompting when stuck or when you ask to do it to fix it)

  • better handling of larger, more complex prompts (will create a memory with a list and check things off one by one – if it runs out of context window or calls, it will prompt you asking if you want to continue).

  • better error handling using context if multiple attempts to fix do not work, it will suggest chat/debug mode (see below) to increase context and use “thinking”/reasoning

  • FAR better commenting throughout code out of the box

  • FAR better logging and alerting out of the box

  • note taking system (optional) – will log changes in markdown notes for changes you want to monitor and use memory to update notes when relevant edits are made

  • better github support – bolt will sync with your repo and contextualize the changes you made on your own time or in another ide.

later:

  • project planning module using claude task master

  • browser crawl/scrape/view to get live data and image on the build.

  • chat/debug mode; switches to a larger reasoning model if able to, looks more intently at the codebase and considers memory and context to plan a fix with you. i.e. claude sonnet 4 would switch to claude opus 4 or gemini in this mode.

  • improved prepackaged stack – enable a mix of my own and lovable’s stack, technologies, packages and integration frameworks. makes building much prettier and way easier. helps future proof your software and prepares for expansion + new features. (this would be optional to enable for a project).

can’t wait to sharpen my dev skills and contribute to this awesome project! i hope you all enjoy this contribution and hopefully when i get my full fledged site done you all come and check it out. it’ll be the best one out!

thanks,
keygen / ra

p.s. – if anyone wants to work on this with me or help in any regard, i’d love to have a partner to learn alongside with; lmk!

2 Likes

i’ll also see if i can beat the devs to this one on the official readme, i can make a knowledge base easily i am sure. i’d like to also a web scraper specifically for scraping docs, maybe it could import in:

  • Upload documents for knowledge - UI design templates, a code base to reference coding style, etc.

Consider Firebase instead of Supabase, it is much much better and no one is doing it yet.

No doubt, Firebase still brings that Google firepower—blazing real-time sync, polished mobile SDKs, Genkit for AI orchestration, and auth, so seamlessly, it’s basically invisible. It’s the go-to for shipping fast and scaling faster.

But this project isn’t chasing speed for speed’s sake—it’s building deep. Structured memory, contextual logic, rule systems, GitHub sync, edge compute, and full-stack autonomy. That’s not just backend plumbing—it’s a dev OS.

And that’s where Supabase wins.

With Realtime 2.0 rivaling Firebase, native pgvector 2.0 for AI memory, edge functions that flow like code poetry, and full self-hosting—Supabase isn’t a Firebase alternative. It’s the foundation for AI-native tools that belong to their builders.

Firebase is a race car.
Supabase is a spaceship you built yourself.

Control the stack. Command the future.