Plugin fetch can now connect over a Unix socket instead of a network address, as an experimental option
The 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.
This 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.