Science & Technology

Cursor ditches VS Code, but not everyone is happy...

📚 Main topics

Cursor’s shift to agentsCursor 1.0 and 2.0 added AI autocomplete and agent-driven coding; version 3.0 shifts toward managing swarms of agents across projects, machines, and the cloud. 0:00
Composer 2’s originsCursor presented Composer 2 as a fast, inexpensive model with impressive benchmark results. It was later revealed to be based on Moonshot’s Kimi K2, and Cursor apologized for not being transparent about that. 1:02
A new interfaceCursor 3’s agent-focused interface was rewritten in Rust and TypeScript, while the older VS Code-style editor remains available. The new workspace brings together agents, development tools, remote SSH, and multiple models. 2:06
A project built with agentsThe demo uses parallel agents to plan and build a prototype, work on a landing page, and make changes to a remote server. The interface also supports reviewing agent status, git history, files, terminal output, and the app in a built-in browser. 2:37

✨ Key takeaways

Parallel agent workflowsUsers can switch among projects and run multiple agents at once; status indicators show when an agent needs permission or has finished work for review. 3:08
Visual editingIn design mode, users can highlight an interface element and ask AI to change it, then queue up further fixes while the agents work. 3:39
Performance claimThe video’s sponsor, Blacksmith, describes its GitHub Actions runners as twice as fast and 75% cheaper, with observability for CI pipelines. 4:09

🧠 Lessons learned

Transparency mattersCursor’s disclosure about Composer 2’s foundation came only after its model ID was found in metadata, prompting criticism and an apology. 1:34
Human review still mattersAgents can quickly produce large amounts of code, but may need human permission for unsafe commands and still require review and direction. 3:08

🏁 Conclusion/next steps

A more agent-centered futureCursor 3 recasts the development environment as a place to coordinate AI agents, rather than primarily write code by hand. The video closes by inviting viewers to try Blacksmith’s free GitHub Actions minutes. 4:09

webdev app development lesson tutorial

Transcript excerpt

0:00 Two years ago, Cursor 1.0 was released as a VS Code fork that helped you autocomplete your code with AI, like an airline co-pilot. Then six months ago, a cursor 2.0 was released, but with an upgraded chat view that could take control of your terminal to build entire features, like an airline captain. But then, just a few days ago, a cursor released version 3.0. And this version doesn't even want you writing code anymore. Instead, it wants you to be more like an air traffic controller running swarms of AI agents across multiple repos, machines, and even the

0:31 cloud at the same time. On top of that, Cursor just released their new composer 2 model, which was allegedly trained in-house and is more intelligent than Claude Opus 4.6. That is, if we are to trust these trust me, bro benchmarks. But what's even more crazy is that cursor is not even a VS Code fork anymore and has been completely rewritten from scratch with Rust. That's great news for your RAM, but not everybody is vibing with the new direction of cursor. And in today's video, we'll break down its controversial new features. It is April 6, 2026, and you're watching the code

🔒 The full, searchable transcript is available with Pro.

Suggestions