Where does the bug appear (feature/product)? Background Agent (GitHub, Slack, Web, Linear) Describe the Bug I believe this is more of an incident, rather than a bug; but there isn’t a place to report incidents. Also, Cloudflare is having several maintenances right now ( https://www.cloudflarestatu…

Hi @dny_ex , I’ve reviewed this thread from the beginning with fresh eyes. I owe you an honest answer. After a thorough review, we’ve determined that the api3.cursor.sh error you originally identified – while real – is not connected to Cloud Agents. That endpoint handles other background services. …

Any updates? 3 months without being able to use Cloud Agents.

Hey, sorry for the delay. I see you’ve updated to v2.3.29 and the issue is still there. Thanks for the console video, it helps show the full picture. The bug is already in the backlog. Your curl shows Cloudflare connects, but can’t route to the backend. It’s weird that you’re the only one reporting…

It’s been almost 4 months since I got banned from using Cloud Agents. You’re not gonna solve this, right? Even though I’m paying $500 per month.

I really need a solution here. Worktree agents are failing, Cloud agents are failing…. [image]

[image] Worktree agents forks automatically into separate workspaces Bug Reports Other report: Agent stuck in "Planning...", "Generating..." - #21 by Vidar_Halvorsen

Any updates on this? 4 months and a half without access to Cloud Agents.

Any update on this? 5 months without Cloud Agents and 1 month without Worktree agents: Worktree agents fork automatically into separate workspaces - #18 by dny_ex

Any update on this? 5 months and a half without Cloud Agents and 1 month and a half without Worktree agents: Worktree agents fork automatically into separate workspaces - #18 by dny_ex

You’re really not going to answer and this thread will be open for a year?

I tell you one of the answers that I gave Dean months ago: How me updating Cursor has anything to do with getting a 404 when doing a curl request to https://api3.cursor.sh ? ➜ curl -v https://api3.cursor.sh Host api3.cursor.sh:443 was resolved. IPv6: (none) IPv4: 104.18.18.125, 104.18.19.125 T…

Cloud agent can't connect via api3.cursor.sh

Support Bug Reports

dny_ex June 9, 2026, 9:12am 43

I ended up updating and that fixed the problem.

Thanks for your help man.

Topic		Replies	Views
Agent Execution Time Out Bug Reports performance , crashes	39	960	June 8, 2026
Worktree agents fork automatically into separate workspaces Bug Reports worktrees , subagents	14	241	April 5, 2026
AI features completely unusable (Stuck, Timeouts) - Quota being consumed for nothing Bug Reports chat , performance , windows	4	208	March 29, 2026
Cloud Agent run cannot see enabled Team MCP servers (Server "notion" not found) Bug Reports mcp , teams-enterprise , cloud-agents , linear-linked	10	234	June 4, 2026
Stopped Chats Continue to Use Tokens and Try to Access Resources Bug Reports chat , terminal , browser , plan-mode	19	306	May 26, 2026

Cloud agent can't connect via api3.cursor.sh

Related topics