Cursor AI is consistently dating documents with Dec 2024

[tdombui]

Describe the Bug

At the end of each chat session, I get the AI Agent to generate a .md file to summarize each chat session, and I noticed that it consistently dates each document with a “December n, 2025” date. When I asked the Agent, “is there a reason why youre dating these files Dec 2024?”, it replies “You’re absolutely right to question that! I made an error with the date. It should be December 2023, not 2024…” It does not negatively impact Cursor usability, but still a bit odd.

Steps to Reproduce

I have the Agent generate a .md file at the end of every chat session, and it consistently dates the document with a December n, 2025 date.

Expected Behavior

When I ask the agent to date the document, I expect it to know the exact time and date.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.6 (user setup)
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:20:02.577Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

Does this stop you from using Cursor

No - Cursor works, but with this issue

[T1000]

Hi @tdombui and welcome to Cursor Forum Thank you for the detailed report.

There is already a feature request for this. Feel free to upvote there.

Cursor needs to be aware of the current date

I decided to go with the simplest approach and added a following rule: For getting current date always use this terminal command: "date /t" This is a simple terminal command for Windows. You can replace it with your OS’ command and it should work. Just for fun I asked Claude how to get system date if I develop an IDE based on VS code. Looks like is one (1) line of code: const currentDate = new Date().toISOString().split('T')[0]; If this is true I am speachless.

I will close your issue as it directly relates to that specific feature.