What's the difference between Cursor and the new version of Github Copilot?

[Chieep]

So I've been using cursor for a while and it's absolutely great! But recently I've learned that Github Copilot now offers similar features to Cursor (https://youtu.be/SZVCJRUADc4?si=VhdqTC-KRCPD3kr1). I'm just curious about what differentiates Cursor from the new version of Github Copilot?why should one pay for Cursor and not Github Copilot?

I think Cursor is a great product with huge potential but I think for the longevity of the project this question needs to be answered clearly.

[davemac]

Yes I would like an answer about this as well please.

[alanrichards86]

Same!

[TJtangjun]

I'm a two-production user, so it is suitable for me to answer the question.

• copilot can't control the code context, but Cursor can use @ feature.
• copilot support visual studio,but Cursor can't.
• Cursor use GPT4, but what model copilot use is not confirmed.
• copilot's auto-complete can't change the code you input, but Cursor can change.
• copilot is cheaper than Cursor
• sometimes, copilot is faster than Cursor, but sometimes, the copilot will stuck.

[qiulang]

copilot can't control the code context, but Cursor can use @ feature.

As copilot has @workspace so I not sure how much that statement stands. But I am also curious about what the code context copilot uses, so I commented on https://github.com/orgs/community/discussions/51323