zlacker

>>scared+(OP)
Cursor is trapped in a cat and mouse game against "hacks" where users create new accounts and get unlimited use. The repo was even trending on Github (https://github.com/yeongpin/cursor-free-vip).

Sadly, Cursor will always be hampered by maintaining it's own VSCode fork. Others in this niche are expanding rapidly and I, myself, have started transitioning to using Roo and Cline.

>>thetur+t54
What I don't understand is why maintain a fork instead of just an extension? I would assume an extension like this would be pretty difficult to create but would it be more difficult than literally forking VSCode?

>>_fat_s+R16
Cursor was one of the first AI editors and there was no way to add those features to VSCode thru extensions at that time. Another issue was that VSCode made special exceptions and opened APIs for CoPilot, Microsoft’s product, but not for other players. Not sure if this has changed now.

Cursor took the best course of action at the time by forking but needs to come back into the fold. If VSCode is restricting access to APIs to CoPilot, forking it publicly and putting that in the Readme, “We forked VSCode since they give preferential treatment to CoPilot” would get a lot of community support.