Hi @Muhammed_Altinci I’m sorry for the inconvenience here. This is a known class of bug and we have linked your report to it.
This may be happening because your repo has a .cursor/environment.json file that points Cloud Agents to an old or expired environment snapshot. That file takes priority over the team environment saved in setup, so saving a fresh team environment may keep failing until the file is removed or updated.
Please try this workaround:
Open your repository locally.
Check whether .cursor/environment.json exists.
If your team is not intentionally using this file for a custom Cloud Agent setup, delete it.
If your team does need this file, edit it and remove the stale snapshot reference instead.
Push that change to the branch Cloud Agents is using.
Go back to Cloud Agent setup and run setup again.
Once setup completes, click Save to team again.
After the stale .cursor/environment.json reference is removed, Cloud Agents should use the newly saved team environment instead of the expired snapshot.
