Feature request for product/service
Cursor IDE
Context
Right now, Cursor positions sandbox mode as the safer, more autonomous option, but it removes an important layer of practical control: the ability to say “these specific commands are always safe to run without asking, and everything else should still require approval.”
Why It Matters
That creates a frustrating tradeoff: sandbox and allowlisting solve different parts of the problem, but cannot currently be combined where they matter most.
- Sandbox provides stronger containment
- Allowlist provides fine-grained trust
Today, users effectively have to choose between them.
This matters because even inside the sandbox, there are still many commands I may not want Cursor to run autonomously — for example, commands that modify my repo, install dependencies, or otherwise create unwanted state.
Sandboxing reduces the blast radius if something goes wrong, but it does not answer the separate question of which commands should be trusted to auto-run.
Feature Request
Please add command allowlisting inside sandbox mode so users can combine sandbox isolation with fine-grained permission control, rather than having to trade containment for practical autonomy.