Original: Dan Shipper (Every) · 22/01/2026
Summary
The IDE is kind of dead. *Happening now: We’re hosting with the world’s best experts pushing the limits of what’s possible. Watch live now until 6 p.m. ET, and . Also: This article is based on a sponsored event. Cursor provided $100 in credits to attendees and made this camp possible.—[Kate Lee](https://every.to/on-every/kaKey Insights
“The IDE is kind of dead.” — Lee Robinson’s statement on the declining centrality of traditional IDEs in programming.
“Writing and editing code by hand is shrinking as a percentage of the work.” — Discussion on how AI agents are taking over more of the coding process.
“You need to choose the right model for the job.” — Emphasizes the importance of model selection over prompting tricks in AI coding.
Topics
Full Article
Published: 2026-01-22
Source: https://every.to/source-code/what-the-team-behind-cursor-knows-about-the-future-of-code
Happening now: We’re hosting with the world’s best experts pushing the limits of what’s possible. Watch live now until 6 p.m. ET, and . Also: This article is based on a sponsored event. Cursor provided $100 in credits to attendees and made this camp possible.—Kate Lee
A few minutes into Every’s first Cursor Camp, Cursor developer education lead Lee Robinson made a bold declaration: “The IDE is kind of dead.” IIDE stands for “integrated development environment”—basically Microsoft Word, but for code. It’s where programmers type, organize files, and run programs, and for decades, it has been the center of a programmer’s world. Now, that model is breaking down. The center of gravity has shifted from typing code by hand in an IDE such as Visual Studio Code to managing AI agents that write it for you with a tool such as Cursor. In this session, Lee and Samantha Whitmore, a software engineer at Cursor, walked us through how they work in a post-IDE world. What follows are the workflows, model-selection strategies, and honest limitations they shared—plus where this leaves you if you’re trying to figure out what the future of code looks like.
Key takeaways
- The agent is becoming the core. Writing and editing code by hand is shrinking as a percentage of the work. Developers are now spending more time telling AI agents what to build and reviewing their output.
- Cloud and local agents are merging. You’ll soon be able to start an agent on your computer, hand it off to remote servers when you close your laptop, and pick it back up later—no context lost.
- Model choice matters more than prompting tricks. Prompting gimmicks like, “I’ll pay you $1,000,” which some AI users swore could make AI provide a better output, don’t work anymore. You need to choose the right model for the job—say, one for brainstorming, another for deep bug-hunting.
- Agents can run for weeks. Cursor’s research team built a working web browser from scratch using AI agents that ran for days, producing 3 million lines of code. It cost $80,000 in tokens (the units AI companies use to measure and charge for usage). It’s a research project that’s not available for public use—for now. But it shows where things are heading…
Key Takeaways
Notable Quotes
The IDE is kind of dead.Context: Lee Robinson’s statement on the declining centrality of traditional IDEs in programming.
Writing and editing code by hand is shrinking as a percentage of the work.Context: Discussion on how AI agents are taking over more of the coding process.
You need to choose the right model for the job.Context: Emphasizes the importance of model selection over prompting tricks in AI coding.
Related Topics
- [[topics/agent-native-architecture]]
- [[topics/ai-agents]]
- [[topics/cursor]]
- [[topics/model-selection]]
Related Articles
Cursor's Third Era: Cloud Agents
Swyx · explanation · 77% similar
How to Build Agent-native: Lessons From Four Apps
Dan Shipper (Every) · explanation · 75% similar
From Design doc to code: the Groundhog AI coding assistant (and new Cursor vibecoding meta)
Geoffrey Huntley · explanation · 75% similar
Originally published at https://every.to/source-code/what-the-team-behind-cursor-knows-about-the-future-of-code.