# Pro Users: Version 0.45 Rollout Timeline

**URL:** <https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856>\
**Category:** Discussions\
**Created:** [January 25, 2025, 10:00pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856 "2025-01-25T22:00:07Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![younio](https://avatars.discourse-cdn.com/v4/letter/y/ecd19e/32.png) [@younio](https://forum.cursor.com/u/younio)\
**Post date:** [January 25, 2025, 10:00pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/1 "2025-01-25T22:00:07Z")

</div>

**Hello Cursor team,**

I’m writing as a **Cursor Pro subscriber** regarding access to version **0.45**. While I understand some users have already received the update, many Pro subscribers, including myself, are still waiting for access.

What’s particularly challenging is the lack of clear communication about the rollout timeline. As paying customers who specifically subscribe for access to premium features, we’re eager to understand:

1. When can Pro subscribers expect to receive version 0.45?
2. Could you explain the current rollout process?
3. Are there any temporary solutions available for those who need the new features urgently?

We value Cursor’s services and simply want to make the most of our subscription. Some transparency about the situation would help us better plan our work around the availability of new features.

Thank you for your attention to this matter. I look forward to your response.

---

<div class="post-metadata">

**Author:** ![andreasringdal](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/andreasringdal/32/22286_2.png) [@andreasringdal](https://forum.cursor.com/u/andreasringdal)\
**Post date:** [January 25, 2025, 10:59pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/2 "2025-01-25T22:59:23Z")

</div>

Even with incremental rollouts it would be nice to choose what upgrade path you wanted.  
Beta, Release candidate, Early adopters and a let somebody else discover the bugs options.

For my personal projects at home I’d gladly go for Beta and release candidate, but at work I want it stable and without surprises.

---

<div class="post-metadata">

**Author:** ![Skyfire](https://avatars.discourse-cdn.com/v4/letter/s/6a8cbe/32.png) [@Skyfire](https://forum.cursor.com/u/Skyfire)\
**Post date:** [January 25, 2025, 11:12pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/3 "2025-01-25T23:12:50Z")

</div>

+1 - it’s really annoying.  
Let user choose themself if they want early versions or not.

---

<div class="post-metadata">

**Author:** ![voarsh](https://avatars.discourse-cdn.com/v4/letter/v/e36b37/32.png) [@voarsh](https://forum.cursor.com/u/voarsh)\
**Post date:** [January 26, 2025, 1:30am UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/4 "2025-01-26T01:30:27Z")

</div>

Hmmm. sounds like you want old Cursor Nightly builds

---

<div class="post-metadata">

**Author:** ![norio](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/norio/32/22345_2.png) [@norio](https://forum.cursor.com/u/norio)\
**Post date:** [January 26, 2025, 11:42am UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/5 "2025-01-26T11:42:12Z")

</div>

I have created a proposal to solve this problem. I would love to hear your thoughts on it.

> [@A Proposal to Satisfy Both Early Adopters and Stability-Focused Users in Update Delivery](https://forum.cursor.com/t/a-proposal-to-satisfy-both-early-adopters-and-stability-focused-users-in-update-delivery/44958):
>
> Many Cursor users seem to be early adopters who are highly enthusiastic about trying out new features and technologies. At the same time, there is a significant group of users who prioritize stability, particularly those using Cursor in production environments or professional settings. To address the needs of both user groups, I propose the following approach to how updates are delivered: Proposal: Continue rolling out stable versions incrementally The current method of rolling out stable v…

---

<div class="post-metadata">

**Author:** ![norio](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/norio/32/22345_2.png) [@norio](https://forum.cursor.com/u/norio)\
**Post date:** [January 26, 2025, 11:53am UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/8 "2025-01-26T11:53:47Z")

</div>

me too. (windows user)

---

<div class="post-metadata">

**Author:** ![Gray](https://avatars.discourse-cdn.com/v4/letter/g/5fc32e/32.png) [@Gray](https://forum.cursor.com/u/Gray)\
**Post date:** [January 26, 2025, 6:17pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/9 "2025-01-26T18:17:16Z")

</div>

Same here - pro user, and I’ve repeatedly been frustrated by this. I only need to do coding every so often, and _every single time_ I go to open cursor and see there is a new version in the change log, I go through this incredibly frustrating process of trying to update, and finding myself still on an old version, with the “Cursor: update” command doing nothing and the singular download link on the website not being for the latest version.

I understand new versions might be buggy, but for crying out loud, let us decide what we want to run! Every piece of software ever has had the concept of a “stable” and “beta” release. Have download links for both and let people decide.

I like cursor a lot, but seriously - this is one of the things that makes me frustrated with it and look up the latest alternative IDE reviews on youtube from time to time to see if I might want to jump ship.

Since fixing this would be _completely trivial and require basically zero effort_ and it’s been an issue people have been frustrated with for quite a long time, I think it would make sense to just put a download link out there for people, surely? “Beta - might be unstable” and let people decide.

---

<div class="post-metadata">

**Author:** ![younio](https://avatars.discourse-cdn.com/v4/letter/y/ecd19e/32.png) [@younio](https://forum.cursor.com/u/younio)\
**Post date:** [January 27, 2025, 5:27pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/10 "2025-01-27T17:27:08Z")

</div>

[danperks](https://forum.cursor.com/u/danperks) : could you please help me on getting the 0.45 update? it’s been a while I’ve been waiting, and the Cursor team didn’t comment on this thread at all; the Customer Support didn’t answer my email neither about this rollout strategy…

could you please help on this?

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [January 27, 2025, 5:54pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/11 "2025-01-27T17:54:47Z")

</div>

Hey unfortunately, we’re rolling out this update gradually to catch critical errors early on, and you’ll receive the update when it’s available to you. But you can try forcing an update, and if it’s already available, it will download it. To do this, open the command palette with `Cmd/Ctrl + Shift + P` and type “Attempt update.”

---

<div class="post-metadata">

**Author:** ![younio](https://avatars.discourse-cdn.com/v4/letter/y/ecd19e/32.png) [@younio](https://forum.cursor.com/u/younio)\
**Post date:** [January 27, 2025, 5:55pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/12 "2025-01-27T17:55:29Z")

</div>

I have been doing this multiple times in the last four or five days… i don’t remember…

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [January 28, 2025, 6:38pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/13 "2025-01-28T18:38:51Z")

</div>

Just to say, we are looking at adding a beta-style program that you can opt into, to get these features early under the increased risk you may find some bugs! No ETA right now tho.

---

<div class="post-metadata">

**Author:** ![younio](https://avatars.discourse-cdn.com/v4/letter/y/ecd19e/32.png) [@younio](https://forum.cursor.com/u/younio)\
**Post date:** [January 28, 2025, 6:58pm UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/14 "2025-01-28T18:58:11Z")

</div>

Finally ! Thanks for the info!

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:25am UTC](https://forum.cursor.com/t/pro-users-version-0-45-rollout-timeline/44856/15 "2026-06-18T10:25:57Z")

</div>

Closed on June 18, 2026, 10:25am UTC


