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

Mapping the Landscape: Identifying the Most Active Investors in Asia's Artificial Intelligence Sector
Industry News

Mapping the Landscape: Identifying the Most Active Investors in Asia's Artificial Intelligence Sector

The Asian artificial intelligence landscape is witnessing a significant influx of capital as specialized investors prioritize regional startups. According to data compiled by Tech in Asia, a specific group of venture capital firms and investment entities has emerged as the most active participants in the market. These investors are strategically pouring resources into AI-driven enterprises across the continent, signaling a robust period of growth for the industry. While the specific investment volumes vary, the collective activity of these firms highlights Asia's growing importance as a global hub for AI innovation and development. This report identifies the key players currently leading the charge in funding the next generation of Asian AI technologies.

Industry News

The Resurgence of Free Software: How AI Coding Agents Are Reviving Stallman’s Vision in the SaaS Era

The rise of AI coding agents is shifting the paradigm of software freedom, moving it from an academic debate to a practical necessity. While the Software as a Service (SaaS) model previously rendered the distinction between 'open source' and 'free software' largely irrelevant to average users, AI agents capable of reading and modifying codebases are changing the landscape. By enabling users to customize and repair software through automated agents, the ability to access and modify source code—a core tenet of Richard Stallman’s free software philosophy—becomes a tangible capability. The article explores how the limitations of proprietary SaaS models are becoming apparent when contrasted with the potential of agent-driven customization, echoing historical struggles for software autonomy like Stallman’s 1980 encounter with a proprietary Xerox printer.

Industry News

Inside the Decryption of Cloudflare Turnstile: How ChatGPT Verifies React State Before Allowing User Input

A technical investigation into ChatGPT's security measures reveals that Cloudflare Turnstile performs deep inspections of the React application state before permitting user interaction. By decrypting 377 instances of the Turnstile program, researchers discovered that the system checks 55 distinct properties across the browser, network, and the ChatGPT Single Page Application (SPA) itself. Unlike standard fingerprinting, this method verifies that the specific React environment—including internal objects like __reactRouterContext—has fully booted. The decryption process exposed a multi-layered security chain where the server sends encrypted bytecode (turnstile.dx) that is XOR'd with specific tokens. This deep integration ensures that bots cannot simply spoof browser headers; they must render the actual functional application to pass verification.