Remove sandbox env

Feature request for product/service

Cursor IDE

Describe the request

Sandbox is the biggest headache and biggest waste of a feature you guys have released. I can’t tell you how many times the agent messes up now since it can’t have access to certain things. I can’t even run an npm install since it doesn’t have access to asdf files which I use for version management.

It is the biggest hinderance when working with a model and I always am having to run commands for it. Please please remove it and never release anything like it again. Just run some analytics for how many times a model is stopped after a sandbox command fails and you’ll understand how painful it is to work with.

1 Like

Hey, thanks for the feedback. The issue with accessing the shell environment in the sandbox terminal is known and actively discussed.

Workaround: switch to Legacy Terminal mode:

  • Cursor Settings > Features > Agent > Terminal Tool Mode > select “Legacy Terminal”

Legacy mode gives the Agent access to your standard shell environment, including asdf and other tools.

Detailed discussion and alternative solutions: Cursor Terminal - Shell Profile

The team is aware of the sandbox limitations and is working on improvements.

Voting for its removal. Its been a disaster ever since it was introduced. There are problems at times because it can’t do things, but also, the agents seem to have curious ways around the limitations as well, and I’ve seen it run things, WITHOUT ASKING ME, that were destructive.

Worst feature to land in Cursor since I’ve started using it. Once I discovered the Legacy Terminal setting I’ve enabled it and will never go back, but it DOES concern me that its called Legacy. If this feature is ever removed, its probably the end of Cursor for me, as I WILL NOT use the sandbox mode. Its dangerous and problematic.

2 Likes

also voting for removal. auth related headaches and time spent has soared since intro of sandboxing