Ask HN: Why don't LLM dev tools used by "vibe coders" enforce main/develop?

That viral replit story [0] is stuck in my head. Even if we had AGI vibe coding nirvana, we would still need at least a main/develop branching strategy, wouldn't we?

This seems like such an obvious self-own on the part of the tool devs, that I feel like I must be missing some level of complexity in the implementation.

Why do seemingly all of these LLM-based dev tools appear to default to developing in prod?

For a moment I thought that merge conflicts were the reason, but a single dev and simple main/develop git branching strategy, would never have merge conflicts if hot-fixes were not allowed, correct?

Am I missing something, or are these currently caveman dev tools?

[0] https://news.ycombinator.com/item?id=44625119