[BUG] date handling and not following instructions in CLAUDE.md
Environment
- Platform (select one):
- [ ] Anthropic API
- [ ] AWS Bedrock
- [ x] Google Vertex AI
- [ ] Other:
- Claude CLI version: 1.0.19
- Operating System: Macos 15.5
- Terminal: iterm2
Bug Description
Bug 1: Incorrect Date/Time Handling
- Claude Code should use the client computer's system time
- Currently appears to use an incorrect or outdated time reference
- Example: Answered "December" when the actual month is June 2025
Bug 2: Not Following .claude/CLAUDE.md Instructions
- Instructions in .claude/CLAUDE.md about date handling were ignored
- The file explicitly stated to use Central Time and June 11, 2025 as the date
- Claude Code should consistently read and apply these user-defined instructions
Steps to Reproduce
- edit the .claude/CLAUDE.md file and add this: Important guidance:
- We are in Central Time. Please make sure that all dates, times, etc are created based on Central Time.
- Date Format: Always interpret dates in M/D/YYYY format (US format). For example, 6/10/2025 means June 10, 2025, NOT October 6, 2025.
- launch claude in an empty directory
- ask it what month it is
Expected Behavior
Should reply June
Actual Behavior
Replied "December"
Additional Context
Then I asked it if it read my .claude/CLAUDE.md. Then it apologized and said that it forgot to follow my guidance.
But it would be best for it to handle dates correctly in the first place with out guidance.
Do you mean ~/.claude/CLAUDE.md? These are the 3 options: | 1. Project memory Checked in at ./CLAUDE.md │ │ 2. Project memory (local) Gitignored in ./CLAUDE.local.md │ │ 3. User memory Saved in ~/.claude/CLAUDE.md
Note that .claude/CLAUDE.md isn't one of them
Yes, I do mean ~/.claude/CLAUDE.md.
From: igorkofman @.> Date: Wednesday, June 11, 2025 at 2:52 PM To: anthropics/claude-code @.> Cc: Herring, TJ @.>, Author @.> Subject: [EXTERNAL] Re: [anthropics/claude-code] [BUG] date handling and not following instructions in CLAUDE.md (Issue #1963) [https://avatars.githubusercontent.com/u/469826?s=20&v=4] Caution: This message originated from outside AutoZone. Do not click links or open attachments unless you recognize the sender and know the content is safe.
igorkofman left a comment (anthropics/claude-code#1963)https://github.com/anthropics/claude-code/issues/1963#issuecomment-2963976763
Do you mean ~/.claude/CLAUDE.md? These are the 3 options: | 1. Project memory Checked in at ./CLAUDE.md │ │ 2. Project memory (local) Gitignored in ./CLAUDE.local.md │ │ 3. User memory Saved in ~/.claude/CLAUDE.md
Note that .claude/CLAUDE.md isn't one of them
— Reply to this email directly, view it on GitHubhttps://github.com/anthropics/claude-code/issues/1963#issuecomment-2963976763, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BTPDOXZBGLRZLSMYRNDK6YT3DCCHFAVCNFSM6AAAAAB7DF36FGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNRTHE3TMNZWGM. You are receiving this because you authored the thread.Message ID: @.***>
I have a similar issue with CLAUDE.md not executing required instructions
Bug Description Claude Code failed to follow explicitly documented instructions in CLAUDE.md
Expected Behavior According to CLAUDE.md, Claude should run the mandatory validation checklist after EVERY code change:
deno check file.tsdeno task lintdeno task fmt --check
Actual Behavior
Claude only ran step 1 (deno check) and skipped step 2 (deno lint) until prompted by user
Steps to Reproduce
- Provide CLAUDE.md with explicit mandatory checklist instructions
- Ask Claude to make a code change
- Observe that Claude doesn't run the complete checklist automatically
Context
- The instructions were clear and unambiguous
- Claude acknowledged understanding the instructions
- Claude had access to all required tools
- No technical barriers prevented running the full checklist
Impact This could lead to accumulated technical debt when Claude skips validation steps, which the instructions specifically warn against.
Environment
- Claude Code CLI
- Model: Sonnet 4 (claude-sonnet-4-20250514)
- File: TypeScript in Deno project
This type of instruction-following reliability issue seems worth reporting since it affects workflow consistency.
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.