@leaflow/sdk 0.0.0-dev.363.gedb261b → 0.0.0-dev.367.g5d66ccc

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -109,6 +109,7 @@ export declare const ThreadItemListResponseBody: zod.ZodObject<{
             }, zod.z.core.$strict>, zod.ZodNull]>;
             approvalStatus: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"pending">, zod.ZodLiteral<"reviewing">, zod.ZodLiteral<"approved">, zod.ZodLiteral<"auto_approved">, zod.ZodLiteral<"declined">, zod.ZodLiteral<"unreviewed">, zod.ZodLiteral<null>]>>;
             approvalReason: zod.ZodNullable<zod.ZodString>;
+            approvalSource: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"user">, zod.ZodLiteral<"auto_review">, zod.ZodLiteral<"policy">, zod.ZodLiteral<null>]>>;
             decidedAt: zod.ZodNullable<zod.z.ZodISODateTime>;
             questions: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
                 id: zod.ZodString;
@@ -122,6 +123,7 @@ export declare const ThreadItemListResponseBody: zod.ZodObject<{
             answers: zod.ZodNullable<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
             autoAnswerMs: zod.ZodNullable<zod.ZodInt>;
         }, zod.z.core.$strict>, zod.ZodNull]>;
+        messageIndex: zod.ZodNullable<zod.ZodInt>;
         createdAt: zod.z.ZodISODateTime;
     }, zod.z.core.$strict>>;
     startOrdinal: zod.ZodNullable<zod.ZodInt>;
@@ -213,6 +215,7 @@ export declare const ThreadItemListResponseBody: zod.ZodObject<{
             }, zod.z.core.$strict>, zod.ZodNull]>;
             approvalStatus: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"pending">, zod.ZodLiteral<"reviewing">, zod.ZodLiteral<"approved">, zod.ZodLiteral<"auto_approved">, zod.ZodLiteral<"declined">, zod.ZodLiteral<"unreviewed">, zod.ZodLiteral<null>]>>;
             approvalReason: zod.ZodNullable<zod.ZodString>;
+            approvalSource: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"user">, zod.ZodLiteral<"auto_review">, zod.ZodLiteral<"policy">, zod.ZodLiteral<null>]>>;
             decidedAt: zod.ZodNullable<zod.z.ZodISODateTime>;
             questions: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
                 id: zod.ZodString;
@@ -226,6 +229,7 @@ export declare const ThreadItemListResponseBody: zod.ZodObject<{
             answers: zod.ZodNullable<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
             autoAnswerMs: zod.ZodNullable<zod.ZodInt>;
         }, zod.z.core.$strict>, zod.ZodNull]>;
+        messageIndex: zod.ZodNullable<zod.ZodInt>;
         createdAt: zod.z.ZodISODateTime;
     }, zod.z.core.$strict>>;
     streamCursor: zod.ZodNullable<zod.ZodString>;

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -108,6 +108,7 @@ export declare const ThreadItemResource: zod.ZodObject<{
         }, zod.z.core.$strict>, zod.ZodNull]>;
         approvalStatus: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"pending">, zod.ZodLiteral<"reviewing">, zod.ZodLiteral<"approved">, zod.ZodLiteral<"auto_approved">, zod.ZodLiteral<"declined">, zod.ZodLiteral<"unreviewed">, zod.ZodLiteral<null>]>>;
         approvalReason: zod.ZodNullable<zod.ZodString>;
+        approvalSource: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"user">, zod.ZodLiteral<"auto_review">, zod.ZodLiteral<"policy">, zod.ZodLiteral<null>]>>;
         decidedAt: zod.ZodNullable<zod.z.ZodISODateTime>;
         questions: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
             id: zod.ZodString;
@@ -121,6 +122,7 @@ export declare const ThreadItemResource: zod.ZodObject<{
         answers: zod.ZodNullable<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
         autoAnswerMs: zod.ZodNullable<zod.ZodInt>;
     }, zod.z.core.$strict>, zod.ZodNull]>;
