What task are you trying to do?
When a tool group is still active in the conversation stream, users should see a subtle progress cue in the trow summary text without adding visual noise or hurting runtime performance.
Which area would this change affect?
UI or design system
What do you do today?
PR #874 groups consecutive tool calls into compact trow summaries. The existing TextShimmer component and CSS are still available, but the new trow summary row currently renders plain text with a lightweight fade-in only. This makes active summary changes feel a bit abrupt compared with older tool status titles.
What would a good result look like?
Active trow summaries reuse the existing TextShimmer behavior, or an equally lightweight shared path, so the current active tool/group feels alive while work is still running. The motion should remain subtle, respect reduced-motion preferences, and avoid reintroducing the performance pressure that motivated the trow work.
What would count as done?
- Active trow summary text has a subtle shimmer/progress treatment while the group is running.
- Completed trow summaries render as stable text with no ongoing shimmer.
- The implementation reuses the existing TextShimmer contract where practical instead of adding a second shimmer system.
- Reduced-motion behavior remains respected.
- A focused visual snap or e2e check covers the running trow summary state.
- Perf probe remains green, especially the tool-call-expand and concurrent-shimmer-related scenarios.
What should stay out of scope?
Which audience does this matter to most?
Both
Extra context
Follow-up from PR #874. The current trow CSS exposes a running-state hook, but the summary text is not actually wired to TextShimmer. Keep this as a separate enhancement because the performance impact should be measured independently.
What task are you trying to do?
When a tool group is still active in the conversation stream, users should see a subtle progress cue in the trow summary text without adding visual noise or hurting runtime performance.
Which area would this change affect?
UI or design system
What do you do today?
PR #874 groups consecutive tool calls into compact trow summaries. The existing TextShimmer component and CSS are still available, but the new trow summary row currently renders plain text with a lightweight fade-in only. This makes active summary changes feel a bit abrupt compared with older tool status titles.
What would a good result look like?
Active trow summaries reuse the existing TextShimmer behavior, or an equally lightweight shared path, so the current active tool/group feels alive while work is still running. The motion should remain subtle, respect reduced-motion preferences, and avoid reintroducing the performance pressure that motivated the trow work.
What would count as done?
What should stay out of scope?
Which audience does this matter to most?
Both
Extra context
Follow-up from PR #874. The current trow CSS exposes a running-state hook, but the summary text is not actually wired to TextShimmer. Keep this as a separate enhancement because the performance impact should be measured independently.