Artifact database writes accept file_path pointing at a local JSON file whose top-level object becomes the document, so a large document no longer has to pass through the conversation. Exactly one of inline data or file_path is required; giving both or neither is a validation error.
- The file is read under the normal Read permission rules, parsed as JSON, and must be a top-level object; failures are reported as read denied, file not found, invalid JSON, not an object, or too large.
- Swapping between inline data and a file after approval is refused and forces a fresh permission check.
- The write approval no longer blanket-covers files that need their own Read approval.
file_path does not hold valid JSON \u2014 write_db sends the file's JSON object as the document, saved as local JSON files (the destination follows the file-edit rules), a local JSON file whose top-level object is sent as the document
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
file_path: the source file is not valid UTF-8 text (first invalid byte at line 12, column 40). It may be saved in another encoding or contain binary data. Rewrite it as UTF-8, then publish again. Nothing was published.errors see the edit
Anthropic's documentation has since written up file_path, on Error reference.