fix(web): keep the send action visible during active turns

[Exotic209093]

Problem

While a turn is running, a desktop composer with sendable follow-up text showed only Stop. The send-while-running affordance from #4781 was gated to mobile viewports (\showSendWhileRunning={isMobileViewport}), so on desktop widths the steer submit that Enter already performs had no visible button.

Fix

Removed the viewport gate and the \showSendWhileRunning\ prop entirely. \ComposerPrimaryActions\ now renders Send alongside Stop whenever the composer has sendable content during a running turn, on every viewport. An empty composer still shows Stop only.

Fixes #7750

ox-alpha via opencode

---

Note

Low Risk
UI-only composer action visibility; no auth, data, or send-path logic changes.

Overview
Shows Send next to Stop whenever a running turn has sendable follow-up text, on all viewports—not only mobile.

Removes the showSendWhileRunning gate that hid the button on desktop even though Enter already submitted. An empty composer still shows Stop only.

^{Reviewed by Cursor Bugbot for commit 6d0e2d1. Configure here.}

Note

Keep send button visible during active turns in ChatComposer

• Removes the showSendWhileRunning prop from ComposerFooterPrimaryActions and ComposerPrimaryActions, so the send button is no longer gated on viewport or Enter-to-send availability.
• During a running turn, the send button now renders whenever hasSendableContent is true, and the stop button uses the larger size under the same condition.
• Updates tests in ComposerPrimaryActions.test.tsx to assert send is shown alongside stop when content exists and hidden when the composer is empty.
• Behavioral Change: send button visibility during active turns is now unconditional on viewport or Enter-to-send setting; all callers passing showSendWhileRunning must be updated.

^{Macroscope summarized 6d0e2d1.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d818c900-57a1-487c-a9b2-599b0adc3c20

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved at 6d0e2d1

Macroscope's review found this PR approvable — This PR simplifies UI logic by removing a prop that conditionally showed the send button only on mobile during active turns. The change is small, self-contained, and properly tested - the send button now appears consistently across all viewports when there's sendable content.

^{You can add or adjust custom eligibility rules. Learn more.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch shows Send beside Stop during active turns on desktop and mobile. The same UI choice is already covered by open #7751, which remains open for review. We are closing this parallel implementation.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.