System environment date can be wrong, causing incorrect date-sensitive responses

Bug Report

The system prompt injects a date via The current date is: YYYY-MM-DD, but this can be stale/wrong. In my case, the system said 2026-02-08 when the actual date (from date command) was 2026-02-09 (Monday 9 February).

Impact

This caused Claude to repeatedly tell the user that a same-day meeting was "tomorrow" — even after the user corrected it multiple times. For anyone relying on Claude Code as a PA/scheduling assistant, this is a serious trust-breaking error.

Expected Behavior

The injected date should match the actual system date at the time of the conversation. Alternatively, Claude Code should be instructed to always verify the date via a date command rather than trusting the injected value.

Steps to Reproduce

1. Start a Claude Code session close to midnight (or when system date rolls over)
2. Ask about today's schedule/calendar
3. Observe that the system-injected date may be stale

Suggested Fix

• Ensure the injected date is computed at message time, not session start
• Or: add guidance in the system prompt that the injected date is approximate and should be verified with date for time-sensitive queries