@coral-ai/chat 0.4.2 → 0.6.0

package/README.md

@@ -22,4 +22,18 @@ import { Chat } from "@coral-ai/chat";
 `ChatChunk`s, or a `ChatResponse`. A backend URL can also be supplied via the
 `api` prop or `coral.config.json`'s `chat.api`.
 
+`disclaimer?: React.ReactNode` adds optional content beneath the input. By
+default no disclaimer or footer space is rendered; `undefined`, `null`, and
+`false` also hide it. To retain the previous built-in text, opt in explicitly:
+
+```tsx
+<Chat api="/api/chat" disclaimer="AI makes mistakes. Check outputs." />
+```
+
+Custom React content, such as a policy link, is also supported.
+
 See [coral-ai](https://github.com/mochimilk/coral-ai) for the full project.
+
+## Migrating to 0.6
+
+User-message editing and `useChatContext().editMessage` have been removed. Assistant Copy/Regenerate and error Retry remain. The disclaimer is opt-in: pass `disclaimer` to render footer content; omission reserves no space. Sidecars use the true default 15px assistant font. Message rows use a 0px gap; footer buttons are small with a 2px gap.

package/dist/index.d.ts

@@ -44,18 +44,29 @@ type ChatMessage = {
     approval?: ChatApprovalRequest;
     /**
      * If present, this assistant message carries a multi-step task plan.
-     * Rendered inline as a collapsible checklist above the message text and
-     * persists in history for replay. Updated in place as the agent streams.
+     * Legacy field — new messages use `blocks` to position the todo list
+     * inline at the stream point where it first appeared. Still read by the
+     * renderer as a fallback for persisted messages saved before blocks.
      */
     todos?: ChatTodo[];
     /**
      * If present, this assistant message carries one or more chart specs.
-     * Rendered inline (above the message text) via `<CoralChart>` from
-     * `@coral-ai/charts`. Streamed in incrementally as the agent calls the
-     * built-in `render_chart` tool, and persisted with the conversation so
-     * the visualizations survive reloads.
+     * Legacy field — new messages use `blocks` to position each chart at
+     * the stream point where it was emitted. Still read by the renderer
+     * as a fallback for persisted messages saved before blocks.
      */
     charts?: CoralChartSpec[];
+    /**
+     * Ordered list of inline blocks (text, charts, todos) in the order the
+     * agent emitted them. Renderers iterate this in stream order so a chart
+     * tool call appears at the exact point in the prose where it happened,
+     * matching the convention used by Claude.ai and ChatGPT.
+     *
+     * When absent, the renderer synthesizes blocks from the legacy
+     * `content` / `charts` / `todos` fields so old persisted conversations
+     * still display correctly.
+     */
+    blocks?: ChatBlock[];
     /**
      * If present, the turn that produced this assistant message failed. The
      * message renders as an error card (with a Retry button) instead of normal
@@ -97,6 +108,22 @@ type ChatApprovalRequest = {
         text?: string;
     };
 };
+/**
+ * One inline block within an assistant message. Blocks are rendered in the
+ * order the agent emitted them, so charts and todo lists appear at the exact
+ * stream position where they happened (e.g. text → chart → text), rather than
+ * being pinned above the message.
+ */
+type ChatBlock = {
+    type: "text";
+    content: string;
+} | {
+    type: "chart";
+    spec: CoralChartSpec;
+} | {
+    type: "todos";
+    todos: ChatTodo[];
+};
 /**
  * One step in a multi-step task plan. The agent emits the whole list on each
  * update; the convention is exactly one item `in_progress` at a time.
@@ -200,6 +227,8 @@ interface ChatProps {
      * to invoke `sendMessage(text)` on click.
      */
     promptSuggestions?: React__default.ReactNode;
+    /** Optional content below the input. Omit or pass null to render no footer or reserved space. */
+    disclaimer?: React__default.ReactNode;
     /**
      * Pass `null` to disable the chat's built-in surface motion (input slide to
      * bottom on first message). Omit / leave undefined for default motion.
@@ -523,11 +552,6 @@ interface ChatContextValue {
      * If `messageId` targets a user message, the existing assistant reply for that turn is discarded and re-generated.
      */
     regenerate: (messageId?: string) => Promise<void>;
-    /**
-     * Replaces the content of an existing user message and re-runs from that point.
-     * Truncates everything after the edited message and re-invokes the handler.
-     */
-    editMessage: (messageId: string, newContent: string) => Promise<void>;
     scrollToBottom: () => void;
     /** Pre-binds navigator.clipboard.writeText + the onCopy prop callback. */
     handleCopy: (content: string) => void;