Feature Request: Containerized YOLO Mode Support on macOS
Overview:
It would be great to have an option in Cursor to easily run YOLO mode inside a container (e.g., Docker) to isolate automated terminal commands from the host system, especially on macOS.
Why This Matters:
Security: Keeps potentially risky automated commands confined to a container, reducing the risk of unintended changes on the host.
Workflow Integration: Seamlessly works with existing setups like VS Code Dev Containers, enabling a more robust and isolated development environment.
Ease of Use: Eliminates the need for manual container configuration or third-party workarounds, simplifying the process for users.
Proposed Implementation:
Built-in Container Mode: Add a setting or flag to launch Cursor in a containerized environment with YOLO mode enabled.
Custom Configuration: Provide options for volume mounting, environment variable setup, and command whitelisting directly from the UI or configuration files.
Fallback & Diagnostics: Offer clear error messages and fallback instructions if container mode encounters issues.
Benefits:
Enhanced safety and isolation for executing terminal commands.
Streamlined setup process for developers already using container-based workflows.
Increased adoption of YOLO mode by reducing manual configuration overhead.
I do all my cursor work in dev containers. Cursor runs on mac - using orbstack for docker instead of docker desktop - and its super smooth. Changes auto sync to local workspace, i get the power of my mac so cursor is fast - and im protected from the accidental rm -rf /
Yes. I do this. But that is not the same as installing Cursor into a container. That is Cursor utilizing a container, which is a very very different thing.