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
Share

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.

Read original article

Related News

SpaceX Completes Landmark $60 Billion Acquisition of AI-Powered Coding Tool Cursor
Industry News

SpaceX Completes Landmark $60 Billion Acquisition of AI-Powered Coding Tool Cursor

SpaceX has officially finalized the acquisition of Cursor, a specialized coding tool developed by the San Francisco-based startup Anysphere. The transaction, valued at $60 billion, marks a significant milestone for Anysphere, which was founded in 2022 by four students from the Massachusetts Institute of Technology (MIT). This acquisition brings the innovative software development tool under the SpaceX umbrella, highlighting a massive investment in high-end coding infrastructure. The deal reflects the high valuation of modern software tools and the rapid growth of the startup, which transitioned from a student-led project to a multi-billion dollar asset in just four years. The completion of this buy-out underscores the strategic importance of advanced programming environments in the current technological landscape, particularly for organizations managing complex engineering and software requirements.

Industry News

The Cycle of Reinvention: Why Engineers Often Overlook Historical Precedents in Statistics and Finance

This analysis explores the provocative claim that the engineering community frequently avoids learning from history, leading to the repetitive reinvention of established fields. Based on observations from the tech industry, the article examines how disciplines such as statistics and finance have been 'reinvented' by engineers who apply new technical frameworks to old problems, often without acknowledging prior historical lessons. The narrative highlights a recurring pattern where technical innovation is prioritized over historical context, leading to a cycle that has now reached a new, critical juncture. By analyzing the transition from statistics to finance and into the current era, we uncover the implications of this 'not invented here' syndrome and what it means for the future of technical development and industry stability.

Your AI Slop Bores Me: A New Roleplaying Experience Where Humans Mimic Chatbots to Critique Artificial Intelligence
Industry News

Your AI Slop Bores Me: A New Roleplaying Experience Where Humans Mimic Chatbots to Critique Artificial Intelligence

"Your AI Slop Bores Me" is a unique digital experience that turns the tables on artificial intelligence by having humans roleplay as chatbots. The platform features a simple two-tab interface: one for the "human" requester and one for the "AI" responder. Unlike traditional Large Language Models (LLMs), both sides of this interaction are powered by real people. This setup allows users to engage in a Live Action Role Play (LARP) of an AI, highlighting the often repetitive and predictable nature of machine-generated content. By removing the actual AI from the equation, the project offers a satirical look at current technology trends and the quality of automated responses, challenging the value of the "slop" that currently floods the digital landscape.