@waniwani/sdk 0.5.2 → 0.5.3-beta.0

package/dist/chat/index.d.ts

@@ -76,8 +76,6 @@ interface ChatBaseProps {
     onMessageSent?: (message: string) => void;
     /** Callback fired when a response is received */
     onResponseReceived?: () => void;
-    /** Endpoint URL for fetching MCP app resources (HTML widgets). Defaults to "/api/mcp/resource" */
-    resourceEndpoint?: string;
     /**
      * Enable AI-generated suggestions after each response.
      * `true` enables with defaults (3 suggestions), object allows config, `false`/undefined disables.
@@ -88,17 +86,7 @@ interface ChatBaseProps {
      * Called when a widget uses `callServerTool` (MCP Apps standard).
      * If not provided, defaults to POSTing to `${api}/tool`.
      */
-    onCallTool?: (params: {
-        name: string;
-        arguments: Record<string, unknown>;
-    }) => Promise<{
-        content?: Array<{
-            type: string;
-            text?: string;
-        }>;
-        structuredContent?: Record<string, unknown>;
-        _meta?: Record<string, unknown>;
-    }>;
+    onCallTool?: CallToolHandler;
     /**
      * Enable debug mode. When true, the `_meta` field is shown in tool call
      * inputs and outputs instead of being filtered out.
@@ -117,6 +105,71 @@ interface ChatBarProps extends ChatBaseProps {
     /** Title shown in the header when expanded. Defaults to "Assistant". */
     title?: string;
 }
+/**
+ * MCP Apps configuration for {@link ChatEmbedProps}.
+ *
+ * Only needed when your backend proxies an MCP server whose tools return
+ * widget metadata (`_meta.ui.resourceUri`). Without this, tool calls still
+ * render with collapsible input/output — just no iframe widgets.
+ */
+interface ChatEmbedMcpConfig {
+    /** Endpoint that serves MCP app resources (HTML widgets). Called as `GET ${resourceEndpoint}?uri=...`. */
+    resourceEndpoint: string;
+    /**
+     * Handler for MCP tool calls triggered by widgets via `callServerTool`.
+     * If not provided, widget-initiated tool calls will be ignored.
+     */
+    onCallTool?: CallToolHandler;
+}
+/** Handler signature for MCP tool calls from widgets. */
+type CallToolHandler = (params: {
+    name: string;
+    arguments: Record<string, unknown>;
+}) => Promise<{
+    content?: Array<{
+        type: string;
+        text?: string;
+    }>;
+    structuredContent?: Record<string, unknown>;
+    _meta?: Record<string, unknown>;
+}>;
+/**
+ * Standalone, borderless chat component designed for embedding into existing pages.
+ *
+ * Unlike {@link ChatCardProps} and {@link ChatBarProps}, ChatEmbed does **not** rely on
+ * the WaniWani hosted backend. It does not fetch `/config` or call `/tool` — you bring
+ * your own `api` endpoint.
+ *
+ * The component fills its parent container (`width: 100%; height: 100%`) with no
+ * header, border, or shadow — making it ideal for integrating into an existing layout
+ * that already provides its own chrome.
+ *
+ * To enable MCP App widgets (iframes), pass the optional `mcp` config.
+ *
+ * @example
+ * ```tsx
+ * // Basic — no MCP Apps
+ * <ChatEmbed
+ *   api="/api/my-chat-endpoint"
+ *   body={{ environmentId, sessionId }}
+ *   theme={{ backgroundColor: "#fff" }}
+ * />
+ *
+ * // With MCP Apps support
+ * <ChatEmbed
+ *   api="/api/my-chat-endpoint"
+ *   mcp={{ resourceEndpoint: "/api/mcp/resource" }}
+ * />
+ * ```
+ */
+interface ChatEmbedProps extends Omit<ChatBaseProps, "api" | "onCallTool"> {
+    /** The chat API endpoint URL. Required — there is no default. */
+    api: string;
+    /** Additional class names applied to the root element (e.g. Tailwind classes). */
+    className?: string;
+    /** MCP Apps configuration. Only needed if your backend serves widget resources. */
+    mcp?: ChatEmbedMcpConfig;
+}
 interface ChatCardProps extends ChatBaseProps {
     /** Title shown in the card header. Defaults to "Assistant". */
     title?: string;
@@ -223,9 +276,30 @@ declare function McpAppFrame({ resourceUri, toolInput, toolResult, resourceEndpo
 
 declare const ChatCard: react.ForwardRefExoticComponent<ChatCardProps & react.RefAttributes<ChatHandle>>;
 
+/**
+ * Standalone, borderless chat component — bring your own backend.
+ *
+ * Fills its parent container with no header, border, or shadow.
+ * Does **not** call any WaniWani-specific endpoints (`/config`, `/tool`, `/sessions`).
+ * Point `api` at your own AI-SDK-compatible streaming endpoint and pass extra
+ * request fields via `body`.
+ *
+ * Supports the same ref API as ChatCard (`sendMessage`, `sendMessageAndWait`, `focus`).
+ *
+ * @example
+ * ```tsx
+ * <ChatEmbed
+ *   api={`/api/mcp/projects/${projectId}/chat`}
+ *   body={{ environmentId, chatSessionId }}
+ *   suggestions={{ initial: ["What can you do?"] }}
+ * />
+ * ```
+ */
+declare const ChatEmbed: react.ForwardRefExoticComponent<ChatEmbedProps & react.RefAttributes<ChatHandle>>;
+
 declare const DEFAULT_THEME: Required<ChatTheme>;
 declare const DARK_THEME: ChatTheme;
 declare function mergeTheme(userTheme?: ChatTheme): Required<ChatTheme>;
 declare function themeToCSSProperties(theme: Required<ChatTheme>): Record<string, string>;
 
-export { ChatBar, type ChatBarProps, type ChatBaseProps, ChatCard, type ChatCardProps, type ChatHandle, type ChatTheme, ChatBar as ChatWidget, type ChatWidgetProps, DARK_THEME, DEFAULT_THEME, EvalPanel, type McpAppDisplayMode, McpAppFrame, type McpAppFrameProps, type SuggestionsConfig, mergeTheme, themeToCSSProperties };
+export { ChatBar, type ChatBarProps, type ChatBaseProps, ChatCard, type ChatCardProps, ChatEmbed, type ChatEmbedMcpConfig, type ChatEmbedProps, type ChatHandle, type ChatTheme, ChatBar as ChatWidget, type ChatWidgetProps, DARK_THEME, DEFAULT_THEME, EvalPanel, type McpAppDisplayMode, McpAppFrame, type McpAppFrameProps, type SuggestionsConfig, mergeTheme, themeToCSSProperties };