{"version":"2.1.181","anchor":"sandbox-allowappleevents-setting-macos","canonical_anchor":"sandbox-allowappleevents-setting-macos","heading":"sandbox.allowAppleEvents Setting (macOS)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.181\/e\/sandbox-allowappleevents-setting-macos","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.181","markdown":"### `sandbox.allowAppleEvents` Setting (macOS)\n\n**What**\n\nA new macOS-only sandbox setting that permits sandboxed commands to send Apple Events \u2014 required for `open`, `osascript`, and browser-based auth flows that open URLs.\n\n**Usage**\n\n`\/\/ In user or managed settings (not project settings) { \"sandbox\": { \"allowAppleEvents\": true } }` **Details** - Only honored from user, managed\/policy, or CLI `--settings` settings. Project settings (`.claude\/settings.json` and `.claude\/settings.local.json`) are explicitly ignored. - **Security warning:** Enabling this removes code-execution isolation. Sandboxed commands can launch other applications unsandboxed with no user prompt, and can script running apps (e.g. Terminal) subject to the user's per-app TCC automation consent. - Default: `false`. **Evidence** Setting schema (search for `\"macOS only: Allow sandboxed commands to send Apple Events\"`) \u2014 `allowAppleEvents` field at line ~46966"}