Version Control for AI Coding

Baffling. Not at all clear from the site or video what this does, what problem it is solving, and what about LLM coding is different such that it needs new ideas in version control. Is it just that there are more commits and more conflicts because people are pushing more garbage without regard for consistency and stability? I would suggest solving that by pushing less garbage, or at least having fewer people pushing garbage to the same place at the same time.

How does it resolve conflicts? If you want to resolve conflicts automatically, try the excellent Mergiraf, which works by looking at the AST rather than the line-by-line diff: https://mergiraf.org/

I’m confused on what this is based on the landing page.

Version control isn’t specific to A.I workflows, what does this add on top of git?

Is this a worktree type solution so you could make parallel edits?

Not sure calling the product Branching is a good idea. May cause confusion.

I watched the video and I don't really understand how this maps to the underlying Git operations and what it can do. What happens if I make changes locally while Cursor is doing something? Is this detected properly? (That might be useful.) Can I use it with Claude Code too in some way? Is it primarily for syncing with external tools like Lovable?

Also, the ChatGPT generated copy for the landing page is somewhat off-putting.

We need new version control workflows or just a usability layer on top of git with the Proliferation of agentic coding. But this is not it - jm not sure what ita actually doing and its opaque.

Been posted a few times recently, no indication of what changed

I was today years old when I read that version control has changed because of LLMs.

I’m just gonna keep typing ‘hg commit’ and plow ahead.

Take a look at my thoughts on version control and vibecoding

https://github.com/TZubiri/keyboard-transpositions-checker

My idea is that we should not commit LLM written code, but rather we should commit the prompts. The LLM prompts are source code, the LLM code is target code. If you use typescript and scss, you would commit that, not the generated js and css.

That LLMs are typically non-deterministic introduces some issue, but surely you can achieve determinism with seeds, specific model revisions and 0 temperature.