The time shown in Cursor is weird

Support Bug Reports
1

2b883247b7c22abc163ca51b08f09a96
2b883247b7c22abc163ca51b08f09a961136×102 15.1 KB

Where does the bug appear (feature/product)?

  • Something else… (macOS Cursor.app bundle timestamp / Finder Date Modified)

Describe the Bug
On macOS, Cursor.app shows Date Modified: January 1, 1980 00:00 in Finder (see screenshot). Cursor itself still runs, but the app bundle root timestamp is wrong.

This is not just a Finder display glitch. stat on /Applications/Cursor.app also returns 1980-01-01 00:00:00 for both mtime and birth time. Files inside Contents/ have correct timestamps from the real build/install date (2026-08-11).

1980-01-01 00:00 is the DOS/FAT epoch, which often happens when an .app is packaged via zip without restoring real timestamps.

Steps to Reproduce

  1. Install Cursor 3.15.19 on macOS.
  2. Open Finder → Applications, switch to list view, show the Date Modified column.
  3. Look at Cursor — it shows 1980年1月1日 00:00.
  4. Optionally run:
stat -f '%Sm %SB' -t '%Y-%m-%d %H:%M:%S' /Applications/Cursor.app

Expected Behavior
Cursor.app Date Modified / birth time should match the actual install or build time (for this build: around 2026-08-11), not January 1, 1980.

Screenshots / Screen Recordings
Screenshot attached above.

Operating System

  • MacOS 15.7.7 (Build 24G720)

Version Information

Version: 3.15.19
VSCode Version: 1.128.0
Commit: de07bee81cefe43461ebf4f40c3d2d78d15052a0
Date: 2026-08-11T05:22:54.627Z

For AI issues: which model did you use?
N/A — not an AI issue.

Additional Information
Verified locally:

  • /Applications/Cursor.app mtime + birth = 1980-01-01 00:00:00
  • kMDItemFSContentChangeDate = 1979-12-31 16:00:00 +0000 (UTC equivalent of 1980-01-01 00:00 in UTC+8)
  • /Applications/Cursor.app/Contents mtime = 2026-08-11 06:07:58
  • /Applications/Cursor.app/Contents/MacOS/Cursor mtime = 2026-08-11 06:04:14

Does this stop you from using Cursor?

  • No - Cursor works, but with this issue
2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

7

Hey there! Nothing’s wrong with your install - that 1980 date is just a cosmetic packaging quirk in how macOS updates are archived, not a sign anything’s broken or out of date. Signing, launching, and updates all work normally, and your real version is under Cursor > About Cursor.

It’s not intended behavior and we’ve let the team know, but it’s safe to ignore.