fix(chat): align floating chat send button colors with home/mothership chat

[waleedlatif1]

Summary

• Fixed floating chat send/stop button colors to match home and mothership chat
• Replaced CSS variable-based colors (which produced wrong results after recent styling changes) with the same hardcoded hex values used by the home chat constants
• Added variant='ghost' to both buttons to prevent the default Button variant's background and border from bleeding through and conflicting with custom color classes

Type of Change

• Bug fix

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 1, 2026 1:07am

[cursor]

PR Summary

Low Risk
Low risk UI-only change: updates Button variants and hardcoded colors for the floating chat send/stop controls, with no behavioral or data-flow changes.

Overview
Updates the floating chat input’s send and stop streaming buttons to match the home/mothership chat styling.

This switches the buttons to variant='ghost' and replaces prior CSS-variable-based backgrounds/borders with specific hex color classes (including distinct disabled-state coloring) to prevent default Button styling from bleeding through.

^{Written by Cursor Bugbot for commit 387693a. Configure here.}

[greptile-apps]

Greptile Summary

This PR fixes the floating chat panel's send/stop button colors to match the home and mothership chat by replacing CSS variable-based color values with the same hardcoded hex values used in app/chat/components/input/input.tsx, and adds variant='ghost' to both Button components to remove the default variant's background and border styles.

Changes:

• Stop-streaming button: replaced var(--text-primary) / var(--border-1) / var(--text-secondary) / var(--text-body) with #383838 / #E0E0E0 / #575757 / #CFCFCF and added variant='ghost'
• Send button: same hex color replacement, removed redundant border-0 class (no longer needed with variant='ghost'), and added variant='ghost'
• The ghost variant in the Button CVA provides no border and no background, allowing the explicit bg-[#…] classes to render cleanly without interference from the default variant's border border-[var(--border)] styles

Confidence Score: 5/5

This PR is safe to merge — it is a minimal, targeted visual bug fix with no logic changes.

The change is a straightforward color alignment: same hardcoded hex values already proven correct in the home chat are applied here, and adding variant='ghost' correctly removes the conflicting default Button border/background. No logic, state, or data flow is affected. All remaining observations are P2 or cosmetic.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/chat/chat.tsx	Send and stop button colors updated from CSS variables to hardcoded hex values matching home chat; variant='ghost' added to both buttons to prevent default Button styling from interfering

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Floating Chat Buttons] --> B{isStreaming?}
    B -- Yes --> C[Stop Button
variant=ghost
bg-383838 / dark:bg-E0E0E0
hover:bg-575757 / dark:hover:bg-CFCFCF]
    B -- No --> D{Has input?}
    D -- Yes --> E[Send Button - Active
variant=ghost
bg-383838 / dark:bg-E0E0E0
hover:bg-575757 / dark:hover:bg-CFCFCF]
    D -- No --> F[Send Button - Disabled
variant=ghost
bg-808080 / dark:bg-808080]

Loading

_{Reviews (1): Last reviewed commit: "fix(chat): align floating chat send butt..." | Re-trigger Greptile}