fix(gpui): follow the macOS Reduce Motion setting

[richiemcilroy]

GPUI keeps its own Reduce Motion flag (App::reduce_motion, false at startup) and never reads the OS setting, and nothing in Cap called set_reduce_motion. So every animation that checks the flag ignored macOS's Accessibility > Display > Reduce motion: with_animation everywhere, the camera window's loading glass, and the onboarding welcome screen (found by Capy on #2713).

On macOS the app now reads NSWorkspace.accessibilityDisplayShouldReduceMotion at startup and updates the flag whenever NSWorkspaceAccessibilityDisplayOptionsDidChangeNotification fires, through a main-queue observer that lives for the app. Windows and Linux are unchanged (no-op).

Effect

With Reduce motion on, GPUI animations render their final frame (GPUI's built-in behaviour for the flag) and Cap's own checks (camera_loading, camera_window, the welcome screen) switch to their reduced paths. With it off (the default), nothing changes.

Testing

• Startup read logged on macOS 26 with the setting off: system reduce motion reduce=false.
• Not yet exercised: toggling the setting while Cap runs (needs the real System Settings switch).
• Clippy clean.

Confidence Score: 5/5

The PR appears safe to merge; no actionable defects were found.

Summary

The PR makes Cap follow the macOS Reduce Motion setting.

• The desktop app's animations now follow macOS Reduce Motion.

No actionable issues were found. Live toggling was not verified during this review.

_{Reviews (2) · Last reviewed commit: "fix(gpui): follow the macOS Reduce Motio..." · Reviewed by Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
cap-status	Ready	Preview	Oct 19, 2026 5:39pm UTC

[richiemcilroy]

@greptileai review

[capy-ai]

Capy found no issues.

View 1 other finding in Capy.