Feature request: support extension views in ChatKit UI

[tiven-w]

Summary

Add support in ChatKit UI for rendering extension views, such as remote components, as part of the chat experience.

Motivation

Some AI workflows need to surface richer interactive UI than message bubbles alone can provide. For example, an assistant may need to open a custom tool view, display a business-specific remote component, show contextual details, or let the user complete an action inside an embedded extension view.

Requested capability

It would be helpful if ChatKit UI could support extension views in flexible ways, such as:

• Opening an extension view in a right-side panel that can be shown or hidden by the user.
• Allowing the assistant/runtime to dynamically trigger an extension view based on the conversation state or tool output.
• Supporting remote components as first-class extension view content.
• Providing a clean API for registering, opening, closing, and updating extension views from application code.

Example use cases

• Show a custom business form next to the conversation.
• Display structured tool results in a dedicated panel instead of only rendering them as chat messages.
• Open an approval, configuration, or inspection view when the assistant reaches a specific workflow step.
• Let users switch between the chat thread and richer contextual UI without leaving the ChatKit surface.

Notes

A right-side panel would be a natural default presentation, but it would also be useful if applications could dynamically decide when and how an extension view is displayed.