Companion animations should be opt-in, not opt-out

Status Closed — not planned
Maintainer reply None cached
Activity 2 comments · opened Apr 7, 2026 · closed Apr 9, 2026

Summary

Distracting UI animations (e.g. the Nuzzlix snail companion) are enabled by default and require users to discover and set prefersReducedMotion: true to disable them. This is backwards — animated companions should be opt-in.

Current behavior

  • Animated companions appear by default for all users
  • Disabling requires finding an undocumented settings flag (prefersReducedMotion)
  • The flag name conflates accessibility concerns (reduced motion for vestibular disorders) with a user preference about decorative UI chrome

Expected behavior

  • Animated companions are off by default
  • Users who want them can enable via an explicit, clearly named setting
  • Suggested flag name: enableTackyClippyMode: true (or similar — the point is it should be a deliberate opt-in, not a buried opt-out)

Why this matters

  • Users with ADHD, vestibular disorders, or focus-sensitive workflows are disrupted by unexpected motion
  • prefersReducedMotion is an accessibility setting with a specific meaning — it should not be the only way to turn off decorative animations
  • Opt-in respects user intent; opt-out taxes users who just want a clean workspace

Suggested fix

Add an explicit setting (e.g. companionEnabled: boolean, default false) separate from prefersReducedMotion.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