Cursor Team: Future of Programming with AI | Lex Fridman Podcast #447

Cursor Team: Future of Programming with AI | Lex Fridman Podcast #447

Lex Fridman PodcastOct 6, 20242h 29m

Lex Fridman (host), Michael Truell (guest), Aman Sanger (guest), Arvid Lunnemark (guest), Sualeh Asif (guest), Narrator, Narrator, Narrator

Purpose and evolution of code editors in the age of AICursor’s origin story, architecture, and decision to fork VS CodeAI-assisted coding features: Cursor Tab, Apply, diffs, and codebase chatModel engineering: custom small models, MoE, speculative decoding, KV caching, attention variantsRetrieval and indexing: embeddings, vector DBs, Merkle-style syncing, local vs cloud trade-offsSynthetic data, RLHF/RLAIF, process reward models, and test-time compute (e.g., o1)Future of programming: agents, bug finding, formal verification, and the human–AI hybrid engineer

In this episode of Lex Fridman Podcast, featuring Lex Fridman and Michael Truell, Cursor Team: Future of Programming with AI | Lex Fridman Podcast #447 explores cursor Team Reveals How AI Will Radically Transform Programming Workflows Lex Fridman interviews the founding Cursor team about rethinking the code editor around modern AI models. They explain why they forked VS Code to tightly integrate custom models for autocomplete, code editing, and multi-file diffs, aiming to eliminate “low-entropy” keystrokes and make coding radically faster and more fun. The conversation dives deep into technical topics such as speculative decoding, KV caching, mixture‑of‑experts models, retrieval and embeddings, synthetic data, and test-time compute. Throughout, they argue the near‑ to mid‑term future is a human‑AI hybrid programmer, with humans retaining control, judgment, and system design while AI handles boilerplate, migration, and increasingly sophisticated edits and verification.

Cursor Team Reveals How AI Will Radically Transform Programming Workflows

Lex Fridman interviews the founding Cursor team about rethinking the code editor around modern AI models. They explain why they forked VS Code to tightly integrate custom models for autocomplete, code editing, and multi-file diffs, aiming to eliminate “low-entropy” keystrokes and make coding radically faster and more fun. The conversation dives deep into technical topics such as speculative decoding, KV caching, mixture‑of‑experts models, retrieval and embeddings, synthetic data, and test-time compute. Throughout, they argue the near‑ to mid‑term future is a human‑AI hybrid programmer, with humans retaining control, judgment, and system design while AI handles boilerplate, migration, and increasingly sophisticated edits and verification.

Key Takeaways

Forking the editor enables deeper AI integration than extensions can

Cursor forked VS Code instead of building a plugin so they could control everything from UI to model routing, caching, and background agents. ...

Get the full analysis with uListen AI

The core goal is to delete ‘low-entropy’ work from programming

Cursor aims to remove predictable keystrokes—things the model can confidently infer from context—so humans focus on decisions, design, and intent. ...

Get the full analysis with uListen AI

Custom small models can outperform frontier models on narrow editor tasks

For tasks like fast code edits, next-cursor prediction, and reliably applying diffs, Cursor trains specialized smaller models (often MoE) tuned to long prefill / short output patterns. ...

Get the full analysis with uListen AI

Fast, usable AI coding tools depend heavily on systems-level optimizations

User-perceived speed comes from techniques like KV cache reuse, cache warming while the user types, speculative decoding over existing code, multi-query/MLA attention to shrink KV size, and smart batching. ...

Get the full analysis with uListen AI

Diff and verification UX is now a major bottleneck for large AI changes

As models propose larger multi-file edits, humans can’t realistically review raw diffs. ...

Get the full analysis with uListen AI

Retrieval and codebase understanding will increasingly shift from static embeddings to learned behavior

Today Cursor uses embeddings and vector search over chunked code, with Merkle-style hashing and shared embedding caches to manage scale. ...

Get the full analysis with uListen AI

The medium-term future is a human–AI hybrid engineer, not fully autonomous agents

The team is skeptical that chat-style agents will replace day-to-day programming soon, since much of engineering is iterative, under-specified, and design-heavy. ...

Get the full analysis with uListen AI

Notable Quotes

Fast is fun.

Cursor team

