@leaflow/sdk 0.0.0-dev.523.gcaeef48 → 0.0.0-dev.529.g6a1b7de

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

@@ -0,0 +1,65 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Assistant API
+ * Conversations with agents that operate the Leaflow platform, plus their folders, tasks, files and
+ * chat-app channels.
+ *
+ * A conversation is a thread. A person talks to the main thread; the agent in it can start subagents,
+ * which are threads too and run on their own: stopping the main thread does not stop them, and each
+ * subagent tells its parent when it ends. A thread runs in turns; each turn records the model and
+ * reasoning effort it used and its token usage.
+ *
+ * Models come from the Canopy catalogue. A new thread uses the model it names, the caller's default
+ * from /api/v1/settings, or the first catalogue model that can run an agent. Reasoning models take one
+ * of three efforts — low, medium or high — which are sent to the model unchanged.
+ *
+ * Read a thread's state with get-thread and its transcript with list-thread-items. Follow both live
+ * through EventBus by subscribing to assistant.thread.frame and assistant.resource.updated; after a
+ * reconnection or an assistant.workspace.invalidated message, read them again. list-thread-messages
+ * 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 file id in a message.
+ *
+ * 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";
+export declare const ArtifactResource: zod.ZodObject<{
+    id: zod.ZodString;
+    title: zod.ZodString;
+    latestVersion: 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>;
+    versionCount: zod.ZodInt;
+    createdAt: zod.z.ZodISODateTime;
+    updatedAt: zod.z.ZodISODateTime;
+}, zod.z.core.$strict>;
+export type ArtifactResource = zod.input<typeof ArtifactResource>;
+export type ArtifactResourceOutput = zod.output<typeof ArtifactResource>;

package/dist/assistant/v1/generated/validators/{attachmentResource.zod.js → artifactResource.zod.js}

@@ -20,23 +20,22 @@
  * 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";
-export const AttachmentResource = zod.strictObject({
+import { ArtifactVersionResource } from "./artifactVersionResource.zod.js";
+export const ArtifactResource = zod.strictObject({
     id: zod.string(),
-    type: zod
-        .enum(["image", "text", "binary"])
-        .describe("A client renders an image in place and everything else as a file to download."),
-    filename: zod.string(),
-    byteSize: zod.int(),
-    width: zod
-        .int()
-        .nullable()
-        .describe("Null unless type is image. Lets a client hold the space before the image loads."),
-    height: zod.int().nullable().describe("Null unless type is image."),
+    title: zod.string(),
+    latestVersion: ArtifactVersionResource,
+    versionCount: zod.int().min(1),
+    createdAt: zod.iso.datetime({ offset: true }),
+    updatedAt: zod.iso
+        .datetime({ offset: true })
+        .describe("When the title last changed or the latest version was added."),
 });

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

@@ -0,0 +1,61 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Assistant API
+ * Conversations with agents that operate the Leaflow platform, plus their folders, tasks, files and
+ * chat-app channels.
+ *
+ * A conversation is a thread. A person talks to the main thread; the agent in it can start subagents,
+ * which are threads too and run on their own: stopping the main thread does not stop them, and each
+ * subagent tells its parent when it ends. A thread runs in turns; each turn records the model and
+ * reasoning effort it used and its token usage.
+ *
+ * Models come from the Canopy catalogue. A new thread uses the model it names, the caller's default
+ * from /api/v1/settings, or the first catalogue model that can run an agent. Reasoning models take one
+ * of three efforts — low, medium or high — which are sent to the model unchanged.
+ *
+ * Read a thread's state with get-thread and its transcript with list-thread-items. Follow both live
+ * through EventBus by subscribing to assistant.thread.frame and assistant.resource.updated; after a
+ * reconnection or an assistant.workspace.invalidated message, read them again. list-thread-messages
+ * 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 file id in a message.
+ *
+ * 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";
+export declare const ArtifactVersionListResponseBody: zod.ZodObject<{
+    versions: 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>>;
+    nextCursor: zod.ZodNullable<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type ArtifactVersionListResponseBody = zod.input<typeof ArtifactVersionListResponseBody>;
+export type ArtifactVersionListResponseBodyOutput = zod.output<typeof ArtifactVersionListResponseBody>;

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

@@ -0,0 +1,35 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Assistant API
+ * Conversations with agents that operate the Leaflow platform, plus their folders, tasks, files and
+ * chat-app channels.
+ *
+ * A conversation is a thread. A person talks to the main thread; the agent in it can start subagents,
+ * which are threads too and run on their own: stopping the main thread does not stop them, and each
+ * subagent tells its parent when it ends. A thread runs in turns; each turn records the model and
+ * reasoning effort it used and its token usage.
+ *
+ * Models come from the Canopy catalogue. A new thread uses the model it names, the caller's default
+ * from /api/v1/settings, or the first catalogue model that can run an agent. Reasoning models take one
+ * of three efforts — low, medium or high — which are sent to the model unchanged.
+ *
+ * Read a thread's state with get-thread and its transcript with list-thread-items. Follow both live
+ * through EventBus by subscribing to assistant.thread.frame and assistant.resource.updated; after a
+ * reconnection or an assistant.workspace.invalidated message, read them again. list-thread-messages
+ * 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 file id in a message.
+ *
+ * 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 { ArtifactVersionResource } from "./artifactVersionResource.zod.js";
+export const ArtifactVersionListResponseBody = zod.strictObject({
+    versions: zod.array(ArtifactVersionResource),
+    nextCursor: zod.string().nullable().describe("Null on the last page."),
+});

package/dist/assistant/v1/generated/validators/{uploadedResource.zod.d.ts → artifactVersionResource.zod.d.ts}

@@ -20,25 +20,39 @@
  * 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";
-export declare const UploadedResource: zod.ZodObject<{
-    byteSize: zod.ZodInt;
-    draftExpiresAt: zod.z.ZodISODateTime;
-    filename: zod.ZodString;
-    height: zod.ZodNullable<zod.ZodInt>;
+export declare const ArtifactVersionResource: zod.ZodObject<{
     id: zod.ZodString;
-    type: zod.ZodEnum<{
-        text: "text";
-        image: "image";
-        binary: "binary";
-    }>;
-    width: zod.ZodNullable<zod.ZodInt>;
+    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>;
-export type UploadedResource = zod.input<typeof UploadedResource>;
-export type UploadedResourceOutput = zod.output<typeof UploadedResource>;
+export type ArtifactVersionResource = zod.input<typeof ArtifactVersionResource>;
+export type ArtifactVersionResourceOutput = zod.output<typeof ArtifactVersionResource>;

package/dist/assistant/v1/generated/validators/{attachmentFileResource.zod.js → artifactVersionResource.zod.js}

@@ -20,25 +20,32 @@
  * 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";
-export const AttachmentFileResource = zod.strictObject({
-    byteSize: zod.int(),
-    createdAt: zod.iso.datetime({ offset: true }),
-    draftExpiresAt: zod.iso
-        .datetime({ offset: true })
-        .nullable()
-        .describe("When this draft is cleared if no message ever references it. Null once a message uses it —\na file that belongs to a conversation is kept as long as the conversation is."),
-    filename: zod.string(),
-    height: zod.int().nullable().describe("Null unless type is image."),
+import { FileResource } from "./fileResource.zod.js";
+export const ArtifactVersionResource = zod.strictObject({
     id: zod.string(),
-    mime: zod.string().describe("Detected at intake, not the Content-Type the client sent."),
-    type: zod.enum(["image", "text", "binary"]).describe("How the assistant will see this file."),
-    updatedAt: zod.iso.datetime({ offset: true }),
-    width: zod.int().nullable().describe("Null unless type is image."),
+    artifactId: zod.string(),
+    title: zod.string().describe("The artifact's current title."),
+    version: zod.int().min(1).describe("The position among the artifact's versions, from 1."),
+    file: FileResource,
+    threadId: zod
+        .string()
+        .nullable()
+        .describe("The conversation whose tool call created this version. Null for a version added through the API."),
+    turnId: zod
+        .string()
+        .nullable()
+        .describe("The turn whose tool call created this version. Null for a version added through the API."),
+    itemId: zod
+        .string()
+        .nullable()
+        .describe("The tool call that created this version. Null for a version added through the API."),
+    createdAt: zod.iso.datetime({ offset: true }),
 });

package/dist/assistant/v1/generated/validators/bindingCodeResponseBody.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/bindingCodeResponseBody.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/bindingResource.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/bindingResource.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/channelResource.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/channelResource.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/channelWithSecretResponseBody.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/channelWithSecretResponseBody.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/checkSenderParams.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/checkSenderParams.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/choiceResource.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/choiceResource.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/clientActionRequest.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/clientActionRequest.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/clientContextPart.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/clientContextPart.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/clientContextRequest.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/clientContextRequest.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/clientFunctionRequest.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";