Ive been a heavy user of Cursor since August. In fact I have two accounts - one for work, and for personal. I have created 6 apps on a big part using Cursor. I have noticed that the new Composer2:
1-makes too many mistakes
2-missed a lot of logic or parts
3-doesnt have the ability to look at patterns in other parts of the code even if told clearly,
4-doesnt regress well, if it changes the UI, it forgets to check the routes/repo
5-even changes excellent queries to nested queries of the same thing (this blows my mind)
6-and many more
Speed is not enough measure of productivity if it doesnt do enough to scope out and set the full context of a code change. In the past one week, I have seen more simple mistakes than in the past month of work. I feel the quality of work is inferior - again depth, accuracy, completeness is more important than speed. I spend half of the time checking every part of the agents work.
I learned to love CURSOR. Even if I have CLAUDE on the side doing some of the heavy lifting, I always have CURSOR on the side to do the bulk of the tasks (CLAUDE just sucks up tokens soo fast). But with this experience, Im willing now to take time to test out another LLM (I was in windsurf at the beg for a month, tested grok/openai/gemini LLM via API in the past… maybe moving to codex and go back to pure VSCODE). With the experience I have with Composer2, it’s no longer a happy place to do work… it’s becoming a pain to spend half of the time checking, fixing, and telling CURSOR to show the gaps). My 2 subscriptions will end in a week.
The only option I can see is if I can go back Composer 1.5. Is this possible?
Also, this is an echo of a similar post below… Maybe if there are more posts like this, CURSOR will hear us. Get rid off Kimi!