@copilotkit/react-core 1.56.5-canary.1778052912 → 1.56.5-canary.1778068503

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@copilotkit/react-core",
-  "version": "1.56.5-canary.1778052912",
+  "version": "1.56.5-canary.1778068503",
   "private": false,
   "keywords": [
     "ai",
@@ -73,11 +73,11 @@
     "untruncate-json": "^0.0.1",
     "use-stick-to-bottom": "^1.1.1",
     "zod-to-json-schema": "^3.24.5",
-    "@copilotkit/a2ui-renderer": "1.56.5-canary.1778052912",
-    "@copilotkit/web-inspector": "1.56.5-canary.1778052912",
-    "@copilotkit/shared": "1.56.5-canary.1778052912",
-    "@copilotkit/runtime-client-gql": "1.56.5-canary.1778052912",
-    "@copilotkit/core": "1.56.5-canary.1778052912"
+    "@copilotkit/a2ui-renderer": "1.56.5-canary.1778068503",
+    "@copilotkit/core": "1.56.5-canary.1778068503",
+    "@copilotkit/runtime-client-gql": "1.56.5-canary.1778068503",
+    "@copilotkit/shared": "1.56.5-canary.1778068503",
+    "@copilotkit/web-inspector": "1.56.5-canary.1778068503"
   },
   "devDependencies": {
     "@tailwindcss/cli": "^4.1.11",

package/src/v2/components/chat/CopilotChatMessageView.tsx

@@ -8,11 +8,12 @@ import React, {
 } from "react";
 import { useVirtualizer } from "@tanstack/react-virtual";
 import { ScrollElementContext } from "./scroll-element-context";
-import { WithSlots, renderSlot, isReactComponentType } from "../../lib/slots";
+import type { WithSlots } from "../../lib/slots";
+import { renderSlot, isReactComponentType } from "../../lib/slots";
 import CopilotChatAssistantMessage from "./CopilotChatAssistantMessage";
 import CopilotChatUserMessage from "./CopilotChatUserMessage";
 import CopilotChatReasoningMessage from "./CopilotChatReasoningMessage";
-import {
+import type {
   ActivityMessage,
   AssistantMessage,
   Message,
@@ -283,63 +284,25 @@ const MemoizedCustomMessage = React.memo(
       message: Message;
       position: "before" | "after";
     }) => React.ReactElement | null;
-    stateSnapshot: unknown;
-    numberOfMessagesInRun: number | undefined;
-    isInLatestRun: boolean | undefined;
-    isRunning: boolean;
+    stateSnapshot?: unknown;
   }) {
     return renderCustomMessage({ message, position });
   },
   (prevProps, nextProps) => {
-    // Skip the re-render unless an input that an authored renderer can
-    // observe has changed. Each branch returns false to invalidate.
+    // Only re-render if the message or position changed
     if (prevProps.message.id !== nextProps.message.id) return false;
     if (prevProps.position !== nextProps.position) return false;
+    // Compare message content - for assistant messages this is a string, for others may differ
     if (prevProps.message.content !== nextProps.message.content) return false;
     if (prevProps.message.role !== nextProps.message.role) return false;
-    // State snapshot — custom renderers may read it. Deep-compare via
-    // JSON.stringify (state-manager already deep-copies on each call, so
-    // reference equality would never hit anyway).
+    // Compare state snapshot - custom renderers may depend on state
     if (
       JSON.stringify(prevProps.stateSnapshot) !==
       JSON.stringify(nextProps.stateSnapshot)
     )
       return false;
-    // Re-render when this message's run grows. The runId-to-message
-    // association is unidirectional in StateManager (only set, never
-    // revoked except via clearAgentState/clearThreadState which wipe
-    // wholesale), so in practice this fires only on growth as new messages
-    // stream into the run. Slots in completed runs are unaffected — their
-    // count is stable once the run has finished.
-    if (prevProps.numberOfMessagesInRun !== nextProps.numberOfMessagesInRun)
-      return false;
-    // Re-render when this message's run stops being the latest run on the
-    // thread — e.g. a new run starts and previously-completed messages need
-    // to drop "is this the latest activity?" indicators. Only the slots
-    // belonging to the run that just lost its "latest" status are
-    // invalidated; the new run's slots and any older runs are unaffected.
-    if (prevProps.isInLatestRun !== nextProps.isInLatestRun) return false;
-    // Re-render when isRunning flips, but only for slots known to belong
-    // to the latest run (`isInLatestRun === true`). Slots whose run is
-    // older or whose run-id hasn't been recorded yet (undefined) are not
-    // invalidated on isRunning changes — this preserves the perf guarantee
-    // that completed messages skip re-renders during streaming.
-    //
-    // Renderers that gate solely on `agent.isRunning` and attach to a
-    // message added before any run started (e.g. a user message inserted
-    // before runAgent fires) won't observe the false→true transition for
-    // the first run. In practice this is rare; the canonical pattern is
-    // to gate on the slot's own runId membership (see
-    // intelligence-indicator/__tests__/IntelligenceIndicator.e2e.test.tsx
-    // for the recommended renderer shape).
-    if (
-      nextProps.isInLatestRun &&
-      prevProps.isRunning !== nextProps.isRunning
-    )
-      return false;
-    // Note: renderCustomMessage's reference is intentionally not compared —
-    // it's a closure that changes frequently. The inputs above are the only
-    // observable signals.
+    // Note: We don't compare renderCustomMessage function reference because it changes
+    // frequently. The message and state comparison is sufficient to determine if a re-render is needed.
     return true;
   },
 );
@@ -453,48 +416,6 @@ export function CopilotChatMessageView({
     return () => subscription.unsubscribe();
   }, [copilotkit]);
 
