@mastra/client-js 1.40.1-alpha.7 → 1.41.0-alpha.9

package/CHANGELOG.md

@@ -1,5 +1,38 @@
 # @mastra/client-js
 
+## 1.41.0-alpha.9
+
+### Patch Changes
+
+- Preserve tool-call `providerMetadata` at the message-part level during client-tool continuations. ([#21703](https://github.com/mastra-ai/mastra/pull/21703))
+
+  The stream reducers nested `providerMetadata` inside `toolInvocation`, but the server reads it from `part.providerMetadata` when rebuilding the prompt. As a result the metadata was dropped on the recursive request, and Gemini thinking models (e.g. `gemini-3-flash-preview`) failed the follow-up turn with `Function call is missing a thought_signature in functionCall parts`.
+
+- Updated dependencies [[`b0a2a07`](https://github.com/mastra-ai/mastra/commit/b0a2a07800d42bd9823292e7db832374ed084c9c), [`ccbbcd9`](https://github.com/mastra-ai/mastra/commit/ccbbcd974eedff4367a54ed0e24c9ee742ab2f61), [`3f5c6f7`](https://github.com/mastra-ai/mastra/commit/3f5c6f728ea35da344248de9aa070f12849f3aa0), [`77e6b1b`](https://github.com/mastra-ai/mastra/commit/77e6b1bc4c46ce94fe501023fb4393c812ec6be3), [`2e1d098`](https://github.com/mastra-ai/mastra/commit/2e1d0984e325fd319d32ea182f596b3170be3847)]:
+  - @mastra/core@1.60.0-alpha.9
+
+## 1.41.0-alpha.8
+
+### Minor Changes
+
+- Added `Agent.readPlan()` for loading submitted plan Markdown. ([#21658](https://github.com/mastra-ai/mastra/pull/21658))
+
+  ```ts
+  const agent = client.getAgent('agent-id');
+  const plan = await agent.readPlan('.mastracode/plans/add-dark-mode.md');
+  ```
+
+### Patch Changes
+
+- `session.state()` now accepts a `threadId`, so reopening a chat can load the durable task list for that specific thread. ([#21545](https://github.com/mastra-ai/mastra/pull/21545))
+
+  ```ts
+  const state = await session.state({ threadId: 'thread-123' });
+  ```
+
+- Updated dependencies [[`4e7a421`](https://github.com/mastra-ai/mastra/commit/4e7a421dce8a48742f785d1e93ad2f43a572b282), [`242e324`](https://github.com/mastra-ai/mastra/commit/242e3241e73cbd5c9bb86a31ebb49ca0256488d4), [`217e967`](https://github.com/mastra-ai/mastra/commit/217e9672d8b3160eb729d8e9f0044949e88da239), [`d774e89`](https://github.com/mastra-ai/mastra/commit/d774e8930c781df8c9effe3763e6b501c099b6cc), [`9c27a53`](https://github.com/mastra-ai/mastra/commit/9c27a53cd9d3de4f3f025bc387d94ce371c33f95), [`dff25a1`](https://github.com/mastra-ai/mastra/commit/dff25a1103fa72ee082a9b6f805ebeb5ce400753), [`217e967`](https://github.com/mastra-ai/mastra/commit/217e9672d8b3160eb729d8e9f0044949e88da239), [`7f78585`](https://github.com/mastra-ai/mastra/commit/7f785857e401570e2ffb316911f126ed363aa537), [`f2a4afd`](https://github.com/mastra-ai/mastra/commit/f2a4afd7e37e809669001ed17724b341a5c1f45e), [`d438148`](https://github.com/mastra-ai/mastra/commit/d438148e222c1e2fb3c652725ce75680962ebec4), [`ba05fe0`](https://github.com/mastra-ai/mastra/commit/ba05fe0738f70cb686777546e968237d09269142), [`d26a8d4`](https://github.com/mastra-ai/mastra/commit/d26a8d4281f28414715b333c85bedaf70d0b2890), [`677cdc6`](https://github.com/mastra-ai/mastra/commit/677cdc6af564dec29a13464d12b7ab2a4efc22e9), [`a318490`](https://github.com/mastra-ai/mastra/commit/a318490e17da32f338d50929c770d901a9b3dd72), [`763e0c6`](https://github.com/mastra-ai/mastra/commit/763e0c61e04d76ad9a9efd301aa57525ca0cbea9), [`23e0be2`](https://github.com/mastra-ai/mastra/commit/23e0be261381e49534b4ff3101c60ee64a946cbf), [`7fc8806`](https://github.com/mastra-ai/mastra/commit/7fc880627d3cbf995d31ea0e8b807bf15417e651), [`0e02eac`](https://github.com/mastra-ai/mastra/commit/0e02eacdb2e30e1697a41910b41163742a181dc1), [`4df174c`](https://github.com/mastra-ai/mastra/commit/4df174c32bddf093a82f273070b8380aef7c9e90), [`f7c25b5`](https://github.com/mastra-ai/mastra/commit/f7c25b5106ddfb48e591f98df7a51e0f2dd01dba), [`dc09cc1`](https://github.com/mastra-ai/mastra/commit/dc09cc1083d861cde192c1cd235324dc75b8c731), [`36b4649`](https://github.com/mastra-ai/mastra/commit/36b4649045a3a380cbab8ceca866db4086223aff), [`377eb81`](https://github.com/mastra-ai/mastra/commit/377eb81ce43b964e3a6b541df172da74a8ff3716)]:
+  - @mastra/core@1.60.0-alpha.8
+
 ## 1.40.1-alpha.7
 
 ### Patch Changes

package/dist/docs/SKILL.md

@@ -3,7 +3,7 @@ name: mastra-client-js
 description: Documentation for @mastra/client-js. Use when working with @mastra/client-js APIs, configuration, or implementation.
 metadata:
   package: "@mastra/client-js"
-  version: "1.40.1-alpha.7"
+  version: "1.41.0-alpha.9"
 ---
 
 ## When to use
@@ -16,12 +16,12 @@ Read the individual reference documents for detailed explanations and code examp
 
 ### Docs
 
-- [A2A (Agent-to-Agent)](references/docs-agents-a2a.md) - Expose and call remote Mastra agents over the Agent-to-Agent protocol.
-- [Editor](references/docs-editor-overview.md) - Let collaborators update an agent in Studio, test their changes, and publish without editing code.
-- [Schedules](references/docs-long-running-agents-schedules.md) - Run an agent on a cron schedule to deliver a recurring prompt, with optional thread delivery and lifecycle hooks.
-- [Signals](references/docs-long-running-agents-signals.md) - Learn how to send real-time messages and context into a Mastra agent thread.
-- [JSON Web Token](references/docs-server-auth-jwt.md) - Documentation for JSON Web Token usage inside Mastra.
+- [JSON Web Token](references/docs-auth-jwt.md) - Documentation for JSON Web Token usage inside Mastra.
+- [A2A (Agent-to-Agent)](references/docs-connections-a2a.md) - Expose and call remote Mastra agents over the Agent-to-Agent protocol.
+- [Schedules](references/docs-harness-schedules.md) - Run an agent on a cron schedule to deliver a recurring prompt, with optional thread delivery and lifecycle hooks.
+- [Signals](references/docs-harness-signals.md) - Learn how to send real-time messages and context into a Mastra agent thread.
 - [Mastra client](references/docs-server-mastra-client.md) - Learn how to set up and use the Mastra Client SDK
+- [Editor](references/docs-studio-editor.md) - Let collaborators update an agent in Studio, test their changes, and publish without editing code.
 
 ### Integrations
 

package/dist/docs/assets/SOURCE_MAP.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.40.1-alpha.7",
+  "version": "1.41.0-alpha.9",
   "package": "@mastra/client-js",
   "exports": {},
   "modules": {}

package/dist/docs/references/{docs-agents-a2a.md → docs-connections-a2a.md}

@@ -80,7 +80,7 @@ Use `A2AAgent` when another Mastra agent should delegate work to a remote agent.
 
 ## Consume A2A agents as subagents
 
-Use `A2AAgent` to wrap a remote A2A agent, then add it to a parent agent with the [supervisor agents](https://mastra.ai/docs/capabilities/subagents) pattern. Pass an explicit agent card URL when the remote server hosts multiple agents or uses a custom well-known path.
+Use `A2AAgent` to wrap a remote A2A agent, then add it to a parent agent with the [supervisor agents](https://mastra.ai/docs/subagents) pattern. Pass an explicit agent card URL when the remote server hosts multiple agents or uses a custom well-known path.
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -221,7 +221,7 @@ A2A models human-in-the-loop (HITL) work with the `input-required` task state. W
 
 Mastra maps its agent suspension model to this state in both directions:
 
-- **As a server**: when an exposed agent suspends, the task transitions to `input-required`. This includes suspensions caused by [tool approval](https://mastra.ai/docs/agents/agent-approval) or a tool that calls `suspend()`. The task status message includes a text prompt and a data part with the structured `suspendPayload` and `resumeSchema`. A follow-up `message/send` or `message/stream` request with the same `taskId` resumes the suspended run with the provided input.
+- **As a server**: when an exposed agent suspends, the task transitions to `input-required`. This includes suspensions caused by [tool approval](https://mastra.ai/docs/agents/human-in-the-loop) or a tool that calls `suspend()`. The task status message includes a text prompt and a data part with the structured `suspendPayload` and `resumeSchema`. A follow-up `message/send` or `message/stream` request with the same `taskId` resumes the suspended run with the provided input.
 - **As a client**: when a remote task reaches `input-required` or `auth-required`, `A2AAgent` returns a suspended result with `finishReason: 'suspended'` and a `suspendPayload`. Calling `resumeGenerate()` or `resumeStream()` sends the input or credentials back to the remote task with the original `taskId`.
 
 ```typescript

package/dist/docs/references/{docs-long-running-agents-schedules.md → docs-harness-schedules.md}

@@ -6,11 +6,11 @@
 
 > **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
-A schedule runs an agent on a cron cadence. On each fire, Mastra sends a prompt to the agent, either as a [signal](https://mastra.ai/docs/long-running-agents/signals) into a thread or as a threadless [`agent.generate()`](https://mastra.ai/reference/agents/generate) run. Use schedules for recurring agent work such as daily summaries, periodic checks, or scheduled nudges into a conversation.
+A schedule runs an agent on a cron cadence. On each fire, Mastra sends a prompt to the agent, either as a [signal](https://mastra.ai/docs/harness/signals) into a thread or as a threadless [`agent.generate()`](https://mastra.ai/reference/agents/generate) run. Use schedules for recurring agent work such as daily summaries, periodic checks, or scheduled nudges into a conversation.
 
 Schedules are persisted, so they survive restarts and redeploys. Manage them at runtime through [`mastra.schedules`](https://mastra.ai/reference/schedules/overview), the canonical create, read, update, and delete (CRUD) surface. The same surface also manages [workflow schedules](https://mastra.ai/docs/workflows/scheduled-workflows) (pass `workflowId` instead of `agentId` to schedule a workflow).
 
-> **Note:** Schedules require a [storage](https://mastra.ai/docs/storage/overview) adapter that implements the schedules domain. See the [`mastra.schedules` reference](https://mastra.ai/reference/schedules/overview) for supported adapters and API behavior.
+> **Note:** Schedules require a [storage](https://mastra.ai/docs/storage) adapter that implements the schedules domain. See the [`mastra.schedules` reference](https://mastra.ai/reference/schedules/overview) for supported adapters and API behavior.
 
 ## Quickstart
 
@@ -71,7 +71,7 @@ Without a `threadId`, each fire is an isolated `agent.generate()` run. Nothing i
 
 ### Threaded
 
-With a `threadId`, the schedule sends a [signal](https://mastra.ai/docs/long-running-agents/signals) into that thread, so the prompt joins the agent's conversation. Threaded schedules require a `resourceId` alongside the `threadId`.
+With a `threadId`, the schedule sends a [signal](https://mastra.ai/docs/harness/signals) into that thread, so the prompt joins the agent's conversation. Threaded schedules require a `resourceId` alongside the `threadId`.
 
 ```typescript
 await mastra.schedules.create({
@@ -83,7 +83,7 @@ await mastra.schedules.create({
 })
 ```
 
-Threaded schedules accept extra fields that control how the signal behaves, including the signal type, XML tag, tag attributes, and active-or-idle delivery behavior. They mirror the options [`agent.sendSignal()`](https://mastra.ai/docs/long-running-agents/signals) accepts and stay JSON-serializable so they persist with the schedule.
+Threaded schedules accept extra fields that control how the signal behaves, including the signal type, XML tag, tag attributes, and active-or-idle delivery behavior. They mirror the options [`agent.sendSignal()`](https://mastra.ai/docs/harness/signals) accepts and stay JSON-serializable so they persist with the schedule.
 
 These fields require a `threadId`. For the full threaded input shape, see the [agent schedule input reference](https://mastra.ai/reference/schedules/overview).
 
@@ -197,5 +197,5 @@ Hook exceptions are caught and logged. They never re-route the worker or trigger
 ## Related
 
 - [`mastra.schedules`](https://mastra.ai/reference/schedules/overview): API reference for creating and managing schedules.
-- [Signals](https://mastra.ai/docs/long-running-agents/signals): the delivery mechanism behind threaded schedules.
+- [Signals](https://mastra.ai/docs/harness/signals): the delivery mechanism behind threaded schedules.
 - [Scheduled workflows](https://mastra.ai/docs/workflows/scheduled-workflows): declare a cron schedule on a workflow definition.

package/dist/docs/references/docs-server-mastra-client.md

@@ -2,7 +2,7 @@
 
 # Mastra client
 
-The Mastra Client SDK provides a concise and type-safe interface for interacting with your [Mastra Server](https://mastra.ai/docs/server/mastra-server) from your client environment.
+The Mastra Client SDK provides a concise and type-safe interface for interacting with your [Mastra Server](https://mastra.ai/docs/server/overview) from your client environment.
 
 ## Prerequisites
 
@@ -59,7 +59,7 @@ export const mastraClient = new MastraClient({
 The Mastra Client SDK exposes all resources served by the Mastra Server.
 
 - **[Agents](https://mastra.ai/reference/client-js/agents)**: Generate responses and stream conversations.
-- **[A2A](https://mastra.ai/docs/agents/a2a)**: Discover agents through agent cards and work with task-based A2A streams.
+- **[A2A](https://mastra.ai/docs/connections/a2a)**: Discover agents through agent cards and work with task-based A2A streams.
 - **[Memory](https://mastra.ai/reference/client-js/memory)**: Manage conversation threads and message history.
 - **[Tools](https://mastra.ai/reference/client-js/tools)**: Executed and managed tools.
 - **[Workflows](https://mastra.ai/reference/client-js/workflows)**: Trigger workflows and track their execution.

package/dist/docs/references/integrations-auth-workos.md

@@ -89,7 +89,7 @@ By default, `MastraAuthWorkos` grants access to any authenticated WorkOS user. T
 
 ### FGA membership loading
 
-Set `fetchMemberships: true` when you use [`MastraFGAWorkos`](https://mastra.ai/docs/server/auth/fga). This tells the auth provider to load the user's WorkOS organization memberships during authentication so FGA checks can resolve the correct organization membership ID.
+Set `fetchMemberships: true` when you use [`MastraFGAWorkos`](https://mastra.ai/docs/auth/fga). This tells the auth provider to load the user's WorkOS organization memberships during authentication so FGA checks can resolve the correct organization membership ID.
 
 ```typescript
 import { MastraAuthWorkos, MastraFGAWorkos } from '@mastra/auth-workos'

package/dist/docs/references/reference-client-js-agents.md

@@ -285,7 +285,7 @@ await subscription.processDataStream({
 
 ### `streamUntilIdle()`
 
-Stream a response and keep the stream open until every [background task](https://mastra.ai/docs/long-running-agents/background-tasks) dispatched during the run completes. The server re-enters the agentic loop on each task completion so the LLM can react to results in the same call. Requires background tasks to be [enabled on the Mastra instance](https://mastra.ai/reference/configuration) and a memory thread; otherwise the call uses a plain `stream()`.
+Stream a response and keep the stream open until every [background task](https://mastra.ai/docs/harness/background-tasks) dispatched during the run completes. The server re-enters the agentic loop on each task completion so the LLM can react to results in the same call. Requires background tasks to be [enabled on the Mastra instance](https://mastra.ai/reference/configuration) and a memory thread; otherwise the call uses a plain `stream()`.
 
 ```typescript
 const response = await agent.streamUntilIdle('Research solana for me', {
@@ -307,7 +307,7 @@ response.processDataStream({
 
 ### `resumeStreamUntilIdle()`
 
-Resume a suspended agent stream with custom data and keep the stream open until every [background task](https://mastra.ai/docs/long-running-agents/background-tasks) dispatched during the run completes. Use this to continue execution after a suspension point, such as a workflow suspend within an agent. Requires background tasks to be [enabled on the Mastra instance](https://mastra.ai/reference/configuration) and a memory thread; otherwise the call uses a plain `resumeStream()`:
+Resume a suspended agent stream with custom data and keep the stream open until every [background task](https://mastra.ai/docs/harness/background-tasks) dispatched during the run completes. Use this to continue execution after a suspension point, such as a workflow suspend within an agent. Requires background tasks to be [enabled on the Mastra instance](https://mastra.ai/reference/configuration) and a memory thread; otherwise the call uses a plain `resumeStream()`:
 
 ```typescript
 const response = await agent.resumeStreamUntilIdle(
@@ -497,7 +497,7 @@ if (output.finishReason === 'suspended') {
 
 ## Agent schedules
 
-Use the client SDK schedule methods to manage persisted agent schedules over the `/api/schedules` routes. For concepts and server-side examples, see [Schedules](https://mastra.ai/docs/long-running-agents/schedules) and the [`mastra.schedules` reference](https://mastra.ai/reference/schedules/overview).
+Use the client SDK schedule methods to manage persisted agent schedules over the `/api/schedules` routes. For concepts and server-side examples, see [Schedules](https://mastra.ai/docs/harness/schedules) and the [`mastra.schedules` reference](https://mastra.ai/reference/schedules/overview).
 
 ### `createSchedule()`
 
@@ -839,7 +839,7 @@ console.log(result.success) // true
 
 ## Version management
 
-Both `Agent` (code-defined) and `StoredAgent` instances have methods for managing configuration versions. See [Editor versioning](https://mastra.ai/docs/editor/overview) for lifecycle and selection behavior.
+Both `Agent` (code-defined) and `StoredAgent` instances have methods for managing configuration versions. See [Editor versioning](https://mastra.ai/docs/studio/editor) for lifecycle and selection behavior.
 
 ### Getting an agent with a specific version
 

package/dist/docs/references/reference-editor-versioning.md

@@ -4,7 +4,7 @@
 
 Editor versions stored agents and prompt blocks. Database-backed resources use draft and publish operations. Code-backed agent overrides use deterministic files and Git history.
 
-See [Editor versioning](https://mastra.ai/docs/editor/overview) for release and experimentation patterns.
+See [Editor versioning](https://mastra.ai/docs/studio/editor) for release and experimentation patterns.
 
 ## Database lifecycle
 
@@ -35,7 +35,7 @@ See [`MastraEditor`](https://mastra.ai/reference/editor/mastra-editor) for sourc
 
 ## Select an agent version
 
-Calling [`mastra.getAgentById()`](https://mastra.ai/reference/core/getAgentById) without a selector returns the registered code-defined agent. Pass `status` or `versionId` to apply a stored override. See [Select a version](https://mastra.ai/docs/editor/overview) for a TypeScript example.
+Calling [`mastra.getAgentById()`](https://mastra.ai/reference/core/getAgentById) without a selector returns the registered code-defined agent. Pass `status` or `versionId` to apply a stored override. See [Select a version](https://mastra.ai/docs/studio/editor) for a TypeScript example.
 
 With the default server prefix, pass selectors as query parameters under `/api`:
 
@@ -54,7 +54,7 @@ See the [Client SDK agents reference](https://mastra.ai/reference/client-js/agen
 
 ## Sub-agent versioning
 
-Version overrides propagate through [supervisor-agent delegation](https://mastra.ai/docs/capabilities/subagents) in request context. Define selectors at three levels:
+Version overrides propagate through [supervisor-agent delegation](https://mastra.ai/docs/subagents) in request context. Define selectors at three levels:
 
 1. `Mastra` instance `versions`: Defaults for every invocation
 2. Server request-body `versions`: Per-request values added to request context

package/dist/index.cjs

@@ -884,6 +884,15 @@ var Agent = class extends BaseResource {
 		return this.request(`/agents/${this.agentId}${this.getQueryString(requestContext)}`);
 	}
 	/**
+	* Reads a markdown plan submitted by this agent through the core submit_plan tool.
+	* The server only serves paths under `.mastracode/plans/` and only when the
+	* agent exposes that capability.
+	*/
+	readPlan(path, requestContext) {
+		const contextQuery = this.getQueryString(requestContext, "&");
+		return this.request(`/agents/${this.agentId}/plans/file?path=${encodeURIComponent(path)}${contextQuery}`);
+	}
+	/**
 	* Probe the agent's browser session state before opening a screencast WebSocket.
 	*
 	* Returns `{ hasSession, screencastAvailable }`. Use this to avoid opening a WS
@@ -1404,13 +1413,22 @@ var Agent = class extends BaseResource {
 		let currentTextPart = void 0;
 		let currentReasoningPart = void 0;
 		let currentReasoningTextDetail = void 0;
-		function updateToolInvocationPart(toolCallId, invocation) {
+		function updateToolInvocationPart(toolCallId, invocation, partProviderMetadata) {
 			const part = message.parts.find((part) => part.type === "tool-invocation" && part.toolInvocation.toolCallId === toolCallId);
-			if (part != null) part.toolInvocation = invocation;
-			else message.parts.push({
-				type: "tool-invocation",
-				toolInvocation: invocation
-			});
+			if (part != null) {
+				part.toolInvocation = invocation;
+				if (partProviderMetadata !== void 0) part.providerMetadata = {
+					...part.providerMetadata ?? {},
+					...partProviderMetadata
+				};
+			} else {
+				const newPart = {
+					type: "tool-invocation",
+					toolInvocation: invocation
+				};
+				if (partProviderMetadata !== void 0) newPart.providerMetadata = partProviderMetadata;
+				message.parts.push(newPart);
+			}
 		}
 		const data = [];
 		let messageAnnotations = replaceLastMessage ? lastMessage?.annotations : void 0;
@@ -1548,7 +1566,7 @@ var Agent = class extends BaseResource {
 					if (message.toolInvocations == null) message.toolInvocations = [];
 					message.toolInvocations.push(invocation);
 				}
-				updateToolInvocationPart(value.toolCallId, invocation);
+				updateToolInvocationPart(value.toolCallId, invocation, value.providerMetadata);
 				execUpdate();
 				if (onToolCall) {
 					const result = await onToolCall({ toolCall: value });
@@ -1560,7 +1578,7 @@ var Agent = class extends BaseResource {
 							result
 						};
 						message.toolInvocations[message.toolInvocations.length - 1] = invocation;
-						updateToolInvocationPart(value.toolCallId, invocation);
+						updateToolInvocationPart(value.toolCallId, invocation, value.providerMetadata);
 						execUpdate();
 					}
 				}
@@ -1576,7 +1594,7 @@ var Agent = class extends BaseResource {
 					...value
 				};
 				toolInvocations[toolInvocationIndex] = invocation;
-				updateToolInvocationPart(value.toolCallId, invocation);
+				updateToolInvocationPart(value.toolCallId, invocation, value.providerMetadata);
 				execUpdate();
 			},
 			onDataPart(value) {
@@ -1656,13 +1674,22 @@ var Agent = class extends BaseResource {
 		let currentTextPart = void 0;
 		let currentReasoningPart = void 0;
 		let currentReasoningTextDetail = void 0;
-		function updateToolInvocationPart(toolCallId, invocation) {
+		function updateToolInvocationPart(toolCallId, invocation, partProviderMetadata) {
 			const part = message.parts.find((part) => part.type === "tool-invocation" && part.toolInvocation.toolCallId === toolCallId);
-			if (part != null) part.toolInvocation = invocation;
-			else message.parts.push({
-				type: "tool-invocation",
-				toolInvocation: invocation
-			});
+			if (part != null) {
+				part.toolInvocation = invocation;
+				if (partProviderMetadata !== void 0) part.providerMetadata = {
+					...part.providerMetadata ?? {},
+					...partProviderMetadata
+				};
+			} else {
+				const newPart = {
+					type: "tool-invocation",
+					toolInvocation: invocation
+				};
+				if (partProviderMetadata !== void 0) newPart.providerMetadata = partProviderMetadata;
+				message.parts.push(newPart);
+			}
 		}
 		const data = [];
 		let messageAnnotations = replaceLastMessage ? lastMessage?.annotations : void 0;
@@ -1758,7 +1785,7 @@ var Agent = class extends BaseResource {
 							if (message.toolInvocations == null) message.toolInvocations = [];
 							message.toolInvocations.push(invocation);
 						}
-						updateToolInvocationPart(chunk.payload.toolCallId, invocation);
+						updateToolInvocationPart(chunk.payload.toolCallId, invocation, chunk.payload.providerMetadata);
 						execUpdate();
 						if (onToolCall) {
 							const result = await onToolCall({ toolCall: chunk.payload });
@@ -1770,7 +1797,7 @@ var Agent = class extends BaseResource {
 									result
 								};
 								message.toolInvocations[message.toolInvocations.length - 1] = invocation;
-								updateToolInvocationPart(chunk.payload.toolCallId, invocation);
+								updateToolInvocationPart(chunk.payload.toolCallId, invocation, chunk.payload.providerMetadata);
 								execUpdate();
 							}
 						}
@@ -1827,7 +1854,7 @@ var Agent = class extends BaseResource {
 							...chunk.payload
 						};
 						toolInvocations[toolInvocationIndex] = invocation;
-						updateToolInvocationPart(chunk.payload.toolCallId, invocation);
+						updateToolInvocationPart(chunk.payload.toolCallId, invocation, chunk.payload.providerMetadata);
 						execUpdate();
 						break;
 					}
@@ -5989,8 +6016,9 @@ var AgentControllerSession = class extends BaseResource {
 		});
 	}
 	/** Get the current mode, model, and thread (for initial UI hydration). */
-	state() {
-		return this.request(this.url(this.base()));
+	state(options) {
+		const path = options?.threadId ? `${this.base()}?threadId=${encodeURIComponent(options.threadId)}` : this.base();
+		return this.request(this.url(path));
 	}
 	/** Merge key-value pairs into the session state. Existing keys not in the payload are preserved. */
 	async setState(updates) {