Cursor’s status move calls for a check of your alert channels

A quiet alert channel can mean nothing happened. It can also mean the channel no longer receives updates. That distinction matters if Cursor is part of the work you have promised to deliver.

Cursor’s October 19 migration notice set October 26 for status information to move to status.x.ai. The old status homepage now redirects there. This is a newly effective notification change, not a new model release or an outage report. Official notice.

Check the destination you actually rely on

The notice says email subscriptions move automatically. Slack users are directed to subscribe to the new feed, and RSS readers should use https://status.x.ai/feed.xml. It says SMS, Microsoft Teams and webhooks stop on October 26, offering email or RSS instead.

A personal inbox and a team automation solve different problems. In an illustrative setup, a webhook might create an incident task while email merely tells one person. Replacing the webhook with that person’s inbox would leave a gap even if the email arrives correctly. Review where the old alert went and what it triggered before choosing a replacement.

The retained notice is still marked “scheduled.” We observed the homepage redirect but did not test a replacement subscription, feed or alert delivery. Treat the documented channel changes as a reason to check your setup, rather than proof that a particular alert has or has not been sent.

Start by finding your existing status subscription or integration. Keep a suitable route to the current status board available when a task stalls. The local-agent remote-control article covers a separate Cursor workflow change; our AI workflow risk guide helps distinguish a working process from an assumed one.