{"version":"2.1.210","anchor":"sendfile-send-files-between-claude-code-sessions","canonical_anchor":"sendfile-send-files-between-claude-code-sessions","heading":"SendFile \u2014 Send Files Between Claude Code Sessions","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.210\/e\/sendfile-send-files-between-claude-code-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.210","markdown":"### SendFile \u2014 Send Files Between Claude Code Sessions\n\n**What**\n\nA new `SendFile` tool lets Claude send one or more local files to another Claude Code session \u2014 a peer session on the same machine or a Remote Control \/ cloud session on a different machine.\n\n**Details**\n\n- Local sessions are addressed by name or by explicit `uds:<socket>` address. Cloud sessions use `bridge:<session-id>`.\n- Files are verified with a SHA-256 digest after transfer, so the receiver can confirm integrity.\n- Same-machine transfers travel over a Unix domain socket (no data leaves the host). Cross-machine transfers upload file contents through Anthropic servers; this path can be restricted with the `isolatePeerMachines` setting.\n- An optional `message` parameter delivers a short note alongside the files.\n- Agents within the same session are explicitly excluded \u2014 they already share the filesystem, so there is nothing to transfer.\n- When `isolatePeerMachines` is enabled, cross-machine sends require explicit approval before anything is uploaded.\n- To find available peer sessions, use the existing session-listing tool: `Use <ListSessions> to see the sessions you can send files to`.\n\n**Evidence**\n\nTool definition with name `\"SendFile\"` (search for `\"Send one or more files to another Claude Code session\"`)"}