Cloud Agent Development Environment with 5 repos saves successfully, but the environment does not appear in the dashboard and duplicate-name error occurs

Support Bug Reports
1

Where does the bug appear (feature/product)?
Cloud Agents

Describe the Bug
I have a Cloud Agent Development Environment with multiple repositories. I can save it successfully, but it shows a save confirmation and I still do not see it in the dashboard. If I try to create it again, I get a message that an environment with the same name already exists, even though I cannot see the environment anywhere.

It seems like the environment exists somewhere behind the scenes, but it is not visible in the dashboard. That makes it impossible for me to manage, edit, or delete it.

Steps to Reproduce

  1. Create a Cloud Agent Development Environment with multiple repositories.
  2. Save the environment.
  3. Wait for the confirmation that it has been saved.
  4. Check the dashboard.
  5. Notice that the environment does not appear.
  6. Try to create the environment again with the same name.
  7. Receive an error that an environment with the same name already exists.

Expected Behavior
The saved environment should appear in the dashboard so it can be managed, edited, or deleted. If an environment with the same name already exists, it should be visible there.

Additional Information
The system indicates that an environment with this name already exists, which suggests there is a hidden or duplicated backend entry. This makes it impossible for me to manage the environment properly.

Does this stop you from using Cursor?
Sometimes - I can sometimes use Cursor

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

7

Hey there!

This is a known bug on our side, and your environment did save. That “an environment with the same name already exists” message is actually the proof it saved, so nothing is lost. It’s a dashboard visibility issue where some multi-repo environments save correctly but don’t show up in the list, which is why you can’t manage or delete it from there.

To get you unblocked now:

  1. Recreate it with a different, unique name you haven’t used before. That avoids the clash with the hidden one and should give you a manageable environment in the dashboard.
  2. When you start a new agent, check the environment picker too — the saved environment is often still selectable and usable there even when the dashboard doesn’t list it.

I’ve logged your report alongside the others we’ve seen. Let me know if the different-name approach gets you sorted!