fix(react-core): IntelligenceIndicator stays through tool-result interleaving

The pill's gate "the message must be the last message of its run" was
suppressed every time a `role: "tool"` result arrived between
successive assistant-with-tool-call messages. Real MCP recall flows
always interleave tool results between assistant tool-call messages,
so the assistant message holding the matching tool call lost its
"last in run" claim immediately, the indicator returned `null`, and
the pill flashed off. By the time the run finished, the final
prose-only assistant message was the last in the run and the pill
on the bash-bearing assistant stayed suppressed. Net result: the
user saw no pill at all during a real recall.

Change the gate to "the latest assistant-with-matching-tool-call
message in the run". Tool result messages (`role: "tool"`) and
prose-only assistant messages now skip through the walk without
invalidating an earlier matching-assistant's claim on the slot, so
the pill stays continuously through a multi-step tool chain and
transitions to checkmark on `isRunning` falling (debounced 500 ms,
unchanged) as before.

The existing test suite did not cover this case — none of the
walkthrough scenarios emit `role: "tool"` between successive
assistant messages. A regression test that interleaves a tool result
will land alongside this fix.

Author: lukasmoschitz

packages/react-core/src/v2/components/intelligence-indicator/IntelligenceIndicator.tsx

@@ -76,10 +76,16 @@ export interface IntelligenceIndicatorProps {
  *   1. `copilotkit.intelligence !== undefined` (Intelligence runtime
  *      is configured; checked by the parent before mounting, and
  *      again here as a defence)
- *   2. The message is the last message of its run
+ *   2. The message is an assistant message with at least one tool call
+ *      whose name matches {@link DEFAULT_TOOL_PATTERNS}
  *   3. The message's run is the latest run on the thread
- *   4. The message has at least one tool call whose name matches
- *      {@link DEFAULT_TOOL_PATTERNS}
+ *   4. The message is the *latest* such matching-assistant message in
+ *      its run — i.e. no later assistant-with-matching-tool-call
+ *      message exists in the same run. Tool result messages
+ *      (`role: "tool"`) and prose-only assistant messages do NOT
+ *      invalidate this slot, so the pill stays continuously through a
+ *      multi-step bash chain instead of flickering off every time a
+ *      tool result arrives.
  *   5. The phase machine is not yet `hidden`
  *
  * Phase machine (per-instance, all timers local):
@@ -185,31 +191,54 @@ export function IntelligenceIndicator(
   if (!hasMatch) return null;
 
   // The message must belong to the latest run on the thread, AND must
-  // be the LAST message in its run. We derive both by walking
-  // `agent.messages` from the end:
+  // be the latest assistant-with-matching-tool-call message in its
+  // run. We derive both by walking `agent.messages` from the end:
   //   - the most recent run-associated message defines the latest run
-  //   - if `message` is the last message in `agent.messages` whose
-  //     runId matches `messageRunId`, it's the last in its run
+  //   - the first match-eligible assistant message we hit (walking
+  //     backwards) within `messageRunId` is the canonical pill slot
+  //
+  // Tool result messages (`role: "tool"`) and prose-only assistant
+  // messages are skipped during the walk: they don't invalidate an
+  // earlier matching-assistant message's claim on the slot. This is
+  // what keeps the pill continuously visible through a multi-step
+  // tool chain (each MCP tool reply is a `role: "tool"` message that
+  // would otherwise become "the last message in the run" and suppress
+  // the pill on every cycle).
   const messageRunId = copilotkit.getRunIdForMessage(
     agentId,
     config.threadId,
     message.id,
   );
   if (!messageRunId) return null;
   let latestRunId: string | undefined;
-  let lastMessageIdInThisRun: string | undefined;
+  let latestMatchingAssistantIdInRun: string | undefined;
   for (let i = agent.messages.length - 1; i >= 0; i -= 1) {
     const m = agent.messages[i]!;
     const r = copilotkit.getRunIdForMessage(agentId, config.threadId, m.id);
     if (latestRunId === undefined && r) latestRunId = r;
-    if (lastMessageIdInThisRun === undefined && r === messageRunId) {
-      lastMessageIdInThisRun = m.id;
+    if (
+      latestMatchingAssistantIdInRun === undefined &&
+      r === messageRunId &&
+      m.role === "assistant"
+    ) {
+      const tcs = Array.isArray(m.toolCalls) ? m.toolCalls : [];
+      const isMatch = tcs.some((tc) => {
+        const name = tc?.function?.name;
+        return (
+          typeof name === "string" &&
+          DEFAULT_TOOL_PATTERNS.some((p) => p.test(name))
+        );
+      });
+      if (isMatch) latestMatchingAssistantIdInRun = m.id;
     }
-    if (latestRunId !== undefined && lastMessageIdInThisRun !== undefined)
+    if (
+      latestRunId !== undefined &&
+      latestMatchingAssistantIdInRun !== undefined
+    )
       break;
   }
   if (latestRunId !== messageRunId) return null;
-  if (lastMessageIdInThisRun !== message.id) return null;
+  if (latestMatchingAssistantIdInRun !== message.id) return null;
 
   // ─── Visual ──────────────────────────────────────────────────────────