{"version":"2.1.323","anchor":"macos-sandbox-profile-denies-process-info-by-default-and-all","canonical_anchor":"macos-sandbox-profile-denies-process-info-by-default-and-all","heading":"macOS sandbox now blocks most process information but allows listing processes","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/macos-sandbox-profile-denies-process-info-by-default-and-all","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### macOS sandbox now blocks most process information but allows listing processes\n\nOn macOS, sandboxed commands can still list process IDs, but a new rule denies them other process information by default\n\n**Unclear.** It is unclear whether processes inside the same sandbox can still be inspected, because the new deny rule comes before the old allow rule.\n\n**What**\n\nOn macOS, Claude Code can run commands inside a sandbox, a fenced-off space that limits what the command can reach. The sandbox rules changed in two ways:\n\n- A new rule denies access to process information by default, and shows a message when it does.\n\n- A new rule allows listing process IDs, where macOS supports that permission.\n\nThe rule allowing information about processes inside the same sandbox is still there.\n\n**Why**\n\nTools that inspect running processes, such as `ps`, may behave differently or fail inside the sandbox.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}