Outage alerts · Cursor status
Cursor status alerts in Slack
When Cursor's agent or completions stall, engineers lose time checking their own setup first. AI Drops posts Cursor incidents to Slack as soon as the status page reports them.
What gets posted
- Incident opened
- Threaded updates
- Resolution
Example message
AI Drops in #ai-status
Incident
Cursor: slow tab completions
Investigating increased latency on completions. Agent requests unaffected.
How to set it up
- 01
Get early access
Tell us about your team on the onboarding page. We email you when you can add AI Drops to Slack and approve the scopes.
- 02
Pick a channel for Cursor status
Choose an existing channel, for example #ai-status. For a private channel, invite the app first.
- 03
Follow the Cursor status feed
Turn on the status feed and choose which components and severities to post.
- 04
Wait for the first drop
The next incident posts automatically.
Want to read the history first? See the Cursor changelog on getaidrops.com. Compare plans.
Questions
+Can I combine all AI status alerts in one channel?
Yes. Many teams use one #ai-status channel for Claude, OpenAI and Cursor.
Other feeds
- Claude Code updates in Slack
- Claude updates in Slack
- ChatGPT updates in Slack
- Codex releases in Slack
- OpenAI API changelog in Slack
- Cursor changelog in Slack
- Claude status alerts in Slack
- OpenAI status alerts in Slack
- Gemini CLI releases in Slack
- Gemini API updates in Slack
- GitHub Copilot updates in Slack
- Windsurf changelog in Slack