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

Capcom Outlines Future AI Collaboration by Upgrading Proprietary RE Engine Through the REX Project
Industry News

Capcom Outlines Future AI Collaboration by Upgrading Proprietary RE Engine Through the REX Project

At the Capcom Open Conference RE: 2026, Japanese gaming powerhouse Capcom unveiled its vision for modern game development, preparing for a future where creators build titles alongside artificial intelligence. During a technical presentation by programmer Satoshi Ishida regarding the outlook and future of the REX Project—an evolutionary overhaul designed to upgrade the proprietary RE Engine for the next generation—the company detailed its strategy to integrate AI deeply into backend development workflows. Rather than generating finalized in-game assets with generative models, Capcom focuses on streamlining complex production pipelines, automating quality assurance, enhancing debugging systems, and improving iteration times across massive projects. By modernizing core engine systems and open-sourcing select components for AI training, Capcom establishes a balanced roadmap aimed at sustaining human artistic control while leveraging automated developer tooling.

Splice CEO Kakul Srivastava Warns That AI-Generated Emails Are Undermining Authentic Human Conversations
Industry News

Splice CEO Kakul Srivastava Warns That AI-Generated Emails Are Undermining Authentic Human Conversations

In an interview with The Verge, Splice CEO Kakul Srivastava expressed concerns that the increasing reliance on artificial intelligence for email generation is degrading genuine conversations. As the leader of Splice—a music sample platform widely used by music producers and behind chart-topping tracks like Lisa's 'Money' and Sabrina Carpenter's 'Espresso'—Srivastava brings a creator-centric perspective to modern communication technology. While AI tools continue to permeate daily productivity and business communication workflows, Srivastava argues that automating correspondence compromises the depth, nuance, and intent of interpersonal dialogue. This analysis explores Srivastava's perspective, examines Splice's influential position in creative audio workflows, and investigates the wider implications of automated text generation on professional collaboration.

OpenAI Safety Employee David Robinson Resigns and Sounds the Alarm Over AI Risks in The Atlantic
Industry News

OpenAI Safety Employee David Robinson Resigns and Sounds the Alarm Over AI Risks in The Atlantic

David Robinson, a key OpenAI employee responsible for authoring the formal safety reports accompanying every major model release, has resigned from his position at the company. Following his departure, Robinson authored an editorial in The Atlantic to publicly sound the alarm regarding the dangers and safety concerns surrounding artificial intelligence development. His resignation adds to a growing wave of industry insiders stepping forward to issue warnings about technologies they actively helped create. While public sentiment occasionally skews cynical toward former lab personnel voicing delayed warnings, Robinson's departure highlights persistent questions surrounding internal safety evaluations, organizational transparency, and public oversight across the AI ecosystem.