{"version":"2.1.304","anchor":"file-upload-validation-generalized-beyond-chrome-with-a-saf","canonical_anchor":"file-upload-validation-generalized-beyond-chrome-with-a-saf","heading":"Browser file upload check reworked, and bad batch action names are cleaned in errors","tier":"internal","area":"Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/file-upload-validation-generalized-beyond-chrome-with-a-saf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Browser file upload check reworked, and bad batch action names are cleaned in errors\n\nThe file upload path check is no longer tied to Chrome only, and invalid browser_batch action names are cleaned before an error shows them\n\n**What**\n\nThe check on `file_upload`, which makes sure Claude only uploads files you have shared with the session, used to be written for Claude in Chrome alone. It now takes a separate set of rules for each place it runs, and Chrome has its own set.\n\nWhen a `browser_batch` call (one call that bundles several browser actions) contains an action name that is not valid, the error used to repeat that name exactly as given. Control characters in the name, which are invisible characters that can change how text is shown or read, are now replaced with a placeholder character before the name appears in the error.\n\n**Why**\n\nCleaning the name stops a bad action name from slipping hidden instructions or odd characters into the error text that Claude then reads. The reworked upload check also lets the same rule be used somewhere other than Chrome.\n\n- Area: Browser\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}