When asking cursor to add the current date to documents it used an incorrect date

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I asked cursor to post today’s date and it used January 27,2025 instead of the actual date October 7, 2025, it perptrated this through multiple files in my codebase and I only caught it on manual review. It even used that incorrect date in changelog and on web pages.

Steps to Reproduce

asked it to update something with today’s date. It has not repeated that since I told it to correct the date today.

Expected Behavior

Post the actual date of the day it actually is.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.38 (user setup)
VSCode Version: 1.99.3
Commit: fe5d1728063e86edeeda5bebd2c8e14bf4d0f960
Date: 2025-10-06T18:18:58.523Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

model set auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
2

A common problem with all LLMs is date awareness:

There are 2 workarounds; a datetime MCP, or I prefer requesting that the model uses the terminal to get the current date.

I have noticed Sonnet 4.5 doesn’t seem to present the same date issues as other models.

3

yeh, this happens with most of the llm’s, its not specifically a cursor issue.
knowing never to trust it to know the date, even when you tell it earlier in a session, is a base solution if you can’t find a more permanent one.

1 Like
4

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.