@leaflow/sdk 0.179.0 → 0.181.0

package/dist/assistant/v1/generated/functions.d.ts

@@ -15,14 +15,15 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.
  * OpenAPI spec version: 2.0.0
  */
-import type { AnswerQuestionRequestBody, BindingCodeResponseBody, BindingResource, ChannelResource, ChannelWithSecretResponseBody, CheckSenderParams, CompleteUploadRequestBody, CreateChannelRequestBody, CreateFolderRequestBody, CreateTaskRequestBody, CreateThreadRequestBody, CreateThreadResponseBody, CreateUploadRequestBody, DecideToolCallsRequestBody, ErrorResponse, FolderListResponseBody, FolderResource, LengthAwarePageBindingResource, LengthAwarePageChannelResource, ListBindingsParams, ListChannelRejectionsParams, ListChannelsParams, ListTaskRunsParams, ListThreadItemsParams, ListThreadMessagesParams, ListThreadTurnsParams, LoginResource, MemoryListResponseBody, MoveFolderRequestBody, OpenRealtimeParams, PlaceThreadRequestBody, PlatformListResponseBody, PutUploadPartHeaders, PutUploadPartParams, RealtimeExchange, RealtimeTicketResource, RejectionListResponseBody, ResumeThreadRequestBody, RevertRequestBody, RevertedCountResponseBody, RotateSecretRequestBody, SearchTasksRequestBody, SearchThreadsRequestBody, SendMessageRequestBody, SendMessageResponseBody, SenderCheckResource, SettingsResource, SkillEnabledRequestBody, SkillListResponseBody, SkillRequestBody, SkillResource, TaskListResponseBody, TaskResource, TaskRunListResponseBody, TaskRunResource, ThreadItemListResponseBody, ThreadItemResource, ThreadListResponseBody, ThreadMessageListResponseBody, ThreadResource, ThreadTurnListResponseBody, ToolResultRequestBody, TurnStartedResponseBody, UpdateChannelRequestBody, UpdateFolderRequestBody, UpdateSettingsRequestBody, UpdateTaskRequestBody, UpdateThreadRequestBody, UpdateUploadRequestBody, UploadAttachmentParams, UploadConfigurationResource, UploadListResponseBody, UploadPartResource, UploadResource, UploadedResource, VerifyCodeRequestBody, WebhookSecretResponseBody } from "./models.js";
+import type { AnswerQuestionRequestBody, BindingCodeResponseBody, BindingResource, ChannelResource, ChannelWithSecretResponseBody, CheckSenderParams, CompleteUploadRequestBody, CreateChannelRequestBody, CreateFolderRequestBody, CreateTaskRequestBody, CreateThreadRequestBody, CreateThreadResponseBody, CreateUploadRequestBody, DecideToolCallsRequestBody, ErrorResponse, FolderListResponseBody, FolderResource, LengthAwarePageBindingResource, LengthAwarePageChannelResource, ListBindingsParams, ListChannelRejectionsParams, ListChannelsParams, ListTaskRunsParams, ListThreadItemsParams, ListThreadMessagesParams, ListThreadTurnsParams, LoginResource, MemoryListResponseBody, MoveFolderRequestBody, PlaceThreadRequestBody, PlatformListResponseBody, PutUploadPartHeaders, PutUploadPartParams, RejectionListResponseBody, ResumeThreadRequestBody, RevertRequestBody, RevertedCountResponseBody, RotateSecretRequestBody, SearchTasksRequestBody, SearchThreadsRequestBody, SendMessageRequestBody, SendMessageResponseBody, SenderCheckResource, SettingsResource, SkillEnabledRequestBody, SkillListResponseBody, SkillRequestBody, SkillResource, TaskListResponseBody, TaskResource, TaskRunListResponseBody, TaskRunResource, ThreadItemListResponseBody, ThreadItemResource, ThreadListResponseBody, ThreadMessageListResponseBody, ThreadResource, ThreadTurnListResponseBody, ToolResultRequestBody, TurnStartedResponseBody, UpdateChannelRequestBody, UpdateFolderRequestBody, UpdateSettingsRequestBody, UpdateTaskRequestBody, UpdateThreadRequestBody, UpdateUploadRequestBody, UploadAttachmentParams, UploadConfigurationResource, UploadListResponseBody, UploadPartResource, UploadResource, UploadedResource, VerifyCodeRequestBody, WebhookSecretResponseBody } from "./models.js";
 export type HTTPStatusCode1xx = 100 | 101 | 102 | 103;
 export type HTTPStatusCode2xx = 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207;
 export type HTTPStatusCode3xx = 300 | 301 | 302 | 303 | 304 | 305 | 307 | 308;
@@ -944,61 +945,6 @@ export declare const getUpdateSettingsUrl: () => string;
  * @summary Update settings
  */
 export declare const updateSettings: (updateSettingsRequestBody: UpdateSettingsRequestBody, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<updateSettingsResponse>;
-export type createRealtimeTicketResponse201 = {
-    data: RealtimeTicketResource;
-    status: 201;
-};
-export type createRealtimeTicketResponseDefault = {
-    data: ErrorResponse;
-    status: Exclude<HTTPStatusCodes, 201>;
-};
-export type createRealtimeTicketResponseSuccess = createRealtimeTicketResponse201 & {
-    headers: Headers;
-};
-export type createRealtimeTicketResponseError = createRealtimeTicketResponseDefault & {
-    headers: Headers;
-};
-export type createRealtimeTicketResponse = createRealtimeTicketResponseSuccess | createRealtimeTicketResponseError;
-export declare const getCreateRealtimeTicketUrl: () => string;
-/**
- * Returns the address and a short-lived ticket for the realtime WebSocket. Open
- * `{url}?ticket={ticket}`; the ticket stands in for the bearer token, which a browser cannot set
- * on a WebSocket. One connection carries every subscription of a client.
- *
- * Messages are JSON text frames. The client sends `RealtimeClientMessage` and receives
- * `RealtimeServerMessage`. Subscribe to `workspace` for every conversation, folder and task of the
- * caller in this project, and to `thread:{id}` for the transcript of one conversation. A
- * transcript subscription takes the `streamCursor` from list-thread-items and replays what was
- * written after it; when the cursor is too old the server sends `resync` and the client reads the
- * items again.
- *
- * Reconnect with a new ticket after the connection closes. Ping at least every 30 seconds.
- * @summary Issue a realtime ticket
- */
-export declare const createRealtimeTicket: (options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<createRealtimeTicketResponse>;
-export type openRealtimeResponse200 = {
-    data: RealtimeExchange;
-    status: 200;
-};
-export type openRealtimeResponseDefault = {
-    data: ErrorResponse;
-    status: Exclude<HTTPStatusCodes, 200>;
-};
-export type openRealtimeResponseSuccess = openRealtimeResponse200 & {
-    headers: Headers;
-};
-export type openRealtimeResponseError = openRealtimeResponseDefault & {
-    headers: Headers;
-};
-export type openRealtimeResponse = openRealtimeResponseSuccess | openRealtimeResponseError;
-export declare const getOpenRealtimeUrl: (params: OpenRealtimeParams) => string;
-/**
- * Upgrades to a WebSocket. The ticket from create-realtime-ticket authenticates the connection;
- * a missing, expired or foreign ticket closes it with code 4401. The 200 response documents the
- * message a client receives on the socket; the endpoint never answers with a plain HTTP body.
- * @summary Open the realtime WebSocket
- */
-export declare const openRealtime: (params: OpenRealtimeParams, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<openRealtimeResponse>;
 export type uploadAttachmentResponse201 = {
     data: UploadedResource;
     status: 201;
@@ -1719,3 +1665,24 @@ export declare const getSubmitWeixinVerifyCodeUrl: (login: string) => string;
  * @summary Submit a login verification code
  */
 export declare const submitWeixinVerifyCode: (login: string, verifyCodeRequestBody: VerifyCodeRequestBody, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<submitWeixinVerifyCodeResponse>;
+export type renewThreadPresenceResponse204 = {
+    data: void;
+    status: 204;
+};
+export type renewThreadPresenceResponseDefault = {
+    data: ErrorResponse;
+    status: Exclude<HTTPStatusCodes, 204>;
+};
+export type renewThreadPresenceResponseSuccess = renewThreadPresenceResponse204 & {
+    headers: Headers;
+};
+export type renewThreadPresenceResponseError = renewThreadPresenceResponseDefault & {
+    headers: Headers;
+};
+export type renewThreadPresenceResponse = renewThreadPresenceResponseSuccess | renewThreadPresenceResponseError;
+export declare const getRenewThreadPresenceUrl: (thread: string) => string;
+/**
+ * Renews an already announced browser client while the thread is open. It does not create or replace the client catalogue.
+ * @summary Renew client presence
+ */
+export declare const renewThreadPresence: (thread: string, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<renewThreadPresenceResponse>;

package/dist/assistant/v1/generated/functions.js

@@ -1048,60 +1048,6 @@ export const updateSettings = async (updateSettingsRequestBody, options, fetchFn
     const data = body ? JSON.parse(body) : {};
     return { data, status: res.status, headers: res.headers };
 };
-export const getCreateRealtimeTicketUrl = () => {
-    return `https://assistant.leaflow.cloud/api/v1/realtime/tickets`;
-};
-/**
- * Returns the address and a short-lived ticket for the realtime WebSocket. Open
- * `{url}?ticket={ticket}`; the ticket stands in for the bearer token, which a browser cannot set
- * on a WebSocket. One connection carries every subscription of a client.
- *
- * Messages are JSON text frames. The client sends `RealtimeClientMessage` and receives
- * `RealtimeServerMessage`. Subscribe to `workspace` for every conversation, folder and task of the
- * caller in this project, and to `thread:{id}` for the transcript of one conversation. A
- * transcript subscription takes the `streamCursor` from list-thread-items and replays what was
- * written after it; when the cursor is too old the server sends `resync` and the client reads the
- * items again.
- *
- * Reconnect with a new ticket after the connection closes. Ping at least every 30 seconds.
- * @summary Issue a realtime ticket
- */
-export const createRealtimeTicket = async (options, fetchFn) => {
-    const res = await (fetchFn ?? fetch)(getCreateRealtimeTicketUrl(), {
-        ...options,
-        method: "POST",
-    });
-    const body = [204, 205, 304].includes(res.status) ? null : await res.text();
-    const data = body ? JSON.parse(body) : {};
-    return { data, status: res.status, headers: res.headers };
-};
-export const getOpenRealtimeUrl = (params) => {
-    const normalizedParams = new URLSearchParams();
-    Object.entries(params || {}).forEach(([key, value]) => {
-        if (value !== undefined) {
-            normalizedParams.append(key, value === null ? "null" : String(value));
-        }
-    });
-    const stringifiedParams = normalizedParams.toString();
-    return stringifiedParams.length > 0
-        ? `https://assistant.leaflow.cloud/api/v1/realtime?${stringifiedParams}`
-        : `https://assistant.leaflow.cloud/api/v1/realtime`;
-};
-/**
- * Upgrades to a WebSocket. The ticket from create-realtime-ticket authenticates the connection;
- * a missing, expired or foreign ticket closes it with code 4401. The 200 response documents the
- * message a client receives on the socket; the endpoint never answers with a plain HTTP body.
- * @summary Open the realtime WebSocket
- */
-export const openRealtime = async (params, options, fetchFn) => {
-    const res = await (fetchFn ?? fetch)(getOpenRealtimeUrl(params), {
-        ...options,
-        method: "GET",
-    });
-    const body = [204, 205, 304].includes(res.status) ? null : await res.text();
-    const data = body ? JSON.parse(body) : {};
-    return { data, status: res.status, headers: res.headers };
-};
 export const getUploadAttachmentUrl = (params) => {
     const normalizedParams = new URLSearchParams();
     Object.entries(params || {}).forEach(([key, value]) => {
@@ -1897,3 +1843,19 @@ export const submitWeixinVerifyCode = async (login, verifyCodeRequestBody, optio
     const data = body ? JSON.parse(body) : {};
     return { data, status: res.status, headers: res.headers };
 };
+export const getRenewThreadPresenceUrl = (thread) => {
+    return `https://assistant.leaflow.cloud/api/v1/threads/${encodeURIComponent(String(thread))}/presence`;
+};
+/**
+ * Renews an already announced browser client while the thread is open. It does not create or replace the client catalogue.
+ * @summary Renew client presence
+ */
+export const renewThreadPresence = async (thread, options, fetchFn) => {
+    const res = await (fetchFn ?? fetch)(getRenewThreadPresenceUrl(thread), {
+        ...options,
+        method: "POST",
+    });
+    const body = [204, 205, 304].includes(res.status) ? null : await res.text();
+    const data = body ? JSON.parse(body) : undefined;
+    return { data, status: res.status, headers: res.headers };
+};

package/dist/assistant/v1/generated/models.d.ts

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.
@@ -1431,103 +1432,6 @@ export interface UpdateSettingsRequestBody {
     defaultModelId?: string | null;
     defaultReasoningEffort?: ReasoningEffort | null;
 }
-export interface RealtimeTicketResource {
-    /** The WebSocket address, absolute or relative to the API origin. */
-    url: string;
-    ticket: string;
-    expiresAt: string;
-}
-export type RealtimeClientMessageType = (typeof RealtimeClientMessageType)[keyof typeof RealtimeClientMessageType];
-export declare const RealtimeClientMessageType: {
-    readonly subscribe: "subscribe";
-    readonly unsubscribe: "unsubscribe";
-    readonly ping: "ping";
-};
-/**
- * A message from the client. `type` determines which fields apply.
- */
-export interface RealtimeClientMessage {
-    type: RealtimeClientMessageType;
-    /**
-     * `workspace` or `thread:{id}`. For subscribe and unsubscribe.
-     * @maxLength 128
-     */
-    topic?: string;
-    /**
-     * For a `thread:{id}` subscription, the `streamCursor` to replay from.
-     * @maxLength 128
-     */
-    cursor?: string;
-}
-export type RealtimeServerMessageType = (typeof RealtimeServerMessageType)[keyof typeof RealtimeServerMessageType];
-export declare const RealtimeServerMessageType: {
-    readonly subscribed: "subscribed";
-    readonly unsubscribed: "unsubscribed";
-    readonly threadupdated: "thread.updated";
-    readonly threaddeleted: "thread.deleted";
-    readonly turnupdated: "turn.updated";
-    readonly folderupdated: "folder.updated";
-    readonly folderdeleted: "folder.deleted";
-    readonly taskupdated: "task.updated";
-    readonly taskdeleted: "task.deleted";
-    readonly itemframe: "item.frame";
-    readonly resync: "resync";
-    readonly error: "error";
-    readonly pong: "pong";
-};
-export type ItemFrameOp = (typeof ItemFrameOp)[keyof typeof ItemFrameOp];
-export declare const ItemFrameOp: {
-    readonly add: "add";
-    readonly set: "set";
-    readonly append: "append";
-};
-/**
- * An edit to the transcript as returned by list-thread-items. `path` is a JSON Pointer under
- * `/items`: `add` appends `value` to `/items` or replaces the item with the same id, `set`
- * replaces the value at `path`, and `append` concatenates the string `value` to the string at
- * `path`, which is how answer text streams in.
- */
-export interface ItemFrame {
-    path: string;
-    op: ItemFrameOp;
-    value: unknown;
-}
-/**
- * A message from the server. `type` determines which fields apply:
- *
- * - `subscribed` / `unsubscribed` — `topic`
- * - `thread.updated` — `thread`; `thread.deleted` — `threadId`
- * - `turn.updated` — `turn`, sent while a turn runs so its usage can be shown live
- * - `folder.updated` — `folder`; `folder.deleted` — `folderId`
- * - `task.updated` — `task`; `task.deleted` — `taskId`
- * - `item.frame` — `threadId`, `cursor` and `frame`, an edit to the transcript
- * - `resync` — `topic`; the client lost events and reads the current state again
- * - `error` — `code` and `message`
- * - `pong`
- */
-export interface RealtimeServerMessage {
-    type: RealtimeServerMessageType;
-    topic?: string;
-    thread?: ThreadResource;
-    threadId?: string;
-    turn?: ThreadTurnResource;
-    folder?: FolderResource;
-    folderId?: string;
-    task?: TaskResource;
-    taskId?: string;
-    /** For `item.frame`. Resubscribe from this cursor to continue after a reconnect. */
-    cursor?: string;
-    frame?: ItemFrame;
-    code?: string;
-    message?: string;
-}
-/**
- * Both directions of the WebSocket protocol, for code generation.
- */
-export interface RealtimeExchange {
-    client: RealtimeClientMessage;
-    server: RealtimeServerMessage;
-}
 /**
  * How the assistant will see this file.
  *
@@ -2113,12 +2017,6 @@ export type ListTaskRunsParams = {
      */
     limit?: number;
 };
-export type OpenRealtimeParams = {
-    /**
-     * @maxLength 4096
-     */
-    ticket: string;
-};
 export type UploadAttachmentParams = {
     /**
      * The name to show and to give the assistant. Images do not need one; anything else does, because the name is most of what says what the file is. Falls back to a generated name.

package/dist/assistant/v1/generated/models.js

@@ -172,31 +172,6 @@ export const DefaultModelResourceSource = {
     user: "user",
     catalog: "catalog",
 };
-export const RealtimeClientMessageType = {
-    subscribe: "subscribe",
-    unsubscribe: "unsubscribe",
-    ping: "ping",
-};
-export const RealtimeServerMessageType = {
-    subscribed: "subscribed",
-    unsubscribed: "unsubscribed",
-    threadupdated: "thread.updated",
-    threaddeleted: "thread.deleted",
-    turnupdated: "turn.updated",
-    folderupdated: "folder.updated",
-    folderdeleted: "folder.deleted",
-    taskupdated: "task.updated",
-    taskdeleted: "task.deleted",
-    itemframe: "item.frame",
-    resync: "resync",
-    error: "error",
-    pong: "pong",
-};
-export const ItemFrameOp = {
-    add: "add",
-    set: "set",
-    append: "append",
-};
 export const UploadedResourceType = {
     image: "image",
     text: "text",

package/dist/assistant/v1/generated/schemas.zod.d.ts

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.
@@ -617,16 +618,6 @@ export declare const UpdateSettingsBody: zod.ZodObject<{
         medium: "medium";
     }>, zod.ZodNull]>>;
 }, zod.z.core.$strict>;
-/**
- * Upgrades to a WebSocket. The ticket from create-realtime-ticket authenticates the connection;
- * a missing, expired or foreign ticket closes it with code 4401. The 200 response documents the
- * message a client receives on the socket; the endpoint never answers with a plain HTTP body.
- * @summary Open the realtime WebSocket
- */
-export declare const openRealtimeQueryTicketMax = 4096;
-export declare const OpenRealtimeQueryParams: zod.ZodObject<{
-    ticket: zod.ZodString;
-}, zod.z.core.$strict>;
 /**
  * The body is the file bytes themselves, not multipart, one file per request. The type is determined from the content, not from Content-Type or from the name. Put the returned id in attachmentIds when sending a message.
  *
@@ -912,3 +903,11 @@ export declare const SubmitWeixinVerifyCodeParams: zod.ZodObject<{
 export declare const SubmitWeixinVerifyCodeBody: zod.ZodObject<{
     code: zod.ZodString;
 }, zod.z.core.$strict>;
+/**
+ * Renews an already announced browser client while the thread is open. It does not create or replace the client catalogue.
+ * @summary Renew client presence
+ */
+export declare const renewThreadPresencePathThreadMax = 64;
+export declare const RenewThreadPresenceParams: zod.ZodObject<{
+    thread: zod.ZodString;
+}, zod.z.core.$strict>;

package/dist/assistant/v1/generated/schemas.zod.js

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.
@@ -567,16 +568,6 @@ export const GetTaskRunParams = zod.strictObject({
  * @summary Update settings
  */
 export const UpdateSettingsBody = UpdateSettingsRequestBody;
-/**
- * Upgrades to a WebSocket. The ticket from create-realtime-ticket authenticates the connection;
- * a missing, expired or foreign ticket closes it with code 4401. The 200 response documents the
- * message a client receives on the socket; the endpoint never answers with a plain HTTP body.
- * @summary Open the realtime WebSocket
- */
-export const openRealtimeQueryTicketMax = 4096;
-export const OpenRealtimeQueryParams = zod.strictObject({
-    ticket: zod.string().max(openRealtimeQueryTicketMax),
-});
 /**
  * The body is the file bytes themselves, not multipart, one file per request. The type is determined from the content, not from Content-Type or from the name. Put the returned id in attachmentIds when sending a message.
  *
@@ -853,3 +844,14 @@ export const SubmitWeixinVerifyCodeParams = zod.strictObject({
     login: zod.uuid(),
 });
 export const SubmitWeixinVerifyCodeBody = VerifyCodeRequestBody;
+/**
+ * Renews an already announced browser client while the thread is open. It does not create or replace the client catalogue.
+ * @summary Renew client presence
+ */
+export const renewThreadPresencePathThreadMax = 64;
+export const RenewThreadPresenceParams = zod.strictObject({
+    thread: zod
+        .string()
+        .max(renewThreadPresencePathThreadMax)
+        .describe("A thread id. Subagents are threads as well."),
+});

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.

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

@@ -15,8 +15,9 @@
  * 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. list-thread-messages outlines the
- * person's messages for navigating a long conversation.
+ * 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 attachment id in a message.