@runtypelabs/persona 4.23.1 → 4.24.0

package/dist/history-view.d.cts

@@ -106,6 +106,7 @@ type RuntypeExecutionStreamEvent = ({
     turnIndex?: number;
     type: "turn_start";
 }) | ({
+    attributes?: Record<string, string | number | boolean>;
     completedAt?: string;
     content?: string;
     cost?: number;
@@ -164,7 +165,8 @@ type RuntypeExecutionStreamEvent = ({
     };
     turnId?: string;
     type: "model_call_start";
-} | {
+} | ({
+    attributes?: Record<string, string | number | boolean>;
     completedAt?: string;
     cost?: number;
     durationMs?: number;
@@ -188,10 +190,11 @@ type RuntypeExecutionStreamEvent = ({
         cacheWrite?: number;
         input: number;
         output: number;
+        reasoning?: number;
     };
     turnId?: string;
     type: "model_call_complete";
-} | {
+}) | {
     executionId: string;
     id: string;
     index?: number;
@@ -809,6 +812,24 @@ type AgentMessageMetadata = {
      * never re-resume the call.
      */
     suggestRepliesResolved?: boolean;
+    /**
+     * The client-tool answer the server accepted through `/resume`, kept so
+     * later proxy/agent turns can replay the call and its result to the model.
+     * `toolName` is the widget's internal name (`webmcp:<name>` or a bare
+     * built-in). Set only after the resume succeeds; preserved across
+     * re-emissions of the tool message.
+     */
+    clientToolAnswer?: {
+        toolCallId: string;
+        toolName: string;
+        args: unknown;
+        result: unknown;
+        /**
+         * Shared by the answers posted in one `/resume`, i.e. one assistant
+         * turn's parallel calls; a chained call gets a new batch.
+         */
+        batch?: string;
+    };
 };
 /**
  * Copy overrides for the visitor-facing conversation history surface. These are
@@ -1094,6 +1115,8 @@ type AgentWidgetReasoning = {
     durationMs?: number;
 };
 type AgentWidgetToolCall = {
+    /** Optional approval state for activity-row status chrome. */
+    approvalStatus?: "pending" | "approved" | "denied" | "timeout";
     id: string;
     name?: string;
     status: "pending" | "running" | "complete";

package/dist/history-view.d.ts

@@ -106,6 +106,7 @@ type RuntypeExecutionStreamEvent = ({
     turnIndex?: number;
     type: "turn_start";
 }) | ({
+    attributes?: Record<string, string | number | boolean>;
     completedAt?: string;
     content?: string;
     cost?: number;
@@ -164,7 +165,8 @@ type RuntypeExecutionStreamEvent = ({
     };
     turnId?: string;
     type: "model_call_start";
-} | {
+} | ({
+    attributes?: Record<string, string | number | boolean>;
     completedAt?: string;
     cost?: number;
     durationMs?: number;
@@ -188,10 +190,11 @@ type RuntypeExecutionStreamEvent = ({
         cacheWrite?: number;
         input: number;
         output: number;
+        reasoning?: number;
     };
     turnId?: string;
     type: "model_call_complete";
-} | {
+}) | {
     executionId: string;
     id: string;
     index?: number;
@@ -809,6 +812,24 @@ type AgentMessageMetadata = {
      * never re-resume the call.
      */
     suggestRepliesResolved?: boolean;
+    /**
+     * The client-tool answer the server accepted through `/resume`, kept so
+     * later proxy/agent turns can replay the call and its result to the model.
+     * `toolName` is the widget's internal name (`webmcp:<name>` or a bare
+     * built-in). Set only after the resume succeeds; preserved across
+     * re-emissions of the tool message.
+     */
+    clientToolAnswer?: {
+        toolCallId: string;
+        toolName: string;
+        args: unknown;
+        result: unknown;
+        /**
+         * Shared by the answers posted in one `/resume`, i.e. one assistant
+         * turn's parallel calls; a chained call gets a new batch.
+         */
+        batch?: string;
+    };
 };
 /**
  * Copy overrides for the visitor-facing conversation history surface. These are
@@ -1094,6 +1115,8 @@ type AgentWidgetReasoning = {
     durationMs?: number;
 };
 type AgentWidgetToolCall = {
+    /** Optional approval state for activity-row status chrome. */
+    approvalStatus?: "pending" | "approved" | "denied" | "timeout";
     id: string;
     name?: string;
     status: "pending" | "running" | "complete";