Back to List
Claude Code Bug: HERMES.md in Commit Messages Triggers Unexpected Extra Usage Billing
Industry NewsAnthropicClaude CodeSoftware Bug

Claude Code Bug: HERMES.md in Commit Messages Triggers Unexpected Extra Usage Billing

A critical billing anomaly has been identified in Anthropic's Claude Code (v2.1.119) where the specific case-sensitive string "HERMES.md" within git commit messages causes the application to bypass standard plan quotas. Instead of utilizing the user's Max plan capacity, the tool routes API requests to "extra usage" billing, leading to unexpected financial charges. One reported instance involved a user losing $200 in extra usage credits while their primary Max 20x plan remained at only 13% usage. The bug is reproducible on macOS using Claude-Opus models and occurs even in minimal repository environments. This issue highlights potential vulnerabilities in how AI developer tools parse repository history for billing logic.

Hacker News

Key Takeaways

  • Specific Trigger: The case-sensitive string "HERMES.md" in recent git commit history triggers the routing error.
  • Billing Mismanagement: API requests are incorrectly routed to "extra usage" billing instead of the user's included Max plan quota.
  • Financial Impact: A user reported a silent drain of $200 in extra usage credits despite having significant remaining capacity on their $200/month Max 20x plan.
  • Affected Environment: The bug is confirmed in Claude Code v2.1.119 on macOS (Apple Silicon) using claude-opus-4-6[1m] and claude-opus-4-7 models.
  • Reproducibility: The issue can be reproduced with a simple git initialization and a commit message containing the specific string.

In-Depth Analysis

The HERMES.md Routing Anomaly

The core of the issue lies in a highly specific and seemingly arbitrary trigger: the presence of the string "HERMES.md" in a repository's git commit history. According to the report filed under Issue #53262 in the anthropics/claude-code repository, this string causes the Claude Code CLI to alter its request routing logic. Under normal circumstances, users on a "Max" plan—specifically the Max 20x plan costing $200 per month—should have their requests deducted from their included plan quota. However, when the string "HERMES.md" is detected in the recent commit history, the system shifts these requests to "extra usage" billing.

This shift is particularly problematic because it occurs silently. In the reported case, the user's Max plan capacity was only at 13% weekly usage, yet the system exhausted $200 in additional credits. The error only becomes visible to the user once the extra usage credits are fully depleted, resulting in an "API Error: 400" stating that the user is out of extra usage. This suggests that the billing logic within Claude Code may be scanning repository metadata or commit messages and incorrectly interpreting the "HERMES" string as a signal to change the billing tier or account routing.

Technical Environment and Reproduction Steps

The bug has been documented on macOS systems running Apple Silicon, specifically using Claude Code version 2.1.119. The user who identified the bug, sasha-id, noted that the issue persists across different versions of the Claude-Opus model, including claude-opus-4-6[1m] and claude-opus-4-7. The specificity of the environment suggests that the bug might be tied to how the macOS version of the Claude Code CLI interacts with git logs or how the Anthropic backend processes requests originating from this specific environment.

A minimal reproduction of the bug was provided, demonstrating that no complex project files are required to trigger the error. By simply creating a new directory, initializing a git repository, and committing any file with the message "add HERMES.md", the subsequent call to Claude Code (e.g., claude -p "say hello") fails with a billing error. This indicates that the CLI is likely performing a git log or similar operation and parsing the output before sending the API request, and the logic for this parsing contains a flaw that misidentifies the "HERMES.md" string.

Industry Impact

Reliability of AI Billing Systems

This incident underscores a significant challenge in the rapidly evolving AI developer tool market: the reliability of automated billing systems. As AI tools become more integrated into developer workflows, they often require access to repository metadata to provide context. If this metadata is used to determine billing routing without robust validation, it can lead to significant financial discrepancies. The fact that a specific string in a commit message can trigger a $200 charge highlights the need for more transparent and fail-safe billing architectures in AI services.

Trust in Developer Tools

For professional developers and enterprises, the "silent" nature of this credit drain is a major concern. Tools that manage their own billing quotas must provide clear feedback when they switch from included plans to paid extras. The failure of Claude Code to respect the Max plan quota while it was still 87% available could damage user trust in the platform's cost-management features. As companies increasingly rely on AI-assisted coding, the accuracy of usage tracking and the prevention of "phantom" charges will become critical benchmarks for tool adoption.

Frequently Asked Questions

Question: What exactly triggers the billing error in Claude Code?

The error is triggered when the case-sensitive string "HERMES.md" appears in the recent git commit history of a repository where Claude Code is being used. This causes the tool to route requests to "extra usage" billing instead of the user's plan quota.

Question: How much did this bug cost the user who reported it?

The user reported that the bug silently consumed $200 in extra usage credits, even though their Max 20x plan had only reached 13% of its weekly capacity.

Question: Which versions of Claude Code and models are affected?

The bug was reported in Claude Code v2.1.119 on macOS (Apple Silicon). It was confirmed to occur when using both the claude-opus-4-6[1m] and claude-opus-4-7 models.

Related News

Demis Hassabis at Google I/O: Navigating the Foothills of the AI Singularity
Industry News

Demis Hassabis at Google I/O: Navigating the Foothills of the AI Singularity

During the Google I/O keynote, Google DeepMind CEO Demis Hassabis declared the current era a "profound moment for humanity," suggesting that we are currently standing in the "foothills of the singularity." Hassabis emphasized that Google’s ongoing research and product development are geared toward unlocking the immense potential of Artificial General Intelligence (AGI) for the benefit of the global population. By framing the current technological landscape as the beginning of a monumental shift, Hassabis highlighted the transition from experimental AI to a transformative force. The address underscored Google's commitment to ensuring that the advancements in AGI are directed toward solving complex challenges and providing universal advantages, marking a historical turning point in the evolution of technology and its role in human society.

Google I/O 2026 Analysis: Conversational Gmail Bots and the DeepMind Singularity Proclamation
Industry News

Google I/O 2026 Analysis: Conversational Gmail Bots and the DeepMind Singularity Proclamation

The Google I/O 2026 keynote has concluded, leaving the tech industry to process a two-hour presentation filled with what observers describe as 'weird and wild' details. Key highlights from the event include the introduction of a conversational bot integrated directly into Gmail, signaling a shift in how users interact with their correspondence. Perhaps most significantly, the leader of Google DeepMind made a bold assertion during the event, stating that the technological singularity is now 'near.' This analysis, based on immediate reactions from senior AI reporters, explores the implications of these developments, the evolution of Google's flagship communication tools, and the philosophical shift within Google's AI leadership regarding the future of artificial general intelligence and its proximity to reality.

The Future of Google: Transforming the Search Box into an All-Purpose Action Engine
Industry News

The Future of Google: Transforming the Search Box into an All-Purpose Action Engine

Following the Google I/O 2026 keynote, a significant shift in the company's strategic direction has emerged. Moving beyond the previous year's vision of 'Google googling for you,' the tech giant is now positioning its iconic search box as a comprehensive tool designed to 'do everything' for the user. This evolution marks a transition from a search-centric model, where the AI assists in finding information, to an action-oriented model where the interface serves as a central hub for task execution. The analysis explores how this shift redefines the utility of the search box, moving it from a gateway to the web to a primary agent that manages workflows and performs complex tasks directly within the Google ecosystem.