{"version":"2.1.265","anchor":"artifact-file-read-schema-adds-contentcontent-scrubbed-fiel","canonical_anchor":"file-read-tool-result-can-now-inline-the-files-full-content","heading":"Artifact file_read results can now inline the file's full content","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/artifact-file-read-schema-adds-contentcontent-scrubbed-fiel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Artifact file_read results can now inline the file's full content\n\nReading a file through the Artifact tool can now show the file's content inline instead of requiring a separate read\n\n**What**\n\n- When the Artifact tool's `file_read` result is rendered, if the read includes a `content` string it's now appended in full below the summary line, so the caller no longer necessarily needs to separately read the saved file.\n\n- A note is shown when the content is a \"reading copy\" with reserved tag names neutralized.\n\n- The underlying schema for served files gained `content` (capped in length) and `content_scrubbed` fields; elsewhere, `content`\/`content_scrubbed` are stripped from `file_read` payloads before being logged.\n\n**Why** Inlining the file content saves an extra round trip: Claude can see what it just read without issuing a follow-up read call, while the scrubbing step keeps sensitive content out of logs.\n\n- Area: Artifacts\n- Names: `content_scrubbed`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}