What's the biggest pain point you've hit using vibe coding tools?

After building with vibe coding tools for a while, here's what bugs me most — curious if it's just me:

• They don't do anything unless I tell them to.

• I'm still the one who has to figure out what to do next.

• To get good work out of them, I'm the one feeding them all the context.

Notice the pattern? In every case, I'm the brain and the glue. The tool waits, I think. The tool executes, I carry the context between GitHub, the App Store, analytics, Slack, Notion... It's powerful, but it's reactive — I'm stuck doing the part that actually drains me.

So my team is building something to flip that. It's called Bottari (still early — this is the first time I'm sharing it anywhere 🙈).

The idea: pull the context scattered across your product's tools — GitHub, App Store, analytics, Slack, Notion — into one actionable memory, then use it to propose the next move to grow the product, ship it, learn from the result, and propose the next one. A loop that runs on its own, instead of waiting to be told.

Still figuring a lot of it out, which is exactly why I'm asking:

• What's the biggest pain point you've felt using vibe coding tools?

• Is it the "won't act unless told" part, the "I decide what's next" part, the "I feed it all the context" part — or something else entirely?

Would love to hear what actually hurts 👇