{"version":"2.1.286","anchor":"remote-bridge-user-message-ahead-of-attached-files","canonical_anchor":"remote-bridge-user-message-ahead-of-attached-files","heading":"Remote messages with files can start before the files are saved","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/remote-bridge-user-message-ahead-of-attached-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Remote messages with files can start before the files are saved\n\nA remote user message with attached files can now start Claude's reply before the files are written, and Claude is told if any could not be saved\n\n**Unclear.** It is not clear what decides whether a message takes this earlier-start path.\n\n**What**\n\nWhen a message arrives from a remote connection with files attached, Claude Code used to save the files before Claude started replying. Now the reply can start first, while the files are still being written. If some files are still missing afterwards, Claude receives a note saying how many of them could not be fetched or saved.\n\nThe earlier start is skipped, and the message waits for its files as before, in these cases:\n\n- messages from peers rather than from the user\n\n- attachments that are not binary files\n\n- when prompt hooks are set up (hooks are commands Claude Code runs automatically at set moments)\n\n**Why**\n\nRemote messages that carry files get a reply sooner. If a file fails to arrive, Claude knows it is missing instead of assuming it is there.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}