I often need to add a last updated timestamp to my apps. For example on developer documentation etc.
Cursor consistently gets the date and year incorrect and when I query it, says it doesn’t have access to the date and time.
is this normal ?
Prompt: Can you tell me what day and date and time it is?
Cursor: Today is Wednesday, February 14, 2024. I don’t have access to the current time.
Hey, yes, that’s normal. No AI through an API will tell you what today’s date is because they don’t have access to real-time updates.
OpenAI:
Anthropic:
Its unexpected in the context of coding. Certain files need current date at least if not even time. I believe as Cursor added coding features for AI this part is missing
I also would like to use the current date in the naming of my adrs for instance.
I wonder if you could work around this limitation of LLMs with an mdc rule forcing cursor to run ‘date “+%Y-%m-%d”’ at the beginning of a composer session and use it inside the files created.
Here is my workaround that works in composer.
.cursor/rules/105-composer-date.mdc file with the below content# Composer Date Handling
## Context
- When working with composer files or documentation that requires current date
- When date formatting needs to be consistent across the project
- When automated date insertion is needed
## Requirements
- Execute `date +%Y-%m-%d` to get the current date in YYYY-MM-DD format
- Store the date result in context for use in the current session
- Use the stored date consistently across all files that need it
- Update the date when a new session starts or when explicitly requested
## Examples
<example>
When asked about the current date or needing to insert it:
1. Execute: `date +%Y-%m-%d`
2. Store result (e.g., "2024-03-21")
3. Use stored date in files or responses
</example>
<example type="invalid">
- Do not hardcode dates
- Do not use different date formats
- Do not skip executing the date command when a new date is needed
</example>
Kinda overengineered, but why not 
sure but spending a prompt every time the IDE needs to include a date into code or docu? ufff
FYI: The ChatGPT interface includes the current date in its system prompt, and Zed supports this via a command.
To work around this I created a crontab in my system that will update a Cursor rule e.g. 0000-current-datetime.mdc with the current datetime e.g. 2025-03-03 17:56 CET. You then have to gitignore that file.
This is way over engineered as well but at least it does not require any command breaking the LLM output streaming.
@Cursor team please add this in context 
yeah, its interesting that Cursor always ads CWD to the prompt where its actually strange to have it sent to AI all the time unnecessarily. date-time would help so much.
That’s “normal” but it would be trivial to include the date of the current day in Cursor’s system prompt, and furthermore the current time.
I have a recurring issue in Cursor, where I give it instructions to look in my application’s logs for errors, but it will bring back days old issues as it has absolutely no sense of time and as people previously said I see this being an issue with things like updating documentation and such…
Including in Cursor’s system prompt the date would only add a few tokens per request, if that’s too expensive to include in all requests for Cursor by default it would be nice to at least have the option of including the current time.
Wouldnt being more specific at what logs to look at or to look at highest date or latest entries etc. help with this?
Sure, and Cursor already has the idea to pipe my log command through tail to get the last fifty lines, I think I’ll just add this to my instructions, but if I get a longer error message it may truncate it halfway through…
And including date and time would still be a positive change for other reasons, maybe there’s a technical reason why Cursor’s engineers don’t include it in their system prompt, but as ChatGPT does it I don’t see why it would be more of an issue in Cursor.
Yeah it would be practical, agreed 
As a workaround for now some use scripts to insert date at end of .cursorrules when they start Cursor, or anywhere else practical (incl. snippets as keyboard shortcuts etc..)
update: I use this mcp server now. quite easy to extend it with a always applied or agent requested mcp rule so that
it can figure out when to use it
Hmm the agent 2 agent (A2A) protocol could also be added by having a local LLM check if an agent is doing work and inject the current time into prompt. Just kidding.
Most performant solution is a date statement in the shell init file to output on shell start the current date and time. No MCP calls required, no prompt injections etc.
Ah yes, more cursorrules cause why not? At this point, I have more cursor rules than my actual code.
Same issue still happening.
From today (June 24 2025):
That’s definitely interesting and clearly a bug! June 24, 2025 is in the future - that date hasn’t happened yet. This suggests there’s a date/time handling issue, likely related to your recent migration.
I understand some people say that AI knowing the date isn’t part of it’s remit and it shouldn’t access the users internal computer clock. But if it can access the web, it could simply check in on any internet clock etc.
In my use case, I have launched a web app where exact timing of SSL Certificates lifespan is critical on (https://www.ChillSSL.com).
Although most of the date and time function is handled by other integrations, almost every time we create a dated PRD or are bug-fixing a time stamp issue, Cursor will tell me I’m either picking a date in the future or think it’s 2024.
