Cloud Agents: 500 error on Development Setup Save Environment

Where does the bug appear (feature/product)?

Cursor Cloud Agents (Web UI)

Describe the Bug

I tried Cursor for the first time today. I used Cursor Cloud Agents and the agent was able to understand and set up my environment. Some code changes were needed but it created a GitHub pull request. I followed the “Setup” pane and the next step after “Setting Up Environment” is “Save Environment”. I tried several times but I receive a 500 error when saving the environment. Without getting past this step it seems like all my future agents will not have the environment ready and will recreate it from scratch. Can you please help?

Steps to Reproduce

  1. Sign up for Cursor and open Cloud Agents for first time at https://cursor.com/onboard
  2. Select repo and add secrets then submit to create a “Development environment setup” agent tht sets up the environment.
  3. Wait until the environment is setup successfully.
  4. In the Save Environment step click “Save”
    Actual behaviour: 500 error is returned.
    “Failed to save: 500” is shown in UI.

In the Network tab the https://cursor.com/api/background-composer/snapshot-and-save-environment endpoint returns a 500 with body: {“error”:{“message”:“internal error”,“details”:}}

Expected Behavior

Environment is saved.
I can reuse the environment and easily create more cloud agents.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

I was using Cloud Agents Web Interface but my Cursor IDE version this anyway:

Version: 2.6.22
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z (6 days ago)
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

It stops me using Cursor Cloud Agents

2 Likes

Hi @jlawsh Thanks for reporting this and welcome to Cursor! We’re thrilled to have you onboard.

While we investigate this further, do you want to try setting up the agent’s environment here: https://cursor.com/agents rather than in Cursor App?

Additionally, can you also update your Cursor App? We launched Cursor 3.0 today.

Let me know if neither of these options get you unblocked and we’ll look into this further. Thanks!

Running into a similar issue. Using cursor webapp:

62348-b72c800e1a7459…GQXqiqSejK56gbxTu:1 
 POST https://cursor.com/api/background-composer/snapshot-and-save-environment 500 (Internal Server Error)
list-artifacts:1 
 Failed to load resource: the server responded with a status of 500 ()

I reported the same issue in another thread: Failed to save: 500 when trying to save an environment.

I’m running into the same issue.

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I have a repo for which the environment stopped working. New agents fail with:

We couldn’t start the agent’s computer, please help us set it up again
No personal or team snapshot is currently saved for this repo. Open Setup and save a snapshot, > then retry.

I tried to recreate the environment going through the web flow. The agent to create the environment succeeds but clicking on the button to save the environment errors out with:

Failed to save: 500

Steps to Reproduce

  1. Start the Development Environment Setup flow.
  2. Press “Save to Team” or “Save to Personal”

Expected Behavior

Environment saved without errors and usable by agents.

Operating System

MacOS

Version Information

Cursor Web Agent

Does this stop you from using Cursor

Yes - Cursor is unusable

2 Likes

I am also running into this issue.

I’m experiencing the exact same problem right now with cursor agents

add me to the list! Haven’t been able to save a cloud environment for a couple days now from the web interface.
Failed to save: 500

Same here. These are all recent posts so I’ll wait it out and stop work.

Hi all,

Thank for your patience - we are aware of this issue, and I will update you when it is resolved. I’m sorry for the impact this has on your workflows.

@here We’ve identified and implemented a fix for this today. Please let us know if you are still seeing the same errors.

3 Likes

Works for me! Thanks for the quick turnaround.

1 Like

I can confirm everything is working for me too! Thanks for your help Kevin, and thanks to everyone else on the team.

confirmed fixed