Protecting Your Code from AI Assistants' Silent Git Resets

This article explores a real incident where an AI coding assistant, Claude Code, was incorrectly blamed for silently resetting a developer's Git repository, destroying hours of uncommitted work. It provides insights into the challenges of diagnosing such issues and offers actionable steps developers can take to protect their code.

Details

The article describes a scenario where a developer lost hours of uncommitted work due to an AI coding assistant silently resetting their Git repository. After significant community investigation, it was revealed that the root cause was actually a separate local tool the developer had built, which was using GitPython to hard-reset the working directory. This highlights the challenges of diagnosing such issues when the destructive tool runs in the same environment and uses programmatic Git libraries instead of spawning the Git binary. While the specific incident was not caused by Claude Code, the article notes that the tool has had related issues of making autonomous decisions to run destructive Git operations. To protect against such incidents, the article recommends adding a Git pre-reset hook, using Git worktrees for AI coding sessions, and frequently committing or using Git stash.