# Cloud Agents Broken II **URL:** \ **Category:** Bug Reports\ **Tags:** cloud-agents\ **Created:** [May 19, 2026, 4:54pm UTC](https://forum.cursor.com/t/cloud-agents-broken-ii/161036 "2026-05-19T16:54:37Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![elliottlawson](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/elliottlawson/32/105370_2.png) [@elliottlawson](https://forum.cursor.com/u/elliottlawson)\ **Post date:** [May 19, 2026, 4:54pm UTC](https://forum.cursor.com/t/cloud-agents-broken-ii/161036/1 "2026-05-19T16:54:37Z")
### Where does the bug appear (feature/product)? Background Agent (GitHub, Slack, Web, Linear) ### Describe the Bug Cloud agents are failing to spin up today, they were working just fine yesterday. I started multiple sessions and have been waiting 10+ minutes for them to start. ### Steps to Reproduce Start a conversation with a cloud agent. ### Expected Behavior The conversation with the cloud agent starts ### Operating System MacOS ### Version Information Web ### For AI issues: which model did you use? Composer 2 & 2.5 ### Does this stop you from using Cursor Yes - Cursor is unusable ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [May 19, 2026, 5:59pm UTC](https://forum.cursor.com/t/cloud-agents-broken-ii/161036/4 "2026-05-19T17:59:58Z")
4 posts were merged into an existing topic: [Repeated cloud agent failures, going on 24h](https://forum.cursor.com/t/repeated-cloud-agent-failures-going-on-24h/161038) ---
**Author:** ![elliottlawson](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/elliottlawson/32/105370_2.png) [@elliottlawson](https://forum.cursor.com/u/elliottlawson)\ **Post date:** [May 19, 2026, 5:36pm UTC](https://forum.cursor.com/t/cloud-agents-broken-ii/161036/7 "2026-05-19T17:36:09Z")
Thanks for the update, @deanrie , we can close out as a duplicate. Minor feedback, but the “all systems operational” banner at the top is misleading. It would be nice to have known incidents at the top of the page versus the bottom. ![image](https://us1.discourse-cdn.com/cursor1/original/3X/e/6/e681c5f328cec1e4295272e96fe844fbd85b84e9.png) ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [May 19, 2026, 5:58pm UTC](https://forum.cursor.com/t/cloud-agents-broken-ii/161036/8 "2026-05-19T17:58:02Z")
Thanks for the feedback on the status page, that’s fair. Having the green All Systems Operational at the top while there’s an active incident below does look contradictory. I’ll pass this on to the team that owns the page. You can track progress for the incident here: [Cursor Status - Degraded behavior in cloud agents and automations.](https://status.cursor.com/incidents/7ps07tjsr5z5) ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [May 19, 2026, 6:00pm UTC](https://forum.cursor.com/t/cloud-agents-broken-ii/161036/9 "2026-05-19T18:00:05Z")