Where does the bug appear (feature/product)?
Cloud Agents & Automations (cursor.com/agents, scheduled/event)
Describe the Bug
I have two environments configured as team environments in Cursor Cloud, but neither of them appears in the environment picker at the top level, just above the text input where you start a new agent. Because they never show up in that picker, there’s no way to select which environment an agent should run in. The most recently created environment is always selected by default, with no option to switch to the other one.
The same problem appears when setting up an Automation (scheduled/event agent): the team environments don’t show in the environment picker there either, so we can’t choose which environment automated runs use.
Separately, there’s no way for a team to set a preferred default team environment — the default is just whichever environment was created most recently, rather than one we explicitly chose.
Steps to Reproduce
- Set up two environments as team environments in Cursor Cloud.
- Go to start a new agent and open the environment picker just above the text input.
- Notice that the team environments do not appear in the picker, so neither can be selected. The most recently created environment is selected by default with no way to change it.
Expected Behavior
Both team environments should appear in the new-agent environment picker so I can select which one to use. Additionally, teams should be able to explicitly choose a default team environment, rather than the default always being the most recently created one.
Screenshots / Screen Recordings
Operating System
MacOS
Version Information
Latest cursor cloud version
For AI issues: which model did you use?
N/A — this is an environment/UI issue, not a model issue.
For AI issues: add Request ID with privacy disabled
N/A
For Background Agent issues, also post the ID:
N/A
Additional Information
This affects team environments specifically. The environments are correctly configured as team environments but are simply absent from the environment picker when starting a new agent. This blocks our team’s workflow: we need multiple environments and the ability to choose which one an agent runs in, and right now we can’t — every agent is forced onto whichever environment was created most recently.
Does this stop you from using Cursor?
Yes - Cursor is unusable (for our team’s Cloud agent workflow — we can’t run agents in the correct environment because team environments can’t be selected).