{"version":"2.1.321","anchor":"mcp-connector-file-uploads-are-waited-on-with-an-fsync-sett","canonical_anchor":"mcp-connector-file-uploads-are-waited-on-with-an-fsync-sett","heading":"Files sent to connectors in remote sessions are now fully written before they are read","tier":"notice","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-connector-file-uploads-are-waited-on-with-an-fsync-sett","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Files sent to connectors in remote sessions are now fully written before they are read\n\nIn remote sessions, Claude Code now waits for a file to be fully stored before reading it for a connector upload, and logs less about failures\n\n**What**\n\nConnectors link Claude Code to outside tools through MCP, a standard way of plugging in tools. Several things change in how files are passed to them:\n\n- When `CLAUDE_CODE_REMOTE` is true, Claude Code now waits until the file store has fully taken a file before reading it. Before, it read the file straight away.\n\n- If that wait fails, it logs that it did not wait for the file store to take the file.\n\n- When an upload fails, the error text is no longer logged, because it can name the file or the upload address.\n\n- Claude Code now keeps track of files that connector servers report as delivered.\n\n**Why**\n\nIn remote sessions, an attached file could be read before it had finished being written. Waiting first stops that, and the logs no longer reveal file names or upload addresses.\n\n- Area: Connectors\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}