@leaflow/sdk 0.210.0 → 0.211.0

package/dist/assistant/v1/generated/validators/threadItemListResponseBody.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
@@ -71,19 +72,22 @@ export declare const ThreadItemListResponseBody: zod.ZodObject<{
                 text: "text";
             }>;
             text: zod.ZodNullable<zod.ZodString>;
-            attachmentId: zod.ZodNullable<zod.ZodString>;
-        }, zod.z.core.$strict>>;
-        attachments: zod.ZodArray<zod.ZodObject<{
-            id: zod.ZodString;
-            type: zod.ZodEnum<{
-                text: "text";
-                image: "image";
-                binary: "binary";
-            }>;
-            filename: zod.ZodString;
-            byteSize: zod.ZodInt;
-            width: zod.ZodNullable<zod.ZodInt>;
-            height: zod.ZodNullable<zod.ZodInt>;
+            file: zod.ZodUnion<readonly [zod.ZodObject<{
+                id: zod.ZodString;
+                filename: zod.ZodString;
+                mediaType: zod.ZodString;
+                type: zod.ZodEnum<{
+                    text: "text";
+                    image: "image";
+                    binary: "binary";
+                }>;
+                byteSize: zod.ZodInt;
+                width: zod.ZodNullable<zod.ZodInt>;
+                height: zod.ZodNullable<zod.ZodInt>;
+                draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+                createdAt: zod.z.ZodISODateTime;
+                updatedAt: zod.z.ZodISODateTime;
+            }, zod.z.core.$strict>, zod.ZodNull]>;
         }, zod.z.core.$strict>>;
         clientContext: zod.ZodArray<zod.ZodObject<{
             type: zod.ZodString;
@@ -126,6 +130,48 @@ export declare const ThreadItemListResponseBody: zod.ZodObject<{
             }, zod.z.core.$strict>>>;
             answers: zod.ZodNullable<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
             autoAnswerMs: zod.ZodNullable<zod.ZodInt>;
+            contentFiles: zod.ZodArray<zod.ZodObject<{
+                id: zod.ZodString;
+                filename: zod.ZodString;
+                mediaType: zod.ZodString;
+                type: zod.ZodEnum<{
+                    text: "text";
+                    image: "image";
+                    binary: "binary";
+                }>;
+                byteSize: zod.ZodInt;
+                width: zod.ZodNullable<zod.ZodInt>;
+                height: zod.ZodNullable<zod.ZodInt>;
+                draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+                createdAt: zod.z.ZodISODateTime;
+                updatedAt: zod.z.ZodISODateTime;
+            }, zod.z.core.$strict>>;
+            artifacts: zod.ZodArray<zod.ZodObject<{
+                id: zod.ZodString;
+                artifactId: zod.ZodString;
+                title: zod.ZodString;
+                version: zod.ZodInt;
+                file: zod.ZodObject<{
+                    id: zod.ZodString;
+                    filename: zod.ZodString;
+                    mediaType: zod.ZodString;
+                    type: zod.ZodEnum<{
+                        text: "text";
+                        image: "image";
+                        binary: "binary";
+                    }>;
+                    byteSize: zod.ZodInt;
+                    width: zod.ZodNullable<zod.ZodInt>;
+                    height: zod.ZodNullable<zod.ZodInt>;
+                    draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+                    createdAt: zod.z.ZodISODateTime;
+                    updatedAt: zod.z.ZodISODateTime;
+                }, zod.z.core.$strict>;
+                threadId: zod.ZodNullable<zod.ZodString>;
+                turnId: zod.ZodNullable<zod.ZodString>;
+                itemId: zod.ZodNullable<zod.ZodString>;
+                createdAt: zod.z.ZodISODateTime;
+            }, zod.z.core.$strict>>;
         }, zod.z.core.$strict>, zod.ZodNull]>;
         messageIndex: zod.ZodNullable<zod.ZodInt>;
         createdAt: zod.z.ZodISODateTime;
@@ -177,19 +223,22 @@ export declare const ThreadItemListResponseBody: zod.ZodObject<{
                 text: "text";
             }>;
             text: zod.ZodNullable<zod.ZodString>;
