When I accept a command that required internet access or they are on my allowlist, the models gets an error and just stops the process, this is very annoying.
For example, I have a rule to create the changelog since last tag, where the model needs to read all the commits, then commit, create a tag, push, and create a PR. Since those are not in the allow list they do not run automatically but I expect that If I manually accept the command they should be able to run.
Or that the system understands it and tries to run it again with full permissions. But I currently find my self adding in several of my cursor rules a text like do not run this in sandbox mode, use full permissions.
Steps to Reproduce
Ask any model to git push, accept the command, it will get an error, and just stop (sometimes it tries again with full permissions)
Expected Behavior
I expect that if I accept a command and it does not work due to sandbox that the model tries again with full permissions
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Hey, thanks for the report. You’ve found a workflow issue with sandbox mode.
Current sandbox behavior: when commands fail due to sandbox restrictions, the agent doesn’t always retry with full permissions after you manually accept them. This is frustrating, especially for git operations like git push.
Yes! Thank you so much that is what I was looking for! The legacy system was just perfect for me and what I would expect as behaviour. To me the bug you mentioned is not the same issue though, in my case it is using properly the allowlist, just it is runnning the commands without full permissions and therefore getting an error.
I hope in the future this will be a forth option, meaning run in full permission mode, using allowlist, and if a command is not in the allowlist then ask me, if I confirm it should still have full permissions
The legacy terminal tool toggle did not fix this for me. With it toggled on and auto-run mode set to ask every time i still get messages like this. “I can’t run Alembic migrations in this sandbox (no DB access).“ Very frustrating given the lack of control and how intermittent it is.