{"version":"2.1.299","anchor":"remote-control-device-hooks-and-bridge-changes-missing-fil","canonical_anchor":"remote-control-device-hooks-and-bridge-changes-missing-fil","heading":"Remote Control now keeps track of attachments that could not be saved","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/remote-control-device-hooks-and-bridge-changes-missing-fil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Remote Control now keeps track of attachments that could not be saved\n\nMessages arriving through Remote Control now report attachments whose files could not be created, and queued notifications are handled differently mid-turn\n\n**Unclear.** What a user of Remote Control actually sees differently because of these changes is not stated.\n\n**What**\n\nRemote Control lets you drive a Claude Code session from another device. Several things changed in how Claude Code handles messages that arrive this way:\n\n- attachments that could not be turned into files are now listed and tracked\n\n- notifications queued while Claude is in the middle of a turn now go through a different route\n\n- an interruption queued for after a turn now runs an extra cleanup step\n\n**Why**\n\nThese changes affect how messages from a remote device travel into the session.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}