The End of Software Is Headless: Only One Kind of Software Will Be Left

The fish trap exists for the fish; once you have the fish, you forget the trap. — Zhuangzi, “External Things” (筌者所以在鱼，得鱼而忘筌)

Let me start with the conclusion:

In the future, only one kind of software will exist: AI software.

Not software with an “AI button” bolted on, not software with a little chat assistant popping up in the corner. I mean software that has changed its form entirely — no interface, no menus, no forms, just a set of APIs with a large language model behind them.

I call it “headless software.”

1. Grok bot already showed us the answer

You’re scrolling X and see a post you don’t understand. What do you do?

A lot of people now just reply underneath: @grok what does this mean?

And Grok shows up. It explains, fact-checks, summarizes, even generates an image for you.

Notice something — in that scenario, Grok has no “interface” of its own.

You didn’t open an app, click a menu or hunt for a setting. It lives inside a reply box. You speak plainly, and it gets to work.

That is what future software looks like.

Software stops being something you have to “open,” “learn” and click around in. Software becomes a capability that sits behind the scenes. You speak, it acts.

2. The interface was always a compromise

The graphical interfaces we take for granted — buttons, dropdowns, tables, modals, pagination — why do they exist?

Because machines couldn’t understand human language.

Say you want to “mark every unpaid order from last month as expired.” A machine couldn’t parse that sentence. So programmers broke the task into buttons and filters: pick a date range, pick a status, select all, click bulk action, click confirm.

The interface is a translation humans invented to accommodate machines.

It’s Zhuangzi’s fish trap. What we always wanted was the fish — getting the job done. The trap was just a tool.

Now large language models understand human language.

When you can grab the fish directly, who cares how nicely the trap is woven?

Catch the fish, forget the trap.

3. The great form has no shape: what “headless” means

If you’ve done web scraping or front-end work, “headless” is a familiar word — a headless browser has no window, yet it still loads pages and runs scripts.

Scale that idea up to the whole software industry:

Software of the past = data + business logic + interface
Software of the future = data + business logic + API, handed to an LLM

The interface layer gets swallowed whole by the model.

Users no longer face your software. Users face an AI, and the AI calls your API on their behalf.

Laozi wrote: “The greatest sound is barely heard; the greatest form has no shape” (大音希声，大象无形). The best software may be software you never notice. It has no shape, but it’s always working.

4. My laziness was actually foresight

Let me talk about myself.

The software and tools I’ve built — honestly, these days I can’t be bothered to operate them by hand.

But my laziness didn’t start yesterday. Long ago I picked up a habit: every tool I write gets a set of API endpoints. Even when the interface was perfectly fine, even when I was the only user.

I couldn’t have told you why back then. It just felt wrong that data and operations should only be reachable through a page.

Looking back, that’s what the Chinese call 未雨绸缪 — mending the roof before it rains.

Because those endpoints are paying off now. A complex operation used to go like this:

Open the admin panel
Log in
Find the right page
Filter, tick boxes, page through results
Edit records one by one, then check everything again

Create, read, update, delete — click until your hand aches.

Now? I say one sentence to the AI:

“Find the records in this batch with the wrong status, fix them, delete the duplicates while you’re at it, and tell me what you changed.”

The AI reads the API docs, calls the query endpoint, makes the judgment calls, calls the update and delete endpoints, and hands me a list at the end.

I didn’t click a single page.

Xunzi wrote: “The gentleman is not different by birth; he is simply good at making use of things” (君子生非异也，善假于物也). People aren’t so different from one another; the difference is whether they know how to borrow the power of tools. We used to borrow interfaces. Now we borrow AI. And I can borrow AI’s power only because I left a door open in my software: the API.

Software without that door? However smart the AI is, it can only stand outside and stare.

5. What this means for people who build software

If you agree that only AI software will be left, the way you build software has to flip.

1. API first, interface second.

We used to design the screens and patch in endpoints later. From now on, design the API first; the interface is optional. If a feature can only be done by clicking and not through an API, it might as well not exist in the AI era.

2. Documentation is written for AI.

Endpoint names, parameter meanings, what comes back on an error — we used to write these for colleagues. From now on the main reader is a language model. Clear names and clear errors, and the AI gets it instantly; vague ones, and the AI only half-understands. That’s why protocols like MCP have taken off: at heart, they give software a manual an AI can read (I wrote about this in What Is an MCP Server, worth reading alongside this one).

3. Permissions matter more than ever.

An AI that can create, read, update and delete for you can also wipe your database for you. As the saying goes, a thousand-mile dyke collapses from an ant hole (千里之堤，溃于蚁穴). Your APIs need authentication, permission levels and audit logs; dangerous operations need a second confirmation and a way to roll back. Don’t throw the door wide open just because you’re the only user.

6. Will interfaces disappear completely?

Not completely, but they’ll move to the back row.

I think future interfaces will have only two jobs:

Showing results: once the AI is done, give me a chart or a table so I can see what happened at a glance.
Confirming: for anything involving money, deletion or irreversible actions, show a button I have to click to confirm.

Beyond that, the sprawling forms, nested menus and admin systems that need training to use will slowly become history.

Future software might be nothing more than an input box and a confirm button.

Closing: a thousand sails pass the sunken ship

Beside the sunken ship, a thousand sails go by; before the withered tree, ten thousand trees are in spring. — Liu Yuxi (沉舟侧畔千帆过，病树前头万木春)

Every shift in how we interact with computers wipes out a generation of software. The command line gave way to the GUI, desktop software gave way to the web, and the web lost half its ground to apps.

This time, it’s the interface itself.

Software that has only an interface and no API will be the sunken ship. Software that opens up its capabilities so AI can call them directly will be the thousand sails.

So if you’re writing a tool right now, however small, take my advice:

Give it an API.

One day you’ll be like me, too lazy to click any page — and glad you left that door open.