### Problem to solve Sending a GitLab Duo Chat prompt too early, or having a different thought while waiting, leads to the desire to cancel the request. In this example, I want to edit my prompt to add `project` into the context, and not wait until completion.  Neither the IDE integrations nor the GitLab UI provide a button action to cancel the current request. Not having this will cost the users (unnecessary waiting) time, which is exactly the opposite of what Duo chat aims to do - save time. ### Proposal Allow the users to cancel the current request by replacing the disabled submit button with a stop button. For screen readers announce the string "Stop generating" when focus has moved to the button. | Current | Proposed | |---------|----------| |  |  | ### Architecture & Implementation Plan: **Goal:** Enhance user control by introducing an abort functionality that allows users to cancel ongoing server processes initiated by chat prompts. This feature is aimed at improving responsiveness and reducing unnecessary waiting times. #### Current Implementation (Already Built): 1. **Initialize Subscription:** Clients start a subscription to receive real-time updates based on user session or prompt ID. 2. **Send Prompt Mutation:** Users send prompts via a mutation, which triggers server processing. 3. **Stream Responses:** Server processes the prompts and streams responses back to the client. #### Features to Implement: 4. **User Triggers Abort:** Users can click an abort button to stop the process at any time. This code will remain in the GitLabUI project. 5. **Handle Aborted Requests:** When the abort event is triggered, the UI will return to a state where it can accept new prompts. The host application must ensure that no more chunks from the aborted request ID are displayed. Subsequent chunks sent to the DuoChat library must have a fresh request ID.