{"version":"2.1.321","anchor":"edit-tool-existence-checks-consolidated-connector-file-mess","canonical_anchor":"edit-tool-existence-checks-consolidated-connector-file-mess","heading":"Write refuses to replace a file Claude has only seen the start of","tier":"notice","area":"Tools","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/edit-tool-existence-checks-consolidated-connector-file-mess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Write refuses to replace a file Claude has only seen the start of\n\nWrite now refuses to overwrite a file when only its start was shown in the session, so the rest is not lost\n\n**What**\n\nWrite is the tool Claude uses to create or replace a whole file. It now refuses when only the beginning of the file was shown in the session, with the message \"Only the start of this file was given in this session, so a Write could lose the rest.\"\n\nTwo smaller changes:\n\n- Edit checks: the checks the Edit tool makes for a file that already exists or is a Jupyter notebook now run through shared code. The messages are the same.\n\n- Connector uploads: when uploading a file to a connector (a link to an outside service) fails, the message now adds that it is unknown whether the file reached the connector.\n\n**Why**\n\nReplacing a whole file Claude had only partly seen could silently delete the part it never read. That is now blocked.\n\n- Area: Tools\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}