The user_info block passed in the system context uses the wrong year for “Today’s date”, it is still stuck in 2025.
This causes Cursor to use the wrong date wherever a timestamp is needed (e. g.: creating Doctrine migrations).
Steps to Reproduce
Ask Cursor to “display user_info”.
Expected Behavior
“display user_info” should return the correct Date:
Today’s date: Tuesday Mar 17, 2026 (or whatever the actual current date is).
Hey @Igor_Treptau It looks like this issue has already been reported by other users and has been classified as a bug by the Cursor team.
Based on their latest reply, recent changes to the system prompt have had mixed results, and they expect the issue to be resolved in a future model release.
Hey, this is a known issue. There are already a few threads about it: Today is the Wrong Year
We shipped a fix before, but the bug can still happen for some users. The team is aware.
Can you send the Request ID from the chat where the date was wrong? Chat menu in the top right > Copy Request ID. This will help us see what exactly the server is sending.
As a temporary workaround, you can explicitly include the year in your prompt, like “it is 2026 now”, or add it to your project rules.