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

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

@@ -15,14 +15,14 @@
  * 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 type { AnswerQuestionRequestBody, BindingCodeResponseBody, BindingResource, ChannelResource, ChannelWithSecretResponseBody, CheckSenderParams, CommandListResponseBody, CommandResultResource, CompleteUploadRequestBody, CreateChannelRequestBody, CreateFolderRequestBody, CreateTaskRequestBody, CreateThreadRequestBody, CreateThreadResponseBody, CreateUploadRequestBody, DecideToolCallsRequestBody, ErrorResponse, FolderListResponseBody, FolderResource, LengthAwarePageBindingResource, LengthAwarePageChannelResource, ListBindingsParams, ListChannelRejectionsParams, ListChannelsParams, ListTaskRunsParams, ListThreadItemsParams, ListThreadTurnsParams, LoginResource, MemoryListResponseBody, MoveFolderRequestBody, OpenRealtimeParams, PlaceThreadRequestBody, PlatformListResponseBody, PutUploadPartHeaders, PutUploadPartParams, RealtimeExchange, RealtimeTicketResource, RejectionListResponseBody, ResumeThreadRequestBody, RevertRequestBody, RevertedCountResponseBody, RotateSecretRequestBody, RunCommandRequestBody, SearchTasksRequestBody, SearchThreadsRequestBody, SendMessageRequestBody, SendMessageResponseBody, SenderCheckResource, SettingsResource, SkillEnabledRequestBody, SkillListResponseBody, SkillRequestBody, SkillResource, TaskListResponseBody, TaskResource, TaskRunListResponseBody, TaskRunResource, ThreadItemListResponseBody, ThreadItemResource, ThreadListResponseBody, 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, 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";
 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;
@@ -339,6 +339,34 @@ export declare const getGetThreadItemUrl: (thread: string, item: string) => stri
  * @summary Get a transcript item
  */
 export declare const getThreadItem: (thread: string, item: string, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<getThreadItemResponse>;
+export type listThreadMessagesResponse200 = {
+    data: ThreadMessageListResponseBody;
+    status: 200;
+};
+export type listThreadMessagesResponseDefault = {
+    data: ErrorResponse;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type listThreadMessagesResponseSuccess = listThreadMessagesResponse200 & {
+    headers: Headers;
+};
+export type listThreadMessagesResponseError = listThreadMessagesResponseDefault & {
+    headers: Headers;
+};
+export type listThreadMessagesResponse = listThreadMessagesResponseSuccess | listThreadMessagesResponseError;
+export declare const getListThreadMessagesUrl: (thread: string, params?: ListThreadMessagesParams) => string;
+/**
+ * An outline of the messages the person sent in this conversation, from the console or a chat
+ * app, oldest first: what a timeline needs to place and preview every message without reading
+ * the transcript. Replies, tool calls and messages from subagents, tasks or other conversations
+ * are not included, nor are reverted messages or messages waiting in the queue.
+ *
+ * `index` is the message's position, from 1, and matches `messageIndex` on the transcript item.
+ * Read the message N with `offset` N-1. Open it in the transcript with list-thread-items
+ * `around` its `ordinal`. `total` equals the thread's `messageCount`.
+ * @summary List the person's messages
+ */
+export declare const listThreadMessages: (thread: string, params?: ListThreadMessagesParams, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<listThreadMessagesResponse>;
 export type sendMessageResponse202 = {
     data: SendMessageResponseBody;
     status: 202;
@@ -465,56 +493,6 @@ export declare const getListThreadTurnsUrl: (thread: string, params?: ListThread
  * @summary List turns
  */
 export declare const listThreadTurns: (thread: string, params?: ListThreadTurnsParams, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<listThreadTurnsResponse>;
-export type listCommandsResponse200 = {
-    data: CommandListResponseBody;
-    status: 200;
-};
-export type listCommandsResponseDefault = {
-    data: ErrorResponse;
-    status: Exclude<HTTPStatusCodes, 200>;
-};
-export type listCommandsResponseSuccess = listCommandsResponse200 & {
-    headers: Headers;
-};
-export type listCommandsResponseError = listCommandsResponseDefault & {
-    headers: Headers;
-};
-export type listCommandsResponse = listCommandsResponseSuccess | listCommandsResponseError;
-export declare const getListCommandsUrl: () => string;
-/**
- * The slash commands a person can type in a conversation, such as /status or /compact. The same
- * commands work in the console and in chat apps, so a client builds its command menu from this
- * list.
- * @summary List commands
- */
-export declare const listCommands: (options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<listCommandsResponse>;
-export type runCommandResponse200 = {
-    data: CommandResultResource;
-    status: 200;
-};
-export type runCommandResponseDefault = {
-    data: ErrorResponse;
-    status: Exclude<HTTPStatusCodes, 200>;
-};
-export type runCommandResponseSuccess = runCommandResponse200 & {
-    headers: Headers;
-};
-export type runCommandResponseError = runCommandResponseDefault & {
-    headers: Headers;
-};
-export type runCommandResponse = runCommandResponseSuccess | runCommandResponseError;
-export declare const getRunCommandUrl: (thread: string) => string;
-/**
- * Runs a slash command against the conversation. Commands act directly and never reach the model.
- * The result carries a plain-text `message`, which is what a chat app shows, and structured fields
- * for clients that render more, such as `status` for /status.
- *
- * /new is carried out by the client, which opens an empty conversation, and fails here with 422
- * and code COMMAND_CLIENT_ONLY. Fails with 404 and code COMMAND_NOT_FOUND for an unknown command,
- * and with 422 and code COMMAND_ARGUMENTS_INVALID when the arguments do not fit.
- * @summary Run a command
- */
-export declare const runCommand: (thread: string, runCommandRequestBody: RunCommandRequestBody, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<runCommandResponse>;
 export type listFoldersResponse200 = {
     data: FolderListResponseBody;
     status: 200;

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

@@ -342,6 +342,38 @@ export const getThreadItem = async (thread, item, options, fetchFn) => {
     const data = body ? JSON.parse(body) : {};
     return { data, status: res.status, headers: res.headers };
 };
+export const getListThreadMessagesUrl = (thread, 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/threads/${encodeURIComponent(String(thread))}/messages?${stringifiedParams}`
+        : `https://assistant.leaflow.cloud/api/v1/threads/${encodeURIComponent(String(thread))}/messages`;
+};
+/**
+ * An outline of the messages the person sent in this conversation, from the console or a chat
+ * app, oldest first: what a timeline needs to place and preview every message without reading
+ * the transcript. Replies, tool calls and messages from subagents, tasks or other conversations
+ * are not included, nor are reverted messages or messages waiting in the queue.
+ *
+ * `index` is the message's position, from 1, and matches `messageIndex` on the transcript item.
+ * Read the message N with `offset` N-1. Open it in the transcript with list-thread-items
+ * `around` its `ordinal`. `total` equals the thread's `messageCount`.
+ * @summary List the person's messages
+ */
+export const listThreadMessages = async (thread, params, options, fetchFn) => {
+    const res = await (fetchFn ?? fetch)(getListThreadMessagesUrl(thread, 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 getSendMessageUrl = (thread) => {
     return `https://assistant.leaflow.cloud/api/v1/threads/${encodeURIComponent(String(thread))}/messages`;
 };
@@ -520,63 +552,6 @@ export const listThreadTurns = async (thread, params, options, fetchFn) => {
     const data = body ? JSON.parse(body) : {};
     return { data, status: res.status, headers: res.headers };
 };
-export const getListCommandsUrl = () => {
-    return `https://assistant.leaflow.cloud/api/v1/commands`;
-};
-/**
- * The slash commands a person can type in a conversation, such as /status or /compact. The same
- * commands work in the console and in chat apps, so a client builds its command menu from this
- * list.
- * @summary List commands
- */
-export const listCommands = async (options, fetchFn) => {
-    const res = await (fetchFn ?? fetch)(getListCommandsUrl(), {
-        ...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 getRunCommandUrl = (thread) => {
-    return `https://assistant.leaflow.cloud/api/v1/threads/${encodeURIComponent(String(thread))}/commands`;
-};
-/**
- * Runs a slash command against the conversation. Commands act directly and never reach the model.
- * The result carries a plain-text `message`, which is what a chat app shows, and structured fields
- * for clients that render more, such as `status` for /status.
- *
- * /new is carried out by the client, which opens an empty conversation, and fails here with 422
- * and code COMMAND_CLIENT_ONLY. Fails with 404 and code COMMAND_NOT_FOUND for an unknown command,
- * and with 422 and code COMMAND_ARGUMENTS_INVALID when the arguments do not fit.
- * @summary Run a command
- */
-export const runCommand = async (thread, runCommandRequestBody, options, fetchFn) => {
-    const getHeaders = (h) => {
-        if (!h)
-            return {};
-        if (h instanceof Headers)
-            return Object.fromEntries(h.entries());
-        if (Symbol.iterator in h) {
-            return Object.fromEntries(Array.from(h, (entry) => Array.from(entry)));
-        }
-        const headers = {};
-        for (const [name, value] of Object.entries(h)) {
-            if (value !== undefined)
-                headers[name] = value;
-        }
-        return headers;
-    };
-    const res = await (fetchFn ?? fetch)(getRunCommandUrl(thread), {
-        ...options,
-        method: "POST",
-        headers: { "Content-Type": "application/json", ...getHeaders(options?.headers) },
-        body: JSON.stringify(runCommandRequestBody),
-    });
-    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 getListFoldersUrl = () => {
     return `https://assistant.leaflow.cloud/api/v1/folders`;
 };

package/dist/assistant/v1/generated/models.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.
@@ -265,6 +265,11 @@ export interface ThreadResource {
     /** The assistant replied after the conversation was last marked read. */
     unread: boolean;
     archived: boolean;
+    /**
+     * How many messages the person has sent in this conversation, as listed by list-thread-messages.
+     * @minimum 0
+     */
+    messageCount: number;
     createdAt: string;
     /** The last activity. Renaming or moving the conversation does not change it. */
     updatedAt: string;
@@ -614,6 +619,14 @@ export interface ThreadTurnResource {
     toolCalls: number;
     /** Tokens used by every model request of this turn, including title generation, review and compaction. */
     usage: Usage;
+    /**
+     * An estimate of the output tokens of the model request in progress, which `usage` does not
+     * count yet. It grows about once a second while the model writes and returns to 0 when the
+     * request ends and its exact usage is added. Show `usage.outputTokens` plus this while the turn
+     * runs.
+     * @minimum 0
+     */
+    streamingOutputTokens: number;
     startedAt: string;
     /**
      * When the first output token arrived. Null until then.
@@ -788,6 +801,18 @@ export declare const ToolCallResourceApprovalStatus: {
     readonly declined: "declined";
     readonly unreviewed: "unreviewed";
 };
+/**
+ * Who decided the call. `user` is the person, in the console or a chat app; `auto_review` is
+ * the automatic reviewer; `policy` is the tool itself, which cannot be called this way. Null
+ * when nobody decided, including calls that needed no decision.
+ * @nullable
+ */
+export type ToolCallResourceApprovalSource = (typeof ToolCallResourceApprovalSource)[keyof typeof ToolCallResourceApprovalSource] | null;
+export declare const ToolCallResourceApprovalSource: {
+    readonly user: "user";
+    readonly auto_review: "auto_review";
+    readonly policy: "policy";
+};
 export interface ChoiceResource {
     label: string;
     description: string;
@@ -832,6 +857,13 @@ export interface ToolCallResource {
     approvalStatus: ToolCallResourceApprovalStatus;
     /** @nullable */
     approvalReason: string | null;
+    /**
+     * Who decided the call. `user` is the person, in the console or a chat app; `auto_review` is
+     * the automatic reviewer; `policy` is the tool itself, which cannot be called this way. Null
+     * when nobody decided, including calls that needed no decision.
+     * @nullable
+     */
+    approvalSource: ToolCallResourceApprovalSource;
     /**
      * When a person or the reviewer decided the call or answered its questions.
      * @nullable
@@ -901,8 +933,47 @@ export interface ThreadItemResource {
     clientContext: ClientContextPart[];
     /** The call, for a `tool_call` item. Null for other items. */
     toolCall: ToolCallResource | null;
+    /**
+     * The position of a `user_message` among the person's messages, from 1, as in
+     * list-thread-messages. Null for other items, and for messages that are reverted or waiting
+     * in the queue.
+     * @minimum 1
+     * @nullable
+     */
+    messageIndex: number | null;
+    createdAt: string;
+}
+/**
+ * One message the person sent, as an entry of the conversation's outline.
+ */
+export interface ThreadMessageResource {
+    /** The transcript item. */
+    id: string;
+    /**
+     * The position among the person's messages, from 1.
+     * @minimum 1
+     */
+    index: number;
+    /** The item's position in the transcript, for list-thread-items `around`. */
+    ordinal: number;
+    turnId: string;
+    /** The beginning of the message's text, at most 120 characters. Empty for a message with only attachments. */
+    preview: string;
+    /**
+     * How many files the message carries.
+     * @minimum 0
+     */
+    attachments: number;
     createdAt: string;
 }
+export interface ThreadMessageListResponseBody {
+    messages: ThreadMessageResource[];
+    /**
+     * How many messages the person has sent in this conversation, the same as the thread's `messageCount`.
+     * @minimum 0
+     */
+    total: number;
+}
 export interface ThreadItemListResponseBody {
     /** Oldest first. */
     items: ThreadItemResource[];
@@ -983,63 +1054,6 @@ export interface ToolResultRequestBody {
      */
     nextCursor?: string;
 }
-export interface CommandResource {
-    /** The command without the slash, for example `status`. */
-    name: string;
-    /** Other names that run the same command. */
-    aliases: string[];
-    description: string;
-    /** How to write the arguments, for example `<model id>`. Empty when the command takes none. */
-    argumentHint: string;
-}
-export interface CommandListResponseBody {
-    commands: CommandResource[];
-}
-export interface RunCommandRequestBody {
-    /**
-     * The command or one of its aliases, without the slash.
-     * @minLength 1
-     * @maxLength 32
-     */
-    name: string;
-    /**
-     * Everything typed after the command name.
-     * @maxLength 2000
-     */
-    arguments?: string;
-}
-/**
- * The conversation's configuration and resource use, as shown by /status.
- */
-export interface StatusReportResource {
-    threadId: string;
-    modelId: string;
-    /** The model's display name in the Canopy catalogue. Falls back to modelId. */
-    modelName: string;
-    reasoningEffort: ReasoningEffort | null;
-    approvalMode: ApprovalMode;
-    status: ThreadStatus;
-    context: ContextUsageResource;
-    /** Token usage over the whole conversation. */
-    usage: Usage;
-    /** The most recent turn with its own usage. Null before the first message. */
-    lastTurn: ThreadTurnResource | null;
-}
-export interface CommandResultResource {
-    /** The command that ran, after resolving aliases. */
-    name: string;
-    /** The result as plain text. */
-    message: string;
-    /** The conversation after the command. */
-    thread: ThreadResource | null;
-    /**
-     * The turn the command started, for example the compaction turn of /compact.
-     * @nullable
-     */
-    turnId: string | null;
-    /** Set by /status. */
-    status: StatusReportResource | null;
-}
 /**
  * `inbox` holds the conversations nobody filed. Each caller has one per project.
  */
@@ -1209,6 +1223,16 @@ export declare const TaskRunResourceStatus: {
     readonly cancelled: "cancelled";
     readonly timed_out: "timed_out";
 };
+/**
+ * How the run started: `schedule` by the task's own trigger, including a task set to run now;
+ * `manual` by a person running it outside its schedule; `assistant` by the assistant.
+ */
+export type TaskRunResourceTrigger = (typeof TaskRunResourceTrigger)[keyof typeof TaskRunResourceTrigger];
+export declare const TaskRunResourceTrigger: {
+    readonly schedule: "schedule";
+    readonly manual: "manual";
+    readonly assistant: "assistant";
+};
 export interface TaskRunResource {
     id: string;
     taskId: string;
@@ -1232,6 +1256,11 @@ export interface TaskRunResource {
      * @nullable
      */
     errorCode: string | null;
+    /**
+     * How the run started: `schedule` by the task's own trigger, including a task set to run now;
+     * `manual` by a person running it outside its schedule; `assistant` by the assistant.
+     */
+    trigger: TaskRunResourceTrigger;
 }
 export interface TaskResource {
     id: string;
@@ -1995,6 +2024,20 @@ export type ListThreadItemsParams = {
      */
     turns?: number;
 };
+export type ListThreadMessagesParams = {
+    /**
+     * Items to skip. Defaults to 0; at most 10000.
+     * @minimum 0
+     * @maximum 10000
+     */
+    offset?: number;
+    /**
+     * Items returned in this page. Defaults to 50; at most 200.
+     * @minimum 1
+     * @maximum 200
+     */
+    limit?: number;
+};
 export type ListThreadTurnsParams = {
     /**
      * @minItems 1

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

@@ -110,6 +110,11 @@ export const ToolCallResourceApprovalStatus = {
     declined: "declined",
     unreviewed: "unreviewed",
 };
+export const ToolCallResourceApprovalSource = {
+    user: "user",
+    auto_review: "auto_review",
+    policy: "policy",
+};
 export const FolderResourceType = {
     inbox: "inbox",
     custom: "custom",
@@ -142,6 +147,11 @@ export const TaskRunResourceStatus = {
     cancelled: "cancelled",
     timed_out: "timed_out",
 };
+export const TaskRunResourceTrigger = {
+    schedule: "schedule",
+    manual: "manual",
+    assistant: "assistant",
+};
 export const SearchTasksRequestBodyStatus = {
     active: "active",
     paused: "paused",

package/dist/assistant/v1/generated/schemas.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.
@@ -231,6 +231,30 @@ export declare const GetThreadItemParams: zod.ZodObject<{
     thread: zod.ZodString;
     item: zod.ZodString;
 }, zod.z.core.$strict>;
+/**
+ * An outline of the messages the person sent in this conversation, from the console or a chat
+ * app, oldest first: what a timeline needs to place and preview every message without reading
+ * the transcript. Replies, tool calls and messages from subagents, tasks or other conversations
+ * are not included, nor are reverted messages or messages waiting in the queue.
+ *
+ * `index` is the message's position, from 1, and matches `messageIndex` on the transcript item.
+ * Read the message N with `offset` N-1. Open it in the transcript with list-thread-items
+ * `around` its `ordinal`. `total` equals the thread's `messageCount`.
+ * @summary List the person's messages
+ */
+export declare const listThreadMessagesPathThreadMax = 64;
+export declare const ListThreadMessagesParams: zod.ZodObject<{
+    thread: zod.ZodString;
+}, zod.z.core.$strict>;
+export declare const listThreadMessagesQueryOffsetDefault = 0;
+export declare const listThreadMessagesQueryOffsetMin = 0;
+export declare const listThreadMessagesQueryOffsetMax = 10000;
+export declare const listThreadMessagesQueryLimitDefault = 50;
+export declare const listThreadMessagesQueryLimitMax = 200;
+export declare const ListThreadMessagesQueryParams: zod.ZodObject<{
+    offset: zod.ZodDefault<zod.ZodInt>;
+    limit: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;
 /**
  * Starts a turn and returns at once; a turn can run for tens of minutes and its progress arrives
  * on /api/v1/realtime. Sending while the assistant is working is allowed: the message is queued
@@ -345,24 +369,6 @@ export declare const ListThreadTurnsQueryParams: zod.ZodObject<{
     cursor: zod.ZodOptional<zod.ZodString>;
     limit: zod.ZodDefault<zod.ZodInt>;
 }, zod.z.core.$strict>;
-/**
- * Runs a slash command against the conversation. Commands act directly and never reach the model.
- * The result carries a plain-text `message`, which is what a chat app shows, and structured fields
- * for clients that render more, such as `status` for /status.
- *
- * /new is carried out by the client, which opens an empty conversation, and fails here with 422
- * and code COMMAND_CLIENT_ONLY. Fails with 404 and code COMMAND_NOT_FOUND for an unknown command,
- * and with 422 and code COMMAND_ARGUMENTS_INVALID when the arguments do not fit.
- * @summary Run a command
- */
-export declare const runCommandPathThreadMax = 64;
-export declare const RunCommandParams: zod.ZodObject<{
-    thread: zod.ZodString;
-}, zod.z.core.$strict>;
-export declare const RunCommandBody: zod.ZodObject<{
-    name: zod.ZodString;
-    arguments: zod.ZodOptional<zod.ZodString>;
-}, zod.z.core.$strict>;
 /**
  * A folder groups conversations on the board and does nothing else: the assistant is never told
  * which folder a conversation is in. New folders go after the existing ones.

package/dist/assistant/v1/generated/schemas.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.
@@ -36,7 +36,6 @@ import { PlaceThreadRequestBody } from "./validators/placeThreadRequestBody.zod.
 import { ResumeThreadRequestBody } from "./validators/resumeThreadRequestBody.zod.js";
 import { RevertRequestBody } from "./validators/revertRequestBody.zod.js";
 import { RotateSecretRequestBody } from "./validators/rotateSecretRequestBody.zod.js";
-import { RunCommandRequestBody } from "./validators/runCommandRequestBody.zod.js";
 import { SendMessageRequestBody } from "./validators/sendMessageRequestBody.zod.js";
 import { SkillEnabledRequestBody } from "./validators/skillEnabledRequestBody.zod.js";
 import { SkillRequestBody } from "./validators/skillRequestBody.zod.js";
@@ -246,6 +245,43 @@ export const GetThreadItemParams = zod.strictObject({
         .describe("A thread id. Subagents are threads as well."),
     item: zod.string().max(getThreadItemPathItemMax).describe("A transcript item id."),
 });
+/**
+ * An outline of the messages the person sent in this conversation, from the console or a chat
+ * app, oldest first: what a timeline needs to place and preview every message without reading
+ * the transcript. Replies, tool calls and messages from subagents, tasks or other conversations
+ * are not included, nor are reverted messages or messages waiting in the queue.
+ *
+ * `index` is the message's position, from 1, and matches `messageIndex` on the transcript item.
+ * Read the message N with `offset` N-1. Open it in the transcript with list-thread-items
+ * `around` its `ordinal`. `total` equals the thread's `messageCount`.
+ * @summary List the person's messages
+ */
+export const listThreadMessagesPathThreadMax = 64;
+export const ListThreadMessagesParams = zod.strictObject({
+    thread: zod
+        .string()
+        .max(listThreadMessagesPathThreadMax)
+        .describe("A thread id. Subagents are threads as well."),
+});
+export const listThreadMessagesQueryOffsetDefault = 0;
+export const listThreadMessagesQueryOffsetMin = 0;
+export const listThreadMessagesQueryOffsetMax = 10000;
+export const listThreadMessagesQueryLimitDefault = 50;
+export const listThreadMessagesQueryLimitMax = 200;
+export const ListThreadMessagesQueryParams = zod.strictObject({
+    offset: zod
+        .int()
+        .min(listThreadMessagesQueryOffsetMin)
+        .max(listThreadMessagesQueryOffsetMax)
+        .default(listThreadMessagesQueryOffsetDefault)
+        .describe("Items to skip. Defaults to 0; at most 10000."),
+    limit: zod
+        .int()
+        .min(1)
+        .max(listThreadMessagesQueryLimitMax)
+        .default(listThreadMessagesQueryLimitDefault)
+        .describe("Items returned in this page. Defaults to 50; at most 200."),
+});
 /**
  * Starts a turn and returns at once; a turn can run for tens of minutes and its progress arrives
  * on /api/v1/realtime. Sending while the assistant is working is allowed: the message is queued
@@ -349,24 +385,6 @@ export const ListThreadTurnsQueryParams = zod.strictObject({
         .default(listThreadTurnsQueryLimitDefault)
         .describe("Items returned in this page. Defaults to 50; at most 200."),
 });
-/**
- * Runs a slash command against the conversation. Commands act directly and never reach the model.
- * The result carries a plain-text `message`, which is what a chat app shows, and structured fields
- * for clients that render more, such as `status` for /status.
- *
- * /new is carried out by the client, which opens an empty conversation, and fails here with 422
- * and code COMMAND_CLIENT_ONLY. Fails with 404 and code COMMAND_NOT_FOUND for an unknown command,
- * and with 422 and code COMMAND_ARGUMENTS_INVALID when the arguments do not fit.
- * @summary Run a command
- */
-export const runCommandPathThreadMax = 64;
-export const RunCommandParams = zod.strictObject({
-    thread: zod
-        .string()
-        .max(runCommandPathThreadMax)
-        .describe("A thread id. Subagents are threads as well."),
-});
-export const RunCommandBody = RunCommandRequestBody;
 /**
  * A folder groups conversations on the board and does nothing else: the assistant is never told
  * which folder a conversation is in. New folders go after the existing ones.

package/dist/assistant/v1/generated/validators/answerQuestionRequestBody.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/answerQuestionRequestBody.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/approvalMode.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.