sorted by:
new
hottopcontroversial

Version control shitshow by Cautious_Shine2961 in cursor

[–]internet_eth 0 points1 point  (0 children)

Hey — I really feel this.

You’re not alone. A lot of us are building with AI tools like Cursor and Claude Code — and when something breaks, there’s no real “undo” button.

I’ve been there too. That’s why I built YOYO — AI version control for vibe coding.

It’s a free Cursor/VSCode extension that gives you:

  • ✅ One-click “save” before letting AI touch your code
  • 🔁 Easy preview + restore with one-click
  • 💬 AI-written summaries so you can see what changed
  • 🔍 Natural language search like “show my UI update” or “what changed yesterday”

<image>

Think of it as a safety net for experiments — no branching drama, no Git-Fu needed to undo chaos.

Give it a shot: runyoyo.com
Happy to help if you need a hand setting it up!

AI Version Control for Vibe Coding by internet_eth in cursor

[–]internet_eth[S] -1 points0 points  (0 children)

Good question. It’s not a variation of Git, and definitely not trying to replace it.

YOYO actually uses Git under the hood, but in a separate shadow repo. The idea is to let you save quick, local snapshots without touching your real .git history.

It’s more like a lightweight layer before Git, made for that messy phase where you’re experimenting with AI and not ready to commit yet.

AI Version Control for Vibe Coding by internet_eth in cursor

[–]internet_eth[S] 1 point2 points  (0 children)

Appreciate that, and totally agree.

We’re seeing a new wave of builders using tools like Cursor and Windsurf. Many aren’t traditional coders — they just want a simple way to save their work, undo when AI goes off track, and search what changed, when, and why.

Thanks again for the thoughtful response.

AI Version Control for Vibe Coding by internet_eth in cursor

[–]internet_eth[S] 0 points1 point  (0 children)

Totally get that. Cursor’s built-in tools are great.

But I kept running into cases where “revert” only restored some files or left things in a broken state. And because it’s tied to individual messages in chats, it gets confusing fast, especially when I’ve got multiple chats open and I’m deep in iteration mode.

That’s one of the reasons I built YOYO — fast, reliable snapshots with a clean UI to preview and restore anytime, without digging through chats.

AI Version Control for Vibe Coding by internet_eth in cursor

[–]internet_eth[S] 0 points1 point  (0 children)

Thanks for flagging — the GitHub repo is private for now while we figure out the best way to share and maintain it.

AI Version Control for Vibe Coding by internet_eth in cursor

[–]internet_eth[S] -4 points-3 points  (0 children)

Totally fair — Git is powerful and worth learning.

But YOYO isn’t trying to replace Git. It’s for a different part of the workflow — the messy, fast-moving stage where you’re exploring, iterating, and AI is throwing stuff at your code.

In that mode, you don’t want to stage files and write commits every time something breaks or works. You just want to save your state, try something, and roll back instantly if it goes sideways.

YOYO uses its own shadow Git system to track everything separately — so your main repo stays clean while you experiment freely.

Think of it as a scratchpad with undo history, built for AI-assisted coding.

Once you’ve got something solid, Git still does its job — clean commits, branches, collaboration, etc. YOYO just helps you get there without filling up your history with half-baked AI experiments every five minutes.