-            attachmentId: zod.ZodNullable<zod.ZodString>;
-        }, zod.z.core.$strict>>;
-        attachments: zod.ZodArray<zod.ZodObject<{
-            id: zod.ZodString;
-            type: zod.ZodEnum<{
-                text: "text";
-                image: "image";
-                binary: "binary";
-            }>;
-            filename: zod.ZodString;
-            byteSize: zod.ZodInt;
-            width: zod.ZodNullable<zod.ZodInt>;
-            height: zod.ZodNullable<zod.ZodInt>;
+            file: zod.ZodUnion<readonly [zod.ZodObject<{
+                id: zod.ZodString;
+                filename: zod.ZodString;
+                mediaType: zod.ZodString;
+                type: zod.ZodEnum<{
+                    text: "text";
+                    image: "image";
+                    binary: "binary";
+                }>;
+                byteSize: zod.ZodInt;
+                width: zod.ZodNullable<zod.ZodInt>;
+                height: zod.ZodNullable<zod.ZodInt>;
+                draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+                createdAt: zod.z.ZodISODateTime;
+                updatedAt: zod.z.ZodISODateTime;
+            }, zod.z.core.$strict>, zod.ZodNull]>;
         }, zod.z.core.$strict>>;
         clientContext: zod.ZodArray<zod.ZodObject<{
             type: zod.ZodString;
@@ -232,6 +281,48 @@ export declare const ThreadItemListResponseBody: zod.ZodObject<{
             }, zod.z.core.$strict>>>;
             answers: zod.ZodNullable<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
             autoAnswerMs: zod.ZodNullable<zod.ZodInt>;
+            contentFiles: zod.ZodArray<zod.ZodObject<{
+                id: zod.ZodString;
+                filename: zod.ZodString;
+                mediaType: zod.ZodString;
+                type: zod.ZodEnum<{
+                    text: "text";
+                    image: "image";
+                    binary: "binary";
+                }>;
+                byteSize: zod.ZodInt;
+                width: zod.ZodNullable<zod.ZodInt>;
+                height: zod.ZodNullable<zod.ZodInt>;
+                draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+                createdAt: zod.z.ZodISODateTime;
+                updatedAt: zod.z.ZodISODateTime;
+            }, zod.z.core.$strict>>;
+            artifacts: zod.ZodArray<zod.ZodObject<{
+                id: zod.ZodString;
+                artifactId: zod.ZodString;
+                title: zod.ZodString;
+                version: zod.ZodInt;
+                file: zod.ZodObject<{
+                    id: zod.ZodString;
+                    filename: zod.ZodString;
+                    mediaType: zod.ZodString;
+                    type: zod.ZodEnum<{
+                        text: "text";
+                        image: "image";
+                        binary: "binary";
+                    }>;
+                    byteSize: zod.ZodInt;
+                    width: zod.ZodNullable<zod.ZodInt>;
+                    height: zod.ZodNullable<zod.ZodInt>;
+                    draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+                    createdAt: zod.z.ZodISODateTime;
+                    updatedAt: zod.z.ZodISODateTime;
+                }, zod.z.core.$strict>;
+                threadId: zod.ZodNullable<zod.ZodString>;
+                turnId: zod.ZodNullable<zod.ZodString>;
+                itemId: zod.ZodNullable<zod.ZodString>;
+                createdAt: zod.z.ZodISODateTime;
+            }, zod.z.core.$strict>>;
         }, zod.z.core.$strict>, zod.ZodNull]>;
         messageIndex: zod.ZodNullable<zod.ZodInt>;
         createdAt: zod.z.ZodISODateTime;

package/dist/assistant/v1/generated/validators/threadItemListResponseBody.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadItemResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
@@ -70,19 +71,22 @@ export declare const ThreadItemResource: zod.ZodObject<{
             text: "text";
         }>;
         text: zod.ZodNullable<zod.ZodString>;
