Cancelling Cursor
A long-time user of the Cursor AI code editor explains their decision to cancel their subscription. The author cites concerns over outdated VSCode base versions, persistent UI bugs, and the feeling that standalone AI agents are becoming more efficient than the integrated tool.
Why it matters
It highlights the growing tension between integrated AI coding environments and the rapid evolution of specialized, modular AI agent tools.
back to Jitbit Blog home About this blog Cancelling Cursor by Alex Yumashev · Aug 1 2026 I've been a Cursor fan - and a paying customer - for years. I still remember the first time I tried that magical tab-completion, the "shut up and take my money" moment 2 years ago. But it's getting harder and harder to justify the subscription.
This has been a problem for years now. Cursor is always based on a 7-8 month old VSCode build on average, and that matters because extension updates simply refuse to install.
For the last 10 months Cursor has been based on VSCode release 1.105.0. Before that - a similar 9-month cycle on version 1.99.3. Two weeks ago they bumped the version to 1.125.0 which is already 7 releases behind.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in