This is a tantalizing problem for me as a UX designer. My approach, which I'm quite proud of, places a UI primitive (Todo lists) center stage, with the chat thr

This is a tantalizing problem for me as a UX designer. My approach, which I'm quite proud of, places a UI primitive (Todo lists) center stage, with the chat thread on the side similar to Canvas or Claude's Artifacts. The interaction works like this: 1. User gets shown a list GUI based on their requirement (Meal Planning, Shopping List...) 2. Users speak directly to the list while the LLM listens in realtime 3. The LLM acknowledges with emojis that flash to confirm understanding 4. The LLM creates, updates or deletes the list items in turn (stored in localStorage or a Durable Object -> shout out https://tinybase.org/ https://tinybase.org/) The lists are React components, designed to be malleable. They can be re-written in-app by the LLM, while still taking todos. The react code also provide great context for the LLM — a shared contract between user and AI. I'm excited to experiment with streaming real-time screenshots of user interactions with the lists for even deeper mind-melding. I believe the cursor and chat thread remain critical. They ground the user and visually express the shared context between LLM and user. And of course, all these APIs are fundamentally structured around sequential message exchanges. So it will be an enduring UI pattern. If you're curious I have a demo here -> https://app.tinytalkingtodos.com/ https://app.tinytalkingtodos.com/