What happened
While the agent is working, the Control UI composer footer shows the run status as a bordered pill: a rounded-full chip with a 1px info-blue border, tinted spinner, and blue text (" is responding...", "Sending message...", "Preparing model..."). The pill reads like an alert chip and visually competes with the composer controls next to it. On mobile the same status renders as an even heavier full-width bordered box above the input.
Meanwhile, running tool rows in the chat transcript already use a much quieter "active work" language: a small pulsing dot plus a left-to-right text-color wave. The two surfaces disagree about how "the agent is working" should look.
Current UI
Expected
The working indicator should read as quiet status text, not an alert: no border, no pill background — a small pulsing dot plus the same text shimmer used on running tool rows, so active work looks identical everywhere. Terminal states (Done / Interrupted) keep their icon and semantic color, minus the pill chrome.
What happened
While the agent is working, the Control UI composer footer shows the run status as a bordered pill: a rounded-full chip with a 1px info-blue border, tinted spinner, and blue text (" is responding...", "Sending message...", "Preparing model..."). The pill reads like an alert chip and visually competes with the composer controls next to it. On mobile the same status renders as an even heavier full-width bordered box above the input.
Meanwhile, running tool rows in the chat transcript already use a much quieter "active work" language: a small pulsing dot plus a left-to-right text-color wave. The two surfaces disagree about how "the agent is working" should look.
Current UI
Expected
The working indicator should read as quiet status text, not an alert: no border, no pill background — a small pulsing dot plus the same text shimmer used on running tool rows, so active work looks identical everywhere. Terminal states (Done / Interrupted) keep their icon and semantic color, minus the pill chrome.