Hey, thanks for the report, this is a known issue. There’s already a similar thread.
The problem is that the user_info context sends 2025 instead of 2026. The team is aware, but there’s no timeline for a fix yet. Your report helps show that this also affects Composer 1.5, not just Auto mode.
If you can reproduce this @Datahenge, can you send over a Request ID with privacy mode disabled (Cursor Settings > General > Privacy) before starting the request?
If you can reproduce this @Danny_Rappleyea, can you send over a Request ID with privacy mode disabled (Cursor Settings > General > Privacy) before starting the request?
The metadata Cursor sends to the AI at the start of a conversation includes a “Today’s date” field. That value can be wrong by one year (e.g. “Saturday Feb 21, 2025” when the actual date is in February 2026). The AI may then use the wrong year (e.g. in copyright text).
Steps to Reproduce
Start a new Cursor conversation in February 2026 (or when your system date is 2026).
Ask the AI to do something that uses “today’s date” (e.g. add an MIT LICENSE with the current year).
Check what year the AI used (e.g. in the LICENSE file).
Expected Behavior
“Today’s date” in the context sent to the AI should match the user’s current system date (e.g. 2026 when it is 2026).
System date/time was correct (2026). The wrong year (2025) appeared to come from the user_info (or equivalent) context Cursor injects, not from the OS.
Turns out this can still show up and is quite baked into the model itself (our changes to the system prompt have had mixed results). We expect this to get fixed in future model releases!
