{"version":"2.1.314","anchor":"file-references-multiple-per-call-and-re-checked-on-send","canonical_anchor":"file-references-multiple-per-call-and-re-checked-on-send","heading":"File references are now checked one by one and checked again before sending","tier":"notice","area":"Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/file-references-multiple-per-call-and-re-checked-on-send","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### File references are now checked one by one and checked again before sending\n\nFile references can now come several to a call, and each is checked again at send time for being added, changed, removed or gone\n\n**What**\n\nClaude Code checks file references, which point to files to be attached, before using them. It now handles several references in one call, and each error says which reference it is about. Only one reference used to be checked. When the references are sent, each one is compared with what was checked earlier. Any difference is reported as changed after the check, with one of these reasons:\n\n- `reference_added`, a reference that was not there at check time\n\n- `reference_changed`, a reference that differs from what was checked\n\n- `reference_removed`, a reference that was dropped\n\n- `reference_gone`, a reference that no longer exists\n\nThe checks for Windows file paths now apply to every reference.\n\n**Why**\n\nFiles that change between being checked and being sent are now caught, so what gets sent matches what was checked.\n\n- Area: Attachments\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}