The demo opens the same way every time. A screen. A box. A cursor blinking in it. The presenter says you can ask it anything.
Sixteen months ago I wrote that I don’t want to chat with you. The argument then was about attention. Chat interrupts. It pulls you out of the work to have a conversation about the work. I stand by that. It was also the smaller point.
The bigger one took me a while to say plainly. A chat box is not a user experience. It is the absence of one.
A language model takes text and returns text. Ask it the same thing twice, and you get two answers. That is the raw shape of the thing. A chat box is that shape with a scrollbar. Nothing has been designed. The model has been exposed.
User experience is the layer between a person and a system. Its job is to take something that could come back a hundred ways and turn it into one action the person can trust. A button does that. A form does that. A ranked list does that. A chat box does none of it. It passes the hundred ways straight through to the person and lets them sort it out.
So the person sorts it out. They rephrase. They add the detail the system should have had. They read five paragraphs to find the one line that matters. They try again. Every one of those moves is work the interface was supposed to do.
This is not a design failure. It is a design not yet started.
Nobody knows what the job is. That is the honest reason every product got a box. The technology arrived before the use cases did. Teams had a capability and no defined task for it, so they shipped the one interface that works for every task and fits almost none. The box is what you ship before you know what you’re shipping.
A version of this is fine. A blank box is the right tool for a question that has no shape yet. That is research. You type things, you see what comes back, you learn what the model can do and where it falls down. Every product should start there. The problem is when that step gets called the product.
The tell is simple. Watch whether the box asks you what to do or tells you what it did.
The consumer AI products already show where this goes. The most chat-native tools on the market grew deterministic surfaces around the box. Files you can attach. Projects that hold context. Code that runs. Documents you edit in place instead of asking for a rewrite. The box stopped being the product even where the box was the product. Every one of those features is a job someone finally defined.
Enterprise software is behind that curve. The workflows are known. Route this ticket. Reconcile that account. Find what changed before the outage. The job has a shape, and the shape has had a shape for twenty years. Putting a cursor in front of it is not a simplification. It is a placeholder.
I get asked what Kosmos’s interface looks like. We haven’t shipped a box. We are still learning what the job is, and we are doing that in conversations with customers, not by handing them a cursor and watching what they type.
The demo opens with a box because the vendor is still deciding. The day they decide, the box gets deleted.