What problem does it solve? After publishing an EAS Update, teams lack a quick terminal-based way to verify rollout health, forcing them to open the Expo dashboard to check crash rates, adoption counts, and whether users are on the embedded build or an OTA update. ## Core Features & Use Cases - Update health checks: Run eas update:insights <groupId> to get per-platform launches, failed installs, crash rate, unique users, payload size, and a daily time series. - Channel-level adoption: Run eas channel:insights to compare embedded-build users versus OTA users and rank the most popular updates for a channel and runtime version. - CI gating and regression detection: All commands support --json --non-interactive output for scripting, such as failing a pipeline when crash rate exceeds a threshold. - Use Case: After publishing a fix to the production branch, grab the latest group ID with eas update:list, then check crashRatePercent per platform to confirm the rollout is healthy before widening it. ## Quick Start Ask the assistant to check whether the latest update published to the production branch is healthy, including its crash rate and user adoption.