I grew up on the command line. My first machines were old Tandy computers running DOS, and there was no other way to use them. You didn't click anything. You typed. Loading a game, copying a file, formatting a disk, it all happened at a prompt. The CLI wasn't a power-user feature. It was how you made the computer work, period.

Then Windows and the Mac took over, and for the next thirty years the entire software industry worked on hiding that prompt. Prettier interfaces. Drag and drop. WYSIWYG editors. No-code platforms. The command line got pushed into a corner where only developers and sysadmins ever went. A black screen with a blinking cursor. If you didn't already know what to type, you were stuck.

Then AI showed up, and the terminal won anyway.

The numbers are hard to ignore

The clearest example is Claude Code, Anthropic's AI coding tool. It doesn't run in a slick web app. It runs in the terminal. The same interface we've had since the 1970s.

And it's the fastest-growing software product most of us have ever seen. It hit $1 billion in annualized revenue six months after its public launch, and $2.5 billion by February 2026, according to Reuters and Anthropic's own reporting. For comparison, Cursor, another popular AI coding tool, took more than a year to cross $500 million.

Usage numbers tell the same story. SemiAnalysis found that by early February 2026, Claude Code was authoring roughly 4 percent of all public GitHub commits, around 135,000 commits per day, and projected it could reach 20 percent or more by the end of the year. Anthropic reported that weekly active users doubled in the first weeks of 2026 alone, and business subscriptions quadrupled.

Meanwhile, the Pragmatic Engineer survey from February 2026 found that 73 percent of engineering teams now use AI coding tools daily, up from 41 percent a year earlier. At small companies and startups, Claude Code adoption sits around 75 percent. Three out of four.

Think about what that means. The hottest interface in software right now is a text prompt in a terminal window. Not despite being a terminal. Because of it.

And it's not just developers anymore

Here's the part that really gets me. I'm watching designers, marketers, and project managers open a terminal like it's nothing. People who would have laughed at you five years ago if you suggested they use the CLI.

Anthropic's own Economic Index research shows the shift. Coding is still the biggest use case, around 35 percent of conversations, but usage is spreading fast across other kinds of work. The top ten tasks made up 24 percent of all activity in late 2025 and only 19 percent by February 2026. The tool is diffusing outward, from developers to everyone else. Analysts covering the space say the same pattern showing up in engineering is arriving in marketing, finance, legal, and operations, just a year or so behind.

Non-developers aren't learning the command line. They're skipping the part that made it hard.

The interface was never the problem

This is the lesson, and it's one I've been preaching for years.

The CLI wasn't scary because it was ugly. It was scary because you had to already know what to type. Every GUI ever built was an attempt to solve that knowledge problem with buttons. AI solved it with language. You say what you want. It figures out the rest.

And once the knowing part was fixed, it turns out people are perfectly happy with a blinking cursor. Nobody misses the ribbon menus.

That should tell you something about how much of modern software is over-engineered. We spent decades stacking abstraction on abstraction, framework on framework, trying to make things "easier." The terminal is basically unchanged since the 70s. It does one thing. You tell it what you want, it does it. It outlived every trend because it's simple and it works.

Things don't need to be the latest and greatest to be the best.

What this means if you run a business

If you're a contractor or a business owner reading this, here's the takeaway. The tools your vendors and partners use are changing fast. Real fast. Development that took weeks now takes days. Teams in published case studies report development velocity gains of 2x to 10x after adopting these tools.

But here's what hasn't changed. Someone still has to understand what got built. AI can generate code faster than anyone can type it. It can't tell you whether that code is the right code for your business, whether it's secure, whether it'll survive the next platform update, or what breaks when something changes. Writing code was never the bottleneck. Comprehension was, and still is.

So when you're evaluating a digital partner, don't ask whether they use AI. Everyone does now, or will soon. Ask whether they understand what they're shipping. Ask who's accountable when it breaks. The tools got faster. The responsibility didn't move.

The command line won because it kept things simple and it worked. That's not a bad standard for the rest of your technology either.

Sources: