Skip to content

feat: adjust order of agent status and text box#2447

Open
alexhancock wants to merge 2 commits into
block:mainfrom
alexhancock:flip-composer-status-order
Open

feat: adjust order of agent status and text box#2447
alexhancock wants to merge 2 commits into
block:mainfrom
alexhancock:flip-composer-status-order

Conversation

@alexhancock

@alexhancock alexhancock commented Jul 23, 2026

Copy link
Copy Markdown

I noticed a UI issue where the text entry box doesn't have consistent padding vertically and horizontally because the agent status bar (which is only active sometimes) sits below it. This makes the text box further away from the bottom than it is from the sides when the agent isn't doing anything and looked a bit off to me.

This change flips it so the agent status bar is above the text entry box, and the text entry box can sit in a more natural spot. It also subtly moves the messages up when the agent status bar is there so that they don't run under the status bar.

Before

Screenshot 2026-07-22 at 8 43 25 PM

After

Screenshot 2026-07-22 at 8 49 38 PM

Agent Active State

Screenshot 2026-07-22 at 8 49 48 PM

@alexhancock
alexhancock requested a review from a team as a code owner July 23, 2026 00:59
…rder

The composer status/activity row moved above the text box, so:

- The corner-mask CSS was pinned at bottom:2.5rem, calibrated for the
  old layout (composer pb-2 + 32px activity row below). With the row now
  above the composer and the composer padded to pb-5 (1.25rem), the masks
  no longer aligned to the composer's bottom edge, breaking the
  channel-composer-overflow overlay-mask tests. Repin to 1.25rem.

- The activity row is now conditionally rendered (only on bot/typing
  activity). The date-divider test navigates to a channel with no such
  activity, so its incidental activity-row style assertions failed with
  element-not-found. Drop those assertions; they are unrelated to the
  date-divider behavior under test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant