@aigentyc/chat-sdk 0.2.5 → 0.3.0

package/bin/aigentyc.mjs

@@ -3,12 +3,14 @@
  * aigentyc — CLI router for @aigentyc/chat-sdk.
  *
  * Subcommands:
- *   doctor   diagnose install / config issues
- *   add      integrate the SDK into an existing project
+ *   doctor              diagnose install / config issues
+ *   add                 integrate the SDK into an existing project
+ *   skill install       drop the Claude Code skill into .claude/skills/
  *
  * Usage:
  *   npx @aigentyc/chat-sdk add
  *   npx @aigentyc/chat-sdk doctor
+ *   npx @aigentyc/chat-sdk skill install
  *   npx @aigentyc/chat-sdk          → shows help
  */
 
@@ -21,8 +23,9 @@ const HELP = `
     npx @aigentyc/chat-sdk <command>
 
   Commands:
-    add      Integrate the SDK into an existing Vite/Next/CRA project
-    doctor   Diagnose install + configuration
+    add              Integrate the SDK into an existing Vite/Next/CRA project
+    doctor           Diagnose install + configuration
+    skill install    Install Claude Code skill into .claude/skills/
 
   Docs: https://www.npmjs.com/package/@aigentyc/chat-sdk
 `;
@@ -38,6 +41,9 @@ if (sub === "doctor") {
 } else if (sub === "add") {
   const { run } = await import("./lib/add.mjs");
   await run();
+} else if (sub === "skill") {
+  const { run } = await import("./lib/skill.mjs");
+  await run(process.argv.slice(3));
 } else {
   console.error(`\n  Unknown command: ${sub}`);
   console.log(HELP);

package/bin/lib/skill.mjs

@@ -0,0 +1,84 @@
+/**
+ * `aigentyc skill install` — drop the Claude Code skill for this SDK
+ * into the user's project at `.claude/skills/aigentyc-chat-sdk/`.
+ *
+ * The skill is bundled in the npm package at `claude-skill/aigentyc-chat-sdk/`
+ * (see package.json "files" entry). This command just copies it into place
+ * so any Claude Code / Claude Desktop session running in that workspace can
+ * pick it up automatically.
+ */
+
+import { cp, mkdir, stat } from "node:fs/promises";
+import { existsSync } from "node:fs";
+import { dirname, join, resolve } from "node:path";
+import { fileURLToPath } from "node:url";
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+// bin/lib/skill.mjs -> up to package root
+const PKG_ROOT = resolve(__dirname, "..", "..");
+const SKILL_SRC = resolve(PKG_ROOT, "claude-skill", "aigentyc-chat-sdk");
+
+const HELP = `
+  aigentyc skill install [--force] [--global]
+
+  Installs the Claude Code skill for @aigentyc/chat-sdk.
+
+  Flags:
+    --force    Overwrite existing skill if present
+    --global   Install to ~/.claude/skills/ (default: ./.claude/skills/)
+
+  After install, any Claude Code / Claude Desktop session in this workspace
+  will auto-load the skill for help with this SDK.
+`;
+
+export async function run(argv = []) {
+  const sub = argv[0];
+  if (sub === "--help" || sub === "-h") {
+    console.log(HELP);
+    return;
+  }
+
+  if (sub !== "install") {
+    console.error(`\n  Unknown skill subcommand: ${sub ?? "(none)"}`);
+    console.log(HELP);
+    process.exit(2);
+  }
+
+  const flags = new Set(argv.slice(1).filter((a) => a.startsWith("--")));
+  const force = flags.has("--force");
+  const globalInstall = flags.has("--global");
+
+  // Target dir
+  const rootDir = globalInstall
+    ? resolve(process.env.HOME || "~", ".claude", "skills")
+    : resolve(process.cwd(), ".claude", "skills");
+  const target = join(rootDir, "aigentyc-chat-sdk");
+
+  if (!existsSync(SKILL_SRC)) {
+    console.error(
+      `\n  ✖  Can't find skill source at: ${SKILL_SRC}\n` +
+        `     (Are you running from a checkout, or an old SDK version? Reinstall with \`npm install @aigentyc/chat-sdk@latest\`.)\n`,
+    );
+    process.exit(1);
+  }
+
+  if (existsSync(target)) {
+    if (!force) {
+      console.error(
+        `\n  ✖  Skill already installed at:\n     ${target}\n\n` +
+          `     Re-run with --force to overwrite, or delete the folder first.\n`,
+      );
+      process.exit(1);
+    }
+  }
+
+  await mkdir(rootDir, { recursive: true });
+  await cp(SKILL_SRC, target, { recursive: true });
+
+  const size = await stat(target);
+  console.log(
+    `\n  ✓  Installed @aigentyc/chat-sdk skill to:\n     ${target}\n\n` +
+      `     Claude Code / Desktop will now auto-load help for this SDK.\n` +
+      (size.isDirectory() ? "" : ""),
+  );
+}

package/claude-skill/README.md

@@ -0,0 +1,32 @@
+# Claude Code skill for @aigentyc/chat-sdk
+
+This folder ships inside the npm package so developers using the SDK can install the skill into their Claude Code / Claude Desktop workspace.
+
+## Install in an existing project
+
+```bash
+npx @aigentyc/chat-sdk skill install
+```
+
+Drops the skill into `./.claude/skills/aigentyc-chat-sdk/`. Any Claude Code session running in that workspace then gets automatic help with the SDK — slot patterns, auth setup, troubleshooting, headless hook recipes, etc.
+
+Flags:
+- `--force` — overwrite an existing install
+- `--global` — install to `~/.claude/skills/` so every project sees it
+
+## Auto-install (new projects)
+
+`npm create aigentyc-chat@latest my-app` drops the skill into the scaffolded project automatically. No separate step.
+
+## What the skill covers
+
+- Decision tree: `<Chat>` vs `<ChatWidget>` vs `<ChatProvider>` vs `useAigentycChat()`
+- Required setup (the three props + CSS import + `apiKey` gotcha)
+- Slots: full list, the `tools` vs `toolRenderers` confusion, type-safe override pattern
+- Theming / dark mode
+- Tool rendering + `normalizeToolRows` helper
+- Event callbacks
+- Troubleshooting table
+- Rules (do / don't)
+
+Content is a superset of `llms.txt`, formatted for Claude Code's progressive-disclosure skill model.

package/claude-skill/aigentyc-chat-sdk/SKILL.md

@@ -0,0 +1,339 @@
+---
+name: aigentyc-chat-sdk
+description: Expert help for building apps with @aigentyc/chat-sdk — the React 19 SDK for embedding Aigentyc-powered AI chat. Trigger when the user imports `@aigentyc/chat-sdk`, mentions `<Chat />` or `<ChatWidget />`, asks how to embed a chat widget, customize slots, theme, tools, handle auth (`apiKey`, 401 errors), or use `useAigentycChat` headless hook.
+---
+
+# @aigentyc/chat-sdk — Integration Guide
+
+You are an expert on the `@aigentyc/chat-sdk` React SDK. Use this skill when the user is building, debugging, or extending an app that uses the SDK.
+
+## Decision tree: pick the right component
+
+```
+Drop-in full-page chat?       → <Chat projectId apiEndpoint apiKey />
+Floating chat bubble?         → <ChatWidget projectId apiEndpoint apiKey />
+Custom layout, own container? → <ChatProvider> + <ChatInterface />
+Completely custom UI?         → useAigentycChat() hook
+```
+
+Component props are identical between `<Chat>` and `<ChatWidget>` — swap freely.
+
+## Required setup (every integration)
+
+1. `npm install @aigentyc/chat-sdk` (peer: `react>=19`)
+2. Import CSS once: `import "@aigentyc/chat-sdk/theme/styles.css"`
+3. Pass **three** props: `projectId`, `apiEndpoint`, `apiKey`
+
+**`apiKey` IS required for third-party domain embeds.** Without it, `/api/kb/chat` returns 401. The "no apiKey needed" path only works inside `app.aigentyc.com`. Get a project-scoped key from the dashboard (Settings → API Keys) with permission `Chat: Full` and add the embed domain to Allowed Origins.
+
+Environment-variable pattern:
+- Next.js: `NEXT_PUBLIC_AIGENTYC_API_KEY`
+- Vite: `VITE_AIGENTYC_API_KEY`
+
+## Slots system (how to customize UI)
+
+The `slots` prop replaces specific pieces. Every slot receives `DefaultComponent` so you can compose or fully replace.
+
+**Two slot categories commonly confused:**
+- `slots.tools` — **keyed by tool NAME** (e.g. `searchProducts`). Use for per-tool display.
+- `slots.toolRenderers` — **keyed by render MODE** (`visualization`, `json_render`, `legacy`, `preset`, `text`). Use to swap an entire category of renderers.
+
+**All available slots:**
+- Layout: `header`, `footer`, `input`, `welcomePage`, `loader`, `emptyState`
+- Messages: `assistantMessage`, `userMessage`, `systemMessage`, `feedback`
+- Tools: `tools` (by name), `toolRenderers` (by mode)
+- Live chat: `liveChatPanel`, `satisfactionRating`, `visitorIdentityForm`
+- Widget: `floatingButton`
+
+**Pattern for a slot override:**
+
+```tsx
+import type { AssistantMessageSlotProps } from "@aigentyc/chat-sdk";
+
+function MyAssistant({ text, message, DefaultComponent, ...rest }: AssistantMessageSlotProps & { DefaultComponent: any }) {
+  // Wrap the default:
+  return <div className="my-wrapper"><DefaultComponent text={text} message={message} {...rest} /></div>;
+  // OR replace it entirely:
+  // return <div className="my-bubble">{text}</div>;
+}
+
+<Chat slots={{ assistantMessage: MyAssistant }} projectId="..." apiEndpoint="..." apiKey="..." />
+```
+
+## Theming
+
+CSS vars under `[data-aigentyc-chat]`. Pass `theme` prop:
+
+```tsx
+<Chat theme={{ primaryColor: "#eb1d22", fontFamily: "Inter, sans-serif" }} ... />
+```
+
+Or override CSS vars directly: `--ac-primary`, `--ac-background`, `--ac-card`, `--ac-text`, `--ac-user-bubble-bg`, `--ac-assistant-bubble-bg`.
+
+**Dark mode works automatically** — the SDK uses `bg-background`/`bg-card` with theme vars, not hardcoded whites.
+
+## Tool rendering (backend-driven custom UI)
+
+Custom tools configured in the dashboard return a result with `uiRenderMode`:
+- `visualization` → recharts (10 chart types)
+- `json_render` → `@json-render/shadcn` spec
+- `legacy` → HTML/CSS template with `{{field}}` / `{{#each}}` substitution
+- `preset` / `text` → JSON card
+- `hidden` / `none` → render nothing
+
+Override via `slots.tools[toolName]`:
+
+```tsx
+import type { ToolRendererProps } from "@aigentyc/chat-sdk";
+import { normalizeToolRows } from "@aigentyc/chat-sdk";
+
+function ProductGrid({ result }: ToolRendererProps) {
+  const rows = normalizeToolRows(result?.data);  // handles flat | wrapped | raw DB shapes
+  return <div className="grid grid-cols-2 gap-2">{rows.map((r, i) => <Card key={i} {...r} />)}</div>;
+}
+
+<Chat slots={{ tools: { searchProducts: ProductGrid } }} ... />
+```
+
+## Event callbacks
+
+Attach analytics/side-effect hooks via top-level props (they flow into `ChatEventCallbacks`):
+
+```tsx
+<Chat
+  onMessageSent={(m) => analytics.track("sent", m)}
+  onMessageReceived={(m) => analytics.track("received", m)}
+  onNewConversation={(sessionId) => console.log("new session", sessionId)}
+  onStopGeneration={() => console.log("user stopped stream")}
+  onToolCall={(name, args) => console.log("tool", name)}
+  onToolResult={(name, result) => console.log("result", name)}
+  onError={(err) => Sentry.captureException(err)}
+/>
+```
+
+## Headless hook
+
+```tsx
+import { useAigentycChat } from "@aigentyc/chat-sdk/hooks";
+
+const {
+  messages, status, sendMessage, stopGeneration,
+  newConversation, clearMessages,
+  activeTools, liveChat, sessionId,
+} = useAigentycChat({ projectId, apiEndpoint, apiKey });
+```
+
+Build any UI you want on top. All events (`onMessageSent`, `onStopGeneration`, `onNewConversation`, etc.) work the same.
+
+## Common props reference
+
+| Prop | Type | Notes |
+|------|------|-------|
+| `projectId` | `string` | **required** |
+| `apiEndpoint` | `string` | **required** — typically `https://app.aigentyc.ai` |
+| `apiKey` | `string` | Required for embeds on non-aigentyc domains |
+| `theme` | `ThemeConfig` | Brand colors, fonts |
+| `slots` | `SlotMap` | UI customization |
+| `language` | `"en" \| "he" \| string` | Sets RTL for `he` automatically |
+| `messagePartOrder` | `"text-first" \| "tools-first" \| "stream-order"` | **new** — text/tool sort inside each message |
+| `showSources` | `boolean` | Citation list under assistant messages |
+| `persistMessages` | `boolean` | Default `true`, localStorage keyed by projectId |
+| `enableLiveChat` | `boolean` | Human handoff (needs `socket.io-client`) |
+| `chatServiceUrl` | `string` | WebSocket URL for live chat |
+
+## Rules — things to do / not to do
+
+**Do:**
+- Always include the CSS import
+- Always pass `apiKey` for third-party embeds
+- Use `slots` over forking the SDK
+- Use `useAigentycChat` when you need full UI control
+- Use `normalizeToolRows(result?.data)` when writing custom tool renderers
+- Wrap untested custom renderers in `<ChatErrorBoundary>`
+
+**Do not:**
+- Add `"use client"` to files that wrap SDK components (the SDK already declares it)
+- Import from `@aigentyc/chat-sdk/dist/*` — use public entry points only
+- Hard-code API keys in committed source — always env vars
+- Mix `slots.tools` (by name) and `slots.toolRenderers` (by mode) — dev console warns
+- Downgrade React below 19
+
+## Troubleshooting — quick fixes
+
+| Symptom | Fix |
+|---------|-----|
+| "Missing Authorization" / 401 | Add `apiKey` prop — see Auth section above |
+| Origin rejected / 403 | Add your embed domain to the API key's Allowed Origins |
+| Unstyled chat | Missing `import "@aigentyc/chat-sdk/theme/styles.css"` |
+| Slot override doesn't show | `toolRenderers` is by mode, not tool name — use `slots.tools` |
+| Welcome won't reset | Upgrade SDK (0.2+ fixes bidirectional welcome toggle) |
+| Raw JSON from tool | Tool has no `uiRenderMode` or no renderer — set server-side or add `slots.tools[name]` |
+| Hebrew shows LTR | Pass `language="he"` |
+| Next.js hydration warning | Ensure you don't add `"use client"` yourself; SDK handles it |
+
+## Advanced: JSON-render tools (declarative UI)
+
+JSON-render lets you describe UI as a spec (`root` + `elements` + `state`) with state binding, actions, and validation — no custom React code needed. Used for forms, dashboards, interactive tool output.
+
+**Supported components** (from `@json-render/shadcn`): `Stack`, `Grid`, `Card`, `Tabs`, `Accordion`, `Heading`, `Text`, `Badge`, `Alert`, `Input`, `Textarea`, `Select`, `Checkbox`, `Radio`, `Switch`, `Slider`, `Button`, `Table`, `LineChart`, `BarChart`, `PieChart`, `AreaChart`, `Progress`, `Spinner`, `Image`, `Avatar`, `Pagination`, `Dialog`, `Drawer`.
+
+**State binding** — paths are forward-slash (e.g. `/form/name`):
+- `{ $bindState: "/form/name" }` — two-way binding (inputs)
+- `{ $state: "/form/name" }` — one-way read (use in `body`, `endpoint`, etc.)
+
+**Actions on `on.press`**:
+- `navigate_url` → `{ url, target? }`
+- `send_message` → `{ message }` — sends a follow-up chat message as the user
+- `call_api` → `{ endpoint, method?, body? }` — validates inputs, resolves `$state` refs, handles form submit
+
+**Form tool pattern** (email submission):
+
+```json
+{
+  "toolType": "data_store",
+  "displayType": "json_render",
+  "jsonRenderSpec": {
+    "root": "form",
+    "elements": {
+      "form": { "type": "Stack", "props": { "gap": "md" }, "children": ["name", "phone", "submit"] },
+      "name": {
+        "type": "Input",
+        "props": {
+          "label": "שם", "name": "name", "placeholder": "הכנס שם",
+          "value": { "$bindState": "/form/name" },
+          "checks": [{ "type": "required", "message": "חובה" }]
+        }
+      },
+      "phone": {
+        "type": "Input",
+        "props": {
+          "label": "טלפון", "name": "phone",
+          "value": { "$bindState": "/form/phone" },
+          "checks": [
+            { "type": "required", "message": "חובה" },
+            { "type": "pattern", "args": { "pattern": "^[0-9]{10}$" }, "message": "10 ספרות" }
+          ]
+        }
+      },
+      "submit": {
+        "type": "Button",
+        "props": { "label": "שלח", "variant": "primary" },
+        "on": {
+          "press": {
+            "action": "call_api",
+            "params": {
+              "endpoint": "https://app.aigentyc.ai/api/kb/form-submit",
+              "method": "POST",
+              "body": {
+                "toolId": "<TOOL_ID>",
+                "projectId": "<PROJECT_ID>",
+                "formData": {
+                  "name": { "$state": "/form/name" },
+                  "phone": { "$state": "/form/phone" }
+                }
+              }
+            },
+            "onSuccess": { "set": { "/formSubmitted": true } },
+            "onError":   { "set": { "/formError": "$error.message" } }
+          }
+        }
+      }
+    },
+    "state": { "form": { "name": "", "phone": "" }, "formSubmitted": false, "formError": "" },
+    "_formConfig": {
+      "mode": "email",
+      "to": "you@example.com",
+      "subject": "New form submission",
+      "successMessage": "Submitted, thank you!",
+      "errorMessage": "Something went wrong",
+      "hideFormAfter": true
+    }
+  }
+}
+```
+
+`_formConfig` lives **inside** `jsonRenderSpec`. The backend reads it when `/api/kb/form-submit` fires. Two modes:
+- `mode: "email"` — routes via internal email service (`to`, `subject` required). Conversation summary auto-attached.
+- `mode: "custom"` — proxies to `customEndpoint` (SSRF-protected: no localhost/private IPs).
+
+## Advanced: Flows (multi-step tool chains)
+
+Flows orchestrate multiple tool steps — REST calls, custom-execute transforms, AI reranking, data store lookups. Configure via `flows_create` MCP tool with an opaque spec:
+
+```typescript
+// CreateToolFlowInput
+{
+  name: "findAndRank",             // camelCase for AI
+  displayName: "Find + rank",
+  description: "Search products then rerank by relevance",
+  inputSchema: [{ name: "query", type: "string", required: true }],
+  steps: [
+    {
+      id: "search", order: 1, name: "Search", type: "tool_reference",
+      toolId: "tool_abc",
+      inputMapping: [{ target: "q", source: { type: "flow_input", flowInputParam: "query" } }],
+    },
+    {
+      id: "rerank", order: 2, name: "Rerank", type: "ai_rerank",
+      aiRerankConfig: { model: "gpt-4o-mini", systemPrompt: "...", maxResults: 5 },
+      inputMapping: [{ target: "items", source: { type: "step_output", stepId: "search" } }],
+      onError: "skip",
+    },
+  ],
+  uiRenderMode: "json",
+  jsonRenderSpec: { /* renders the final merged output */ }
+}
+```
+
+Step types:
+- `api` — REST call (uses `apiConfig`)
+- `tool_reference` — call an existing tool (by `toolId`)
+- `transform` — sandboxed JS (`transformCode`)
+- `ai_rerank` — OpenAI-based filter/sort
+- `data_store` — query a data store (uses `dataStoreConfig`)
+
+Error handling per step: `stop` | `skip` | `default` (with `defaultValue`).
+
+## MCP capability reference
+
+Which advanced fields are settable via `@aigentyc/mcp` tools:
+
+| Feature | Via `tools_create` | Notes |
+|---|---|---|
+| `displayType` | ✅ (new — recommended) | Normalized to `uiRenderMode` automatically |
+| `jsonRenderSpec` | ✅ opaque record | Includes `_formConfig` nested |
+| `customHtml` / `customCss` | ✅ |  |
+| `mobileGridCols` / `desktopGridCols` | ✅ |  |
+| `componentActions` | ✅ opaque |  |
+| `uiRenderMode` | ✅ full enum | `legacy \| json \| json_render \| visualization \| preset \| text \| hidden \| none` |
+| `toolType` | ✅ | `rest_api \| custom_execute \| transform \| hybrid \| data_store \| web_search` (`transform` is an alias for `custom_execute`) |
+| Flow steps (`flows_create`) | ✅ opaque spec | Full `FlowStep[]` supported |
+| Form submit endpoint | ❌ no dedicated MCP tool | Form tools = `toolType: "data_store"` + `jsonRenderSpec._formConfig` |
+
+## Transform tools — hoisting render keys
+
+If you write a `custom_execute` / `transform` tool and want the runtime output to control rendering, return an object with these keys at the top level:
+
+```js
+// transformCode
+return {
+  data: [...],                     // actual payload
+  uiRenderMode: "json",            // overrides tool config
+  jsonRenderSpec: { root: ... },   // overrides tool config
+  componentActions: [...],         // overrides tool config
+  loadingText: "...",
+  uiComponent: "MyComponent",
+};
+```
+
+The backend hoists these to the top-level of the tool result so the SDK sees them. This lets you compute the spec dynamically per-call.
+
+## Further reading
+
+- Full recipe book: see `llms.txt` in the package root (or fetch `https://unpkg.com/@aigentyc/chat-sdk/llms.txt`)
+- Package: https://www.npmjs.com/package/@aigentyc/chat-sdk
+- Dashboard (get projectId + apiKey): https://app.aigentyc.ai
+
+## When you finish a change
+
+Check: did you add an `apiKey`? Did you pass `projectId` + `apiEndpoint`? Did you import the CSS exactly once in the layout/root? For slot overrides — did you use the correct slot name (warnings land in dev console)?

package/context7.json

@@ -1,4 +1,4 @@
 {
-  "url": "https://context7.com/llmstxt/cdn_jsdelivr_net_npm_aigentyc_chat-sdk_0_2_5_llms_txt",
+  "url": "https://context7.com/llmstxt/cdn_jsdelivr_net_npm_aigentyc_chat-sdk_0_3_0_llms_txt",
   "public_key": "pk_dHiyF4hGXkgbb1jdrT7TU"
 }

package/dist/ChatInterface-B0zbA3Lm.d.cts

@@ -0,0 +1,64 @@
+import * as react_jsx_runtime from 'react/jsx-runtime';
+import { Q as QuestionConfig } from './types-DlNwk-bG.cjs';
+
+interface ChatInterfaceProps {
+    /** Allow per-instance overrides of any context value */
+    isOpen?: boolean;
+    onClose?: () => void;
+    onNewConversation?: () => void;
+    logoUrl?: string;
+    questions?: QuestionConfig[];
+    pageQuestions?: QuestionConfig[];
+    footerText?: string;
+    welcomeTitle?: string;
+    welcomeSubtitle?: string;
+    hideWelcomeHeader?: boolean;
+    showFirstMessage?: boolean;
+    hideHeader?: boolean;
+    pendingMessage?: string | null;
+    onPendingMessageConsumed?: () => void;
+    pageUrl?: string;
+    pageTitle?: string;
+    pageContextLoading?: boolean;
+    pageWelcomeTitle?: string;
+    pageWelcomeSubtitle?: string;
+    questionsLayout?: "vertical" | "horizontal";
+    questionsLayoutMobile?: "vertical" | "horizontal";
+    /**
+     * Show citation sources under each assistant message that used the
+     * `searchKnowledgeBase` tool. Off by default.
+     */
+    showSources?: boolean;
+    /**
+     * Controls the rendering order of message parts (text vs tool results).
+     * - `"text-first"` (default) — text parts render before tool cards
+     * - `"tools-first"` — tool cards render before text
+     * - `"stream-order"` — parts render in the order received from the API
+     */
+    messagePartOrder?: "text-first" | "tools-first" | "stream-order";
+}
+interface AssistantMessageSlotProps {
+    message: {
+        id: string;
+        parts?: Array<{
+            type: string;
+            text?: string;
+        }>;
+    };
+    partIndex: number;
+    text: string;
+}
+interface UserMessageSlotProps {
+    message: {
+        id: string;
+        parts?: Array<{
+            type: string;
+            text?: string;
+        }>;
+    };
+    partIndex: number;
+    text: string;
+}
+declare function ChatInterface(props: ChatInterfaceProps): react_jsx_runtime.JSX.Element;
+
+export { type AssistantMessageSlotProps as A, type ChatInterfaceProps as C, type UserMessageSlotProps as U, ChatInterface as a };

package/dist/ChatInterface-f8ftS56n.d.ts

@@ -0,0 +1,64 @@
+import * as react_jsx_runtime from 'react/jsx-runtime';
+import { Q as QuestionConfig } from './types-DlNwk-bG.js';
+
+interface ChatInterfaceProps {
+    /** Allow per-instance overrides of any context value */
+    isOpen?: boolean;
+    onClose?: () => void;
+    onNewConversation?: () => void;
+    logoUrl?: string;
+    questions?: QuestionConfig[];
+    pageQuestions?: QuestionConfig[];
+    footerText?: string;
+    welcomeTitle?: string;
+    welcomeSubtitle?: string;
+    hideWelcomeHeader?: boolean;
+    showFirstMessage?: boolean;
+    hideHeader?: boolean;
+    pendingMessage?: string | null;
+    onPendingMessageConsumed?: () => void;
+    pageUrl?: string;
+    pageTitle?: string;
+    pageContextLoading?: boolean;
+    pageWelcomeTitle?: string;
+    pageWelcomeSubtitle?: string;
+    questionsLayout?: "vertical" | "horizontal";
+    questionsLayoutMobile?: "vertical" | "horizontal";
+    /**
+     * Show citation sources under each assistant message that used the
+     * `searchKnowledgeBase` tool. Off by default.
+     */
+    showSources?: boolean;
+    /**
+     * Controls the rendering order of message parts (text vs tool results).
+     * - `"text-first"` (default) — text parts render before tool cards
+     * - `"tools-first"` — tool cards render before text
+     * - `"stream-order"` — parts render in the order received from the API
+     */
+    messagePartOrder?: "text-first" | "tools-first" | "stream-order";
+}
+interface AssistantMessageSlotProps {
+    message: {
+        id: string;
+        parts?: Array<{
+            type: string;
+            text?: string;
+        }>;
+    };
+    partIndex: number;
+    text: string;
+}
+interface UserMessageSlotProps {
+    message: {
+        id: string;
+        parts?: Array<{
+            type: string;
+            text?: string;
+        }>;
+    };
+    partIndex: number;
+    text: string;
+}
+declare function ChatInterface(props: ChatInterfaceProps): react_jsx_runtime.JSX.Element;
+
+export { type AssistantMessageSlotProps as A, type ChatInterfaceProps as C, type UserMessageSlotProps as U, ChatInterface as a };

package/dist/{SlotsContext-CBtt36al.d.ts → SlotsContext-BjiX1mRx.d.ts}

@@ -1,5 +1,6 @@
+import * as React from 'react';
 import { RefObject, ComponentType } from 'react';
-import { f as LiveChatState, e as LiveChatMessage, C as ChatProviderProps, c as ChatMessage, a as ChatConfig, b as ChatEventCallbacks } from './types-DKJ_-nbG.js';
+import { f as LiveChatState, e as LiveChatMessage, C as ChatProviderProps, c as ChatMessage, a as ChatConfig, b as ChatEventCallbacks } from './types-DlNwk-bG.js';
 
 type ChatStatus$1 = "idle" | "streaming" | "error";
 interface ActiveTool$1 {
@@ -144,5 +145,19 @@ declare function useSlots(): SlotMap;
  * Returns the override component for the given slot name, or undefined if none is set.
  */
 declare function useSlot<P = Record<string, unknown>>(name: SlotName): SlotComponent<P> | undefined;
+/**
+ * Renders a slot: if an override exists, renders it with `{...props, DefaultComponent}`.
+ * Otherwise renders the DefaultComponent with the given props.
+ *
+ * The generic `P` is NOT constrained to `Record<string, unknown>` so concrete
+ * component prop types (e.g. `ChatHeaderProps`) flow through at call sites
+ * without `as never` casts. Internal spreads are cast through
+ * `Record<string, unknown>` — safe because JSX spread accepts any record.
+ *
+ * @param name - The slot name
+ * @param props - Props to pass to the component
+ * @param DefaultComponent - The built-in fallback component
+ */
+declare function renderSlot<P>(name: SlotName, props: P, DefaultComponent: ComponentType<P>, slots: SlotMap): React.ReactElement;
 
-export { type LiveChatReturn as L, type UseAigentycChatOptions as U, type UseAigentycChatReturn as a, useChatContext as b, useLiveChat as c, useSlot as d, useSlots as e, useAigentycChat as u };
+export { type LiveChatReturn as L, type SlotComponent as S, type UseAigentycChatOptions as U, type SlotName as a, type UseAigentycChatReturn as b, useChatContext as c, useLiveChat as d, useSlot as e, useSlots as f, renderSlot as r, useAigentycChat as u };