Make Auto-Run configurable per environment (host vs. dev-container)

Feature request for product/service

Cursor IDE

Describe the request

I’m developing a .NET MAUI app, which cannot be built on Linux.
For that reason, I work in two environments with the same project folder:

inside a Linux dev-container (for editing and testing non-build steps)

on Windows (for building and debugging the app)

The problem: Cursor stores the Auto-Run setting globally.
If I enable Auto-Run in the dev-container for convenience, it remains enabled when I open the same folder on Windows — where automatic code execution is unsafe and can trigger unintended builds or host-side actions.

Expected behavior
Cursor should distinguish between environments and allow separate settings for Auto-Run (and similar execution-related options) per environment or runtime context.

Proposed solution

Detect when running inside a dev-container and isolate environment-specific settings, or

Support a command-line flag like

cursor --env devcontainer --set cursor.autoRun=true
cursor --env host --set cursor.autoRun=false

Impact
Developers working across both Linux containers and Windows hosts risk unsafe or unwanted host-side code execution, since the global Auto-Run setting persists across environments.

Operating System (if it applies)

Windows 10/11