You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: Keep chat activity headers on one line with a clear disclosure caret #36591
When an agent's activity run contains one long command, the folded run header shows that command and wraps it onto a second line. This happens on desktop (line-clamp-2) and on the phone (numberOfLines={2}). Narrow windows and phones are affected most.
The desktop run header also has no expansion caret, so it is not obvious that it opens. The individual tool rows inside a run already show a caret on both desktop and phone; the run header itself has none on either platform.
Suggested priority: P3 / usability improvement, subject to maintainer triage. No execution or approval behavior change is requested.
Proposed solution
Keep the folded run header's summary on one line on desktop and phone, ending long text with an ellipsis. Add the desktop run-header caret using the existing icon, spacing, focus and reduced-motion styles of the tool rows.
Acceptance:
A long label stays on one row in a narrow window without covering adjacent controls.
Keyboard and tap disclosure, and aria-expanded, keep working.
The desktop caret follows the open state and respects reduced motion.
Opening the run still makes the full command readable. A command shorter than the 80-character summary limit but wider than the row must not become unreadable in both the folded and the opened state.
Alternatives or additional context
This presentational story was previously mixed into #33363. It is independent of successful-review grouping (#36590) and of the completed permission notices already shipped by #36304, and should be reviewed and merged on its own. Showing a tool call's complete input when its row opens is a separate proposal (#36633 / #36634).
Activity