I noticed something while working with interns and junior developers.
People are building more than ever. Cursor, Claude, Copilot. The AI tools are insane. You can ship features in hours that used to take days. But there's a problem.
Nobody's actually learning.
They're building complex things without understanding the engineering behind them. Database schemas, API designs, component patterns. All generated. All shipped. None of it absorbed.
The Problem
When you vibe code, a lot happens under the hood. Real engineering decisions. Trade-offs. Patterns that took years to evolve. But you're moving fast. You accept the suggestion, it works, you move on.
And that's fine for shipping. But if you want to grow as an engineer, you need to understand what you're shipping.
I saw this with interns. They could build anything with AI assistance, but when asked to explain why they made certain decisions, they couldn't. Because they didn't make those decisions. The AI did.
The Solution
So I built Cursor Learn.
trycursor.ai
The idea is simple. Even if you're vibe coding all day, at the end of it, you can do a postmortem. Look at what actually happened. What engineering decisions were made. What patterns were used. What concepts you should understand.
It's like having a learning layer on top of your Cursor conversations.
How It Works
Cursor Learn reads your local Cursor chat history and extracts the lessons.
Overviews turn your vibe coded sessions into actual programming lessons. Every AI-generated component, every schema, every API design contains lessons about software engineering. We extract them.
Interactive Learning helps you build muscle memory. Not just reading about patterns, but actually practicing them.
Agents let you explore your codebase with AI that has full context of your previous conversations. Ask follow-up questions. Go deeper.
Notes & Snippets for saving the important stuff. Concepts, code patterns, things you want to remember.
And everything stays local. Your chats can have API keys, sensitive info. Cursor Learn keeps it all on your machine.
Why I Built This
Honestly, I use it myself too. Managing my own learning, keeping track of concepts, doing postmortems on what I built.
Lee Robinson from Vercel tweeted something that resonated with me:
He's right. And I don't think the answer is to stop using AI. The answer is to build systems that help you learn while you use AI.
That's what Cursor Learn is.
Try It
It's a desktop app. Open source. Free.
This is my first time building a desktop app, so expect some bugs and rough edges. But I'd love to hear how you use it and any feedback you have.
The goal is simple: vibe code all you want, but actually learn from it.