Whenever Cursor pushes out a “pop-up dialog announcement” about some ‘new’ thing in Cursor it immediately causes my devcontainer to pop-up dialog saying it needs to “reload window” (which never works for me), so it basically means shutdown Cursor or click the “Rebuild Container” button (and thank goodness for Docker cached layers, so its rather quick).
Steps to Reproduce
Use Cursor with a devcontainer and just wait for a Cursor announcement to kill you!
Hey, thanks for the report. I can see the screenshot with the Composer 2 popup.
The issue is that when these announcements show up in a devcontainer session, it triggers a window reload because Cursor is updating its built-in extensions. In a remote context, this always requires a full reload instead of a light extension restart. That’s definitely inconvenient.
I’ve shared this with the team. I’ll update the thread if there’s any news.
Thanks for the feedback and acknowledgement of this issue. How about just disable these announcements? Checkbox option in settings?
IMHO a proper well-formatted changelog that appears as a TAB in Cursor after a version update (what VS Code provides for each new version installed, with a checkbox to disable if a user wishes) which could include fancy graphics/thumbnails to video links, etc introducing the new major feature(s) would be a far superior way to interact and inform your already engaged Cursor users/customers.
I’m also taking this opportunity to remind Cursor that your lack of comprehensive changelog is a constant concern for users…
Currently, you are causing instability and essentially a ticking time bomb whenever I use Cursor with a devcontainer. I might be running a multi-minute process like: “terraform apply” and if a Cursor announcement arrives, then my session goes bang.