-        attachmentId: zod.ZodNullable<zod.ZodString>;
-    }, zod.z.core.$strict>>;
-    attachments: zod.ZodArray<zod.ZodObject<{
-        id: zod.ZodString;
-        type: zod.ZodEnum<{
-            text: "text";
-            image: "image";
-            binary: "binary";
-        }>;
-        filename: zod.ZodString;
-        byteSize: zod.ZodInt;
-        width: zod.ZodNullable<zod.ZodInt>;
-        height: zod.ZodNullable<zod.ZodInt>;
+        file: zod.ZodUnion<readonly [zod.ZodObject<{
+            id: zod.ZodString;
+            filename: zod.ZodString;
+            mediaType: zod.ZodString;
+            type: zod.ZodEnum<{
+                text: "text";
+                image: "image";
+                binary: "binary";
+            }>;
+            byteSize: zod.ZodInt;
+            width: zod.ZodNullable<zod.ZodInt>;
+            height: zod.ZodNullable<zod.ZodInt>;
+            draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+            createdAt: zod.z.ZodISODateTime;
+            updatedAt: zod.z.ZodISODateTime;
+        }, zod.z.core.$strict>, zod.ZodNull]>;
     }, zod.z.core.$strict>>;
     clientContext: zod.ZodArray<zod.ZodObject<{
         type: zod.ZodString;
@@ -125,6 +129,48 @@ export declare const ThreadItemResource: zod.ZodObject<{
         }, zod.z.core.$strict>>>;
         answers: zod.ZodNullable<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
         autoAnswerMs: zod.ZodNullable<zod.ZodInt>;
+        contentFiles: zod.ZodArray<zod.ZodObject<{
+            id: zod.ZodString;
+            filename: zod.ZodString;
+            mediaType: zod.ZodString;
+            type: zod.ZodEnum<{
+                text: "text";
+                image: "image";
+                binary: "binary";
+            }>;
+            byteSize: zod.ZodInt;
+            width: zod.ZodNullable<zod.ZodInt>;
+            height: zod.ZodNullable<zod.ZodInt>;
+            draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+            createdAt: zod.z.ZodISODateTime;
+            updatedAt: zod.z.ZodISODateTime;
+        }, zod.z.core.$strict>>;
+        artifacts: zod.ZodArray<zod.ZodObject<{
+            id: zod.ZodString;
+            artifactId: zod.ZodString;
+            title: zod.ZodString;
+            version: zod.ZodInt;
+            file: zod.ZodObject<{
+                id: zod.ZodString;
+                filename: zod.ZodString;
+                mediaType: zod.ZodString;
+                type: zod.ZodEnum<{
+                    text: "text";
+                    image: "image";
+                    binary: "binary";
+                }>;
+                byteSize: zod.ZodInt;
+                width: zod.ZodNullable<zod.ZodInt>;
+                height: zod.ZodNullable<zod.ZodInt>;
+                draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+                createdAt: zod.z.ZodISODateTime;
+                updatedAt: zod.z.ZodISODateTime;
+            }, zod.z.core.$strict>;
+            threadId: zod.ZodNullable<zod.ZodString>;
+            turnId: zod.ZodNullable<zod.ZodString>;
+            itemId: zod.ZodNullable<zod.ZodString>;
+            createdAt: zod.z.ZodISODateTime;
+        }, zod.z.core.$strict>>;
     }, zod.z.core.$strict>, zod.ZodNull]>;
     messageIndex: zod.ZodNullable<zod.ZodInt>;
     createdAt: zod.z.ZodISODateTime;

package/dist/assistant/v1/generated/validators/threadItemResource.zod.js

@@ -20,14 +20,14 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-import { AttachmentResource } from "./attachmentResource.zod.js";
 import { ClientContextPart } from "./clientContextPart.zod.js";
 import { ItemSourceResource } from "./itemSourceResource.zod.js";
 import { PartResource } from "./partResource.zod.js";
@@ -75,8 +75,7 @@ export const ThreadItemResource = zod
         .describe("How long the reasoning or the tool call took. Null while it runs and for other items."),
     parts: zod
         .array(PartResource)
-        .describe("The content, in the order it was written. Text arrives as `append` frames on the realtime\nstream. An attachment belongs where it was written, so render parts in order. Empty for\ntool calls; their outcome is in `toolCall.detail` and `toolCall.presentation`."),
-    attachments: zod.array(AttachmentResource),
+        .describe("The content, in the order it was written. Text arrives as `append` frames on the realtime\nstream. A file the person attached belongs where it was written, so render parts in order.\nEmpty for tool calls; their outcome is in `toolCall`."),
     clientContext: zod
         .array(ClientContextPart)
         .describe("The `data-*` blocks the client attached to a user message. They are not part of what the\nperson wrote; render the message from `parts` and leave these out of the bubble."),

package/dist/assistant/v1/generated/validators/threadListResponseBody.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadListResponseBody.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadMessageListResponseBody.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadMessageListResponseBody.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadMessageResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadMessageResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadStatus.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadStatus.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadTurnListResponseBody.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadTurnListResponseBody.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadTurnResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/threadTurnResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/todoResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/todoResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";