The environment creation wizard for the old “Cursor Web” used to end up creating a VM snapshot and offering the option to save it to the repo, so that one could version the snapshot being used and/or other Cursor users on the same repo would use the same. Furthermore environment.json supported install/start script invocation. This worked independently of Teams accounts.
The new “Cursor Cloud” (aka with Desktop and Terminal tabs) has a new configuration wizards which doesn’t offer this option at all. It seems the snapshot created can only be saved at user account level.
Thats a big step back for us. We relied on all of the functionalities of environment.json, but cannot feed it with new snapshots now, since the old wizard seems to be gone.
Am I missing anything? Was environment.json really deprecated? How are we supposed to version and share environments now?
Hey, environment.json isn’t deprecated. It’s still fully supported and documented.
The environment resolution order works like this:
.cursor/environment.json in the repo (highest priority)
Personal environment configuration
Team environment configuration
So repo-level config takes precedence over anything set through the UI wizard.
The new wizard creates a snapshot at the user or team level, but you can still create and maintain .cursor/environment.json manually in your repo to version and share the environment across team members. It supports dockerfile, install, and terminals config. Full spec is here: https://www.cursor.com/schemas/environment.schema.json
Suggested workflow: use the wizard to create a snapshot, then reference the desired config in .cursor/environment.json committed to your repo. That way everyone on the team gets the same setup automatically.
Got it. But one question remains: how do I update the snapshot in environment.jsonwith the new wizard? The old one had the option to save it there and the new one doesn’t to my understanding. Does it give me the snapshot ID somewhere?
ahh sorry, the full view is there only when you’ve clicked Save (to either Personal or Team). will work on improving that UI for runs that you haven’t saved yet.
