Vibe computing.

For decades, the person at the computer was the operator. You knew the controls. You executed the steps. You moved between the apps, copied things across, filled out the forms. Every interaction was a small translation. What you meant, converted into something the machine could accept.

We got very good at it. We called it computer literacy. We taught it in schools. We sold software based on whose syntax was less painful. The people who couldn’t pick it up, like older parents or anyone whose work didn’t force them to, ended up on the wrong side of a wall.

That arrangement is changing.

The interesting move isn’t replacing the apps. It’s the opposite.

Same Gmail. Same Notion. Same legacy form from 2003 that nobody’s allowed to redesign. None of it has to be rebuilt. The screen you stare at every day stays. The tools you’ve memorised stay. The integrations your company already paid for stay.

What changes is who’s at the controls. The keyboard is no longer the only input. The mouse is no longer the only way through. The screen still shows the same surface. But a different hand can move across it now.

An AI sits there with you. It clicks the buttons. It types the words. It moves between the apps. In realtime. On the screen you’re already looking at.

It sees what you see. The same inbox. The same draft. The same row in the same spreadsheet. The context isn’t piped in through an API. It’s the literal pixels in front of you. When you say this one, the AI knows which one.

You don’t hand the work off and walk away. You watch it happen. You correct it midway. You take the mouse back when you want to. It’s less like dispatching a remote assistant and more like working next to someone, both of you in the same chair, taking turns.

The way you direct it isn’t another input device. It’s the one you already have.

You’re three messages into a difficult thread and you say draft my response so it doesn’t make things worse. You’re scheduling a call and you say find me a slot that doesn’t sit between two other meetings. You’re behind on a brief and you say turn everything from this week into a one-page memo.

You don’t learn a syntax. You don’t memorise commands. You speak the way you’d describe the work to a colleague. Words go out. The cursor moves. The work happens.

This isn’t AI that writes for you and stops there. It isn’t a back-room engine that ships a result. It isn’t a chatbot you have a conversation with about doing the work.

It’s an AI that operates your computer the way you operate it, sitting in the same chair, clicking the same buttons, working in the same apps. Vibe-coding gave us a name for the version of this that happens when you’re writing software. Vibe-computing names the rest of it: the practice of working with a computer by saying what you mean, while the system handles the how.

That’s vibe-computing.