Agent doesn't know what day it is

[baronyoung]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Often when I send the first prompt for a day, especially after a weekend, the agent is confused about what day it is. This usually results in a wasted prompt as I have to explain what day it is. I suspect it’s because the chat was opened on a different day and I continue with a new prompt on a new day. I’d think it makes sense though to make sure with each prompt there’s a current timestamp associated with it. If this is already happening there is an issue with it.

Steps to Reproduce

Open a chat on a Saturday. On Monday, send a prompt that has something to do with the current day (e.g. ask about a current stock price). It’ll say “Since it’s Saturday the market is closed.”

Expected Behavior

The prompt should be accompanied by a timestamp or there should be at least some way for the agent to know what day it is when prompted without that having to be included.

Operating System

Linux

Version Information

Version: 2.6.18
VSCode Version: 1.105.1
Commit: 68fbec5aed9da587d1c6a64172792f505bafa250
Date: 2026-03-10T02:01:17.430Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Linux x64 6.17.0-19-generic

For AI issues: which model did you use?

Opus 4.6 Max

Does this stop you from using Cursor

No - Cursor works, but with this issue

[MidnightOak]

I do think a feature request could be to add the timestamp of the local machine with every request. But for now, this is a workaround:

Create a rule:
when a request is related to the time or date or day of the week, use a cmd date command to get the current date before responding

Then add PowerShell or cmd (whichever it prompts) to allow list.

---

Before

Which like you said is probably something defined when the chat is started.

After

[deanrie]

Hey, thanks for the report. This is expected behavior right now, the current date and time aren’t passed to the agent prompt. This came up before, and there’s an open feature request you can vote for: Cursor needs to be aware of the current date

@MidnightOak suggested a working workaround above using a rule, that’s the simplest option for now. Alternatively, you can use a Time MCP server, for example this one: GitHub - fisher1006/time-mcp · GitHub

Let me know if the workaround helps.

[baronyoung]

Thanks for the suggestion. Yes, that’s a perfectly reasonable solution (a rule).