fix(web): show send during active turns

[obinnanwachukwu1]

Problem

The desktop composer hides Send for the entire duration of an active turn, even after the user types a follow-up. Enter already submits that follow-up as a steer, but the equivalent visible action was limited to mobile viewports.

Fix

The shared composer primary actions now show:

• Stop while a turn is running and the composer is empty;
• Stop and Send while a turn is running and the composer has sendable content.

This removes the viewport-specific showSendWhileRunning path and gives desktop and responsive web the same behavior. Stop remains available, so this does not change interrupt or Queue/Steer semantics.

UI changes

Before	After

Verification

• vp test run apps/web/src/components/chat/ComposerPrimaryActions.test.tsx — 15 tests passed
• vp run --filter @t3tools/web typecheck
• targeted lint
• targeted formatting check
• git diff --check

Closes#7750

Built with GPT-5.6 Sol through the Codex harness in T3 Code.

Note

Always show send button during active turns when composer has content

• Removes the showSendWhileRunning prop from ComposerPrimaryActions and ComposerFooterPrimaryActions, and stops forwarding it from ChatComposer.
• 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 — no longer gated by mobile viewport or Enter-to-send availability.
• Updates ComposerPrimaryActions tests to match the new behavior and removes the test that tied send visibility to Enter-to-send.
• Behavioral Change: send button is now visible on all viewports during active turns when content is present, not just mobile; reviewers should check ComposerPrimaryActions.tsx and ChatComposer.tsx for any remaining references to the removed prop.

^{Macroscope summarized 3133379.}

---

Note

Low Risk
UI-only composer action visibility; interrupt and send semantics are unchanged.

Overview
During an active turn, the composer now shows Stop + Send whenever there is sendable content, on desktop as well as mobile. An empty composer still shows only Stop.

This drops the viewport-gated showSendWhileRunning flag. Enter-to-send already steered follow-ups on desktop; the visible Send button now matches that.

