for anyone building interactive MCP UI widgets on ChatGPT Apps: the follow-up message flow (the mechanism where a widget informs the agent that something happened, like a button click or a selection) has several open bugs that will likely cost you time if you don't know about
Computer Scientist. Principal Architect at Salesforce AI Applications Platform. ECMA TC39 Member, Former Editor of ECMA402. Yahoo! Alumni & Former YUI Core Team
- i've been posting about what agent-composed UI looks like, but you have to see it and feel it in practice. it's very much experimental, but give it a shot and tell me what you see. the setup: you take any MCP server you already have wired up in your host (a catalog, a CRM
- i think #MCPUI is going to end up serving a much smaller role than its current positioning suggests. not because it doesn't work, it does, but because the class of conversational moments that genuinely need a custom, tool-authored widget is narrow, and it's about to get narrower.
- here's a small example that exposes a structural limit of #MCPUI widgets. the user says "i don't like emojis" partway through a conversation, or "stop showing me pricing," or "i prefer compact views." from that point forward, every response should honor that preference. if the
- i think the cheapest, highest-leverage UX primitive in conversational agents is a small set of bounded affordances at the end of every meaningful response. two to four next-turn buttons, sized for the moment, and the user advances by clicking instead of typing. mechanically,

