@copilotkitnext/core 1.54.0-next.6 → 1.54.0-next.7

package/dist/index.cjs

@@ -891,7 +891,10 @@ var RunHandler = class {
 				}
 			}
 		}
-		if (needsFollowUp) return await this.runAgent({ agent });
+		if (needsFollowUp) {
+			await this._internal.waitForPendingFrameworkUpdates();
+			return await this.runAgent({ agent });
+		}
 		this._internal.suggestionEngine.reloadSuggestions(agentId);
 		return runAgentResult;
 	}
@@ -1172,6 +1175,7 @@ var RunHandler = class {
 				};
 				agent.messages.push(userMessage);
 			}
+			await this._internal.waitForPendingFrameworkUpdates();
 			await this.runAgent({ agent });
 		}
 		return {
@@ -1685,6 +1689,24 @@ var CopilotKitCore = class {
 	buildFrontendTools(agentId) {
 		return this.runHandler.buildFrontendTools(agentId);
 	}
+	/**
+	* Called before each follow-up agent run (after tool execution).
+	*
+	* When a frontend tool handler calls framework state setters (e.g. React's
+	* setState), those updates are batched and deferred — they do not take effect
+	* until the framework's scheduler runs (React uses MessageChannel).
+	* useAgentContext registers context via useLayoutEffect, which runs
+	* synchronously after React commits that deferred batch.
+	*
+	* Without yielding here, the follow-up runAgent reads the context store
+	* synchronously while the deferred updates are still pending, producing stale
+	* context for the next agent turn.
+	*
+	* Override in framework-specific subclasses to yield to the framework
+	* scheduler before the follow-up run. The base implementation is a no-op
+	* because non-React environments have no deferred state to flush.
+	*/
+	async waitForPendingFrameworkUpdates() {}
 };
 
 //#endregion