{"version":"1.0.120","anchor":"unix-domain-socket-support-for-network-permissions","canonical_anchor":"unix-domain-socket-support-for-network-permissions","heading":"Unix Domain Socket Support for Network Permissions","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/1.0.120\/e\/unix-domain-socket-support-for-network-permissions","release_url":"https:\/\/changelogs.core-directive.com\/v\/1.0.120","markdown":"### Unix Domain Socket Support for Network Permissions\n\n**What:** Network permissions now support Unix domain sockets for local IPC, enabling tools like SSH agents and Docker to work within the sandbox.\n\n**How to configure:**\n\n`{ \"permissions\": { \"network\": { \"allowUnixSockets\": true \/\/ Allow all Unix sockets } } }` Or with specific paths:\n\n`{ \"permissions\": { \"network\": { \"allowUnixSockets\": [ \"\/var\/run\/docker.sock\", \"~\/.ssh\/agent.sock\" ] } } }` **Details:**\n\n- Three modes: `true` (allow all), `false` (block all - default), or array of specific socket paths\n- Currently implemented for macOS sandbox profiles using `(remote unix-socket)` directive\n- Essential for Docker, SSH agents, and other development tools requiring local IPC\n- Type: `boolean | string[]`\n\n**Evidence**\n\nSchema definition at lines 354206-354217, implementation at lines 374968-374975, parameter usage at line 375216"}