{"version":"2.1.312","anchor":"macos-sandbox-local-binding-ports-are-now-denied-rather-tha","canonical_anchor":"macos-sandbox-local-binding-ports-are-now-denied-rather-tha","heading":"macOS sandbox now blocks commands from listening on the proxy ports","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/macos-sandbox-local-binding-ports-are-now-denied-rather-tha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### macOS sandbox now blocks commands from listening on the proxy ports\n\nOn macOS, sandboxed commands can no longer bind to or accept connections on the proxy ports, but can still connect out to them\n\n**What**\n\nOn macOS, Claude Code can run commands in a sandbox, a fenced-off space that limits what they can reach. Claude Code uses proxy ports, local network ports that carry traffic for those commands. For these ports, the sandbox rules have changed:\n\n- Binding and accepting incoming connections were allowed on localhost. Both are now denied on any local address\n\n- Connecting out to localhost on these ports is still allowed\n\n**Why**\n\nA sandboxed command can no longer claim one of the proxy ports or listen on it. It can still send traffic through them.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}