While agents that can book a hair appointment are interesting, that's more of a workaround than the kind of UI I think we're going for. The visual appearance of the software itself must change dynamically according not only to the task but to the user's preferences. This is something we haven't seen demonstrated yet.
Your point about the visual appearance changing dynamically is the 'Holy Grail' I touch on in the 'Generative UI' section. We are currently stuck designing static screens for dynamic problems.
I agree we haven't seen a true demonstration yet. Do you think that shift happens at the App level first (e.g., a dynamic Spotify), or does it require a whole new OS paradigm (a 'Generative OS') to work?
It implies that design systems are about to change fundamentally. Instead of shipping a library of static components, we'll need to ship a set of constraints and rules that tell the RAG model how it's allowed to construct the UI on the fly.