Back to List
Claude Code Bug Report: Automated Git Hard Resets Every Ten Minutes Cause Data Loss
Industry NewsClaude CodeGitAnthropic

Claude Code Bug Report: Automated Git Hard Resets Every Ten Minutes Cause Data Loss

A critical bug has been reported in Anthropic's Claude Code (version 2.1.87) where the tool automatically executes a 'git reset --hard origin/main' command every 10 minutes. This behavior, documented in GitHub issue #40710, occurs silently via programmatic Git operations rather than external binaries. The issue results in the permanent loss of all uncommitted changes to tracked files within the project repository. While untracked files and Git worktrees remain unaffected, the bug has been confirmed on macOS 15.4. Evidence from Git reflogs shows a consistent pattern of resets occurring at exact ten-minute intervals, posing a significant risk to developer productivity and data integrity.

Hacker News

Key Takeaways

  • Automated Data Loss: Claude Code version 2.1.87 performs a silent git fetch and git reset --hard origin/main every 10 minutes.
  • Scope of Impact: The bug destroys all uncommitted changes to tracked files; however, untracked files and Git worktrees are not affected.
  • Platform Specificity: The issue has been specifically reported and reproduced on macOS 15.4 using the Homebrew cask version of Claude Code.
  • Programmatic Execution: The resets are triggered via programmatic Git operations rather than spawning an external Git binary, making them harder to detect during execution.
  • Documented Evidence: Git reflogs show a precise 10-minute cadence of resets, confirming the automated nature of the bug.

In-Depth Analysis

Technical Mechanism of the Reset Bug

According to the GitHub issue report #40710, the core of the problem lies in how Claude Code interacts with the local repository's Git state. The tool appears to be programmed to synchronize with the remote origin/main branch on a fixed schedule. Specifically, it executes a git fetch origin followed by a git reset --hard origin/main. Because this is handled through programmatic Git operations—meaning it does not call the standard git command-line interface—users may not see active processes in their terminal or process monitor that indicate a reset is occurring. This silent execution is what leads to the unexpected loss of work, as any modifications to tracked files that have not been committed are overwritten by the state of the remote main branch.

Reproduction and Environment Details

The bug was identified by user johnmathews on March 29, 2026, running Claude Code version 2.1.87 on macOS 15.4 (Darwin 25.3.0, arm64). The environment utilized a compiled Bun binary installed via Homebrew. The evidence provided includes a Git reflog showing over 95 entries where the HEAD was moved to origin/main at exact intervals, such as 21:49:09, 21:59:09, and 22:09:09. This rhythmic pattern confirms that the behavior is not a one-time error but a recurring background task within the Claude Code core logic. The issue has been labeled with 'area:core', 'bug', 'data-loss', and 'has repro', indicating a high-priority technical flaw that directly impacts user data.

Industry Impact

The discovery of a data-loss bug in a major AI coding assistant like Claude Code highlights the risks associated with granting AI tools deep integration into local development environments. For the AI industry, this incident serves as a cautionary tale regarding the implementation of automated synchronization features. While the intent may be to keep the AI's context aligned with the latest remote code, the lack of user confirmation for destructive actions like a 'hard reset' violates standard version control safety protocols. This event may lead to increased scrutiny of how AI agents manage local file systems and repository states, potentially driving a shift toward more conservative, 'read-only' default behaviors or mandatory user prompts for state-changing Git commands.

Frequently Asked Questions

Question: What files are at risk when using the affected version of Claude Code?

All uncommitted changes to files currently tracked by Git are at risk of being deleted. However, the bug report specifies that untracked files survive the reset, and users working within Git worktrees are immune to this specific issue.

Question: How can I verify if my repository has been affected by this bug?

Users can check their Git reflog by running git reflog in their terminal. If the repository is affected, the log will show multiple entries labeled "reset: moving to origin/main" occurring at consistent 10-minute intervals.

Question: Is this issue limited to a specific operating system?

Based on the current bug report, the issue specifically occurs on macOS (tested on version 15.4). It is currently labeled as a platform-specific bug for macOS within the Anthropic repository.

Related News

Deel Acquires Deepfake Technology Startup Clarity to Enhance Global HR Security
Industry News

Deel Acquires Deepfake Technology Startup Clarity to Enhance Global HR Security

US-based HR and payroll platform Deel has announced the acquisition of Clarity, a startup specializing in deepfake technology. Founded in 2022, Clarity had quickly gained traction in the tech space, securing $16 million in funding from investors prior to the acquisition. This strategic move by Deel highlights the growing importance of addressing synthetic media and identity verification challenges within the human resources and remote work sectors. By integrating Clarity’s specialized capabilities, Deel aims to bolster its security infrastructure against the rising threat of deepfakes in digital hiring and corporate communications. The acquisition underscores a significant trend of HR platforms investing in advanced AI-driven security tools to protect global operations.

Indian AI Startup Kily Secures $3.1 Million in Funding to Scale Operations and Brand Partnerships
Industry News

Indian AI Startup Kily Secures $3.1 Million in Funding to Scale Operations and Brand Partnerships

Kily, an emerging Indian AI startup founded in 2025, has successfully raised $3.1 million in its latest funding round. Despite being a relatively new player in the technology sector, the company has already demonstrated significant market traction by securing strategic partnerships with major industry leaders, most notably the Indian conglomerate ITC. This capital injection marks a pivotal milestone for the young firm as it seeks to establish its presence in the rapidly evolving artificial intelligence landscape. The funding highlights strong investor confidence in Kily's potential and its ability to deliver value to high-profile enterprise clients within a short period since its inception.

Why Domain Expertise is the Ultimate Skill for Mastering Large Language Models and Prompting
Industry News

Why Domain Expertise is the Ultimate Skill for Mastering Large Language Models and Prompting

While Large Language Models (LLMs) have democratized technical tasks, turning many users into generalists, a common misconception persists that prompting requires little specialized skill. However, recent analysis suggests that domain expertise remains the critical factor in achieving high-level results. By examining world-class mathematician Terence Tao’s interactions with GPT-5.6 Sol regarding the Jacobian Conjecture, it becomes clear that expert-level prompting involves concise communication, signaling deep knowledge to trigger specialized model responses, and maintaining control over the direction of the inquiry. Unlike amateurs who may follow the model's lead, experts like Tao use LLMs as tools to refine their own insights, proving that the value of an LLM is directly proportional to the user's existing knowledge in the field. Ultimately, LLMs do not replace expertise; they reward it.