Nightly cursor should run nightly agents

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I expect that Nightly cursor should run Nightly windows, but it runs “Stable Cursor” for some reason. They should not interfere.

Steps to Reproduce

see the image

Expected Behavior

see above

Operating System

MacOS

Version Information

cursor 3.6.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi Eugen,

I’m not sure what you’re showing me in your screenshot! Could you add some more detail? Where do you see nightly cursor running “stable cursor”?

Nightly version is sandy. There I clicked (1) and that click ran the usual cursor (2). I expect to continue to work at Nightly.

Interesting. I can’t reproduce that on my end, and it shouldn’t be possible for that button to launch a different install! How did you determine that it’s opening a different flavor of Cursor?

The nightly has solarized theme, but this new window has a theme from Cursor stable installation.

I just tried to check the version for that window and got this:

So I am not sure / can not confirm the exact version of Cursor for this new version.
My version is:
Version: 3.6.33
VS Code Extension API: 1.105.1
Commit: 453f0b5a181a2308f4194369774059e533143529
Date: 2026-06-01T01:38:32.281Z
Layout: editor
Build Type: Nightly
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Darwin arm64 25.3.0

Though for 3.0.48 (pre 48?) I had not seen crash.

Have you explicitly configured the Agent Window to have a solarized theme? Themes do not automatically carry over between the Editor Window and the Agents Window; they must be configured under Settings > Appearance.

If your application name in the upper left of your screen remains Cursor (Nightly) and not Cursor, you should be confident you stayed in the same app!

Have you explicitly configured the Agent Window to have a solarized theme?

No, I suppose the theme configuration is global. Why a separate configuration should be done for every window?? I do not expect that.

f your application name in the upper left of your screen remains Cursor (Nightly) and not Cursor,

I do not know, at the moment it crashes instantly =(

Ok. After today’s upgrade the Cursor crashes instantly. I see this white/black theme from the start. It works 5-10 seconds and then crashes.

I even can not copy the version, But I saw 3.7.9.

it seems Cursor nightly stopped to load the correct theme. I am not sure how theme belongs to crashes though.

here is those 5seconds when I can do screenshot:

Ok. It seems now I was faster:

Version: 3.7.9
VS Code Extension API: 1.105.1
Commit: e79e90140506f7e19909b732104fb7c8ba2df099
Date: 2026-06-04T01:37:37.170Z
Layout: glass
Build Type: Nightly
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.3.0