What does this MR do?
This change adds support for custom message renderers in the web agentic chat component. Previously, the system had a fixed set of message types (like user messages, agent messages, tool messages) that were hardcoded. Now the GitLab application can pass in custom components to handle specific types of messages or override the default ones.
The main improvements include:
- A new
messageRenderers property that accepts an array of custom message handlers, each with a component and a function to determine when to use it.
- The custom renderers are checked first, allowing them to override default behavior.
- Better organization of tool-related messages, separating approval tools from visualization tools.
- The custom renderers get passed down through multiple layers of the chat interface (from the main chat component to individual messages).
This makes the chat system more flexible and extensible, allowing different parts of the application to customize how messages are displayed without modifying the core chat components. For example, one area might want to show code snippets differently, or another might need special formatting for certain types of responses.
Screenshots or screen recordings
This MR doesn't introduce visual changes to any component.
Integration merge requests
Does this MR meet the acceptance criteria?
This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.
Toggle the acceptance checklist
Conformity
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
Accessibility
If this MR adds or modifies a component, take a few moments to review the following:
