FIX: Hide Stop Button Once Response Streaming Begins

[tahierhussain]

What

• Added isResponseStreaming computed state to detect when response has started streaming
• Updated Stop button condition to only show during thought chain phase
• Once response starts streaming, the Send button is displayed instead of Stop button

Why

• Previously, the Stop button was shown throughout the entire prompt execution (thought chain + response streaming)
• Users don't need the Stop button once the response has started streaming
• This provides a cleaner UX by showing the Send button earlier, allowing users to prepare their next prompt

How

• Added isResponseStreaming useMemo in ExistingChat.jsx that computes:
  • isPromptRunning && lastMessage?.response?.length > 0
• Threaded isResponseStreaming prop through the component hierarchy:
  • ExistingChat.jsx -> InputPrompt.jsx -> PromptInput.jsx -> MonacoPromptInput.jsx / DefaultPromptInput.jsx
• Updated button condition from isPromptRunning to isPromptRunning && !isResponseStreaming

Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)

• No, this PR should not break existing features
• The change only affects the visual display of the Stop/Send button
• All existing functionality (prompt submission, stopping prompts during thought chain) remains intact
• The prop defaults to false, so NewChat.jsx (which has no chat messages) works without changes

Database Migrations

• None

Env Config

• None

Relevant Docs

• None

Related Issues or PRs

• None

Dependencies Versions

• No new dependencies added

Notes on Testing

• Start a new prompt and verify Stop button appears during thought chain phase
• Once response starts streaming (text appears below thought chain), verify Send button replaces Stop button
• Test with both Monaco editor and default input modes
• Verify NewChat component still works correctly (no regressions)

Screenshots

The "Stop" button is replaced by the "Send" button once the response starts streaming.

Checklist

I have read and understood the Contribution Guidelines.

[greptile-apps]

Greptile Summary

This PR introduces an isResponseStreaming computed state in ExistingChat.jsx that hides the Stop button once the AI response starts streaming text, replacing it with a (disabled) Send button. The logic is correctly threaded through five components in the hierarchy, with prop defaults cleanly applied at each layer.

Confidence Score: 5/5

Safe to merge — logic is correct, all edge cases handled, no regressions introduced.

No P0 or P1 issues found. The isResponseStreaming computation is correct, dependency arrays are complete, and the disabled-button change prevents double submissions.

No files require special attention.

Important Files Changed

Filename	Overview
frontend/src/ide/chat-ai/ExistingChat.jsx	Adds isResponseStreaming useMemo with correct dependencies and passes it down to InputPrompt.
frontend/src/ide/chat-ai/InputPrompt.jsx	Threads isResponseStreaming prop with a default of false, correctly covering the NewChat use case.
frontend/src/ide/chat-ai/PromptInput.jsx	Passes isResponseStreaming to both child components; no default in destructuring but safe given InputPrompt always provides one.
frontend/src/ide/chat-ai/MonacoPromptInput.jsx	Correctly updates button condition and Send button disabled state; default for isResponseStreaming now added.
frontend/src/ide/chat-ai/DefaultPromptInput.jsx	Mirrors MonacoPromptInput changes for the default (non-Monaco) input path; both conditions updated consistently.

_{Reviews (3): Last reviewed commit: "fix: prevent concurrent submissions in M..." | Re-trigger Greptile}

[wicky-zipstack]

LGTM

[abhizipstack]

LGTM