Claude Code development environment, leading to unexpected financial charges for users. Engineers discovered that including specific text strings in Git commit messages triggers an erroneous billing event that drains user credits prematurely.
Bug Triggers Unintended Billing for Claude Code Users
The issue centers on the inclusion of the string HERMES.md within a Git commit message. When this specific filename appears in a commit, the system incorrectly routes requests to a pay-as-you-go billing tier rather than utilizing the user’s existing subscription quota.
One affected engineer, known as sasha-id, reported that they were subscribed to the Max 20x plan. Despite having consumed only 13% of their weekly allocation, the system prematurely deducted $200.98 in credits. This depletion triggered an “Insufficient remaining data” error, effectively halting the user’s ability to utilize the service.
Technical Investigation of the Billing Anomaly
Following the discovery, users investigated the scope of the GitHub issue to determine the exact conditions causing the error. The investigation confirmed that the billing trigger is highly specific to the exact casing and inclusion of the HERMES.md string.
The system reportedly treats these specific commits as external API requests outside the standard plan coverage. If the file name is altered or the casing is changed, the system resumes normal operation. This suggests the bug is tied to how the environment parses repository metadata during the commit process.
Anthropic Response and Resolution Timeline
The incident gained significant traction after being shared on social media on April 26, 2026. Initial responses from Anthropic’s automated support systems indicated that the company would not provide compensation for service degradation or incorrect billing routing caused by technical errors.
However, Thariq, a lead developer associated with the project, later clarified that the issue stemmed from a third-party harness detection mechanism. This component was incorrectly pulling Git status information into the system prompt. Anthropic confirmed that the fraud prevention system had been over-activated, leading to the erroneous charges.
Industry Impact and Community Reaction
The situation escalated when affected users found that promised refunds were not immediately processed despite public assurances. The delay led to the issue becoming a topic of discussion on Hacker News, highlighting the growing tension between developers and platform support responsiveness.
Sasha-id eventually noted that the refund was processed on April 30, 2026, four days after the initial report. The developer confirmed that affected users would receive both a full refund and an additional month of credits as compensation for the disruption.
Future Monitoring of Billing Integrity
Users should remain vigilant regarding their account credit usage when performing automated Git operations. While the specific HERMES.md bug has been addressed, the incident serves as a reminder to monitor billing statements for discrepancies in automated development environments. Continued oversight of platform updates is recommended for all professional users.
Follow Hashlytics on Bluesky, LinkedIn , Telegram and X to Get Instant Updates
