# We need more stable releases for autopushed/"production" releases

**URL:** <https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702>\
**Category:** Feature Requests\
**Created:** [August 26, 2024, 5:03pm UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702 "2024-08-26T17:03:41Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![HedgedAndLevered](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@HedgedAndLevered](https://forum.cursor.com/u/HedgedAndLevered)\
**Post date:** [August 26, 2024, 5:03pm UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702/1 "2024-08-26T17:03:41Z")

</div>

Cursor is great when it works.

Every month or two though, cursor team is getting trigger happy and releasing what is, for all intents and purposes, a beta or alpha release as though it is production. I’ve seen bugs all over this board and people asking for rollbacks, etc

I get that its difficult in software development to catch every corner case before a big deployment, but this is clear this is a problem with the way you do releases. If you can’t get a sufficient level of bug testing done before a release, don’t release it to automatically upgrade.

Different people have different tolerances for crashes. Some would prefer something stable at all costs, and some like frontier AI features.

push-auto-upgrade and hotfix later when things break is not an appropriate release strategy here when people rely on your software for work every day.  
Now I’m having to go through and dig through the forums to see if an upgrade is safe or not, on the main, stable branch. This is bad UX.

---

<div class="post-metadata">

**Author:** ![HedgedAndLevered](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@HedgedAndLevered](https://forum.cursor.com/u/HedgedAndLevered)\
**Post date:** [August 26, 2024, 5:06pm UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702/2 "2024-08-26T17:06:35Z")

</div>

Also I already requested something like this earlier and no responses

> [@Is there a way to disable auto update on close?](https://forum.cursor.com/t/is-there-a-way-to-disable-auto-update-on-close/5348):
>
> Windows force restarted for updates overnight, and when I got back to the desk and fired up cursor it was the newest version. Is there a way to prevent this? I’d like to wait for upgrades for a little while for stability purposes.

---

<div class="post-metadata">

**Author:** ![fun\_strange](https://avatars.discourse-cdn.com/v4/letter/f/8c91f0/32.png) [@fun\_strange](https://forum.cursor.com/u/fun_strange)\
**Post date:** [August 26, 2024, 5:19pm UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702/3 "2024-08-26T17:19:17Z")

</div>

It would be good if there were two or three tiers:

1. Main branch,
2. Beta branch
3. Optionally alpha branch

Switching to beta or alpha would prompt for updates quicker or as soon as they are released, and choosing ‘main’/default would either wait some time before updating (slow roll-out) or allow the user to update manually when they are ready.

This would solve both problems:  
People like me who want to see the new features as fast as possible won’t need to chase the new versions and manually download them from the website to get them quicker.

And people who want the most stability would not get an update pushed too quickly.

Currently with 0.40 it seemed to have been random, but giving an option to choose would satisfy both crowds.

---

<div class="post-metadata">

**Author:** ![amanrs](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/amanrs/32/105_2.png) [@amanrs](https://forum.cursor.com/u/amanrs)\
**Post date:** [August 26, 2024, 5:45pm UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702/4 "2024-08-26T17:45:52Z")

</div>

Hey, thanks for this feedback! We’re definitely considering switching how we roll out releases.

What major bugs have you encountered with 0.40.0?

---

<div class="post-metadata">

**Author:** ![HedgedAndLevered](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@HedgedAndLevered](https://forum.cursor.com/u/HedgedAndLevered)\
**Post date:** [August 26, 2024, 6:21pm UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702/5 "2024-08-26T18:21:28Z")

</div>

Had a pretty awful bug within the first couple hours of using it. Won’t be using composer until this is fixed so will not get to reproducing it, sorry

> [@The window terminated unexpectedly (reason:'crashed', code:'132') and entire composer history wiped](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-132-and-entire-composer-history-wiped/12698/4):
>
> I’ve only been using it today for 2 hours. within that small amount of time it has already crashed and entirely wiped my composer chat while I was in the middle of applying changes. I’m not going to be trying composer again in this version clearly, so I’m not going to get to the point where it is reproducible. For what its worth, my first prompt was about 2 pages of text, then I went back and forth for about 4-5 messages. A long chat but nothing ridiculous.

---

<div class="post-metadata">

**Author:** ![msc](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@msc](https://forum.cursor.com/u/msc)\
**Post date:** [August 27, 2024, 1:49pm UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702/6 "2024-08-27T13:49:06Z")

</div>

Agreed!

---

<div class="post-metadata">

**Author:** ![Anubis](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@Anubis](https://forum.cursor.com/u/Anubis)\
**Post date:** [August 31, 2024, 3:15am UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702/7 "2024-08-31T03:15:23Z")

</div>

The chat interface freezes after a few prompts. Is there a way to rollback…

---

<div class="post-metadata">

**Author:** ![rishabhy](https://avatars.discourse-cdn.com/v4/letter/r/848f3c/32.png) [@rishabhy](https://forum.cursor.com/u/rishabhy)\
**Post date:** [August 31, 2024, 3:57am UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702/8 "2024-08-31T03:57:44Z")

</div>

hey - do you mind sharing a video of the chat freezing? would help debug!

---

<div class="post-metadata">

**Author:** ![thibauld](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/thibauld/32/3844_2.png) [@thibauld](https://forum.cursor.com/u/thibauld)\
**Post date:** [December 11, 2025, 10:27pm UTC](https://forum.cursor.com/t/we-need-more-stable-releases-for-autopushed-production-releases/12702/9 "2025-12-11T22:27:33Z")

</div>

Fully agree with that. I for one would love to stick to the “stable” branch for updates.  
You just cannot debug on your users when it comes to something as sensitive as software development. We use Cursor to do serious work, we cannot install an update one day that - say - makes you lose ALL YOUR CHATS (cf [Cursor AI is no longer able to load chats locally - #13 by hime](https://forum.cursor.com/t/cursor-ai-is-no-longer-able-to-load-chats-locally/143599/13) ), this is not acceptable.

So I really hope the Cursor team will start giving the option to stick to a stable branch when it comes to updates. Sure I won’t get the latest of the latest features, but I don’t care as long as it means that I am safe from losing work.

The time has come. Give us a really “stable” branch for those who count on Cursor to not fail them.
