Technically, nothing. But psychologically git commits represent a unit of completed work, whereas with AI agents what's needed is a kind of agent-wise undo history such that you can revert back to the state of the repo 1 minute ago before Claude did an oopsie all over your repo.

You can definitely use git as a backend for building such a system, but some extra tooling is necessary.

Just create a new branch before you implement new features and if the agent messes up don't merge the branch.

That way you get the best of both worlds. The buggy code is still there in case it's needed but it's not in the main branch

> You can definitely use git as a backend for building such a system, but some extra tooling is necessary

Is it? There’s the stash for storing patches, the index for storing good hunks, branching for trying out different experiments. You can even use worktree if you want separate working directory especially when there will be changes in the untracked files.

Git has a lot of tooling for dealing with changes, directly or at the meta layer.