Is your feature request related to a problem?
Describe the feature you'd like
🌟 Feature Description
Prevent multiple consecutive submissions while the AI response is being processed by temporarily disabling the Send button and displaying a loading indicator. This ensures that users cannot accidentally submit the same prompt multiple times before the previous request is completed.
🔍 Problem Statement
Currently, users can click the Send button multiple times before the AI finishes processing the previous request. This can result in duplicate API calls, repeated task creation, multiple identical chat responses, and unnecessary resource consumption. It also affects the overall user experience by creating confusion and increasing backend workload.
🎯 Expected Outcome
Disable the Send button immediately after a message is submitted.
Display a loading spinner or progress indicator while the AI is generating a response.
Re-enable the button once the request is completed or an error occurs.
Ensure that only one request can be processed at a time from the chat interface.
This enhancement will improve usability, prevent duplicate submissions, and optimize API usage.
📷 Screenshots and Design Ideas
Design Idea:
After clicking Send, replace the send icon with a loading spinner or show a small progress indicator next to the input field.
Keep the input field editable if appropriate, but disable the Send button until the response is received.
Once processing is complete, restore the normal send button.
(No screenshots available at the moment. I can provide UI mockups if required.)
📋 Additional Context
This is a frontend enhancement and does not require modifications to the existing AI processing logic. It can be implemented using a loading state (e.g., isLoading) to control the enabled/disabled state of the send button. The change will improve user experience, reduce duplicate API requests, and make the chat interface more responsive and reliable.
Hi, I would like to work on this issue under GSSoC 2026. Kindly assign it to me if it is available. Thank you!
Record
Is your feature request related to a problem?
Describe the feature you'd like
🌟 Feature Description
Prevent multiple consecutive submissions while the AI response is being processed by temporarily disabling the Send button and displaying a loading indicator. This ensures that users cannot accidentally submit the same prompt multiple times before the previous request is completed.
🔍 Problem Statement
Currently, users can click the Send button multiple times before the AI finishes processing the previous request. This can result in duplicate API calls, repeated task creation, multiple identical chat responses, and unnecessary resource consumption. It also affects the overall user experience by creating confusion and increasing backend workload.
🎯 Expected Outcome
Disable the Send button immediately after a message is submitted.
Display a loading spinner or progress indicator while the AI is generating a response.
Re-enable the button once the request is completed or an error occurs.
Ensure that only one request can be processed at a time from the chat interface.
This enhancement will improve usability, prevent duplicate submissions, and optimize API usage.
📷 Screenshots and Design Ideas
Design Idea:
After clicking Send, replace the send icon with a loading spinner or show a small progress indicator next to the input field.
Keep the input field editable if appropriate, but disable the Send button until the response is received.
Once processing is complete, restore the normal send button.
(No screenshots available at the moment. I can provide UI mockups if required.)
📋 Additional Context
This is a frontend enhancement and does not require modifications to the existing AI processing logic. It can be implemented using a loading state (e.g., isLoading) to control the enabled/disabled state of the send button. The change will improve user experience, reduce duplicate API requests, and make the chat interface more responsive and reliable.
Hi, I would like to work on this issue under GSSoC 2026. Kindly assign it to me if it is available. Thank you!
Record