Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
When performing searches or generating documents that depend on the current time context, the Cursor agent consistently assumes the year 2024 instead of using the actual system date (2025). This happens unless the user explicitly provides the current date or manually runs a script to fetch it.
Example:
In the screenshot below, the agent searched the web using the keyword “Cursor IDE best practices 2024”, even though the current year is 2025
Steps to Reproduce
Open a new Cursor project or chat.
Ask the agent to:
“Search web Cursor IDE .cursor folder best practices.”
or “Generate daily log for today.”
Observe that it references 2024 in the query or generated file.
Expected Behavior
The agent should automatically detect the current year (e.g., 2025) from the system or runtime environment, ensuring that generated queries and files reflect the correct date.
Actual Behavior:
Without explicit date hints, the agent defaults to 2024, producing outdated search queries, filenames, and documentation.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.7.54 (system setup)
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
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
Does this stop you from using Cursor
No - Cursor works, but with this issue
