Windows: duplicate CLAUDE.md loaded due to drive letter casing

[NoRain211]

Description

On Windows, the global ~/.claude/CLAUDE.md file is loaded twice in the same session because the drive letter casing differs between two resolution paths:

1. C:\Users\<user>\.claude\CLAUDE.md (uppercase C:) — resolved by Claude Code itself
2. c:\Users\<user>\.claude\CLAUDE.md (lowercase c:) — resolved by the VSCode extension passing the workspace root

Since Windows paths are case-insensitive, these refer to the same file, but Claude Code treats them as distinct and loads the file twice.

Impact

• ~1.4k tokens wasted per session on duplicate content
• The duplicate appears as two separate entries under Memory Files in /context

Expected Behavior

Claude Code should normalize Windows drive letter casing (or do case-insensitive path comparison) before loading CLAUDE.md files to avoid duplicates.

Environment

• Windows 11 Pro 10.0.26200
• Claude Code v2.1.37
• Running via VSCode extension

[andreszs]

Yet another error for my rapidly growing list of reasons this tool is becoming hard to justify in a paid workflow:

• Claude will revert commits without asking and happily discard uncommitted changes. Then it informs you after the fact with something along the lines of: “Your uncommitted changes were lost; you’ll have to redo them. Good luck with that.”
• Claude will wander into train-of-thought dead ends and effectively burn the customer’s entire approved balance down to $0 with no usable output, instead of detecting that it’s stuck and stopping to ask whether to continue.
• Claude is painfully slow on trivial tasks that Copilot finishes in seconds—Claude takes minutes, consuming far more tokens in the process.
• Claude tends to create corrupt nul files in Windows due to some ill-management of the filesystem.
• Claude will cut off responses mid-edit when tokens run out, leaving your code in a broken/unbuildable state and essentially saying: “See you in 6 hours. Good luck fixing your now-broken code.”

At this point it’s less “AI assistant” and more “surprise-cost generator with a side of repository vandalism.”

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.