^{Reviewed by Cursor Bugbot for commit 3133379. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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: 16b71c98-1965-4a38-99f9-280501c64889

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 3133379

Macroscope's review found this PR approvable — Removes conditional showSendWhileRunning prop to always display the send button during active turns when there's sendable content. This is a minor, self-contained UI simplification that removes more code than it adds.

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

[obinnanwachukwu1]

Problem

The desktop composer hides Send for the entire duration of an active turn, even after the user types a follow-up. Enter already submits that follow-up as a steer, but the equivalent visible action was limited to mobile viewports.

Fix

The shared composer primary actions now show:

• Stop while a turn is running and the composer is empty;
• Stop and Send while a turn is running and the composer has sendable content.

This removes the viewport-specific showSendWhileRunning path and gives desktop and responsive web the same behavior. Stop remains available, so this does not change interrupt or Queue/Steer semantics.

UI changes

Before	After

Verification

• vp test run apps/web/src/components/chat/ComposerPrimaryActions.test.tsx — 15 tests passed
• vp run --filter @t3tools/web typecheck
• targeted lint
• targeted formatting check
• git diff --check

Closes#7750

Built with GPT-5.6 Sol through the Codex harness in T3 Code.

Note

Always show send button during active turns when composer has content

• Removes the showSendWhileRunning prop from ComposerPrimaryActions and ComposerFooterPrimaryActions, and stops forwarding it from ChatComposer.
• 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 — no longer gated by mobile viewport or Enter-to-send availability.
• Updates ComposerPrimaryActions tests to match the new behavior and removes the test that tied send visibility to Enter-to-send.
• Behavioral Change: send button is now visible on all viewports during active turns when content is present, not just mobile; reviewers should check ComposerPrimaryActions.tsx and ChatComposer.tsx for any remaining references to the removed prop.

^{Macroscope summarized 3133379.}

---

Note

Low Risk
UI-only composer action visibility; interrupt and send semantics are unchanged.

Overview
During an active turn, the composer now shows Stop + Send whenever there is sendable content, on desktop as well as mobile. An empty composer still shows only Stop.

This drops the viewport-gated showSendWhileRunning flag. Enter-to-send already steered follow-ups on desktop; the visible Send button now matches that.

^{Reviewed by Cursor Bugbot for commit 3133379. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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: 16b71c98-1965-4a38-99f9-280501c64889

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 3133379

Macroscope's review found this PR approvable — Removes conditional showSendWhileRunning prop to always display the send button during active turns when there's sendable content. This is a minor, self-contained UI simplification that removes more code than it adds.

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

[obinnanwachukwu1]

Problem

The desktop composer hides Send for the entire duration of an active turn, even after the user types a follow-up. Enter already submits that follow-up as a steer, but the equivalent visible action was limited to mobile viewports.

Fix

The shared composer primary actions now show:

• Stop while a turn is running and the composer is empty;
• Stop and Send while a turn is running and the composer has sendable content.

This removes the viewport-specific showSendWhileRunning path and gives desktop and responsive web the same behavior. Stop remains available, so this does not change interrupt or Queue/Steer semantics.

UI changes

Before	After

Verification

• vp test run apps/web/src/components/chat/ComposerPrimaryActions.test.tsx — 15 tests passed
• vp run --filter @t3tools/web typecheck
• targeted lint
• targeted formatting check
• git diff --check

Closes#7750

Built with GPT-5.6 Sol through the Codex harness in T3 Code.

Note

Always show send button during active turns when composer has content

• Removes the showSendWhileRunning prop from ComposerPrimaryActions and ComposerFooterPrimaryActions, and stops forwarding it from ChatComposer.
• 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 — no longer gated by mobile viewport or Enter-to-send availability.
• Updates ComposerPrimaryActions tests to match the new behavior and removes the test that tied send visibility to Enter-to-send.
• Behavioral Change: send button is now visible on all viewports during active turns when content is present, not just mobile; reviewers should check ComposerPrimaryActions.tsx and ChatComposer.tsx for any remaining references to the removed prop.

^{Macroscope summarized 3133379.}

---

Note

Low Risk
UI-only composer action visibility; interrupt and send semantics are unchanged.

Overview
During an active turn, the composer now shows Stop + Send whenever there is sendable content, on desktop as well as mobile. An empty composer still shows only Stop.

This drops the viewport-gated showSendWhileRunning flag. Enter-to-send already steered follow-ups on desktop; the visible Send button now matches that.

^{Reviewed by Cursor Bugbot for commit 3133379. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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: 16b71c98-1965-4a38-99f9-280501c64889

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 3133379

Macroscope's review found this PR approvable — Removes conditional showSendWhileRunning prop to always display the send button during active turns when there's sendable content. This is a minor, self-contained UI simplification that removes more code than it adds.

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

[obinnanwachukwu1]

Problem

The desktop composer hides Send for the entire duration of an active turn, even after the user types a follow-up. Enter already submits that follow-up as a steer, but the equivalent visible action was limited to mobile viewports.

Fix

The shared composer primary actions now show:

• Stop while a turn is running and the composer is empty;
• Stop and Send while a turn is running and the composer has sendable content.

This removes the viewport-specific showSendWhileRunning path and gives desktop and responsive web the same behavior. Stop remains available, so this does not change interrupt or Queue/Steer semantics.

UI changes

Before	After

Verification

• vp test run apps/web/src/components/chat/ComposerPrimaryActions.test.tsx — 15 tests passed
• vp run --filter @t3tools/web typecheck
• targeted lint
• targeted formatting check
• git diff --check

Closes#7750

Built with GPT-5.6 Sol through the Codex harness in T3 Code.

Note

Always show send button during active turns when composer has content

• Removes the showSendWhileRunning prop from ComposerPrimaryActions and ComposerFooterPrimaryActions, and stops forwarding it from ChatComposer.
• 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 — no longer gated by mobile viewport or Enter-to-send availability.
• Updates ComposerPrimaryActions tests to match the new behavior and removes the test that tied send visibility to Enter-to-send.
• Behavioral Change: send button is now visible on all viewports during active turns when content is present, not just mobile; reviewers should check ComposerPrimaryActions.tsx and ChatComposer.tsx for any remaining references to the removed prop.

^{Macroscope summarized 3133379.}

---

Note

Low Risk
UI-only composer action visibility; interrupt and send semantics are unchanged.

Overview
During an active turn, the composer now shows Stop + Send whenever there is sendable content, on desktop as well as mobile. An empty composer still shows only Stop.

This drops the viewport-gated showSendWhileRunning flag. Enter-to-send already steered follow-ups on desktop; the visible Send button now matches that.

^{Reviewed by Cursor Bugbot for commit 3133379. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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: 16b71c98-1965-4a38-99f9-280501c64889

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 3133379

Macroscope's review found this PR approvable — Removes conditional showSendWhileRunning prop to always display the send button during active turns when there's sendable content. This is a minor, self-contained UI simplification that removes more code than it adds.

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

[obinnanwachukwu1]

Problem

The desktop composer hides Send for the entire duration of an active turn, even after the user types a follow-up. Enter already submits that follow-up as a steer, but the equivalent visible action was limited to mobile viewports.

Fix

The shared composer primary actions now show:

• Stop while a turn is running and the composer is empty;
• Stop and Send while a turn is running and the composer has sendable content.

This removes the viewport-specific showSendWhileRunning path and gives desktop and responsive web the same behavior. Stop remains available, so this does not change interrupt or Queue/Steer semantics.

UI changes

Before	After

Verification

• vp test run apps/web/src/components/chat/ComposerPrimaryActions.test.tsx — 15 tests passed
• vp run --filter @t3tools/web typecheck
• targeted lint
• targeted formatting check
• git diff --check

Closes#7750

Built with GPT-5.6 Sol through the Codex harness in T3 Code.

Note

Always show send button during active turns when composer has content

• Removes the showSendWhileRunning prop from ComposerPrimaryActions and ComposerFooterPrimaryActions, and stops forwarding it from ChatComposer.
• 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 — no longer gated by mobile viewport or Enter-to-send availability.
• Updates ComposerPrimaryActions tests to match the new behavior and removes the test that tied send visibility to Enter-to-send.
• Behavioral Change: send button is now visible on all viewports during active turns when content is present, not just mobile; reviewers should check ComposerPrimaryActions.tsx and ChatComposer.tsx for any remaining references to the removed prop.

^{Macroscope summarized 3133379.}

---

Note

Low Risk
UI-only composer action visibility; interrupt and send semantics are unchanged.

Overview
During an active turn, the composer now shows Stop + Send whenever there is sendable content, on desktop as well as mobile. An empty composer still shows only Stop.

This drops the viewport-gated showSendWhileRunning flag. Enter-to-send already steered follow-ups on desktop; the visible Send button now matches that.

^{Reviewed by Cursor Bugbot for commit 3133379. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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: 16b71c98-1965-4a38-99f9-280501c64889

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 3133379

Macroscope's review found this PR approvable — Removes conditional showSendWhileRunning prop to always display the send button during active turns when there's sendable content. This is a minor, self-contained UI simplification that removes more code than it adds.

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

[obinnanwachukwu1]

Problem

The desktop composer hides Send for the entire duration of an active turn, even after the user types a follow-up. Enter already submits that follow-up as a steer, but the equivalent visible action was limited to mobile viewports.

Fix

The shared composer primary actions now show:

• Stop while a turn is running and the composer is empty;
• Stop and Send while a turn is running and the composer has sendable content.

This removes the viewport-specific showSendWhileRunning path and gives desktop and responsive web the same behavior. Stop remains available, so this does not change interrupt or Queue/Steer semantics.

UI changes

Before	After

Verification

• vp test run apps/web/src/components/chat/ComposerPrimaryActions.test.tsx — 15 tests passed
• vp run --filter @t3tools/web typecheck
• targeted lint
• targeted formatting check
• git diff --check

Closes#7750

Built with GPT-5.6 Sol through the Codex harness in T3 Code.

Note

Always show send button during active turns when composer has content

• Removes the showSendWhileRunning prop from ComposerPrimaryActions and ComposerFooterPrimaryActions, and stops forwarding it from ChatComposer.
• 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 — no longer gated by mobile viewport or Enter-to-send availability.
• Updates ComposerPrimaryActions tests to match the new behavior and removes the test that tied send visibility to Enter-to-send.
• Behavioral Change: send button is now visible on all viewports during active turns when content is present, not just mobile; reviewers should check ComposerPrimaryActions.tsx and ChatComposer.tsx for any remaining references to the removed prop.

^{Macroscope summarized 3133379.}

---

Note

Low Risk
UI-only composer action visibility; interrupt and send semantics are unchanged.

Overview
During an active turn, the composer now shows Stop + Send whenever there is sendable content, on desktop as well as mobile. An empty composer still shows only Stop.

This drops the viewport-gated showSendWhileRunning flag. Enter-to-send already steered follow-ups on desktop; the visible Send button now matches that.

^{Reviewed by Cursor Bugbot for commit 3133379. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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: 16b71c98-1965-4a38-99f9-280501c64889

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 3133379

Macroscope's review found this PR approvable — Removes conditional showSendWhileRunning prop to always display the send button during active turns when there's sendable content. This is a minor, self-contained UI simplification that removes more code than it adds.

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

[obinnanwachukwu1]

Problem

The desktop composer hides Send for the entire duration of an active turn, even after the user types a follow-up. Enter already submits that follow-up as a steer, but the equivalent visible action was limited to mobile viewports.

Fix

The shared composer primary actions now show:

• Stop while a turn is running and the composer is empty;
• Stop and Send while a turn is running and the composer has sendable content.

This removes the viewport-specific showSendWhileRunning path and gives desktop and responsive web the same behavior. Stop remains available, so this does not change interrupt or Queue/Steer semantics.

UI changes

Before	After

Verification

• vp test run apps/web/src/components/chat/ComposerPrimaryActions.test.tsx — 15 tests passed
• vp run --filter @t3tools/web typecheck
• targeted lint
• targeted formatting check
• git diff --check

Closes#7750

Built with GPT-5.6 Sol through the Codex harness in T3 Code.

Note

Always show send button during active turns when composer has content

• Removes the showSendWhileRunning prop from ComposerPrimaryActions and ComposerFooterPrimaryActions, and stops forwarding it from ChatComposer.
• 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 — no longer gated by mobile viewport or Enter-to-send availability.
• Updates ComposerPrimaryActions tests to match the new behavior and removes the test that tied send visibility to Enter-to-send.
• Behavioral Change: send button is now visible on all viewports during active turns when content is present, not just mobile; reviewers should check ComposerPrimaryActions.tsx and ChatComposer.tsx for any remaining references to the removed prop.

^{Macroscope summarized 3133379.}

---

Note

Low Risk
UI-only composer action visibility; interrupt and send semantics are unchanged.

Overview
During an active turn, the composer now shows Stop + Send whenever there is sendable content, on desktop as well as mobile. An empty composer still shows only Stop.

This drops the viewport-gated showSendWhileRunning flag. Enter-to-send already steered follow-ups on desktop; the visible Send button now matches that.

^{Reviewed by Cursor Bugbot for commit 3133379. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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: 16b71c98-1965-4a38-99f9-280501c64889

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 3133379

Macroscope's review found this PR approvable — Removes conditional showSendWhileRunning prop to always display the send button during active turns when there's sendable content. This is a minor, self-contained UI simplification that removes more code than it adds.

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

[obinnanwachukwu1]

Problem

The desktop composer hides Send for the entire duration of an active turn, even after the user types a follow-up. Enter already submits that follow-up as a steer, but the equivalent visible action was limited to mobile viewports.

Fix

The shared composer primary actions now show:

• Stop while a turn is running and the composer is empty;
• Stop and Send while a turn is running and the composer has sendable content.

This removes the viewport-specific showSendWhileRunning path and gives desktop and responsive web the same behavior. Stop remains available, so this does not change interrupt or Queue/Steer semantics.

UI changes

Before	After

Verification

• vp test run apps/web/src/components/chat/ComposerPrimaryActions.test.tsx — 15 tests passed
• vp run --filter @t3tools/web typecheck
• targeted lint
• targeted formatting check
• git diff --check

Closes#7750

Built with GPT-5.6 Sol through the Codex harness in T3 Code.

Note

Always show send button during active turns when composer has content

• Removes the showSendWhileRunning prop from ComposerPrimaryActions and ComposerFooterPrimaryActions, and stops forwarding it from ChatComposer.
• 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 — no longer gated by mobile viewport or Enter-to-send availability.
• Updates ComposerPrimaryActions tests to match the new behavior and removes the test that tied send visibility to Enter-to-send.
• Behavioral Change: send button is now visible on all viewports during active turns when content is present, not just mobile; reviewers should check ComposerPrimaryActions.tsx and ChatComposer.tsx for any remaining references to the removed prop.

^{Macroscope summarized 3133379.}

---

Note

Low Risk
UI-only composer action visibility; interrupt and send semantics are unchanged.

Overview
During an active turn, the composer now shows Stop + Send whenever there is sendable content, on desktop as well as mobile. An empty composer still shows only Stop.

This drops the viewport-gated showSendWhileRunning flag. Enter-to-send already steered follow-ups on desktop; the visible Send button now matches that.

^{Reviewed by Cursor Bugbot for commit 3133379. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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: 16b71c98-1965-4a38-99f9-280501c64889

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 3133379

Macroscope's review found this PR approvable — Removes conditional showSendWhileRunning prop to always display the send button during active turns when there's sendable content. This is a minor, self-contained UI simplification that removes more code than it adds.

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