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

AI-Driven Hardware Exploitation: Researcher Uses AI Agents to Reverse Engineer and Control Peripherals
Industry News

AI-Driven Hardware Exploitation: Researcher Uses AI Agents to Reverse Engineer and Control Peripherals

A security researcher has demonstrated the power of agent-driven reverse engineering by gaining unauthorized control over common hardware peripherals. Using Claude Opus 5, the researcher successfully analyzed the firmware of a microphone, a webcam, and a key light. The results include discovering a plaintext command shell within a microphone, the ability to disable a webcam's activity LED during recording, and enabling unauthorized memory writes on a key light via WiFi. This experiment underscores the efficacy of using AI agents to iterate against firmware update mechanisms and protocol surfaces, transforming peripherals—essentially 'tiny computers'—into accessible targets for automated security analysis and exploitation.

Investigating the Origins of Ox Alpha: The Mysterious New Stealth AI Model Sparking Online Speculation
Industry News

Investigating the Origins of Ox Alpha: The Mysterious New Stealth AI Model Sparking Online Speculation

A new and enigmatic AI model known as Ox Alpha has surfaced, triggering a significant wave of interest and intense speculation across various digital communities. Currently characterized as a "stealth model," Ox Alpha has managed to capture the attention of the tech world despite a lack of official documentation or public disclosure regarding its creators. The emergence of this model has driven specific segments of the internet into a "frenzy of speculation," as experts and enthusiasts attempt to identify the organization or individuals behind the project. As the AI industry continues to evolve at a rapid pace, the appearance of unannounced models like Ox Alpha highlights a growing trend of mystery-driven releases that challenge traditional product launch cycles and fuel curiosity within the global developer community.

Industry News

Anthropic's Premium AI Models Face Adoption Challenges as Market Favors Cost-Effective Solutions

Recent market observations indicate that Anthropic's most advanced artificial intelligence models are encountering significant hurdles in attracting a broad user base. Despite the technical prowess of these high-end offerings, there is a visible shift in the industry toward more affordable and accessible AI alternatives. This trend suggests that while performance remains a key metric, the economic reality of AI implementation is driving users toward 'good enough' solutions that offer a better balance of cost and utility. As cheaper tools continue to thrive, the strategic positioning of premium AI developers like Anthropic is being tested, highlighting a potential disconnect between peak model capabilities and actual market demand in an increasingly price-sensitive environment.