Reusable chat components

[jtpio]

Problem

Currently @jupyter/chat can render code blocks and arbitrary HTML, which is useful to consumers of the chat and other extensions because they can inline custom components.

However each extension will end up providing their own components, so it could make sense to have @jupyter/chat provide a common set of components that can be reused by many extensions.

Proposed Solution

Expose a common set of components from @jupyter/chat or another package.

Additional context

jupyterlite-ai has been experimenting with this, here is a quick demo screencast of tool calls and approval steps:

jupyterlite-ai-tool-calls.mp4

[jtpio]

cc @dlqqq @brichet as discussed during the call today.

Also cc @Zsailer who may be interested

[Zsailer]

Yes! I think this is absolutely necessary.

In my mind, Jupyter's ethos is/should be "provide the building blocks for interactive computing". Chat is a necessary UX for today's developer experience interfaces with the rise of AI. It's one foundational building block.

Further, within the chat interface are a bunch of possible components that we're seeing emerge in the AI products popping up. I would love for us to list some of theses and begin to provide our own set of building blocks within the chat experience that developers can use to build rich chat interfaces.

As Jeremy mentioned, the UX for showing a tool call and approval above is beautiful. We definitely need that.

[Zsailer]

I think another common component is a To Do List that can be regularly updated by an agent.