Cursor not aware about the date when thinking

[tiborrr (Tibor)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When looking on the internet for best practices for anything Cursor often uses the wrong year. I think making sure that thinking uses the correct year is something that should be handled by the model and not by the user.

I saw the following log today:

Web search results for query: opentelemetry-python metrics exporter OTLP FastAPI worker 2024

This was using Composer 1.5

Steps to Reproduce

This was my query approximately, but it’s not deterministic offcourse:

I use this stack for monitoring all applications accros different servers.

Currently our applications are not sending any metrics on how they are performing to grafana. Our stack runs mostly FastAPI python applications and scheduled background processes.

What I want is a instruction on how my colleagues need to export metrics on their applications.

Expected Behavior

Web search results for query: opentelemetry-python metrics exporter OTLP FastAPI worker 2026

Operating System

Linux

Version Information

Version: 2.6.11 (user setup)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
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: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer 1.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. This is a known issue that was fixed before, but it looks like it might be happening again with Composer 1.5.

Could you share the Request ID from that chat session? You can copy it from the chat context menu in the top right corner, then select Copy Request ID. That’ll help us figure out what’s going on.

For now, as a workaround, you can mention the current year in your prompt, like “search for 2026 best practices for…” It’s not ideal, but it should help until we get this sorted out.

Let me know if this keeps happening or if it was just a one-off.

[tiborrr (Tibor)]

This is the request ID 735767c8-b828-45b1-8039-fb63ea139cfd