Cursor window shadow on macOS disappeared

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I just updated Cursor to the latest version on macOS. The window shadow has disappeared. It’s impossible to distinguish Cursor windows from the rest of my desktop.

Here is a screenshot of Cursor window on top of another Cursor window. Not really usable.

Is there some configuration I can change on my side, or is this a bug that needs to get fixed?

Steps to Reproduce

Launch Cursor latest version

Expected Behavior

Window has shadow and is usable

Screenshots / Screen Recordings

Screenshot 2025-09-29 at 10.25.19.png
Screenshot 2025-09-29 at 10.25.19.png2574×1754 301 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.12
VSCode Version: 1.99.3
Commit: b3f1951240d5016648330fab51192dc03e8d7050
Date: 2025-09-28T00:58:08.696Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

16 Likes
Cursor Still on VSCode 1.99.3: Update Plans?
2

i also have this, since 1.7

1 Like
3

Hey, thanks for the report. We’ll look into it.

2 Likes
5

I’m having the same problem.

6

Same.

7

Hi everyone. I believe this is was one common issue for VSCode based editors in macOS 26.0 and will likely be available once the upstream bugfix is merged.

8

Hmm. I’ve been on macOS 26 since its original developer beta in June and only began experiencing this Cursor bug today (1.7.12). I don’t get the bug in VSCode (1.104.2).

9

The update is for all macOS versions which is why you may have encountered it after update of Cursor. Its likely the bugfix which prevents macOS 26.0 performance issues. If VSCode didn’t release it yet they may be affected.

10

Same issue here.

Mac OS:

26.0 (25A354)

Cursor:

Version: 1.7.17
VSCode Version: 1.99.3
Commit: 34881053400013f38e2354f1479c88c9067039a0
Date: 2025-09-29T03:10:26.099Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

11

@backbone-link thank you we, team is notified already.

1 Like
12

The latest VSCode Insider build is also experiencing this issue, as it’s aimed at addressing performance problems.

1 Like
13

Same here. Does anyone know how to workaround?

14

Same problem

15

btw, relevant info here https://x.com/normarayr/status/1969940110218055917

16

I’m livid they haven’t fixed this yet. The fix is out and they have rolled an update and it wasn’t incorporated.

2 Likes
17

This issue is still ongoing.

Version: 1.7.38
VSCode Version: 1.99.3
Commit: fe5d1728063e86edeeda5bebd2c8e14bf4d0f960
Date: 2025-10-06T18:18:58.523Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

2 Likes
18

Same here, quite annoying.

4 Likes
19

Same issue here, please correct!

1 Like
20

Is this a big problem? It hasn’t been fixed for half a month. Is it because the problem code cannot be located?

2 Likes
21

Every time I see “a new version is available” I keep hoping it will be fixed, but nope!

6 Likes