Live Feb 28th, 9am PT - drop your questions!

Hi everyone,
CEO of Bolt here! Super excited to open up about our journey and offer any learnings and stories I can to help other makers on their journey. Within a span of 2 months we've grown to $20M in revenue and were recently featured in NYT as paving the way for vibe coding.

I run 8 or more sessions at once, so terminal hangs and crashes show up way more often than I'd like. claude --resume looks like it should help, but it doesn't always pull the whole history back. I've stopped relying on it.

Our workaround is small. Every time the agent finishes a reply, a Stop hook writes a little card for that terminal pane, holding my last instruction, the tail of the agent's answer, the working folder, and the path to the full session log. It's a plain text file that gets overwritten on each run, so it costs zero tokens, and cards older than 7 days get cleaned up on their own.

Opening a new session in the same pane or folder triggers a SessionStart hook that reads the latest card and drops it into the agent's context. That way the new session already knows where the last one stopped, and it can always go read the full log when it needs more detail. Usually that's plenty.

Building used to be the bottleneck. Now I can get a working app faster than I can write a good landing page copy for it. So the "idea guy with no code skills" excuse is basically gone.

But almost none of my vibe-coded weekend projects have real users, and I don't think that's a coding problem anymore.

For those of you actually getting traction - what's eating your time now that building isn't the bottleneck?

I m noticing something weird happening in solo dev land.

We used to compete on:

• remembering docs

• knowing frameworks

• being a better coder

Now it feels like the real edge is:

Hey p/bolt-new community,

I recently started building Couples Hub (https://coupleshub.io/) a React-based application and Next.js based landing page using Bolt.new. Couples Hub is a product of my hobby brand "MD Meets Techie" which I've run for the past four years, creating digital products specifically for couples. Given my technical background, diving into Bolt.new was kind of a fun experiment (esp given how drab and boring my day job is). I noted several challenges along the way and I thought I'll share a few tips on what I've learned thus far. 

Everyone talks about how fast AI can write code now but nobody talks about the mental exhaustion of reviewing three different feature branches at the same time.

I realized last week that if I run more than two agents simultaneously I stop catching small architectural mistakes and just start blindly approving diffs.

Now I cap myself strictly based on how many code reviews I can realistically handle before my focus drops. Do you use any specific workflow or rule to keep yourself from drowning in unreviewed AI-generated code?

We route across 30+ models and for a while the picker just swapped silently. Someone asks for a video, we choose what we think is right, they get a result. Clean, and wrong.

A user can't tell the difference between a deliberate routing decision and a model having a bad day. The output changes, the price changes, and nothing on screen explains either one, so the conclusion they reach is that the product got worse.

So the picker now names what it chose and why before it runs, in one line. It makes the thing look less magic, and I think that's the right trade. Silent routing is the same bet as a silent retry or a silent price change. It holds while the output is good, and the first time it isn't, you've taught someone to distrust the whole product instead of one model.

If you auto route anything, agent, model or tool, do you show the user what got picked, or does it happen behind the curtain?

Arteza opens on a grid showing all six studios at once, image, video, voice, music, avatars, editing. It demos brilliantly. It's the screen people screenshot and it's why anyone understands the product in four seconds.

It's also the screen our heaviest users leave immediately. If you're in it every day you already know which studio you want, so a menu of six is six things to skip. The people who love that grid are the ones seeing it for the first time, and they only see it once.

The mistake underneath is that I designed the first thirty seconds and assumed the next thirty days would sort themselves out. Everything I measure at signup rewards that grid. Nothing I measure rewards the tenth session, so the tenth session never got designed.

Trying to make the home screen a function of what you did last week instead of a fixed grid, which is easy to say and quietly a different product. If you shipped something that demoed well, what did you have to change once people actually lived in it?

The vibe coding aesthetic online is all 'just describe what you want and ship.' The actual best ones I know do something different.

What I keep noticing:

I'm super curious how everyone starts to vibe code? In the beginning I would simply jump into @bolt.new or @Cursor and just do a prompt and continue refining with the AI. I quickly realized this created a lot of issues as I didn't think about the structure, tech stack, and how I wanted the features to interact with each other and how the way I was building things would impact the user experience. I now do the following:

• Write down a simple problem statement: "what am I trying to solve?"

• Write down a simple solution statement: "what does the thing I'm building do (to solve the problem)"

• Share the above with @ChatGPT by OpenAI and word vomit my thoughts, ideas, how I want the user to interact with my app, etc and ASK ChatGPT to turn everything I said and want into an easy to understand directive and instructions for an Engineer.

• I then take the Engineer instructions and give it to a new chat in ChatGPT and ask it to turn those instructions into a prompt for an AI engineer and to break up the project into sections so that each time we focus on a section the app is shippable and keeps things easy to work on.

• I take the output and paste it into my notes. I then give it to Cursor.

• Once in Cursor, I create a new project folder and got at it!

Curious what everyone else does and if you've experience any things to avoid or must do