Something (cursor security reviewer automation?) seem to suddenly be creating a team environment, which breaks the whole team’s usage of cloud agents since we have to use personal environments (team environments have been broken for us for months).
Deleting the team environment makes the personal environments usable again for a few minutes until the team environment is automatically created again, breaking the whole team again
Steps to Reproduce
I have no idea. My guess is that the security reviewer automation is creating the team env but that’s just a guess. Nothing in our security reviewer instructs this.
Expected Behavior
Stop creating team environments automatically since they break personal environments.
hi, could you please clarify what you mean by team environments broken / what’s the broken behavior?
any links or details you can provide would be very helpful, e.g. to the specific environments and agents that are broken when running on the team environment
@nbradford I’d like to focus on unblocking the team by at least figuring out what is creating the team env automatically, since this prevents team members from being able to use personal environnments. I’m happy to create a separate thread to debug our team environment issues, but the presence of a team env is disruptive since it automatically takes precedence.
I understand that, can you please share links and details? Investigating the other part is already underway. This will greatly speed up debugging.
Association of all cloud agents with an environment is intended behavior - if team environments are not working, we need to solve that.
The team environment is not supposed to be taking precedence, and , so understanding why you are not getting the personal environment we also need to solve.
Understanding exactly what is happening will help us determine if unblock you fastest
Thanks, see prev message regarding team envs not working.
What links would you like me to provide to assist with the second point? Link to personal envs? Link to the broken team env? Link to the broken automation runs that are trying to use the team envs?
Yes, all of the above (URLs are fine) and especially a description of what you mean by the team environment being broken / what you see in the UI - does the cloud agent run at all?
(the error above can be ignored - it is expected, just means the client is still polling waiting for the VM to start)
so, it appears my own cloud agents (launched via the agents window in cursor) do correctly use my personal env (this is new), so that particular usage works
that leaves our automations, which all appear to default to the broken team env – here are some run links:
both fail with:
Agent failed to start The background agent could not be launched. Verify the prompt, target repository, and branch configuration are valid.
thanks! i have opted you out of the “automatically create environment” behavior in the meantime while we root cause, can you confirm if once you delete the auto-environment again your automations start working?
(apologies for the regression - i helped implement this feature, will figure out a fix)
Thanks! It seems to be working so far, but out of curiosity, is there a way for individual team members to use their personal envs even when a team env is provisioned?
@Shawn_Jones I’m seeing on my end that actually the personal envs for that repo are still being used over the team environment as expected! Personal env will take precedence, so someone without a personal env will use the team env.
You can also now do things like create named personal or team copies of the same repo/environment and configure them differently, call it “Shawn’s environment” etc.
Let me know if you have any trouble with this or if it is behaving unexpectedly! And if something is wrong please include a link to the cloud agent(s), thanks!
Hmm, I had a personal env with specific skills installed, and when we created a new team env (without those personal skills installed), I was unable to access them unless I stuck them into our team env’s install scripts…
On skills - my understanding is that environments do not carry skills, it is just your repo and plugins in cloud. So there should not be a difference in skill availability between the two. Just configured secrets, env vars, etc.