+    messageIndex: zod.ZodNullable<zod.ZodInt>;
     createdAt: zod.z.ZodISODateTime;
 }, zod.z.core.$strict>;
 export type ThreadItemResource = zod.input<typeof ThreadItemResource>;

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -79,6 +79,11 @@ export const ThreadItemResource = zod
     toolCall: zod
         .union([ToolCallResource, zod.null()])
         .describe("The call, for a `tool_call` item. Null for other items."),
+    messageIndex: zod
+        .int()
+        .min(1)
+        .nullable()
+        .describe("The position of a `user_message` among the person's messages, from 1, as in\nlist-thread-messages. Null for other items, and for messages that are reverted or waiting\nin the queue."),
     createdAt: zod.iso.datetime({ offset: true }),
 })
     .describe("One entry of the transcript. `type` determines which fields it carries.");

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -109,6 +109,7 @@ export declare const ThreadListResponseBody: zod.ZodObject<{
         }, zod.z.core.$strict>;
         unread: zod.ZodBoolean;
         archived: zod.ZodBoolean;
+        messageCount: zod.ZodInt;
         createdAt: zod.z.ZodISODateTime;
         updatedAt: zod.z.ZodISODateTime;
     }, zod.z.core.$strict>>;

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

package/dist/assistant/v1/generated/validators/{commandListResponseBody.zod.d.ts → threadMessageListResponseBody.zod.d.ts}

