after rollback to 0.45, using composer again makes me comfortable
Definitely the 0.45 version is much better
0.45 Composer >>> 0.46 agent
5 Likes
What version of 0.45?
Does version 0.45 have agent or composer? Is Sonnet 3.7 or 3.5 being used? Is it currently running stable on Windows? Exactly which version 0.45 are you using?
0.45.17 I using now
Iām not sure stable at Windows (Iām using mac)
composer with sonnet 3.7, 3.5 is available
3 Likes
I did that too
1 Like
On 0.45.17 as well. It restores much of the functionality, though I canāt get used to Claude 3.7ās character (though my experience might be coloured by cursors ācut offā limit and use of own LLMs)
1 Like
even downgrading 0.45, it seem the āagentā way of coding, is still upā¦
it is worse then beforeā¦
it seems that now it is prompting with āpartā of the code, and not full code, then it is reiterating multiple times in a single file of code.
other behaviour that is different, is that now, it tries to create some tmp files, run command lines, and access other files from project in a āactive wayā, and before, it only do what you ask and put in the contextā¦
it is not like the sameā¦ even in downgraded 0.45
Has anyone here compared 0.45 to 0.48? Is it worth upgrading finally?
I added a feature request, PLEASE VOTE!!!: Easy Roll Back - PLEASE VOTE!
Interesting but I think roll back aint the right solution since we will still miss new features.
Iām still on 0.45 because of different tabs for different modes with different models make sense to me and i can use keyboard shortcuts to them. Iām all about shortcuts.
0.48 anouced a better control over modes configuration, iām not sure about configuring keyboard shortcut though.
Rolling Back to a stable version is the best professional solution for people who work on live projects for clients and for whom workflow is critical. We can go without all the shiny bells and whistles if it breaks our workflow and causes time loss.
We should each definitely take responsibility and implement our own backup system and probably run Dual Versions if we want bleeding edge but having an easy Rollback feature built into the software would provide a good stopgap measure while allowing us to Test. That is why I opened the new feature request.
Please vote! : Easy Roll Back - PLEASE VOTE!
You are right, that new features would be missed.
0.48 has multi chat support and you can set all the shortcuts you want. they even have a shortcuts docu page.
Way more than just custom modes.
Also having to support even more versions due to people having a rollback feature it would be way more complex for an editor that didnt reach v1 yet.
1 Like
I maintain and am still running 45.14
Its the only one I have had happiness with ā and I didnt want to explore outside after following everything beyond and the complaints.
@cursor are fn ghosts at this point, and I do not trust them after applying for a position, and being ghosted.
Ive contributed a fair bit here, and these guys are in over their head in what they have built (which is beautiful, but their face_paint is melting)
1 Like
Iāll definitely give version 0.48 a go because of its configurable modes, it seems to be my way out of v0.45, finally. Whether it was part of their roadmap or theyāre delivering on user requests, kudos to them for providing granular control over the tool.
Regarding complains about model performance between version changes, I believe that no matter which cursor version one uses it wont make a difference because that part of cursor magic happens server side not on our client.
So what differs from one version to another are the new features and user flow/interface, i believe.
We need a āhackable clusterā
whereby @CURSOR mantains an ephemeral cluster we can all attack, sponsered by {vendor} and we just attach the ā ā ā ā out of it,
YOLORENA (Yolo Arena) is what its called and I attempted to build such..)
(@cursor is totally failing in all regards to actually owning this market)
That would actually be pretty cool. 
I just upgraded to 0.48ā¦havenāt tried it out yet, but on the surface it looks like they are listening to feedback. The āManualā mode (only make edits to certain files) seems to be an attempt to give people the 0.45 experience if they want it. And thereās a tick box to enable ālegacyā mode (so old shortcuts work?). Iāll add my feedback after I get some more time with it.
BTW, I had a thought. In 0.45, I had a bunch of custom instructions that presumably got passed on to the LLM each time I sent a query. From my understanding, those are not really used from 0.46 onward, and they were replaced, I think, with something else. I wonder if that might be why many of us noticed a significant deterioration in quality between 0.45 and 0.46ā¦because Claude wasnāt getting our custom instructions anymore.
1 Like