{"version":"2.1.277","anchor":"plugin-fetch-gains-an-experimental-unix-socket-transport","canonical_anchor":"plugin-fetch-gains-an-experimental-unix-socket-transport","heading":"Plugin $.fetch gains an experimental Unix-socket transport (socketPath)","tier":"use","area":"Plugin API","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/plugin-fetch-gains-an-experimental-unix-socket-transport","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Plugin $.fetch gains an experimental Unix-socket transport (socketPath)\n\nPlugin fetch can now connect over a Unix socket instead of a network address, as an experimental option\n\n**What**\n\nThe sandboxed `$.fetch` helper available to plugins now accepts a `socketPath` option to connect over a Unix socket (a local, file-based connection) rather than over the network. The path must be absolute, must not contain a NUL byte, and must not resolve to a network location; if the build doesn't support Unix sockets, it throws \"no Unix socket transport in this build.\" When credentials are used with a socket connection, the request forces strict TLS certificate checking and disables connection keep-alive.\n\n**Why**\n\nThis lets plugins talk to local services listening on a Unix socket, useful for tools that expose a local API without going through the network, while keeping the same path and security validation Claude Code already applies elsewhere.\n\n- Area: Plugin API\n- Names: `socketPath`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}