Cloud agent reports error after initialization without additional information

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I set up environment.json to use my Dockerfile to build an image based on a base I provide. The environment seems to boot up correctly, but after the Loaded snapshot step, it fails with the following message:

“Agent encountered an error
We encountered an unexpected error repeatedly.
You can retry by writing a follow-up below.”

No messages after that point work. It doesn’t seem like sending a message will restart the boot sequence, but it fails again in an identical manner.

Steps to Reproduce

Start a new agent session with “the local server and login,” using the spara-ai/spara-app repo, the adam/cursor-cloud-agents branch and Opus 4.7.

Expected Behavior

The environment should finish booting correctly.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Using Cursor Cloud Agents

Additional Information

Cloud Agent ID: bc-aaa97cc9-b715-415e-ad8c-155d44cc02c5

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. The bcId and repro steps really helped us debug this.

Confirmed bug: the agent correctly brings up the environment and loads the snapshot, but the kickoff message gets dropped before the conversation loop starts, so StreamConversation keeps failing with Missing request message. This isn’t related to your custom Dockerfile or environment.json. It’s an issue with how a web-created agent sends the first message.

We’re already tracking this internally. No exact ETA yet. We’ll post an update in the thread once we have a fix.

As a workaround, try launching the agent from the IDE using Agents window, Cmd+E on the same branch and repo. That uses a different kickoff code path and usually works. Let me know if it helps.

Thanks for the very quick response here! I’ll keep an eye on this thread.

As a workaround, try launching the agent from the IDE using Agents window, Cmd+E on the same branch and repo. That uses a different kickoff code path and usually works. Let me know if it helps.

As an fyi, I followed those exact steps with the same prompt in the IDE and still received an error: “We encountered an unexpected error repeatedly.”

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi Cursor team,
My Background Agent repeatedly fails with:
“Agent encountered an error.
We encountered an unexpected error repeatedly.
You can retry by writing a follow-up below.”
I cannot see “Copy Request ID” in the run UI.
Account email: [email protected]
Repository: bronkocrm/crm
Branch: main
Run URL: https://cursor.com/agents/bc-562898ae-f8f6-4fc6-907c-bba9027cc061
Time (UTC): 2026-05-01 14:38:13 UTC
What I already tried:

  • Retried multiple times
  • Started brand-new agents (not resume)
  • Reconnected GitHub integration
  • Reinstalled/checked GitHub app permissions
  • Tested from other network/VPN
  • Verified git/ssh access
    Please investigate backend logs for this account/repo/time and reset/reclone any stuck cloud-agent environment/cache if needed.
    This is blocking production work.
    I can provide screenshots and additional logs immediately.

Steps to Reproduce

My Background Agent repeatedly fails with:
“Agent encountered an error.
We encountered an unexpected error repeatedly.
What I already tried:

  • Retried multiple times
  • Started brand-new agents (not resume)
  • Reconnected GitHub integration
  • Reinstalled/checked GitHub app permissions
  • Tested from other network/VPN
  • Verified git/ssh access

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Web version (cursor com /agents/), no Desktop IDE/CLI version

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi, not sure if related to this thread, https://cursor.com/agents/bc-20c598cf-d5f9-5bd1-a5ab-870d164f7349

can anyone on cursor’s team take a look. the error message doesn’t give actionable thing on our side to point where to fix