-  // Build per-run metadata once per render, not once per message. The two
-  // memo inputs MemoizedCustomMessage cares about (numberOfMessagesInRun and
-  // isInLatestRun) are both derived from the same scan of `messages` →
-  // `getRunIdForMessage`, so consolidating here turns an O(n²) per-render
-  // pass (one O(n) helper call per message) into a single O(n) pass.
-  //
-  // Re-fires whenever messages, the active agent/thread, or copilotkit
-  // changes. The internal messageToRun map can update without these props
-  // changing (a runId association lands one tick after the message is
-  // appended) — in that case the next external trigger refreshes. Note
-  // the `MemoizedCustomMessage` gate at the `isInLatestRun &&` check is
-  // strict-truthy — slots whose runId is still undefined during that
-  // pre-association window will not re-render on isRunning flips. The
-  // canonical pattern (see the IntelligenceIndicator e2e test) is to gate
-  // the renderer on the slot's own runId membership rather than `isRunning`
-  // alone, so the limitation doesn't bite typical use.
-  const runMetadata = useMemo(() => {
-    if (!config) return null;
-    const runIdByMessageId = new Map<string, string>();
-    for (const msg of messages) {
-      const r = copilotkit.getRunIdForMessage(
-        config.agentId,
-        config.threadId,
-        msg.id,
-      );
-      if (r) runIdByMessageId.set(msg.id, r);
-    }
-    const countByRunId = new Map<string, number>();
-    for (const r of runIdByMessageId.values()) {
-      countByRunId.set(r, (countByRunId.get(r) ?? 0) + 1);
-    }
-    let latestRunId: string | undefined;
-    for (let i = messages.length - 1; i >= 0; i--) {
-      const r = runIdByMessageId.get(messages[i]!.id);
-      if (r) {
-        latestRunId = r;
-        break;
-      }
-    }
-    return { runIdByMessageId, countByRunId, latestRunId };
-  }, [messages, config?.agentId, config?.threadId, copilotkit]);
-
   // Helper to get state snapshot for a message (used for memoization)
   const getStateSnapshotForMessage = (messageId: string): unknown => {
     if (!config) return undefined;
@@ -619,14 +540,6 @@ export function CopilotChatMessageView({
   const renderMessageBlock = (message: Message): React.ReactElement[] => {
     const elements: (React.ReactElement | null | undefined)[] = [];
     const stateSnapshot = getStateSnapshotForMessage(message.id);
-    const messageRunId = runMetadata?.runIdByMessageId.get(message.id);
-    const numberOfMessagesInRun = messageRunId
-      ? runMetadata?.countByRunId.get(messageRunId)
-      : undefined;
-    const isInLatestRun =
-      messageRunId === undefined
-        ? undefined
-        : messageRunId === runMetadata?.latestRunId;
 
     if (renderCustomMessage) {
       elements.push(
@@ -636,9 +549,6 @@ export function CopilotChatMessageView({
           position="before"
           renderCustomMessage={renderCustomMessage}
           stateSnapshot={stateSnapshot}
-          numberOfMessagesInRun={numberOfMessagesInRun}
-          isInLatestRun={isInLatestRun}
-          isRunning={isRunning}
         />,
       );
     }
@@ -692,24 +602,18 @@ export function CopilotChatMessageView({
           position="after"
           renderCustomMessage={renderCustomMessage}
           stateSnapshot={stateSnapshot}
-          numberOfMessagesInRun={numberOfMessagesInRun}
-          isInLatestRun={isInLatestRun}
-          isRunning={isRunning}
         />,
       );
     }
 
     // Auto-mount the IntelligenceIndicator on assistant message slots
     // when the runtime is in intelligence mode. The component self-gates
-    // further (last in run, latest run, matching tool call) so only one
-    // pill renders at a time — but mounting it only for assistant
-    // messages avoids spinning up a `useAgent` subscription, a 200 ms
-    // poll interval, and four effects on every user/reasoning/activity
-    // slot just to have it return null at the role gate.
-    if (
-      copilotkit.intelligence !== undefined &&
-      message.role === "assistant"
-    ) {
+    // further (latest matching-assistant slot, pending tool-call grace
+    // window) so only one pill renders at a time — mounting only for
+    // assistant messages avoids the per-slot `useAgent` subscription
+    // and four effects on user/reasoning/activity slots that would just
+    // return null at the role gate anyway.
+    if (copilotkit.intelligence !== undefined && message.role === "assistant") {
       elements.push(
         <IntelligenceIndicator
           key={`${message.id}-intelligence`}

package/src/v2/components/chat/__tests__/CopilotChatActivityRendering.e2e.test.tsx

@@ -313,13 +313,13 @@ describe("CopilotChat activity message rendering", () => {
     //
     // The trap this catches is a refactor where the renderer pipeline keys
     // on something other than `config.agentId` (e.g. for proxied
-    // registrations, accidentally keying on `proxy.remoteAgentId`). The
+    // registrations, accidentally keying on `proxy.runtimeAgentId`). The
     // assertion shape — "two agents in the registry, the renderer must
     // receive the one matching config.agentId" — is generic to that bug
     // class. The proxy-routing-specific behavior (registering a
-    // ProxiedCopilotRuntimeAgent with `remoteAgentId !== agentId` and
+    // ProxiedCopilotRuntimeAgent with `runtimeAgentId !== agentId` and
     // verifying `getAgent(agentId)` returns the proxy, not the agent at
-    // remoteAgentId) is covered by `core-register-proxied-agent.test.ts`
+    // runtimeAgentId) is covered by `core-register-proxied-agent.test.ts`
     // at the registry level.
     const localAgent = new MockStepwiseAgent();
     localAgent.agentId = "chat-1";