May 19, 2026
Cloudy with a chance of meltdowns
Cursor Cloud Agents Down
Users fume as Cursor’s helpers ghost them and the status page says all is fine
TLDR: Cursor’s cloud helpers failed to start for some users, leaving the tool effectively unusable while people waited and refreshed. The community reaction split between annoyed users calling it unreliable and skeptics asking why the outage was big enough to be news at all.
Cursor users showed up expecting their cloud helpers to jump into action, and instead got the digital equivalent of being left on read. The reported problem was simple but brutal: people started a session, waited more than 10 minutes, and nothing happened. For some, that meant the app was basically unusable. The extra salt in the wound? A user pointed out that the site banner still said “all systems operational,” which made the outage feel less like a glitch and more like a bad joke.
And the comments? Pure mini-drama. One user, mopatches, summed up the mood with the ultra-dry complaint: “On/off for 24h.” That short line says a lot: frustration, exhaustion, and the sense that this wasn’t some cute little hiccup. Meanwhile, swyx came in with a totally different kind of spice, basically asking why this even belonged on Hacker News, the tech-focused discussion site often called HN. So now there were two fights at once: one over the outage itself, and another over whether the outage was even important enough to discuss.
That clash gave the whole thing a weirdly entertaining energy. Some people were annoyed that their tool stopped working; others seemed almost more offended by the post existing at all. The result: a classic tech-community pile-on where the app crashed, the status page got side-eyed, and the comments turned into the real show.
Key Points
- •The reported bug affects Cursor's Background Agent feature.
- •Cloud agents were reported as failing to start, with multiple sessions waiting more than 10 minutes.
- •The expected action was that starting a conversation with a cloud agent would begin normally.
- •The issue was reported in a MacOS and web environment using Composer 2 and Composer 2.5.
- •The reporter said the problem made Cursor unusable, and a follow-up note said the issue could be closed as a duplicate.