Almost, but deleting isn’t the only option. There are three ways to bring a 5-repo environment up to the current config:
- Edit it in the dashboard: open the environment and point its config to
.cursor/environment.jsonfrom the main repo. It’ll update in place, no need to delete it. After that, runs viarepos[]will reuse the already updated config. - Rename it and select by name: give the environment a name via ⋯ > Rename, then run with
env: { "type": "cloud", "name": "<name>" }and withoutrepos. This is the most predictable option for programmatic control because you explicitly choose which environment to use. - Delete and recreate: also works. Delete it in the dashboard, and the next multi-repo run will recreate the environment and pick up
.cursor/environment.jsonsince the file is now on the default branch.
So your understanding is correct, but full deletion is just one option. Editing the config in the dashboard achieves the same result without recreating anything.
On the second part, managing environments from the SDK right now (create with a name, delete, force refresh) isn’t available. It’s web UI only. This is a real gap and I’ve forwarded it as a request. I can’t share an ETA, but similar requests are already tracked here if you want to add a vote or details:
- Cloud Agent Environments – Ability to edit repo list after creation
- Please allow local agents to manage and update automations and cloud agent environments
Let me know how the environment update goes.