Where does the bug appear (feature/product)?
Background Agent (GitHub, Slack, Web, Linear)
Describe the Bug
My self-hosted cloud agents results in error when spawning.
Waiting for self-hosted worker (attempt 3/3)
Agent encountered an error
The worker is identified inside the dashboard.
We encountered an unexpected error repeatedly.
You can retry by writing a follow-up below.
Steps to Reproduce
Try to spawn a self-hosted cloud agents in kubernetes infraestructure.
Expected Behavior
It should work and I would see the session going on.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
WEB - version
Does this stop you from using Cursor
Yes - Cursor is unusable
Colin
(Colin)
April 13, 2026, 5:58pm
5
Hi @Daniel_Weil !
This seems to match a known bug. Take a look at @mohitjain ’s post over here.
Hey @kzab2
Thanks for the thorough report, especially the API vs web UI comparison and the exhaustive testing across multiple EC2 instances.
This is a confirmed bug on our side. Other users have also reported the same behavior in this thread and this earlier thread . Our team is aware and actively investigating a fix.
The issue is that the backend retains a reference to a previous worker identity, and when it tries to dispatch a task, it looks for that old identity instead of the currently-con…
If those wrkarounds don’t work for you, a bug report has been raised, and we can update you when there’s a fix.
Hey @Daniel_Weil ,
The stale worker reference issue that was preventing task dispatch to self-hosted workers has been fixed on our end. Your K8s workers should now correctly receive tasks from the web UI. Let me know if you’re still running into this!