{"version":"2.1.323","anchor":"browser-file-upload-size-limit-error-reworded","canonical_anchor":"browser-file-upload-size-limit-error-reworded","heading":"Claude in Chrome file uploads get their own approval card and clearer errors","tier":"notice","area":"Chrome","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/browser-file-upload-size-limit-error-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Claude in Chrome file uploads get their own approval card and clearer errors\n\nClaude in Chrome's file_upload now needs its own approval card, explains failed or oversized uploads more clearly, and retries tab address lookups\n\n**What**\n\nClaude in Chrome lets Claude control your Chrome browser, and `file_upload` is its action for putting files into a web page. Its permission check was substantially rewritten.\n\n- Upload card: file uploads now get their own permission card. The page's origin (its site address) is put in a standard form, your domain rules are applied, and uploads are refused in plan mode.\n\n- Preparation: before approval, the origin, file paths and file names are checked. If the files cannot be read for the approval, the error says \"Nothing was uploaded, because the files could not be read for the approval. Ask the user to choose the file in their browser themselves.\"\n\n- Card required: if a card was listed (`cardListed`) and the call does not carry the card's key, `file_upload` returns an error unless the permission result was automatic.\n\n- Size limit: the too-large message now says the files in one call can total at most a given size, that nothing in the call was uploaded, and suggests asking you to choose the file. Sizes are now worked out in decimal units.\n\n- Tab address lookup: finding a tab's web address now reads remote settings (`limit_ms`, `second_lookup_after_ms`), races a second lookup, and reports a new `not_connected` failure. Before, there was one fixed timeout.\n\n- Batches: refusing the actions of a `browser_batch` call one by one now goes through a shared helper.\n\n**Why**\n\nUploading a file from your computer into a website now has its own approval step tied to the site and your domain rules, and it is refused in plan mode. When an upload fails, Claude is told that nothing was sent and to ask you to pick the file, and a disconnected browser now shows up as `not_connected`.\n\n- Area: Chrome\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}