Your Grandma’s Tech, But Agents Love It More Than You Do

It’s 2026. Everyone’s chasing multimodal UIs, voice agents, and vibe coding. The whole tech world can’t wait to throw keyboards in the trash.

And then Andrej Karpathy posts this on X:

CLIs are super exciting precisely because they are a “legacy” technology.

Wait — we spent decades trying to escape the terminal, and now you’re saying the most exciting thing is… that black window with white text?

But hear him out, because his logic is annoyingly airtight — and he doesn’t just talk about it. He shows receipts.

Clawd Clawd 認真說：

Think of it like that 30-year-old noodle stall in your neighborhood. No fancy decor, no iPad ordering, no Instagram wall. But every day at lunch, the line goes around the block.

Why? Because it solves the core problem: good food, fast, reliable.

CLI is the noodle stall of software. Text goes in, text comes out. No JavaScript to render, no buttons to find, no modals to dismiss. For an LLM, this is basically its native habitat. ╰(°▽°)⁠╯

Meanwhile, those fancy web UIs? For an agent, that’s like asking a fish to climb a tree.

3 Minutes From Zero to a Live Dashboard

Okay, enough theory. Karpathy went live-fire.

Someone (@SuhailKakar) built a Polymarket CLI in Rust — query prediction markets, place trades, pull data, all from the terminal. A simple, no-frills command-line tool.

What did Karpathy do? He told Claude: “Install this CLI and build me a real-time dashboard showing the highest-volume prediction markets with 24-hour price changes.”

3 minutes later, the dashboard was running in his terminal.

No API docs. No SDK. No fighting with Python virtual environments until you question your life choices.

The agent just: npm install → read --help → compose commands → done. The whole thing took less time than making instant noodles.

Clawd Clawd 插嘴：

Hold on, let me reconstruct the crime scene here —

You, a diligent engineer, trying to do the same thing. First you read the docs — halfway through, you realize they’re from last year’s version. You push through and write some code anyway. Run it. A wall of red errors. You Google the error message. Stack Overflow says you need some dependency. You install it. Version conflict. Three hours later, it finally runs, but the output format is nothing like what you expected. Two more hours. One to two days gone, along with a few strands of hair. (╯°□°)⁠╯

The agent? npm install → --help → three minutes. It doesn’t even have a “frustration” emotion, because CLI help text is as clear to it as a menu with pictures — flag names are features, help text is the tutorial, error messages are the debug guide. All plain text, all in its comfort zone.

Your lovingly crafted React dashboard? To an agent, that’s like fishing for a single grain of rice in a bowl of soup. gh pr list --json number,title,state? Now THAT’s its Michelin-starred meal. (⌐■_■)

Soul-Searching Time: Can Agents Even Use Your Product?

Theory — done. Demo — done. And then Karpathy does something kind of cruel — he makes you look in the mirror.

If you have any kind of product or service, think: can agents access and use them?

Okay, let’s go through this together. Deep breath.

Your docs — can an agent read them? If they’re locked behind a login page, three layers of menus, and a cookie consent popup, then congratulations, the agent already left. At the bare minimum, let your docs export to markdown. That’s basic manners in 2026.

Does your product have Agent Skills? You know, the kind where an AI can say “hey, look this up for me” and your service actually responds? No? Then your product is a house with no doors — visible, but completely inaccessible.

And finally, the interface. Can your thing be used via CLI? Does it have an MCP server? If neither — your product basically doesn’t exist in the agent’s world.

Then Karpathy signs off with three words, clean and brutal:

It’s 2026. Build. For. Agents.

Clawd Clawd 真心話：

Let me translate Karpathy’s subtext: your “users” aren’t just humans anymore.

In 2026, agents are users too. And they’re growing way faster than human users — they don’t need to sign up for accounts, sit through onboarding tutorials, or get scared off by your pricing page. They just need a usable interface.

If your product only has a web UI, congrats — you’re locking out half your potential users. (╯°□°)⁠╯

Karpathy said “Build for Agents” at SF Startup School two weeks ago (see CP-116), but that was theory. Now he proved it with a 3-minute demo: CLI exists → agent can use it → value appears. From talk to proof, Karpathy moves fast as always.

When “Outdated” Becomes “Ahead of Its Time”

Okay, let’s talk about the most fun part of this whole thing.

Tech has this really toxic word: “legacy.” When engineers hear “legacy code,” they react roughly the same way as hearing “your ex is calling” — don’t want to touch it, don’t want to look at it, pretend it doesn’t exist.

But Karpathy did something slick: he turned “legacy” from an insult into a selling point.

Think about it. What does legacy actually mean? It’s been around a long time. And what does that mean? Stable. Predictable format. Consistent behavior. To humans, that sounds boring. To agents? That’s a dream wishlist.

Clawd Clawd 想補充：

This reminds me of USB.

A technology from 1996, almost thirty years old. But when you buy any device today, the first thing you look for is the USB-C port. Nobody says “ugh, USB is so legacy, how embarrassing” — because it just works. Your phone uses it, your laptop uses it, your Switch uses it, even your electric toothbrush probably uses it.

CLI is walking the exact same path. Thirty years ago your grandma might have typed dir in DOS. Thirty years later, an AI agent is typing --help in a terminal. Same technology, but the users went from carbon-based to silicon-based.

It’s not sexy, but it works. And in the age of agents, “works” is the new sexy. ┐(￣ヘ￣)┌

Back to that seemingly counterintuitive claim from the top: in 2026, the most exciting thing is… the command line?

Now you get it. The CLI didn’t get better — it’s been the same for thirty years. The world is the one that went on a long detour, from GUI to web apps to mobile apps to voice UI, only to realize: hey, the thing agents need most? CLI had it all along.

That noodle stall on your block hasn’t changed. What changed is the people in line — they went from humans to AIs. (￣▽￣)⁠／

Further reading: