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

Industry News

Perplexity Deploys GPT-6 Astra Across Critical End-to-End Workflows and Production Systems

According to an update published by OpenAI, Perplexity is leveraging the advanced capabilities of GPT-6 Astra across core end-to-end organizational and technical systems. The implementation spans multiple operational domains, with Perplexity using Astra to draft internal and external communications, modify and update software codebases, and maintain active monitoring over production environments. A notable shift in operational management highlighted in the report is that teams at Perplexity now require substantially fewer check-ins compared to their workflows with earlier artificial intelligence models. This adoption marks a significant milestone in software engineering and system oversight, demonstrating how higher-reliability model architectures enable organizations to delegate mission-critical maintenance and development tasks with less human intervention while sustaining production stability.

Waymo Robotaxi Pulls Over and Alerts San Francisco Police to Detain Armed Juvenile Riders
Industry News

Waymo Robotaxi Pulls Over and Alerts San Francisco Police to Detain Armed Juvenile Riders

In San Francisco, an autonomous Waymo vehicle pulled over and contacted law enforcement after detecting unauthorized activity involving two juvenile passengers. The incident resulted in the arrest of the two minors, who were found in possession of a loaded AR-style ghost gun inside the robotaxi cabin. Both suspects were taken into custody and transported to a juvenile hall. While initial police documentation did not explicitly identify who was operating or managing the vehicle during the ride, the event underscores the operational capabilities of autonomous fleets to monitor cabin security, respond to severe policy violations, and autonomously coordinate with local law enforcement to maintain public safety.

Hyundai Postpones In-House AI Driver-Assist System Launch to 2029 While Partnering with Nvidia
Industry News

Hyundai Postpones In-House AI Driver-Assist System Launch to 2029 While Partnering with Nvidia

Hyundai Motor Group has delayed the debut of its proprietary artificial intelligence driver-assistance software to late 2029, pushing back its original schedule by roughly two years. To maintain commercial competitiveness in the interim, the South Korean automaker is deepening its technical collaboration with Nvidia to roll out advanced Level 2+ and Level 2++ driver-assistance platforms starting in 2028. Hyundai's initial lineup of Nvidia-based vehicles will bypass expensive lidar sensors, relying instead on an integrated suite of optical cameras, radar units, and ultrasonic sensors. While lidar remains under active consideration for higher-tier Level 3 automated driving systems, Hyundai aims to utilize real-world driving data collected from its 2028 commercial fleet to train, validate, and mature its proprietary in-house autonomous software platform ahead of its rescheduled 2029 release.