The goal of Cursor Tab is to eliminate all the low‑entropy actions you take inside the editor.

Michael (Cursor)

We’re building the engineer of the future, a human–AI programmer that’s an order of magnitude more effective than any one engineer.

Cursor engineering manifesto (paraphrased and discussed by the team)

I think Cursor, a year from now, will need to make the Cursor of today look obsolete.

Swale (Cursor)

Agents are not yet super useful for many things… I think we’re getting close to where they will actually be useful.

Arvid (Cursor)

Questions Answered in This Episode

How far can ‘next action prediction’ realistically go before humans start to feel out of control, and how will Cursor decide where to draw that line?

Lex Fridman interviews the founding Cursor team about rethinking the code editor around modern AI models. ...

Get the full analysis with uListen AI

What would a truly AI-assisted diff and verification experience look like for a massive multi-repo change at a large enterprise?

Get the full analysis with uListen AI

Under what concrete conditions would Cursor lean heavily into agentic workflows (e.g., background bug-fixing agents) versus keeping interactions strictly user-driven?

Get the full analysis with uListen AI

How might post-training a model on a single large codebase change the way teams onboard developers or refactor legacy systems?

Get the full analysis with uListen AI

If formal verification and powerful bug-finding models become practical, how will that reshape testing, code review, and the very notion of ‘safe to deploy’?

Get the full analysis with uListen AI

Transcript Preview

Lex Fridman

The following is a conversation with the founding members of the Cursor team, Michael Truhl, Swale Asif, Arvid Lundmark, and Aman Singer. Cursor is a code editor based on VS Code that adds a lot of powerful features for AI-assisted coding. It has captivated the attention and excitement of the programming and AI communities, so I thought this is an excellent opportunity to dive deep into the role of AI in programming. This is a super technical conversation that is bigger than just about one code editor. It's about the future of programming, and in general, the future of human AI collaboration in designing and engineering complicated and powerful systems. This is the Lex Fridman Podcast. To support it, please check out our sponsors in the description. And now, dear friends, here's Michael, Swale, Arvid, and Aman. All right, this is awesome. We have Michael, Aman, Swale, Arvid here from the Cursor team. First up, big ridiculous question, what's the point of a code editor?

Michael Truell

So the- the code editor is largely the place where you build software, and today, or for a long time, that's meant the place where you text edit, uh, a formal programming language. And for people who aren't programmers, the way to think of a code editor is, like, a really souped-up word processor for programmers, where the reason it's- it's souped up is code has a lot of structure. And so the- the, quote unquote, "word processor," the code editor can actually do a lot for you that word processors, you know, sort of in the writing space haven't been able to do for- for people editing text there. And so, you know, that's everything from giving you visual differentiation of, like, the actual tokens in the code to, so you can, like, scan it quickly, to letting you navigate around the code base, sort of like you're navigating around the internet with, like, hyperlinks. You're going to sort of definitions of things you're using, to error checking, um, to, you know, to catch rudimentary bugs. Um, and so traditionally, that's what a code editor has meant, and I think that what a code editor is, is going to change a lot over the next 10 years, um, as what it means to build software maybe starts to look a bit different.

Lex Fridman

I th- I think also a code editor should just be fun.

Aman Sanger

Yes. That is very important. That is very important, and it's actually sort of an underrated aspect of how we decide what to build. Like, a lot of the things that we build, and then we- we try them out, we do an experiment, and then we actually throw them out because they're not fun. And- and so a big part of being fun is, like, being fast a lot of the time. Fast is fun.

Lex Fridman

Yeah, fast is... (laughs)

Aman Sanger

Yeah. (laughs)

Lex Fridman

Oh yeah, that should be a T-shirt.

Aman Sanger

(laughs)

Michael Truell

But, like, fundamentally, I think one of the things that draws a lot of people to- to building stuff on computers is this, like, insane integration speed, where, you know, in other disciplines, you might be sort of gatekept by resources or the ability, even the ability, you know, to get a large group together, and coding is this, like, amazing thing where it's you and the computer, and, uh, that alone, you can- you can build really cool stuff really quickly.

Install uListen to search the full transcript and get AI-powered insights

Get Full Transcript

Get more from every podcast

AI summaries, searchable transcripts, and fact-checking. Free forever.

Add to Chrome