Ghulam Qadir
Engineering2 min read

When the model draws the interface

OpenAI’s GPT-6 rollout puts interactive UI inside the answer. For people who ship products, the interesting part is not the demo. It is who owns the screen.

When the model draws the interface

On 7 October 2026 OpenAI started rolling GPT-6 out to ChatGPT, including an Intelligent UI that can answer with graphics, buttons, forms, charts, and small tools composed in the conversation. Paid tiers get GPT-6 Sol. Free and Go get GPT-6 Luna. The write-up is on OpenAI’s announcement.

I build the other kind of interface: Next.js screens, forms with validation, permissions, and a database behind them. Watching a model assemble a UI in the reply changes the job, and it does not remove it.

The answer is becoming a surface

For a few years the product pattern was simple. The user typed. The model returned text. Your app wrapped that text in a layout you designed. Intelligent UI breaks that split. The model chooses text, a visual, and a control, then keeps going while the person is still reading. OpenAI describes this as progressive composition: partial responses that stay one answer, not a pile of filler.

That is useful for learning a topic or throwing together a one-off calculator. It is a poor place to keep a company’s source of truth. A button inside a chat transcript is not a workflow. It has no audit trail, no role check, and no record of who confirmed the number.

What I would still build by hand

  • Anything that moves money, changes a record, or grants access.
  • Screens a team uses every day. Muscle memory beats a fresh layout on every reply.
  • Empty states, errors, and the boring path where the model is wrong and a person has to fix it.

I would let a model draft a view for exploration: a chart of last month’s leads, a filter the user just described, a comparison they will throw away. I would not let it invent the CRM.

A practical split

Treat generated UI as a sketch layer on top of a stable product. The sketch can be rich. The product stays typed. If ChatGPT can render a form, your API should still be the thing that accepts the submission, with the same validation you would put on a normal page.

The rollout also splits the model by plan. Sol and Luna are both called GPT-6, and they are not the same weight. If your product calls the API rather than relying on ChatGPT’s chat tab, pin the model id. GPT-6 in a marketing sentence is not a contract.

I am glad answers can be visual. I still want the screen a business runs on to be one I can open in the repo.