Agent interprets「今日」from chat summary instead of current session date

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When the user said「今日の分ね」(process today’s batch), the Agent continued work for 20260622 based on a conversation summary from a prior session, instead of treating「今日」as the current calendar date.

Additionally, session user_info injected Today's date: Monday Jun 22, 2026, while the user later corrected that the actual date was June 23. The Agent processed the wrong day’s inbox until explicitly corrected.

Steps to Reproduce

  1. Complete a multi-session Agent task tied to date D (e.g. 20260622).
  2. Next day (D+1), start a new session where user_info may still show D or a summary references D.
  3. User says「今日の分ね」without repeating the date.
  4. Agent continues processing folder D instead of D+1 until user explicitly corrects the date.

Expected Behavior

「今日」should resolve to the session Today's date in user_info. Conversation summaries must not be used as the calendar date for「今日」. Explicit user date corrections must always override prior context.

Operating System

Windows 10/11

Version Information

Cursor IDE on Windows 10 (build 26200). Agent mode. Observed June 23, 2026.

For AI issues: which model did you use?

Agent (various models in multi-session workflow)

Additional Information

Workflow uses date-based inbox folders (YYYYMMDD). User said「今日の分ね」; Agent processed 20260622 until user corrected to June 23. Possible contributing factors: stale user_info Today’s date + conversation summary anchoring to prior session date.

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

When an Agent chat keeps going across more than one calendar day, the “Today’s date” it was handed at the start of that chat sticks for the rest of the conversation instead of rolling over, and a long chat’s running summary can still point at the previous day’s folder. So when you say「今日の分ね」, the agent resolves「今日」to the day the chat began (20260622) rather than the actual current date.

Two things that reliably avoid it:

  1. Start a fresh chat for each day’s batch. A new chat picks up the correct current date and drops the prior day’s summary, so「今日」resolves correctly.
  2. If you keep one long-running chat, name the date explicitly (e.g. “process the 20260623 folder”). An explicit instruction overrides the older context, which matches what you saw when correcting it manually.

I’ve flagged the multi-day date behavior to the team so we can improve how the date refreshes in long-running chats, and I’ll update here if there’s progress.