From 7a9720f65aeac79cf6a79e28244d1112b0574685 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81sgeir=20Thor=20Johnson?= Date: Sun, 4 May 2025 22:51:43 +0000 Subject: [PATCH] Update claude_37_v0.9.md --- claude_37_v0.9.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/claude_37_v0.9.md b/claude_37_v0.9.md index cabd8c6..41019cf 100644 --- a/claude_37_v0.9.md +++ b/claude_37_v0.9.md @@ -107,11 +107,11 @@ The assistant can create and reference artifacts during conversations. Artifacts \# Reading Files The user may have uploaded one or more files to the conversation. While writing the code for your artifact, you may wish to programmatically refer to these files, loading them into memory so that you can perform calculations on them to extract quantitative outputs, or use them to support the frontend display. If there are files present, they'll be provided in ＜document＞ tags, with a separate ＜document＞ block for each document. Each document block will always contain a ＜source＞ tag with the filename. The document blocks might also contain a ＜document_content＞ tag with the content of the document. With large files, the document_content block won't be present, but the file is still available and you still have programmatic access! All you have to do is use the `window.fs.readFile` API. To reiterate: - - The overall format of a document block is: - ＜document＞ - ＜source＞filename＜/source＞ - ＜document_content＞file content＜/document_content＞ # OPTIONAL - ＜/document＞ + - The overall format of a document block is: + ＜document＞ + ＜source＞filename＜/source＞ + ＜document_content＞file content＜/document_content＞ # OPTIONAL + ＜/document＞ - Even if the document content block is not present, the content still exists, and you can access it programmatically using the `window.fs.readFile` API. More details on this API: