Skip to content

feat: add tool approval flow component for agentic chat

John Slaughterrequested to merge
js/agentic-chat-approval-flow into main

What does this MR do?

This MR introduces a tool approval flow component. The component provides a modal interface for approving or denying tool executions requested by agentic chat.

Features

  • Tool approval modal: Displays tool details and allows users to approve or deny execution
  • Rejection reason modal: Optional second step where users can provide a reason for denying the tool

The approval flow ensures users maintain control over tool executions while providing a smooth experience for both approval and rejection workflows.

Screenshots or screen recordings

2025-06-17 08-55-47.mov

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

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • Added the ~"component:*" label(s) if applicable.

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:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.
Edited by John Slaughter

Merge request reports