@@ -15,21 +15,26 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-export declare const CommandListResponseBody: zod.ZodObject<{
-    commands: zod.ZodArray<zod.ZodObject<{
-        name: zod.ZodString;
-        aliases: zod.ZodArray<zod.ZodString>;
-        description: zod.ZodString;
-        argumentHint: zod.ZodString;
+export declare const threadMessageListResponseBodyTotalMin = 0;
+export declare const ThreadMessageListResponseBody: zod.ZodObject<{
+    messages: zod.ZodArray<zod.ZodObject<{
+        id: zod.ZodString;
+        index: zod.ZodInt;
+        ordinal: zod.ZodInt;
+        turnId: zod.ZodString;
+        preview: zod.ZodString;
+        attachments: zod.ZodInt;
+        createdAt: zod.z.ZodISODateTime;
     }, zod.z.core.$strict>>;
+    total: zod.ZodInt;
 }, zod.z.core.$strict>;
-export type CommandListResponseBody = zod.input<typeof CommandListResponseBody>;
-export type CommandListResponseBodyOutput = zod.output<typeof CommandListResponseBody>;
+export type ThreadMessageListResponseBody = zod.input<typeof ThreadMessageListResponseBody>;
+export type ThreadMessageListResponseBodyOutput = zod.output<typeof ThreadMessageListResponseBody>;

package/dist/assistant/v1/generated/validators/{commandListResponseBody.zod.js → threadMessageListResponseBody.zod.js}

@@ -15,15 +15,20 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-import { CommandResource } from "./commandResource.zod.js";
-export const CommandListResponseBody = zod.strictObject({
-    commands: zod.array(CommandResource),
+import { ThreadMessageResource } from "./threadMessageResource.zod.js";
+export const threadMessageListResponseBodyTotalMin = 0;
+export const ThreadMessageListResponseBody = zod.strictObject({
+    messages: zod.array(ThreadMessageResource),
+    total: zod
+        .int()
+        .min(threadMessageListResponseBodyTotalMin)
+        .describe("How many messages the person has sent in this conversation, the same as the thread's `messageCount`."),
 });

package/dist/assistant/v1/generated/validators/{runCommandRequestBody.zod.d.ts → threadMessageResource.zod.d.ts}

@@ -15,19 +15,23 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-export declare const runCommandRequestBodyNameMax = 32;
-export declare const runCommandRequestBodyArgumentsMax = 2000;
-export declare const RunCommandRequestBody: zod.ZodObject<{
-    name: zod.ZodString;
-    arguments: zod.ZodOptional<zod.ZodString>;
+export declare const threadMessageResourceAttachmentsMin = 0;
+export declare const ThreadMessageResource: zod.ZodObject<{
+    id: zod.ZodString;
+    index: zod.ZodInt;
+    ordinal: zod.ZodInt;
+    turnId: zod.ZodString;
+    preview: zod.ZodString;
+    attachments: zod.ZodInt;
+    createdAt: zod.z.ZodISODateTime;
 }, zod.z.core.$strict>;
-export type RunCommandRequestBody = zod.input<typeof RunCommandRequestBody>;
-export type RunCommandRequestBodyOutput = zod.output<typeof RunCommandRequestBody>;
+export type ThreadMessageResource = zod.input<typeof ThreadMessageResource>;
+export type ThreadMessageResourceOutput = zod.output<typeof ThreadMessageResource>;

package/dist/assistant/v1/generated/validators/{commandResultResource.zod.js → threadMessageResource.zod.js}

@@ -15,23 +15,30 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-import { StatusReportResource } from "./statusReportResource.zod.js";
-import { ThreadResource } from "./threadResource.zod.js";
-export const CommandResultResource = zod.strictObject({
-    name: zod.string().describe("The command that ran, after resolving aliases."),
-    message: zod.string().describe("The result as plain text."),
-    thread: zod.union([ThreadResource, zod.null()]).describe("The conversation after the command."),
-    turnId: zod
+export const threadMessageResourceAttachmentsMin = 0;
+export const ThreadMessageResource = zod
+    .strictObject({
+    id: zod.string().describe("The transcript item."),
+    index: zod.int().min(1).describe("The position among the person's messages, from 1."),
+    ordinal: zod
+        .int()
+        .describe("The item's position in the transcript, for list-thread-items `around`."),
+    turnId: zod.string(),
+    preview: zod
         .string()
-        .nullable()
-        .describe("The turn the command started, for example the compaction turn of /compact."),
-    status: zod.union([StatusReportResource, zod.null()]).describe("Set by /status."),
-});
+        .describe("The beginning of the message's text, at most 120 characters. Empty for a message with only attachments."),
+    attachments: zod
+        .int()
+        .min(threadMessageResourceAttachmentsMin)
+        .describe("How many files the message carries."),
+    createdAt: zod.iso.datetime({ offset: true }),
+})
+    .describe("One message the person sent, as an entry of the conversation's outline.");

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -24,6 +24,7 @@
  */
 import * as zod from "zod";
 export declare const threadResourceOrderVersionMin = 0;
+export declare const threadResourceMessageCountMin = 0;
 export declare const ThreadResource: zod.ZodObject<{
     id: zod.ZodString;
     role: zod.ZodEnum<{
@@ -109,6 +110,7 @@ export declare const ThreadResource: zod.ZodObject<{
     }, zod.z.core.$strict>;
     unread: zod.ZodBoolean;
     archived: zod.ZodBoolean;
+    messageCount: zod.ZodInt;
     createdAt: zod.z.ZodISODateTime;
     updatedAt: zod.z.ZodISODateTime;
 }, zod.z.core.$strict>;

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -33,6 +33,7 @@ import { ThreadStatus } from "./threadStatus.zod.js";
 import { TodoResource } from "./todoResource.zod.js";
 import { Usage } from "./usage.zod.js";
 export const threadResourceOrderVersionMin = 0;
+export const threadResourceMessageCountMin = 0;
 export const ThreadResource = zod
     .strictObject({
     id: zod.string(),
@@ -86,6 +87,10 @@ export const ThreadResource = zod
         .boolean()
         .describe("The assistant replied after the conversation was last marked read."),
     archived: zod.boolean(),
+    messageCount: zod
+        .int()
+        .min(threadResourceMessageCountMin)
+        .describe("How many messages the person has sent in this conversation, as listed by list-thread-messages."),
     createdAt: zod.iso.datetime({ offset: true }),
     updatedAt: zod.iso
         .datetime({ offset: true })

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -64,6 +64,7 @@ export declare const ThreadTurnListResponseBody: zod.ZodObject<{
             requests: zod.ZodInt;
             complete: zod.ZodBoolean;
         }, zod.z.core.$strict>;
+        streamingOutputTokens: zod.ZodInt;
         startedAt: zod.z.ZodISODateTime;
         firstTokenAt: zod.ZodNullable<zod.z.ZodISODateTime>;
         completedAt: zod.ZodNullable<zod.z.ZodISODateTime>;

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -24,6 +24,7 @@
  */
 import * as zod from "zod";
 export declare const threadTurnResourceToolCallsMin = 0;
+export declare const threadTurnResourceStreamingOutputTokensMin = 0;
 export declare const ThreadTurnResource: zod.ZodObject<{
     id: zod.ZodString;
     threadId: zod.ZodString;
@@ -64,6 +65,7 @@ export declare const ThreadTurnResource: zod.ZodObject<{
         requests: zod.ZodInt;
         complete: zod.ZodBoolean;
     }, zod.z.core.$strict>;
+    streamingOutputTokens: zod.ZodInt;
     startedAt: zod.z.ZodISODateTime;
     firstTokenAt: zod.ZodNullable<zod.z.ZodISODateTime>;
     completedAt: zod.ZodNullable<zod.z.ZodISODateTime>;

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -29,6 +29,7 @@ import { TurnStatus } from "./turnStatus.zod.js";
 import { TurnType } from "./turnType.zod.js";
 import { Usage } from "./usage.zod.js";
 export const threadTurnResourceToolCallsMin = 0;
+export const threadTurnResourceStreamingOutputTokensMin = 0;
 export const ThreadTurnResource = zod
     .strictObject({
     id: zod.string(),
@@ -56,6 +57,10 @@ export const ThreadTurnResource = zod
         .min(threadTurnResourceToolCallsMin)
         .describe("How many tools the turn called."),
     usage: Usage.describe("Tokens used by every model request of this turn, including title generation, review and compaction."),
+    streamingOutputTokens: zod
+        .int()
+        .min(threadTurnResourceStreamingOutputTokensMin)
+        .describe("An estimate of the output tokens of the model request in progress, which `usage` does not\ncount yet. It grows about once a second while the model writes and returns to 0 when the\nrequest ends and its exact usage is added. Show `usage.outputTokens` plus this while the turn\nruns."),
     startedAt: zod.iso.datetime({ offset: true }),
     firstTokenAt: zod.iso
         .datetime({ offset: true })

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -47,6 +47,7 @@ export declare const ToolCallResource: zod.ZodObject<{
     }, zod.z.core.$strict>, zod.ZodNull]>;
     approvalStatus: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"pending">, zod.ZodLiteral<"reviewing">, zod.ZodLiteral<"approved">, zod.ZodLiteral<"auto_approved">, zod.ZodLiteral<"declined">, zod.ZodLiteral<"unreviewed">, zod.ZodLiteral<null>]>>;
     approvalReason: zod.ZodNullable<zod.ZodString>;
+    approvalSource: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"user">, zod.ZodLiteral<"auto_review">, zod.ZodLiteral<"policy">, zod.ZodLiteral<null>]>>;
     decidedAt: zod.ZodNullable<zod.z.ZodISODateTime>;
     questions: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
         id: zod.ZodString;

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
@@ -52,6 +52,15 @@ export const ToolCallResource = zod.strictObject({
         .nullable()
         .describe("Whether the call needed a decision before it ran. Null for calls that need none.\n`auto_approved` was approved by the automatic reviewer."),
     approvalReason: zod.string().nullable(),
+    approvalSource: zod
+        .union([
+        zod.literal("user"),
+        zod.literal("auto_review"),
+        zod.literal("policy"),
+        zod.literal(null),
+    ])
+        .nullable()
+        .describe("Who decided the call. `user` is the person, in the console or a chat app; `auto_review` is\nthe automatic reviewer; `policy` is the tool itself, which cannot be called this way. Null\nwhen nobody decided, including calls that needed no decision."),
     decidedAt: zod.iso
         .datetime({ offset: true })
         .nullable()

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.

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

@@ -15,8 +15,8 @@
  * 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
- * over the WebSocket described under /api/v1/realtime/tickets. Slash commands such as /status and
- * /compact are listed by list-commands and work the same in the console and in chat apps.
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.