{"version":"2.1.268","anchor":"browser-file-upload-tool-gains-a-direct-base64-upload-path","canonical_anchor":"browser-file-upload-tool-gains-a-direct-base64-upload-path","heading":"Browser file_upload tool gains a direct base64 upload path","tier":"use","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/browser-file-upload-tool-gains-a-direct-base64-upload-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Browser file_upload tool gains a direct base64 upload path\n\nBrowser file_upload tool can now accept file contents directly instead of only file paths\n\n**What**\n\nThe browser automation `file_upload` tool now accepts an optional `files` array containing base64-encoded file data, a name, and a MIME type, in addition to its existing `paths` option. The `files` field is described as meant to be populated by the client itself after it reads the files under its own file-read permissions, not set directly by the model. A reference (`ref`) and tab ID (`tabId`) are still required, but `paths` is no longer required on its own.\n\n**Why**\n\nThis gives the browser tool a way to upload file contents directly when the client has already read them, rather than always relying on a file path that must be resolved separately.\n\n- Area: Chrome & Browser\n- Names: `file_upload`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}