agents 0.3.1 → 0.3.2

package/README.md

@@ -277,6 +277,18 @@ function StateInterface() {
 
 This creates a synchronized state that automatically updates across all connected clients.
 
+### 💬 AI Chat Integration
+
+For building AI-powered chat experiences with persistent conversations, streaming responses, and tool support, see [`@cloudflare/ai-chat`](../ai-chat/README.md).
+
+The `@cloudflare/ai-chat` package provides:
+
+- `AIChatAgent` - Chat-enabled agent class with automatic message persistence
+- `useAgentChat` - React hook for seamless chat interactions
+- Resumable streaming - Automatic recovery from disconnections
+- Tool support - Both server and client-side tool execution
+- AI SDK v6 integration - Built on the latest AI SDK
+
 ### ⏳ Temporal Patterns
 
 Schedule moments of action and reflection:
@@ -310,332 +322,6 @@ export class TimeAwareAgent extends Agent {
 }
 ```
 
-### 💬 AI Dialogue
-
-Create meaningful conversations with intelligence:
-
-```ts
-import { AIChatAgent } from "agents/ai-chat-agent";
-import { openai } from "@ai-sdk/openai";
-import { streamText, generateText, createDataStreamResponse } from "ai";
-
-export class DialogueAgent extends AIChatAgent {
-  async onChatMessage(onFinish) {
-    // Option 1: Streaming responses (recommended for real-time interaction)
-    return createDataStreamResponse({
-      execute: async (dataStream) => {
-        const stream = streamText({
-          model: openai("gpt-4o"),
-          messages: this.messages,
-          // Optional: onFinish is invoked by the AI SDK when generation completes.
-          // Persistence is handled automatically by AIChatAgent after streaming completes.
-          onFinish
-        });
-
-        stream.mergeIntoDataStream(dataStream);
-      }
-    });
-
-    // Option 2: Non-streaming responses (simpler, but no real-time updates)
-    // const result = await generateText({
-    //   model: openai("gpt-4o"),
-    //   messages: this.messages,
-    // });
-    //
-    // // For non-streaming with metadata, use toUIMessage:
-    // const message = result.toUIMessage({
-    //   metadata: {
-    //     model: 'gpt-4o',
-    //     totalTokens: result.usage?.totalTokens,
-    //   }
-    // });
-    //
-    // return new Response(JSON.stringify(message), {
-    //   headers: { 'Content-Type': 'application/json' }
-    // });
-  }
-}
-```
-
-#### Metadata Support
-
-The AI SDK provides native support for message metadata through the `messageMetadata` callback. This allows you to attach custom information to messages at the message level.
-
-##### AIChatAgent Integration
-
-In the context of `AIChatAgent`, you can use metadata like this:
-
-```typescript
-import { AIChatAgent } from "agents/ai-chat-agent";
-import { streamText } from "ai";
-import { openai } from "@ai-sdk/openai";
-
-export class MyAgent extends AIChatAgent<Env> {
-  async onChatMessage(onFinish) {
-    const startTime = Date.now();
-
-    const result = streamText({
-      model: openai("gpt-4o"),
-      messages: this.messages,
-      onFinish
-    });
-
-    return result.toUIMessageStreamResponse({
-      messageMetadata: ({ part }) => {
-        if (part.type === "start") {
-          return {
-            model: "gpt-4o",
-            createdAt: Date.now(),
-            messageCount: this.messages.length
-          };
-        }
-        if (part.type === "finish") {
-          return {
-            responseTime: Date.now() - startTime,
-            totalTokens: part.totalUsage?.totalTokens
-          };
-        }
-      }
-    });
-  }
-}
-```
-
-##### Accessing Metadata on the Client
-
-Access metadata through the `message.metadata` property:
-
-```typescript
-'use client';
-
-import { useChat } from '@ai-sdk/react';
-import { DefaultChatTransport } from 'ai';
-import type { MyUIMessage } from '@/types';
-
-export default function Chat() {
-  const { messages } = useChat<MyUIMessage>({
-    transport: new DefaultChatTransport({
-      api: '/api/chat',
-    }),
-  });
-
-  return (
-    <div>
-      {messages.map(message => (
-        <div key={message.id}>
-          <div>
-            {message.role === 'user' ? 'User: ' : 'AI: '}
-            {message.metadata?.createdAt && (
-              <span className="text-sm text-gray-500">
-                {new Date(message.metadata.createdAt).toLocaleTimeString()}
-              </span>
-            )}
-          </div>
-          {/* Render message content */}
-          {message.parts.map((part, index) =>
-            part.type === 'text' ? <div key={index}>{part.text}</div> : null,
-          )}
-          {/* Display additional metadata */}
-          {message.metadata?.totalTokens && (
-            <div className="text-xs text-gray-400">
-              {message.metadata.totalTokens} tokens
-            </div>
-          )}
-        </div>
-      ))}
-    </div>
-  );
-}
-```
-
-For more details, see the [AI SDK Message Metadata documentation](https://ai-sdk.dev/docs/ai-sdk-ui/message-metadata).
-
-#### Creating the Interface
-
-Connect with your agent through a React interface:
-
-```tsx
-import { useAgent } from "agents/react";
-import { useAgentChat } from "agents/ai-react";
-
-function ChatInterface() {
-  // Connect to the agent
-  const agent = useAgent({
-    agent: "dialogue-agent"
-  });
-
-  // Set up the chat interaction
-  const { messages, input, handleInputChange, handleSubmit, clearHistory } =
-    useAgentChat({
-      agent,
-      maxSteps: 5
-    });
-
-  return (
-    <div className="chat-interface">
-      {/* Message History */}
-      <div className="message-flow">
-        {messages.map((message) => (
-          <div key={message.id} className="message">
-            <div className="role">{message.role}</div>
-            <div className="content">
-              {message.parts.map((part, i) => {
-                if (part.type === "text")
-                  return <span key={i}>{part.text}</span>;
-                // Render other part types (e.g., files, tool calls) as desired
-                return null;
-              })}
-            </div>
-          </div>
-        ))}
-      </div>
-
-      {/* Input Area */}
-      <form onSubmit={handleSubmit} className="input-area">
-        <input
-          value={input}
-          onChange={handleInputChange}
-          placeholder="Type your message..."
-          className="message-input"
-        />
-      </form>
-
-      <button onClick={clearHistory} className="clear-button">
-        Clear Chat
-      </button>
-    </div>
-  );
-}
-```
-
-This creates:
-
-- Real-time message streaming
-- Simple message history
-- Intuitive input handling
-- Easy conversation reset
-
-#### Client-Defined Tools
-
-For scenarios where each client needs to register its own tools dynamically (e.g., embeddable chat widgets), use the `tools` option with `execute` functions.
-
-Tools with an `execute` function are automatically:
-
-1. Sent to the server as schemas with each request
-2. Executed on the client when the AI model calls them
-
-##### Client-Side Tool Definition
-
-```tsx
-import { useAgent } from "agents/react";
-import { useAgentChat, type AITool } from "agents/ai-react";
-
-// Define tools outside component to avoid recreation on every render
-const tools: Record<string, AITool> = {
-  showAlert: {
-    description: "Shows an alert dialog to the user",
-    parameters: {
-      type: "object",
-      properties: { message: { type: "string" } },
-      required: ["message"]
-    },
-    execute: async (input) => {
-      const { message } = input as { message: string };
-      alert(message);
-      return { success: true };
-    }
-  },
-  changeBackgroundColor: {
-    description: "Changes the page background color",
-    parameters: {
-      type: "object",
-      properties: { color: { type: "string" } }
-    },
-    execute: async (input) => {
-      const { color } = input as { color: string };
-      document.body.style.backgroundColor = color;
-      return { success: true, color };
-    }
-  }
-};
-
-function EmbeddableChat() {
-  const agent = useAgent({ agent: "chat-widget" });
-
-  const { messages, input, handleInputChange, handleSubmit } = useAgentChat({
-    agent,
-    tools // Schema + execute in one place
-  });
-
-  return (
-    <div className="chat-widget">
-      {messages.map((message) => (
-        <div key={message.id}>{/* Render message */}</div>
-      ))}
-      <form onSubmit={handleSubmit}>
-        <input value={input} onChange={handleInputChange} />
-      </form>
-    </div>
-  );
-}
-```
-
-##### Server-Side Tool Handling
-
-On the server, use `createToolsFromClientSchemas` to convert client tool schemas to AI SDK format:
-
-```typescript
-import {
-  AIChatAgent,
-  createToolsFromClientSchemas
-} from "agents/ai-chat-agent";
-import { openai } from "@ai-sdk/openai";
-import { streamText, convertToModelMessages } from "ai";
-
-export class ChatWidget extends AIChatAgent {
-  async onChatMessage(onFinish, options) {
-    const result = streamText({
-      model: openai("gpt-4o"),
-      messages: convertToModelMessages(this.messages),
-      tools: {
-        // Server-side tools (execute on server)
-        getWeather: tool({
-          description: "Get weather for a city",
-          parameters: z.object({ city: z.string() }),
-          execute: async ({ city }) => fetchWeather(city)
-        }),
-        // Client-side tools (sent back to client for execution)
-        ...createToolsFromClientSchemas(options?.clientTools)
-      },
-      onFinish
-    });
-    return result.toUIMessageStreamResponse();
-  }
-}
-```
-
-##### Advanced: Custom Request Data
-
-For additional control (custom headers, dynamic context), use `prepareSendMessagesRequest`:
-
-```tsx
-const { messages, handleSubmit } = useAgentChat({
-  agent,
-  tools, // Tool schemas auto-extracted and sent
-  prepareSendMessagesRequest: ({ id, messages }) => ({
-    body: {
-      // Add dynamic context alongside auto-extracted tool schemas
-      currentUrl: window.location.href,
-      userTimezone: Intl.DateTimeFormat().resolvedOptions().timeZone
-    },
-    headers: {
-      "X-Widget-Version": "1.0.0",
-      "X-Request-ID": crypto.randomUUID()
-    }
-  })
-});
-```
-
 ### 🔗 MCP (Model Context Protocol) Integration
 
 Agents can seamlessly integrate with the Model Context Protocol, allowing them to act as both MCP servers (providing tools to AI assistants) and MCP clients (using tools from other services).

package/dist/ai-chat-agent.d.ts

@@ -1,324 +1 @@
-import "./context-DcbQ8o7k.js";
-import "./client-DFotUKH_.js";
-import "./ai-types-0OnT3FHg.js";
-import { n as AgentContext, t as Agent } from "./index-CT2tCrLr.js";
-import {
-  JSONSchema7,
-  StreamTextOnFinishCallback,
-  Tool,
-  ToolSet,
-  UIMessage
-} from "ai";
-
-//#region src/ai-chat-agent.d.ts
-
-/**
- * Schema for a client-defined tool sent from the browser.
- * These tools are executed on the client, not the server.
- *
- * Note: Uses `parameters` (JSONSchema7) rather than AI SDK's `inputSchema` (FlexibleSchema)
- * because this is the wire format. Zod schemas cannot be serialized.
- *
- * @deprecated Define tools on the server using `tool()` from "ai" instead.
- * For tools that need client-side execution, omit the `execute` function
- * and handle them via the `onToolCall` callback in `useAgentChat`.
- */
-type ClientToolSchema = {
-  /** Unique name for the tool */
-  name: string;
-  /** Human-readable description of what the tool does */
-  description?: Tool["description"];
-  /** JSON Schema defining the tool's input parameters */
-  parameters?: JSONSchema7;
-};
-/**
- * Options passed to the onChatMessage handler.
- */
-type OnChatMessageOptions = {
-  /** AbortSignal for cancelling the request */
-  abortSignal?: AbortSignal;
-  /**
-   * Tool schemas sent from the client for dynamic tool registration.
-   * These represent tools that will be executed on the client side.
-   * Use `createToolsFromClientSchemas()` to convert these to AI SDK tool format.
-   *
-   * @deprecated Define tools on the server instead. Use `onToolCall` callback
-   * in `useAgentChat` for client-side execution.
-   */
-  clientTools?: ClientToolSchema[];
-};
-/**
- * Converts client tool schemas to AI SDK tool format.
- *
- * These tools have no `execute` function - when the AI model calls them,
- * the tool call is sent back to the client for execution.
- *
- * @param clientTools - Array of tool schemas from the client
- * @returns Record of AI SDK tools that can be spread into your tools object
- *
- * @deprecated Define tools on the server using `tool()` from "ai" instead.
- * For tools that need client-side execution, omit the `execute` function
- * and handle them via the `onToolCall` callback in `useAgentChat`.
- *
- * @example
- * ```typescript
- * // Server: Define tool without execute
- * const tools = {
- *   getLocation: tool({
- *     description: "Get user's location",
- *     inputSchema: z.object({})
- *     // No execute = client must handle
- *   })
- * };
- *
- * // Client: Handle in onToolCall
- * useAgentChat({
- *   onToolCall: async ({ toolCall, addToolOutput }) => {
- *     if (toolCall.toolName === 'getLocation') {
- *       const pos = await navigator.geolocation.getCurrentPosition();
- *       addToolOutput({ toolCallId: toolCall.toolCallId, output: pos });
- *     }
- *   }
- * });
- * ```
- */
-declare function createToolsFromClientSchemas(
-  clientTools?: ClientToolSchema[]
-): ToolSet;
-/**
- * Extension of Agent with built-in chat capabilities
- * @template Env Environment type containing bindings
- */
-declare class AIChatAgent<
-  Env extends Cloudflare.Env = Cloudflare.Env,
-  State = unknown
-> extends Agent<Env, State> {
-  /**
-   * Map of message `id`s to `AbortController`s
-   * useful to propagate request cancellation signals for any external calls made by the agent
-   */
-  private _chatMessageAbortControllers;
-  /**
-   * Currently active stream ID for resumable streaming.
-   * Stored in memory for quick access; persisted in stream_metadata table.
-   * @internal Protected for testing purposes.
-   */
-  protected _activeStreamId: string | null;
-  /**
-   * Request ID associated with the active stream.
-   * @internal Protected for testing purposes.
-   */
-  protected _activeRequestId: string | null;
-  /**
-   * The message currently being streamed. Used to apply tool results
-   * before the message is persisted.
-   * @internal
-   */
-  private _streamingMessage;
-  /**
-   * Promise that resolves when the current stream completes.
-   * Used to wait for message persistence before continuing after tool results.
-   * @internal
-   */
-  private _streamCompletionPromise;
-  private _streamCompletionResolve;
-  /**
-   * Current chunk index for the active stream
-   */
-  private _streamChunkIndex;
-  /**
-   * Buffer for stream chunks pending write to SQLite.
-   * Chunks are batched and flushed when buffer reaches CHUNK_BUFFER_SIZE.
-   */
-  private _chunkBuffer;
-  /**
-   * Lock to prevent concurrent flush operations
-   */
-  private _isFlushingChunks;
-  /**
-   * Timestamp of the last cleanup operation for old streams
-   */
-  private _lastCleanupTime;
-  /** Array of chat messages for the current conversation */
-  messages: UIMessage[];
-  constructor(ctx: AgentContext, env: Env);
-  /**
-   * Restore active stream state if the agent was restarted during streaming.
-   * Called during construction to recover any interrupted streams.
-   * Validates stream freshness to avoid sending stale resume notifications.
-   * @internal Protected for testing purposes.
-   */
-  protected _restoreActiveStream(): void;
-  /**
-   * Notify a connection about an active stream that can be resumed.
-   * The client should respond with CF_AGENT_STREAM_RESUME_ACK to receive chunks.
-   * Uses in-memory state for request ID - no extra DB lookup needed.
-   * @param connection - The WebSocket connection to notify
-   */
-  private _notifyStreamResuming;
-  /**
-   * Send stream chunks to a connection after receiving ACK.
-   * @param connection - The WebSocket connection
-   * @param streamId - The stream to replay
-   * @param requestId - The original request ID
-   */
-  private _sendStreamChunks;
-  /**
-   * Buffer a stream chunk for batch write to SQLite.
-   * @param streamId - The stream this chunk belongs to
-   * @param body - The serialized chunk body
-   * @internal Protected for testing purposes.
-   */
-  protected _storeStreamChunk(streamId: string, body: string): void;
-  /**
-   * Flush buffered chunks to SQLite in a single batch.
-   * Uses a lock to prevent concurrent flush operations.
-   * @internal Protected for testing purposes.
-   */
-  protected _flushChunkBuffer(): void;
-  /**
-   * Start tracking a new stream for resumable streaming.
-   * Creates metadata entry in SQLite and sets up tracking state.
-   * @param requestId - The unique ID of the chat request
-   * @returns The generated stream ID
-   * @internal Protected for testing purposes.
-   */
-  protected _startStream(requestId: string): string;
-  /**
-   * Mark a stream as completed and flush any pending chunks.
-   * @param streamId - The stream to mark as completed
-   * @internal Protected for testing purposes.
-   */
-  protected _completeStream(streamId: string): void;
-  /**
-   * Clean up old completed streams if enough time has passed since last cleanup.
-   * This prevents database growth while avoiding cleanup overhead on every stream completion.
-   */
-  private _maybeCleanupOldStreams;
-  private _broadcastChatMessage;
-  private _loadMessagesFromDb;
-  onRequest(request: Request): Promise<Response>;
-  private _tryCatchChat;
-  /**
-   * Handle incoming chat messages and generate a response
-   * @param onFinish Callback to be called when the response is finished
-   * @param options Options including abort signal and client-defined tools
-   * @returns Response to send to the client or undefined
-   */
-  onChatMessage(
-    onFinish: StreamTextOnFinishCallback<ToolSet>,
-    options?: OnChatMessageOptions
-  ): Promise<Response | undefined>;
-  /**
-   * Save messages on the server side
-   * @param messages Chat messages to save
-   */
-  saveMessages(messages: UIMessage[]): Promise<void>;
-  persistMessages(
-    messages: UIMessage[],
-    excludeBroadcastIds?: string[]
-  ): Promise<void>;
-  /**
-   * Merges incoming messages with existing server state.
-   * This preserves tool outputs that the server has (via _applyToolResult)
-   * but the client doesn't have yet.
-   *
-   * @param incomingMessages - Messages from the client
-   * @returns Messages with server's tool outputs preserved
-   */
-  private _mergeIncomingWithServerState;
-  /**
-   * Resolves a message for persistence, handling tool result merging.
-   * If the message contains tool parts with output-available state, checks if there's
-   * an existing message with the same toolCallId that should be updated instead of
-   * creating a duplicate. This prevents the "Duplicate item found" error from OpenAI
-   * when client-side tool results arrive in a new request.
-   *
-   * @param message - The message to potentially merge
-   * @returns The message with the correct ID (either original or merged)
-   */
-  private _resolveMessageForToolMerge;
-  /**
-   * Finds an existing assistant message that contains a tool part with the given toolCallId.
-   * Used to detect when a tool result should update an existing message rather than
-   * creating a new one.
-   *
-   * @param toolCallId - The tool call ID to search for
-   * @returns The existing message if found, undefined otherwise
-   */
-  private _findMessageByToolCallId;
-  /**
-   * Sanitizes a message for persistence by removing ephemeral provider-specific
-   * data that should not be stored or sent back in subsequent requests.
-   *
-   * This handles two issues with the OpenAI Responses API:
-   *
-   * 1. **Duplicate item IDs**: The AI SDK's @ai-sdk/openai provider (v2.0.x+)
-   *    defaults to using OpenAI's Responses API which assigns unique itemIds
-   *    to each message part. When these IDs are persisted and sent back,
-   *    OpenAI rejects them as duplicates.
-   *
-   * 2. **Empty reasoning parts**: OpenAI may return reasoning parts with empty
-   *    text and encrypted content. These cause "Non-OpenAI reasoning parts are
-   *    not supported" warnings when sent back via convertToModelMessages().
-   *
-   * @param message - The message to sanitize
-   * @returns A new message with ephemeral provider data removed
-   */
-  private _sanitizeMessageForPersistence;
-  /**
-   * Helper to strip OpenAI-specific ephemeral fields from a metadata object.
-   * Removes itemId and reasoningEncryptedContent while preserving other fields.
-   */
-  private _stripOpenAIMetadata;
-  /**
-   * Applies a tool result to an existing assistant message.
-   * This is used when the client sends CF_AGENT_TOOL_RESULT for client-side tools.
-   * The server is the source of truth, so we update the message here and broadcast
-   * the update to all clients.
-   *
-   * @param toolCallId - The tool call ID this result is for
-   * @param toolName - The name of the tool
-   * @param output - The output from the tool execution
-   * @returns true if the result was applied, false if the message was not found
-   */
-  private _applyToolResult;
-  private _reply;
-  /**
-   * Mark a stream as errored and clean up state.
-   * @param streamId - The stream to mark as errored
-   * @internal Protected for testing purposes.
-   */
-  protected _markStreamError(streamId: string): void;
-  /**
-   * For the given message id, look up its associated AbortController
-   * If the AbortController does not exist, create and store one in memory
-   *
-   * returns the AbortSignal associated with the AbortController
-   */
-  private _getAbortSignal;
-  /**
-   * Remove an abort controller from the cache of pending message responses
-   */
-  private _removeAbortController;
-  /**
-   * Propagate an abort signal for any requests associated with the given message id
-   */
-  private _cancelChatRequest;
-  /**
-   * Abort all pending requests and clear the cache of AbortControllers
-   */
-  private _destroyAbortControllers;
-  /**
-   * When the DO is destroyed, cancel all pending requests and clean up resources
-   */
-  destroy(): Promise<void>;
-}
-//#endregion
-export {
-  AIChatAgent,
-  ClientToolSchema,
-  OnChatMessageOptions,
-  createToolsFromClientSchemas
-};
-//# sourceMappingURL=ai-chat-agent.d.ts.map
+export * from "@cloudflare/ai-chat";