@mastra/libsql 0.0.0-structured-output-issue-20260227214155 → 0.0.0-structured-output-errors-20260409185629

package/dist/docs/references/docs-agents-networks.md

@@ -1,32 +1,16 @@
-# Agent Networks
+# Agent networks
 
-> **Supervisor Pattern Recommended:** The [supervisor pattern](https://mastra.ai/docs/agents/supervisor-agents) using `agent.stream()` or `agent.generate()` is now the recommended approach for coordinating multiple agents. It provides the same multi-agent coordination capabilities as `.network()` with significant improvements:
+> **Deprecated — Use supervisor agents:** Agent networks are deprecated and will be removed in a future major release. [Supervisor agents](https://mastra.ai/docs/agents/supervisor-agents) using `agent.stream()` or `agent.generate()` are now the recommended approach. It provides the same multi-agent coordination with better control, a simpler API, and easier debugging.
 >
-> - **Better control**: Iteration hooks, delegation hooks, and task completion scoring give you fine-grained control over execution
-> - **Simpler API**: Uses familiar `stream()` and `generate()` methods instead of a separate `.network()` API
-> - **More flexible**: Stop execution early, modify delegations, filter context, and provide feedback to guide the agent
-> - **Type-safe**: Full TypeScript support for all hooks and callbacks
-> - **Easier debugging**: Monitor progress with `onIterationComplete`, track delegations with `onDelegationStart`/`onDelegationComplete`
->
-> See the [migration guide](https://mastra.ai/guides/migrations/network-to-supervisor) to upgrade from `.network()`.
-
-Agent networks in Mastra coordinate multiple agents, workflows, and tools to handle tasks that aren't clearly defined upfront but can be inferred from the user's message or context. A top-level **routing agent** (a Mastra agent with other agents, workflows, and tools configured) uses an LLM to interpret the request and decide which primitives (subagents, workflows, or tools) to call, in what order, and with what data.
-
-## When to use networks
+> See the [migration guide](https://mastra.ai/guides/migrations/network-to-supervisor) to upgrade.
 
-Use networks for complex tasks that require coordination across multiple primitives. Unlike workflows, which follow a predefined sequence, networks rely on LLM reasoning to interpret the request and decide what to run.
+A **routing agent** uses an LLM to interpret a request and decide which primitives (subagents, workflows, or tools) to call, in what order, and with what data.
 
-## Core principles
+## Create an agent network
 
-Mastra agent networks operate using these principles:
+Configure a routing agent with `agents`, `workflows`, and `tools`. Memory is required as `.network()` uses it to store task history and determine when a task is complete.
 
-- Memory is required when using `.network()` and is used to store task history and determine when a task is complete.
-- Primitives are selected based on their descriptions. Clear, specific descriptions improve routing. For workflows and tools, the input schema helps determine the right inputs at runtime.
-- If multiple primitives have overlapping functionality, the agent favors the more specific one, using a combination of schema and descriptions to decide which to run.
-
-## Creating an agent network
-
-An agent network is built around a top-level routing agent that delegates tasks to subagents, workflows, and tools defined in its configuration. Memory is configured on the routing agent using the `memory` option, and `instructions` define the agent's routing behavior.
+Each primitive needs a clear `description` so the routing agent can decide which to use. For workflows and tools, `inputSchema` and `outputSchema` also help the router determine the right inputs.
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -35,7 +19,6 @@ import { LibSQLStore } from '@mastra/libsql'
 
 import { researchAgent } from './research-agent'
 import { writingAgent } from './writing-agent'
-
 import { cityWorkflow } from '../workflows/city-workflow'
 import { weatherTool } from '../tools/weather-tool'
 
@@ -43,12 +26,8 @@ export const routingAgent = new Agent({
   id: 'routing-agent',
   name: 'Routing Agent',
   instructions: `
-      You are a network of writers and researchers.
-      The user will ask you to research a topic.
-      Always respond with a complete report—no bullet points.
-      Write in full paragraphs, like a blog post.
-      Do not answer with incomplete or uncertain information.`,
-  model: 'openai/gpt-5.1',
+    You are a network of writers and researchers. The user will ask you to research a topic. Always respond with a complete report—no bullet points. Write in full paragraphs, like a blog post. Do not answer with incomplete or uncertain information.`,
+  model: 'openai/gpt-5.4',
   agents: {
     researchAgent,
     writingAgent,
@@ -68,81 +47,11 @@ export const routingAgent = new Agent({
 })
 ```
 
-### Writing descriptions for network primitives
-
-When configuring a Mastra agent network, each primitive (agent, workflow, or tool) needs a clear description to help the routing agent decide which to use. The routing agent uses each primitive's description and schema to determine what it does and how to use it. Clear descriptions and well-defined input and output schemas improve routing accuracy.
-
-#### Agent descriptions
-
-Each subagent in a network should include a clear `description` that explains what the agent does.
-
-```typescript
-export const researchAgent = new Agent({
-  id: 'research-agent',
-  name: 'Research Agent',
-  description: `This agent gathers concise research insights in bullet-point form.
-    It's designed to extract key facts without generating full
-    responses or narrative content.`,
-})
-```
-
-```typescript
-export const writingAgent = new Agent({
-  id: 'writing-agent',
-  name: 'Writing Agent',
-  description: `This agent turns researched material into well-structured
-    written content. It produces full-paragraph reports with no bullet points,
-    suitable for use in articles, summaries, or blog posts.`,
-})
-```
-
-#### Workflow descriptions
-
-Workflows in a network should include a `description` to explain their purpose, along with `inputSchema` and `outputSchema` to describe the expected data.
-
-```typescript
-export const cityWorkflow = createWorkflow({
-  id: 'city-workflow',
-  description: `This workflow handles city-specific research tasks.
-    It first gathers factual information about the city, then synthesizes
-    that research into a full written report. Use it when the user input
-    includes a city to be researched.`,
-  inputSchema: z.object({
-    city: z.string(),
-  }),
-  outputSchema: z.object({
-    text: z.string(),
-  }),
-})
-```
-
-#### Tool descriptions
-
-Tools in a network should include a `description` to explain their purpose, along with `inputSchema` and `outputSchema` to describe the expected data.
-
-```typescript
-export const weatherTool = createTool({
-  id: 'weather-tool',
-  description: ` Retrieves current weather information using the wttr.in API.
-    Accepts a city or location name as input and returns a short weather summary.
-    Use this tool whenever up-to-date weather data is requested.
-  `,
-  inputSchema: z.object({
-    location: z.string(),
-  }),
-  outputSchema: z.object({
-    weather: z.string(),
-  }),
-})
-```
-
-## Calling agent networks
-
-Call a Mastra agent network using `.network()` with a user message. The method returns a stream of events that you can iterate over to track execution progress and retrieve the final result.
+> **Note:** Subagents need a `description` on the `Agent` instance. Workflows and tools need a `description` plus `inputSchema` and `outputSchema` on `createWorkflow()` or `createTool()`.
 
-### Agent example
+## Call the network
 
-In this example, the network interprets the message and would route the request to both the `researchAgent` and `writingAgent` to generate a complete response.
+Call `.network()` with a user message. The method returns a stream of events you can iterate over.
 
 ```typescript
 const result = await routingAgent.network('Tell me three cool ways to use Mastra')
@@ -155,145 +64,119 @@ for await (const chunk of result) {
 }
 ```
 
-#### Agent output
-
-The following `chunk.type` events are emitted during this request:
-
-```text
-routing-agent-start
-routing-agent-end
-agent-execution-start
-agent-execution-event-start
-agent-execution-event-step-start
-agent-execution-event-text-start
-agent-execution-event-text-delta
-agent-execution-event-text-end
-agent-execution-event-step-finish
-agent-execution-event-finish
-agent-execution-end
-network-execution-event-step-finish
-```
-
-## Workflow example
+## Structured output
 
-In this example, the routing agent recognizes the city name in the message and runs the `cityWorkflow`. The workflow defines steps that call the `researchAgent` to gather facts, then the `writingAgent` to generate the final text.
+Pass `structuredOutput` to get typed, validated results. Use `objectStream` for partial objects as they generate.
 
 ```typescript
-const result = await routingAgent.network('Tell me some historical facts about London')
+import { z } from 'zod'
 
-for await (const chunk of result) {
-  console.log(chunk.type)
-  if (chunk.type === 'network-execution-event-step-finish') {
-    console.log(chunk.payload.result)
-  }
-}
-```
+const resultSchema = z.object({
+  summary: z.string().describe('A brief summary of the findings'),
+  recommendations: z.array(z.string()).describe('List of recommendations'),
+  confidence: z.number().min(0).max(1).describe('Confidence score'),
+})
 
-### Workflow output
+const stream = await routingAgent.network('Research AI trends', {
+  structuredOutput: { schema: resultSchema },
+})
 
-The following `chunk.type` events are emitted during this request:
+for await (const partial of stream.objectStream) {
+  console.log('Building result:', partial)
+}
 
-```text
-routing-agent-end
-workflow-execution-start
-workflow-execution-event-workflow-start
-workflow-execution-event-workflow-step-start
-workflow-execution-event-workflow-step-result
-workflow-execution-event-workflow-finish
-workflow-execution-end
-routing-agent-start
-network-execution-event-step-finish
+const final = await stream.object
+console.log(final?.summary)
 ```
 
-### Tool example
+## Approve and decline tool calls
+
+When a primitive requires approval, the stream emits an `agent-execution-approval` or `tool-execution-approval` chunk. Use `approveNetworkToolCall()` or `declineNetworkToolCall()` to respond.
 
-In this example, the routing agent skips the `researchAgent`, `writingAgent`, and `cityWorkflow`, and calls the `weatherTool` directly to complete the task.
+Network approval uses snapshots to capture execution state. Ensure a [storage provider](https://mastra.ai/docs/memory/storage) is enabled in your Mastra instance.
 
 ```typescript
-const result = await routingAgent.network("What's the weather in London?")
+const stream = await routingAgent.network('Perform some sensitive action', {
+  memory: {
+    thread: 'user-123',
+    resource: 'my-app',
+  },
+})
 
-for await (const chunk of result) {
-  console.log(chunk.type)
-  if (chunk.type === 'network-execution-event-step-finish') {
-    console.log(chunk.payload.result)
+for await (const chunk of stream) {
+  if (chunk.type === 'agent-execution-approval' || chunk.type === 'tool-execution-approval') {
+    // Approve
+    const approvedStream = await routingAgent.approveNetworkToolCall(chunk.payload.toolCallId, {
+      runId: stream.runId,
+      memory: { thread: 'user-123', resource: 'my-app' },
+    })
+
+    for await (const c of approvedStream) {
+      if (c.type === 'network-execution-event-step-finish') {
+        console.log(c.payload.result)
+      }
+    }
   }
 }
 ```
 
-#### Tool output
+To decline instead, call `declineNetworkToolCall()` with the same arguments.
 
-The following `chunk.type` events are emitted during this request:
+## Suspend and resume
 
-```text
-routing-agent-start
-routing-agent-end
-tool-execution-start
-tool-execution-end
-network-execution-event-step-finish
-```
-
-## Structured output
-
-When you need typed, validated results from a network, use the `structuredOutput` option. After the network completes its task, it generates a structured response matching your schema.
+When a primitive calls `suspend()`, the stream emits a suspension chunk (e.g., `tool-execution-suspended`). Use `resumeNetwork()` to provide the requested data and continue execution.
 
 ```typescript
-import { z } from 'zod'
-
-const resultSchema = z.object({
-  summary: z.string().describe('A brief summary of the findings'),
-  recommendations: z.array(z.string()).describe('List of recommendations'),
-  confidence: z.number().min(0).max(1).describe('Confidence score'),
-})
-
-const stream = await routingAgent.network('Research AI trends', {
-  structuredOutput: {
-    schema: resultSchema,
-  },
+const stream = await routingAgent.network('Delete the old records', {
+  memory: { thread: 'user-123', resource: 'my-app' },
 })
 
-// Consume the stream
 for await (const chunk of stream) {
-  if (chunk.type === 'network-object') {
-    // Partial object during generation
-    console.log('Partial:', chunk.payload.object)
-  }
-  if (chunk.type === 'network-object-result') {
-    // Final structured object
-    console.log('Final:', chunk.payload.object)
+  if (chunk.type === 'workflow-execution-suspended') {
+    console.log(chunk.payload.suspendPayload)
   }
 }
 
-// Get the typed result
-const result = await stream.object
-console.log(result?.summary)
-console.log(result?.recommendations)
-console.log(result?.confidence)
+// Resume with user confirmation
+const resumedStream = await routingAgent.resumeNetwork(
+  { confirmed: true },
+  {
+    runId: stream.runId,
+    memory: { thread: 'user-123', resource: 'my-app' },
+  },
+)
+
+for await (const chunk of resumedStream) {
+  if (chunk.type === 'network-execution-event-step-finish') {
+    console.log(chunk.payload.result)
+  }
+}
 ```
 
-### Streaming partial objects
+### Automatic resumption
 
-For real-time updates during structured output generation, use `objectStream`:
+Set `autoResumeSuspendedTools` to `true` so the network resumes suspended primitives based on the user's next message. This creates a conversational flow where users provide the required information naturally.
 
 ```typescript
-const stream = await routingAgent.network('Analyze market data', {
-  structuredOutput: { schema: resultSchema },
+const stream = await routingAgent.network('Delete the old records', {
+  autoResumeSuspendedTools: true,
+  memory: { thread: 'user-123', resource: 'my-app' },
 })
+```
 
-// Stream partial objects as they're generated
-for await (const partial of stream.objectStream) {
-  console.log('Building result:', partial)
-}
+Requirements for automatic resumption:
 
-// Get the final typed result
-const final = await stream.object
-```
+- **Memory configured**: The agent needs memory to track suspended tools across messages.
+- **Same thread**: The follow-up message must use the same `thread` and `resource` identifiers.
+- **`resumeSchema` defined**: The tool must define a `resumeSchema` so the network can extract data from the user's message.
+
+|          | Manual (`resumeNetwork`)                       | Automatic (`autoResumeSuspendedTools`)    |
+| -------- | ---------------------------------------------- | ----------------------------------------- |
+| Best for | Custom UIs with approval buttons               | Chat-style interfaces                     |
+| Control  | Full control over resume timing and data       | Network extracts data from user's message |
+| Setup    | Handle suspension chunks, call `resumeNetwork` | Set flag, define `resumeSchema` on tools  |
 
 ## Related
 
-- [Supervisor Agents](https://mastra.ai/docs/agents/supervisor-agents)
-- [Migration: .network() to Supervisor Pattern](https://mastra.ai/guides/migrations/network-to-supervisor)
-- [Guide: Research Coordinator](https://mastra.ai/guides/guide/research-coordinator)
-- [Agent Memory](https://mastra.ai/docs/agents/agent-memory)
-- [Agent Approval](https://mastra.ai/docs/agents/agent-approval)
-- [Workflows Overview](https://mastra.ai/docs/workflows/overview)
-- [Request Context](https://mastra.ai/docs/server/request-context)
+- [Supervisor agents](https://mastra.ai/docs/agents/supervisor-agents)
+- [Migration: `.network()` to supervisor agents](https://mastra.ai/guides/migrations/network-to-supervisor)

package/dist/docs/references/docs-memory-memory-processors.md

@@ -1,4 +1,4 @@
-# Memory Processors
+# Memory processors
 
 Memory processors transform and filter messages as they pass through an agent with memory enabled. They manage context window limits, remove unnecessary content, and optimize the information sent to the language model.
 
@@ -6,11 +6,11 @@ When memory is enabled on an agent, Mastra adds memory processors to the agent's
 
 Memory processors are [processors](https://mastra.ai/docs/agents/processors) that operate specifically on memory-related messages and state.
 
-## Built-in Memory Processors
+## Built-in memory processors
 
 Mastra automatically adds these processors when memory is enabled:
 
-### MessageHistory
+### `MessageHistory`
 
 Retrieves message history and persists new messages.
 
@@ -45,7 +45,7 @@ const agent = new Agent({
   id: 'test-agent',
   name: 'Test Agent',
   instructions: 'You are a helpful assistant',
-  model: 'openai/gpt-4o',
+  model: 'openai/gpt-5.4',
   memory: new Memory({
     storage: new LibSQLStore({
       id: 'memory-store',
@@ -56,7 +56,7 @@ const agent = new Agent({
 })
 ```
 
-### SemanticRecall
+### `SemanticRecall`
 
 Retrieves semantically relevant messages based on the current input and creates embeddings for new messages.
 
@@ -95,7 +95,7 @@ import { openai } from '@ai-sdk/openai'
 const agent = new Agent({
   name: 'semantic-agent',
   instructions: 'You are a helpful assistant with semantic memory',
-  model: 'openai/gpt-4o',
+  model: 'openai/gpt-5.4',
   memory: new Memory({
     storage: new LibSQLStore({
       id: 'memory-store',
@@ -114,7 +114,7 @@ const agent = new Agent({
 })
 ```
 
-### WorkingMemory
+### `WorkingMemory`
 
 Manages working memory state across conversations.
 
@@ -148,7 +148,7 @@ import { openai } from '@ai-sdk/openai'
 const agent = new Agent({
   name: 'working-memory-agent',
   instructions: 'You are an assistant with working memory',
-  model: 'openai/gpt-4o',
+  model: 'openai/gpt-5.4',
   memory: new Memory({
     storage: new LibSQLStore({
       id: 'memory-store',
@@ -159,9 +159,9 @@ const agent = new Agent({
 })
 ```
 
-## Manual Control and Deduplication
+## Manual control and deduplication
 
-If you manually add a memory processor to `inputProcessors` or `outputProcessors`, Mastra will **not** automatically add it. This gives you full control over processor ordering:
+If you manually add a memory processor to `inputProcessors` or `outputProcessors`, Mastra **won't** automatically add it. This gives you full control over processor ordering:
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -180,7 +180,7 @@ const customMessageHistory = new MessageHistory({
 const agent = new Agent({
   name: 'custom-memory-agent',
   instructions: 'You are a helpful assistant',
-  model: 'openai/gpt-4o',
+  model: 'openai/gpt-5.4',
   memory: new Memory({
     storage: new LibSQLStore({ id: 'memory-store', url: 'file:memory.db' }),
     lastMessages: 10, // This would normally add MessageHistory(10)
@@ -192,7 +192,7 @@ const agent = new Agent({
 })
 ```
 
-## Processor Execution Order
+## Processor execution order
 
 Understanding the execution order is important when combining guardrails with memory:
 
@@ -218,7 +218,7 @@ This means memory loads message history before your processors can validate or f
 
 This ordering is designed to be **safe by default**: if your output guardrail calls `abort()`, the memory processors never run and **no messages are saved**.
 
-## Guardrails and Memory
+## Guardrails and memory
 
 The default execution order provides safe guardrail behavior:
 
@@ -250,7 +250,7 @@ const contentBlocker = {
 const agent = new Agent({
   name: 'safe-agent',
   instructions: 'You are a helpful assistant',
-  model: 'openai/gpt-4o',
+  model: 'openai/gpt-5.4',
   memory: new Memory({ lastMessages: 10 }),
   // Your guardrail runs BEFORE memory saves
   outputProcessors: [contentBlocker],
@@ -289,7 +289,7 @@ const inputValidator = {
 const agent = new Agent({
   name: 'validated-agent',
   instructions: 'You are a helpful assistant',
-  model: 'openai/gpt-4o',
+  model: 'openai/gpt-5.4',
   memory: new Memory({ lastMessages: 10 }),
   // Your guardrail runs AFTER memory loads history
   inputProcessors: [inputValidator],

package/dist/docs/references/docs-memory-message-history.md

@@ -1,4 +1,4 @@
-# Message History
+# Message history
 
 Message history is the most basic and important form of memory. It gives the LLM a view of recent messages in the context window, enabling your agent to reference earlier exchanges and respond coherently.
 
@@ -48,7 +48,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Give your agent a `Memory`:
+Instantiate a [`Memory`](https://mastra.ai/reference/memory/memory-class) instance in your agent:
 
 ```typescript
 import { Memory } from '@mastra/memory'
@@ -66,7 +66,7 @@ export const agent = new Agent({
 
 When you call the agent, messages are automatically saved to the database. You can specify a `threadId`, `resourceId`, and optional `metadata`:
 
-**Generate**:
+**.generate()**:
 
 ```typescript
 await agent.generate('Hello', {
@@ -81,7 +81,7 @@ await agent.generate('Hello', {
 })
 ```
 
-**Stream**:
+**.stream()**:
 
 ```typescript
 await agent.stream('Hello', {
@@ -98,17 +98,19 @@ await agent.stream('Hello', {
 
 > **Info:** Threads and messages are created automatically when you call `agent.generate()` or `agent.stream()`, but you can also create them manually with [`createThread()`](https://mastra.ai/reference/memory/createThread) and [`saveMessages()`](https://mastra.ai/reference/memory/memory-class).
 
-There are two ways to use this history:
+You can use this history in two ways:
 
 - **Automatic inclusion** - Mastra automatically fetches and includes recent messages in the context window. By default, it includes the last 10 messages, keeping agents grounded in the conversation. You can adjust this number with `lastMessages`, but in most cases you don't need to think about it.
 - [**Manual querying**](#querying) - For more control, use the `recall()` function to query threads and messages directly. This lets you choose exactly which memories are included in the context window, or fetch messages to render conversation history in your UI.
 
-## Accessing Memory
+> **Tip:** When memory is enabled, [Studio](https://mastra.ai/docs/studio/overview) uses message history to display past conversations in the chat sidebar.
+
+## Accessing memory
 
 To access memory functions for querying, cloning, or deleting threads and messages, call `getMemory()` on an agent:
 
 ```typescript
-const agent = mastra.getAgent('weatherAgent')
+const agent = mastra.getAgentById('test-agent')
 const memory = await agent.getMemory()
 ```
 
@@ -118,7 +120,7 @@ The `Memory` instance gives you access to functions for listing threads, recalli
 
 Use these methods to fetch threads and messages for displaying conversation history in your UI or for custom memory retrieval logic.
 
-> **Warning:** The memory system does not enforce access control. Before running any query, verify in your application logic that the current user is authorized to access the `resourceId` being queried.
+> **Warning:** The memory system doesn't enforce access control. Before running any query, verify in your application logic that the current user is authorized to access the `resourceId` being queried.
 
 ### Threads