@tanstack/ai-client 0.34.0 → 0.35.1

package/dist/esm/chat-client.d.ts

@@ -143,6 +143,8 @@ export declare class ChatClient<TTools extends ReadonlyArray<AnyClientTool> = an
     private readonly activeRunIds;
     /** Latched by `dispose()`; stops any late async callback starting new work. */
     private disposed;
+    /** The error a failed mount hydration set, cleared by the next successful one. */
+    private hydrationError;
     /** Whether a view is currently watching. See `attach` / `detach`. */
     private tailing;
     /** Constructor inputs `attach()` needs on every re-attach, not just the first. */
@@ -219,6 +221,19 @@ export declare class ChatClient<TTools extends ReadonlyArray<AnyClientTool> = an
      * send that starts first owns the client (hydration then backs off).
      */
     private hydrateFromServer;
+    /**
+     * Surface a mount-hydration failure (`persistence: true`) on the observable
+     * fields, mirroring `GenerationClient.failHydration`, so "this thread failed
+     * to load" is distinguishable from "this thread has no messages" and the app
+     * can show an error / offer a retry. A genuine miss — the server having no
+     * record for a fresh thread — resolves normally and never reaches here; only a
+     * thrown transport / authorize-gate error does.
+     *
+     * Skipped when the view unmounted (`!tailing`) or a `sendMessage` took
+     * ownership while the hydrate GET was in flight, so a live run's state always
+     * wins over a stale mount-time failure — same guard as the success path above.
+     */
+    private failHydration;
     mountDevtools(): void;
     private ensureThreadId;
     /**

package/dist/esm/chat-client.js

@@ -138,10 +138,16 @@ var REJOIN_CONNECT_DEADLINE_MS = 2e3;
 var REJOIN_REBUILD_TRIGGERS = /* @__PURE__ */ new Set([
 	"TEXT_MESSAGE_START",
 	"TEXT_MESSAGE_CONTENT",
+	"REASONING_MESSAGE_CONTENT",
 	"TOOL_CALL_START",
 	"MESSAGES_SNAPSHOT",
 	"SUBAGENT_STARTED"
 ]);
+function rebuildsAssistantMessage(chunk) {
+	if (chunk.type === "REASONING_ENCRYPTED_VALUE") return chunk.subtype === "message" && typeof chunk.encryptedValue === "string" && chunk.encryptedValue.length > 0;
+	if (chunk.type === "STEP_FINISHED") return "signature" in chunk && Boolean(chunk.signature);
+	return REJOIN_REBUILD_TRIGGERS.has(chunk.type);
+}
 /** Every subagent card in the messages, nested cards included. */
 function collectSubagentParts(messages) {
 	const cards = [];
@@ -258,6 +264,8 @@ var ChatClient = class {
 	activeRunIds = /* @__PURE__ */ new Set();
 	/** Latched by `dispose()`; stops any late async callback starting new work. */
 	disposed = false;
+	/** The error a failed mount hydration set, cleared by the next successful one. */
+	hydrationError;
 	/** Whether a view is currently watching. See `attach` / `detach`. */
 	tailing = false;
 	/** Constructor inputs `attach()` needs on every re-attach, not just the first. */
@@ -556,12 +564,18 @@ var ChatClient = class {
 			const generation = this.historyGeneration;
 			try {
 				result = await hydrate(this.threadId, hydrateOptions);
-			} catch {
+			} catch (cause) {
+				if (generation === this.historyGeneration) this.failHydration(cause);
 				return;
 			}
 			if (generation !== this.historyGeneration) return;
 			if (this.disposed || !this.tailing) return;
 			if (this.isLoading || this.abortController) return;
+			if (this.hydrationError && this.error === this.hydrationError) {
+				this.setError(void 0);
+				this.setStatus("ready");
+			}
+			this.hydrationError = void 0;
 			this.applyHydrationPage(result.page);
 			if (result.messages.length > 0) {
 				const windowMessages = normalizeMessagesDates(result.messages);
@@ -578,6 +592,29 @@ var ChatClient = class {
 			else if (result.activeRun?.runId) this.maybeRejoinInFlight(result.activeRun.runId);
 		})();
 	}
+	/**
+	* Surface a mount-hydration failure (`persistence: true`) on the observable
+	* fields, mirroring `GenerationClient.failHydration`, so "this thread failed
+	* to load" is distinguishable from "this thread has no messages" and the app
+	* can show an error / offer a retry. A genuine miss — the server having no
+	* record for a fresh thread — resolves normally and never reaches here; only a
+	* thrown transport / authorize-gate error does.
+	*
+	* Skipped when the view unmounted (`!tailing`) or a `sendMessage` took
+	* ownership while the hydrate GET was in flight, so a live run's state always
+	* wins over a stale mount-time failure — same guard as the success path above.
+	*/
+	failHydration(cause) {
+		if (this.disposed || !this.tailing) return;
+		if (this.isLoading || this.abortController) return;
+		const error = cause instanceof Error ? cause : new Error(String(cause));
+		if (error instanceof ByokMissingError) this.byok?.request(error.provider, "missing");
+		if (error instanceof ByokBlockedError && error.reason === "locked") this.byok?.request(error.provider, "locked");
+		this.hydrationError = error;
+		this.setStatus("error");
+		this.setError(error);
+		this.callbacksRef.current.onError(error);
+	}
 	mountDevtools() {
 		this.ensureThreadId();
 		if (this.devtoolsMounted) return;
@@ -1033,7 +1070,7 @@ var ChatClient = class {
 						attached = true;
 						clearTimeout(connectTimer);
 					}
-					if (!rebuilt && REJOIN_REBUILD_TRIGGERS.has(chunk.type)) {
+					if (!rebuilt && rebuildsAssistantMessage(chunk)) {
 						rebuilt = true;
 						this.dropTrailingInFlightAssistant();
 					}