The email I received in case anyone is wondering:

Hi <makingstuffs>,

I'm Michael, the founder and CEO of Cursor. I noticed you recently canceled your subscription, and I wanted to check in. If we fell short for you, I want to learn why and make it right.

First, if you'd like me to refund your account, please just reply to this email to let me know. I'd be happy to.

Second, could you share a sentence or two on what you disliked about Cursor? Or perhaps a screenshot of where it performed poorly? This will help us improve the product for future users.

I'd be very grateful to understand your candid thoughts. I'm listening and eager to fix our experience for you. Wishing you the best in any case!

Best, Michael

And my reply which I never got a response to:

Hi Michael,

Thanks for reaching out. I have honestly found that recent updates to the app have been extremely detrimental to the DX and productivity. A couple big issues I have found:

1. Removing the floating component window and providing no way to get it back. As a dev who is often travelling and working from a laptop screen I found the floating window to be extremely handy and its removal essentially meant I just do not use the composer anymore.

2. Constantly overriding VSCode native shortcuts. This is the most detrimental thing I have experienced, personally. Shortcuts are crucial to productivity and are engrained in muscle memory over years. Overriding them is essentially removing years of learned behaviour (things like cmd + shift + l)

3. The floating completion windows. These often end up overlapping my code code and break my flow. I have to press escape to close it and the whole experience is just jarring

4. Making the cursor dance around the screen when suggesting completions. I get that completions can sometimes be handy but moving my cursor when I am in the flow just makes me rethink what I am doing so that I can read a guess as to what I want which is often incorrect.

5. Poor suggestions. In the past month (maybe two?) I have noticed the quality of prompts is not up to par. I often find that Cursor will do weird things like import `jest.Mock` in my unit tests when I have not used jest in any repo which I have been actively maintaining since using cursor.

As for the refund I will leave that decision for you. I knew I was entering beta software when I ordered accepted the terms so I wouldn't be annoyed as such. Though, saying that, I do find myself using cursor a lot less now and am going to most likely shift back to plain VSCode as a result of the above.

If I think of anything else I will let you know.

Thanks,

Love, Peace and Happiness,

<makingstuffs>