Skip to content

fix: restore UX after performance improvements - #9799

Merged
t3dotgg merged 3 commits into
mainfrom
t3code/investigate-animation-regressions
Sep 5, 2026
Merged

fix: restore UX after performance improvements#9799
t3dotgg merged 3 commits into
mainfrom
t3code/investigate-animation-regressions

fix(ci): fetch Ubuntu packages over HTTPS

a19faa6
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - UI Consistency succeeded Sep 5, 2026 in 2m 49s

UI Consistency: No issues found

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/ui-consistency.md
More information about how Check Run Agents work can be found in our Help Center.

Reviewed in-scope changed files: apps/web/src/components/chat/ComposerActivityStatus.tsx, ComposerServerUpdateStatus.tsx, MessagesTimeline.tsx, ChatMarkdown.tsx, DiffWorkerPoolProvider.tsx, RenderErrorBoundary.tsx, and apps/web/src/index.css.

  • Composer status rows keep composing ComposerBanner slots; only a ref and animation class were added.
  • New global CSS in index.css is keyframes and animation utilities (play-state, mask-based shimmer), which Tailwind cannot express at the owner, so it falls in the allowed animation exception.
  • New ActivityShimmerOverlay in MessagesTimeline.tsx composes local timeline markup with Tailwind classes rather than duplicating a primitive; no raw controls or primitive geometry overrides were introduced.
🔍 Agent activity — 1 tool call

💭 I'm reviewing the changed files in the chat components and checking whether the new CSS additions—animations, keyframes, and gradient masks—fall within the accepted exceptions for global CSS versus Tailwind utilities. I notice ComposerActivityStatus passes a ref to ComposerBanner.Icon, so I want to check whether that component actually forwards refs properly, since that could be a subtle bug worth flagging even if it's outside the core styling review.

1. browse_code — apps/web/src/components/chat/ComposerBanner.tsx

💭 I'm checking that the ComposerBanner icon ref forwarding works fine in React 19, and that the CSS additions—the shimmer utility classes and the animation-play-state variable—are legitimate animation-related styling rather than something to flag. The MessagesTimeline shimmer overlay usage looks consistent with this pattern too. Overall I don't see any findings, so I'll report all clear.

Agent Credits: 45 credits

Token usage: 4 uncached input · 51,746 cache-read input · 59,371 cache-write input · 1,207 output
Agent Credits may also include non-token charges from external tools such as web research.

View more details on MacroscopeApp