@mastra/mcp-docs-server 1.2.12-alpha.0 → 1.2.12-alpha.4

package/.docs/docs/agents/supervisor-agents.md

@@ -8,7 +8,7 @@ A supervisor agent coordinates multiple subagents using [`Agent.stream()`](https
 
 ## When to use supervisor agents
 
-Use supervisor agents when a task requires multiple agents with different specializations to work together. The supervisor handles delegation decisions, context passing, and result synthesis.
+Use supervisor agents when a task requires multiple agents with different specializations to work together. The supervisor handles delegation decisions and context passing, plus result synthesis.
 
 Common use cases:
 
@@ -43,7 +43,7 @@ const supervisor = new Agent({
   id: 'supervisor',
   instructions: `You coordinate research and writing using specialized agents.
     Delegate to research-agent for facts, then writing-agent for content.`,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   agents: { researchAgent, writingAgent },
   memory: new Memory({
     storage: new LibSQLStore({ id: 'storage', url: 'file:mastra.db' }),
@@ -112,7 +112,7 @@ The `context` object includes:
 
 ### `onDelegationComplete`
 
-Called after a delegation finishes. Use it to inspect results, provide feedback, or stop execution:
+Called after a delegation finishes. Use it to inspect results or provide feedback, or alternatively stop execution:
 
 - `context.bail()`: Stop the supervisor loop immediately
 - Return `{ feedback: '...' }`: Add feedback that gets saved to the supervisor's memory and is visible to subsequent iterations
@@ -147,7 +147,7 @@ The `context` object includes:
 
 ## Message filtering
 
-By default, subagents receive the full conversation context from the supervisor. Use `messageFilter` to control what messages are shared — for example, to remove sensitive data or limit context size.
+By default, subagents receive the full conversation context from the supervisor. Use `messageFilter` to control what messages are shared, for example, to remove sensitive data or limit context size.
 
 ```typescript
 const stream = await supervisor.stream('Research AI trends', {
@@ -173,7 +173,9 @@ The callback receives `messages` (the full conversation history), `primitiveId`
 
 When a subagent completes, the supervisor model receives the subagent's text response in later iterations. Nested tool calls and subagent metadata, such as thread and resource IDs, aren't added to the supervisor model context.
 
-Application code and UI integrations can still inspect the raw delegation result, including `subAgentToolResults`, from the tool result payload. This keeps debugging and display data available without sending nested tool arguments or outputs back into the supervisor's next model call.
+Application code and UI integrations can still inspect `subAgentToolResults` and the rest of the raw delegation result in the tool result payload.
+
+This keeps debugging and display data available without sending nested tool arguments or outputs back into the supervisor's next model call.
 
 Set `includeSubAgentToolResultsInModelContext` to include the full subagent result, including nested tool results and subagent metadata, in the supervisor model context.
 
@@ -187,7 +189,7 @@ await supervisor.generate('Research AI trends', {
 
 ## Iteration monitoring
 
-`onIterationComplete` is called after each iteration of the supervisor loop. Use it to log progress, inject feedback, or stop execution early.
+`onIterationComplete` is called after each iteration of the supervisor loop. Use it to log progress or inject feedback, or alternatively stop execution early.
 
 ```typescript
 const stream = await supervisor.stream('Research AI trends', {
@@ -214,7 +216,7 @@ const stream = await supervisor.stream('Research AI trends', {
 })
 ```
 
-Return `{ continue: true }` to keep iterating, or `{ continue: false }` to stop. Include optional `feedback` to inject guidance into the conversation. When `feedback` is combined with `continue: false`, the model may get one final turn to produce a text response incorporating the feedback, but only if the current iteration is still active (e.g., after tool calls) — otherwise no extra turn is granted.
+Return `{ continue: true }` to keep iterating, or `{ continue: false }` to stop. Include optional `feedback` to inject guidance into the conversation. When `feedback` is combined with `continue: false`, the model may get one final turn to produce a text response incorporating the feedback, but only if the current iteration is still active (e.g., after tool calls), otherwise no extra turn is granted.
 
 ## Memory isolation
 
@@ -226,7 +228,7 @@ How it works:
 2. **Scoped memory saves**: Only the delegation prompt and the subagent's response are saved to the subagent's memory
 3. **Fresh thread per invocation**: Each delegation uses a unique thread ID, ensuring clean separation
 
-This ensures subagents have the context they need without cluttering their memory with the entire supervisor conversation. Visit [memory in multi-agent systems](https://mastra.ai/docs/memory/overview) for more details.
+As a result, subagents have the context they need without cluttering their memory with the entire supervisor conversation. Visit [memory in multi-agent systems](https://mastra.ai/docs/memory/overview) for more details.
 
 ## Tool approval propagation
 
@@ -309,7 +311,7 @@ const stream = await supervisor.stream('Research AI in education', {
 
 The built-in rubric scorer lets you define what "correct" looks like as a checklist and have the agent self-evaluate and iterate until every criterion is satisfied or `maxSteps` is reached.
 
-It works as an **LLM-as-judge** scorer: a separate grader model reviews the agent's output against the rubric after each iteration. If every required criterion passes, the loop ends. If anything falls short, per-criterion feedback is injected back into the conversation and the agent tries again.
+It works as an **LLM-as-judge** scorer. After each iteration, a separate grader model reviews the agent's output against the rubric. The loop ends when every required criterion passes. A failed criterion adds its feedback to the conversation so the agent can try again.
 
 This is most effective for tasks with clear, verifiable success criteria. You can use it like so:
 
@@ -320,7 +322,7 @@ import { createRubricScorer } from '@mastra/evals/scorers/prebuilt'
 const supervisor = new Agent({
   id: 'supervisor',
   instructions: 'You coordinate research and writing using specialized agents.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   agents: { researchAgent, writingAgent },
 })
 
@@ -345,9 +347,13 @@ For full API details, see the [rubric scorer reference](https://mastra.ai/refere
 
 ## Writing effective instructions
 
-Clear instructions are essential for effective delegation. Your supervisor's `instructions` should specify available resources, when to use each one, how to coordinate them, and success criteria.
+Clear instructions are essential for effective delegation.
+
+Your supervisor's `instructions` should specify the available resources and when to use each one. They should also define coordination behavior and success criteria.
+
+Each subagent should have a clear `description` that explains its purpose and return format, including when the supervisor should use it.
 
-Each subagent should have a clear `description` that explains what it does, what format it returns, and when to use it. The supervisor uses these descriptions to make delegation decisions.
+The supervisor uses these descriptions to make delegation decisions.
 
 ```typescript
 const supervisor = new Agent({
@@ -380,7 +386,7 @@ Enable the [backgroundTasks manager](https://mastra.ai/reference/configuration)
 const supervisor = new Agent({
   id: 'supervisor',
   instructions: 'Coordinate research and writing using the available agents.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   agents: { researchAgent, writingAgent },
   backgroundTasks: {
     tools: {

package/.docs/docs/agents/using-tools.md

@@ -60,7 +60,7 @@ export const weatherAgent = new Agent({
   instructions: `
     You are a helpful weather assistant.
     Use the weatherTool to fetch current weather data.`,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   tools: { weatherTool },
 })
 ```
@@ -79,7 +79,7 @@ export const researchAgent = new Agent({
   instructions: `
     You are a helpful research assistant.
     Use web search when you need current information.`,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   tools: {
     webSearch: webSearchTool,
   },
@@ -88,7 +88,7 @@ export const researchAgent = new Agent({
 
 `webSearchTool` supports OpenAI, Anthropic, Google Gemini, and xAI models. If Mastra can't infer one of those providers from the active model, the agent run fails with a `MastraError`.
 
-Only the `webSearchTool` value triggers provider web search. A custom tool named `webSearch` or `web_search` stays unchanged.
+Only the `webSearchTool` value triggers provider web search. Custom tools with the names `webSearch` or `web_search` stay unchanged.
 
 ## Define schemas
 
@@ -170,7 +170,7 @@ export const weatherTool = createTool({
 
 ## Multiple tools
 
-An agent can use multiple tools to handle more complex tasks by delegating specific parts to individual tools. The agent decides which tools to use based on the user's message, the agent's instructions, and the tool descriptions and schemas.
+An agent can use multiple tools to handle more complex tasks by delegating specific parts to individual tools. The agent decides which tools to use based on the user's message and the agent's instructions, plus the tool descriptions and schemas.
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -184,14 +184,14 @@ export const weatherAgent = new Agent({
     You are a helpful weather assistant.
     Use the weatherTool to fetch current weather data.
     Use the hazardsTool to provide information about potential weather hazards.`,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   tools: { weatherTool, hazardsTool },
 })
 ```
 
 ## Agents as tools
 
-Add subagents through the `agents` configuration to create a [supervisor](https://mastra.ai/docs/agents/supervisor-agents). Mastra converts each subagent to a tool named `agent-<key>`. Include a `description` on each subagent so the supervisor knows when to delegate.
+Add subagents through the `agents` configuration to create a [supervisor](https://mastra.ai/docs/agents/supervisor-agents). Mastra converts each subagent to an `agent-<key>` tool. Include a `description` on each subagent so the supervisor knows when to delegate.
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -201,21 +201,21 @@ const writer = new Agent({
   name: 'Writer',
   description: 'Drafts and edits written content',
   instructions: 'You are a skilled writer.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
 })
 
 export const supervisor = new Agent({
   id: 'supervisor',
   name: 'Supervisor',
   instructions: 'Coordinate the writer to produce content.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   agents: { writer },
 })
 ```
 
 ## Workflows as tools
 
-Add workflows through the `workflows` configuration. Mastra converts each workflow to a tool named `workflow-<key>`, using the workflow's `inputSchema` and `outputSchema`. Include a `description` on the workflow so the agent knows when to trigger it.
+Add workflows through the `workflows` configuration. Mastra converts each workflow to a `workflow-<key>` tool that uses the workflow's `inputSchema` and `outputSchema`. Include a `description` on the workflow so the agent knows when to trigger it.
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -225,7 +225,7 @@ export const researchAgent = new Agent({
   id: 'research-agent',
   name: 'Research Agent',
   instructions: 'You are a research assistant.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   workflows: { researchWorkflow },
 })
 ```
@@ -251,7 +251,7 @@ export const weatherAgent = new Agent({
   id: 'weather-agent',
   name: 'Weather Agent',
   instructions: 'Answer questions about current weather.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   tools: { weatherTool },
 })
 ```
@@ -264,7 +264,7 @@ export const travelAgent = new Agent({
   id: 'travel-agent',
   name: 'Travel Agent',
   instructions: 'Help users plan trips.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   tools: { weatherTool },
 })
 ```
@@ -325,7 +325,7 @@ export const supportAgent = new Agent({
   id: 'support-agent',
   name: 'support-agent',
   instructions: 'Help users with their questions.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   hooks: {
     beforeToolCall: ({ toolName, input }) => {
       console.log(`Running ${toolName}`, input)
@@ -337,14 +337,14 @@ export const supportAgent = new Agent({
 })
 ```
 
-`beforeToolCall` runs before the tool executes and receives the tool name, input, and execution context. Return `{ proceed: false, output }` to skip the tool call entirely — the agent receives `output` as the tool result:
+`beforeToolCall` runs before the tool executes and receives the tool name, input, and execution context. Return `{ proceed: false, output }` to skip the tool call entirely, the agent receives `output` as the tool result:
 
 ```typescript
 const guardedAgent = new Agent({
   id: 'guarded-agent',
   name: 'guarded-agent',
   instructions: 'Run shell commands for the user.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   hooks: {
     beforeToolCall: ({ toolName, input }) => {
       const command = (input as { command?: string }).command ?? ''
@@ -423,9 +423,9 @@ export const weatherTool = createTool({
 
 ### Streaming tool input in UIs
 
-When a model generates a tool call, the arguments arrive incrementally as `tool-call-delta` stream chunks before the final `tool-call` chunk. UIs can listen for the corresponding `tool_input_start`, `tool_input_delta`, and `tool_input_end` events to render tool arguments as they stream in — for example, showing a file path or command immediately rather than waiting for the complete tool call.
+When a model generates a tool call, the arguments arrive incrementally as `tool-call-delta` stream chunks before the final `tool-call` chunk. UIs can listen for the corresponding `tool_input_start`, `tool_input_delta`, and `tool_input_end` events to render tool arguments as they stream in, for example, showing a file path or command immediately rather than waiting for the complete tool call.
 
-Using a partial JSON parser on the accumulated `argsTextDelta` fragments lets you extract usable argument values before the JSON is complete. This enables features like live diff previews for edit tools, streaming file content for write tools, and instant display of search patterns or file paths.
+Using a partial JSON parser on the accumulated `argsTextDelta` fragments lets you extract usable argument values before the JSON is complete. It enables features like live diff previews for edit tools, streaming file content for write tools, and instant display of search patterns or file paths.
 
 ## Control tool selection
 
@@ -487,12 +487,12 @@ const orchestrator = new Agent({
 
 Note that for subagents, you'll see two different identifiers in stream responses:
 
-- `toolName: "agent-weather"` in tool call events — the generated tool wrapper name
-- `id: "weather-agent"` in `data-tool-agent` chunks — the subagent's actual `id` property
+- `toolName: "agent-weather"` in tool call events: the generated tool wrapper name
+- `id: "weather-agent"` in `data-tool-agent` chunks: the subagent's actual `id` property
 
 ## Built-in tools
 
-Mastra ships agent-agnostic built-in tools in `@mastra/core/tools` that add interactive and organizational capabilities to any agent.
+Mastra includes agent-agnostic built-in tools in `@mastra/core/tools` that add interactive and organizational capabilities to any agent.
 
 | Tool            | Purpose                                           |
 | --------------- | ------------------------------------------------- |
@@ -505,7 +505,9 @@ Mastra ships agent-agnostic built-in tools in `@mastra/core/tools` that add inte
 
 ### Ask the user a question
 
-Import [`askUserTool`](https://mastra.ai/reference/tools/ask-user-tool) and add it to the agent's toolset. The tool suspends the run, emits a `tool-call-suspended` event with the question, and resumes when you call `resumeStream()` with the user's answer.
+Import [`askUserTool`](https://mastra.ai/reference/tools/ask-user-tool) and add it to the agent's toolset.
+
+The tool suspends the run and emits a `tool-call-suspended` event with the question. It resumes when you call `resumeStream()` with the user's answer.
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -555,7 +557,7 @@ for await (const chunk of stream.fullStream) {
 
 ### Task tracking
 
-The four task tools manage a structured, durable task list for an agent run. They require [Memory](https://mastra.ai/docs/memory/overview) so the list is persisted in a thread-scoped store.
+The task tools manage a structured, durable task list for an agent run. They require [Memory](https://mastra.ai/docs/memory/overview) so the list is persisted in a thread-scoped store.
 
 Add task tracking through [`TaskSignalProvider`](https://mastra.ai/reference/signals/task-signal-provider), which bundles all four tools and the `TaskStateProcessor` in a single registration:
 
@@ -576,7 +578,7 @@ const agent = new Agent({
 
 Only one task can be `in_progress` at a time. The list is stored in the thread-scoped `threadState` storage domain and projected onto the agent's [state-signal](https://mastra.ai/docs/long-running-agents/signals) lane, so it survives observational-memory truncation. See the [Task tools reference](https://mastra.ai/reference/tools/task-tools) for full schemas.
 
-The [AgentController](https://mastra.ai/docs/agent-controller/overview) automatically includes all built-in tools in every mode — you don't need to add them manually. See [Tool approvals](https://mastra.ai/docs/agent-controller/tool-approvals) for AgentController-specific behavior.
+The [AgentController](https://mastra.ai/docs/agent-controller/overview) automatically includes all built-in tools in every mode, you don't need to add them manually. See [Tool approvals](https://mastra.ai/docs/agent-controller/tool-approvals) for AgentController-specific behavior.
 
 ## Related
 

package/.docs/docs/browser/agent-browser.md

@@ -10,7 +10,7 @@ Use AgentBrowser when you need:
 
 - Reliable element targeting through accessibility refs
 - Fine-grained control over browser actions
-- Playwright's robust automation capabilities
+- Playwright's reliable automation capabilities
 - Support for keyboard shortcuts and complex interactions
 
 ## Quickstart
@@ -54,7 +54,7 @@ const browser = new AgentBrowser({
 export const browserAgent = new Agent({
   id: 'browser-agent',
   name: 'Browser Agent',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   browser,
   instructions: `You are a web automation assistant.
 
@@ -65,13 +65,13 @@ When interacting with pages:
 })
 ```
 
-> **Note:** For local launches (the default), AgentBrowser requires a Chromium binary installed via Playwright. This is normally downloaded automatically when you install `@mastra/agent-browser`. If launching the browser fails with `"browser executable is missing"`, run `npx playwright install chromium`. If you connect to a remote browser using the [`cdpUrl`](https://mastra.ai/reference/browser/agent-browser) option, no local Chromium is needed.
+> **Note:** For local launches (the default), AgentBrowser requires a Chromium binary installed via Playwright. This is normally downloaded automatically when you install `@mastra/agent-browser`. If launching the browser fails with `"browser executable is missing"`, run `npx playwright install chromium`. If you connect to a remote browser using the [`cdpUrl`](https://mastra.ai/reference/browser/agent-browser) option, the remote browser provides Chromium.
 
 ## Screenshots
 
 When the agent uses the `browser_screenshot` tool, it captures a PNG image of the current page and returns it as image content that vision-capable models can interpret directly.
 
-Use screenshots when you need to visually inspect the page — for example, evaluating images, layout, or colors. For text or structured data, use `browser_snapshot` instead.
+Use screenshots when you need to visually inspect the page, for example, evaluating images, layout, or colors. For text or structured data, use `browser_snapshot` instead.
 
 To disable the screenshot tool for models that don't support vision, use `excludeTools`:
 

package/.docs/docs/browser/browser-viewer.md

@@ -77,7 +77,7 @@ const workspace = new Workspace({
 
 const browserAgent = new Agent({
   id: 'browser-agent',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   workspace,
   instructions: `You are a web automation assistant.
 Use browser-use commands to navigate and interact with websites.`,
@@ -93,7 +93,7 @@ export const mastra = new Mastra({
 })
 ```
 
-When the agent runs a CLI command like `browser-use open https://example.com`, Mastra automatically launches Chrome, injects the CDP connection, and starts streaming the screencast to Studio.
+When the agent runs a CLI command like `browser-use open https://example.com`, Mastra automatically launches Chrome and injects the CDP connection, plus starts streaming the screencast to Studio.
 
 ## How it works
 

package/.docs/docs/browser/firecrawl.md

@@ -62,7 +62,7 @@ const browser = new FirecrawlBrowser({
 export const firecrawlAgent = new Agent({
   id: 'firecrawl-agent',
   name: 'Firecrawl Agent',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   browser,
   instructions: `You are a web automation assistant.
 

package/.docs/docs/browser/overview.md

@@ -2,7 +2,7 @@
 
 # Browser overview
 
-Browser support enables agents to navigate websites, interact with page elements, fill forms, and extract data. Mastra provides browser capabilities through SDK providers that wrap browser automation libraries and a CLI provider for agents that drive browsers through command-line tools.
+Browser support enables agents to move through websites, interact with page elements, fill forms, and extract data. Mastra provides browser capabilities through SDK providers that wrap browser automation libraries and a CLI provider for agents that drive browsers through command-line tools.
 
 Mastra supports three SDK providers and one CLI provider:
 
@@ -76,7 +76,7 @@ export const webAgent = new Agent({
   id: 'web-agent',
   name: 'Web Agent',
   description: 'A web automation assistant that can navigate websites and complete tasks.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   browser,
   instructions:
     'You are a web automation assistant. Use browser tools to navigate websites and complete tasks.',

package/.docs/docs/browser/recording.md

@@ -87,7 +87,7 @@ import { browser } from '../browsers'
 export const browserAgent = new Agent({
   id: 'browser-agent',
   name: 'Browser Agent',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   browser,
   instructions: `Use browser tools to complete the requested task.
 

package/.docs/docs/browser/stagehand.md

@@ -49,13 +49,13 @@ import { StagehandBrowser } from '@mastra/stagehand'
 
 const browser = new StagehandBrowser({
   headless: false,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
 })
 
 export const stagehandAgent = new Agent({
   id: 'stagehand-agent',
   name: 'Stagehand Agent',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   browser,
   instructions: `You are a web automation assistant.
 
@@ -114,12 +114,12 @@ Returns a list of available actions:
 
 When the agent uses the `stagehand_screenshot` tool, it captures a PNG image of the current page and returns it as image content that vision-capable models can interpret directly.
 
-Use screenshots when you need to visually inspect the page — for example, evaluating images, layout, or colors. For text or structured data, use `stagehand_extract` or `stagehand_observe` instead.
+Use screenshots when you need to visually inspect the page, for example, evaluating images, layout, or colors. For text or structured data, use `stagehand_extract` or `stagehand_observe` instead.
 
 ```typescript
 const browser = new StagehandBrowser({
   headless: false,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
 })
 ```
 
@@ -128,7 +128,7 @@ To disable the screenshot tool for models that don't support vision, use `exclud
 ```typescript
 const browser = new StagehandBrowser({
   headless: false,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   excludeTools: ['stagehand_screenshot'],
 })
 ```
@@ -142,7 +142,7 @@ const browser = new StagehandBrowser({
   env: 'BROWSERBASE',
   apiKey: process.env.BROWSERBASE_API_KEY,
   projectId: process.env.BROWSERBASE_PROJECT_ID,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
 })
 ```
 
@@ -155,7 +155,7 @@ Stagehand can opt into alpha browser recording tools:
 ```typescript
 const browser = new StagehandBrowser({
   headless: false,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   recording: {
     outputDir: './browser-recordings',
   },

package/.docs/docs/capabilities/channels/discord.md

@@ -44,7 +44,7 @@ export const discordAgent = new Agent({
   id: 'discord-agent',
   name: 'Discord Agent',
   instructions: 'Answer questions and help with tasks in Discord.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   channels: {
     adapters: {
       discord: createDiscordAdapter(),

package/.docs/docs/capabilities/channels/other-adapters.md

@@ -41,7 +41,7 @@ Check the adapter's docs for its package name, credential variables, webhook req
 
 ## Use the same Mastra wiring
 
-The Mastra side of each Chat SDK adapter is similar: install the adapter package, add its adapter factory to `channels.adapters`, configure platform credentials, and point the platform webhook to the generated Mastra route.
+The Mastra side of each Chat SDK adapter follows the same setup. Install the adapter package and add its factory to `channels.adapters`. Then configure the platform credentials and point its webhook to the generated Mastra route.
 
 Use one of the platform pages in this section as a reference for the Mastra wiring:
 

package/.docs/docs/capabilities/channels/overview.md

@@ -4,7 +4,7 @@
 
 **Added in:** `@mastra/core@1.22.0`
 
-Channels connect agents to messaging and collaboration platforms like Slack, Microsoft Teams, Discord, Telegram, WhatsApp, GitHub, and Linear. When a user sends a message or comment on a platform, the agent receives it, processes it through the normal agent pipeline, and streams the response back to the conversation. Mastra uses [Chat SDK](https://chat-sdk.dev/) for this channel layer.
+Channels connect agents to messaging and collaboration platforms like Slack, Microsoft Teams, Discord, Telegram, WhatsApp, GitHub, and Linear. When a user sends a message or comment on a platform, the agent receives it and processes it through the normal agent pipeline, plus streams the response back to the conversation. Mastra uses [Chat SDK](https://chat-sdk.dev/) for this channel layer.
 
 Start with the page for your platform:
 
@@ -37,7 +37,7 @@ export const yourAgent = new Agent({
   id: 'your-agent',
   name: 'Your Agent',
   instructions: 'You are a helpful assistant.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   channels: {
     adapters: {
       slack: createSlackAdapter(),
@@ -66,7 +66,7 @@ export const mastra = new Mastra({
 
 ## Webhook routes
 
-Platforms send channel activity to Mastra through webhooks. A webhook is an HTTP endpoint that the platform calls when something happens, such as a new message, a mention, or a user selecting "Approve" on an interactive tool approval card. This is how your agent receives a new message, starts processing it, and responds in the same channel.
+Platforms send channel activity to Mastra through webhooks. A webhook is an HTTP endpoint that the platform calls when something happens, such as a new message, a mention, or a user selecting "Approve" on an interactive tool approval card. This is how your agent receives a new message and starts processing it, plus responds in the same channel.
 
 Mastra registers a webhook route for each configured adapter and handles the request for you:
 
@@ -216,7 +216,7 @@ export const yourAgent = new Agent({
   id: 'your-agent',
   name: 'Your Agent',
   instructions: 'You are a helpful assistant.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   channels: {
     adapters: {
       slack: createSlackAdapter(),
@@ -230,7 +230,11 @@ Vercel and AWS Lambda require `waitUntil`, since they freeze the function as soo
 
 ### Coordinate instances with a shared pub/sub
 
-Channels route messages through the agent's [signal pipeline](https://mastra.ai/docs/long-running-agents/signals), and each run acquires a lease on its thread so one run owns the conversation at a time. The default in-memory pub/sub can't cross instance boundaries, so on serverless a follow-up message can land on a different instance than the one running the agent. Without a shared pub/sub, that instance can't reach the active run and starts its own, leaving the original run untouched and the thread processed twice.
+Channels route messages through the agent's [signal pipeline](https://mastra.ai/docs/long-running-agents/signals), and each run acquires a lease on its thread so one run owns the conversation at a time.
+
+The default in-memory pub/sub can't cross instance boundaries, so on serverless a follow-up message can be routed to a different instance than the one running the agent.
+
+Without a shared pub/sub, that instance can't reach the active run and starts its own, leaving the original run untouched and the thread processed twice.
 
 Configure a shared pub/sub backed by Redis Streams on the `Mastra` instance so leases and signals coordinate across instances:
 

package/.docs/docs/capabilities/channels/slack.md

@@ -158,10 +158,10 @@ settings:
 
 This manifest configures:
 
-- `display_information.name` and `features.bot_user.display_name`: Set your agent's name in Slack. You can update it at any time; remember to reinstall the app after changing names or permissions.
+- `display_information.name` and `features.bot_user.display_name`: Set your agent's name in Slack. You can update it at any time. Remember to reinstall the app after changing names or permissions.
 - `app_home.messages_tab_enabled` and `app_home.messages_tab_read_only_enabled`: Enable direct messages from the Slack app's **Messages** tab.
 - `always_online`: Shows the Slack bot user as always available.
-- `oauth_config.scopes.bot`: Grants the bot permission to post messages, read channel messages where it's present, read mentions, read and write direct messages, and look up users.
+- `oauth_config.scopes.bot`: Grants permission to post and read messages in channels where the bot is present. It also covers mentions and direct messages, together with user lookup.
 - `event_subscriptions`: Tells Slack which message events to send to the webhook.
 - `interactivity`: Enables interactive cards and tells Slack where to send card actions.
 

package/.docs/docs/capabilities/channels/teams.md

@@ -44,7 +44,7 @@ export const teamsAgent = new Agent({
   id: 'teams-agent',
   name: 'Teams Agent',
   instructions: 'Answer questions and help with tasks in Microsoft Teams.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   channels: {
     adapters: {
       teams: createTeamsAdapter({

package/.docs/docs/capabilities/channels/telegram.md

@@ -44,7 +44,7 @@ export const telegramAgent = new Agent({
   id: 'telegram-agent',
   name: 'Telegram Agent',
   instructions: 'Answer questions and help with tasks in Telegram.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   channels: {
     adapters: {
       telegram: createTelegramAdapter(),

package/.docs/docs/capabilities/channels/whatsapp.md

@@ -44,7 +44,7 @@ export const whatsappAgent = new Agent({
   id: 'whatsapp-agent',
   name: 'WhatsApp Agent',
   instructions: 'Answer customer questions and help with tasks in WhatsApp.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   channels: {
     adapters: {
       whatsapp: createWhatsAppAdapter(),

package/.docs/docs/deployment/mastra-server.md

@@ -80,7 +80,7 @@ export const mastra = new Mastra({
 })
 ```
 
-The value of each option can come from a variable, import, or function call. The option itself must remain a direct property. Do not hide build-time options behind a factory call or an object spread:
+The value of each option can come from a variable, import, or function call. The option itself must remain a direct property. Don't hide build-time options behind a factory call or an object spread:
 
 ```typescript
 const options = {

package/.docs/docs/deployment/overview.md

@@ -32,7 +32,7 @@ Read about [monorepo deployment](https://mastra.ai/docs/deployment/monorepo).
 The [Mastra platform](https://mastra.ai/docs/mastra-platform/overview) provides three products for deploying, monitoring, and managing AI applications built with the Mastra framework:
 
 - [**Observability**](https://mastra.ai/docs/mastra-platform/observability): A standalone hosted product for searchable traces, logs, and metrics across Mastra projects and deploys
-- [**Studio**](https://mastra.ai/docs/mastra-platform/studio): A hosted visual environment for testing agents, running workflows, and inspecting traces
+- [**Studio**](https://mastra.ai/docs/mastra-platform/studio): A hosted visual environment for testing agents and running workflows, plus inspecting traces
 - [**Server**](https://mastra.ai/docs/mastra-platform/server): A production deployment target that runs your Mastra application as an API server
 
 Learn more in the [Mastra platform overview](https://mastra.ai/docs/mastra-platform/overview).
@@ -72,4 +72,8 @@ Use these guides when adding Mastra to an existing Next.js or Astro application.
 
 Mastra workflows run using the built-in execution engine by default. For production workloads requiring managed infrastructure, workflows can also be deployed to specialized platforms like [Inngest](https://www.inngest.com) that provide step memoization, automatic retries, and real-time monitoring.
 
-Visit the [Workflow Runners guide](https://mastra.ai/docs/deployment/workflow-runners) for execution options and the [Inngest deployment guide](https://mastra.ai/guides/deployment/inngest) for setup instructions.
+Visit the [Workflow Runners guide](https://mastra.ai/docs/deployment/workflow-runners) for execution options and the [Inngest deployment guide](https://mastra.ai/guides/deployment/inngest) for setup instructions.
+
+## Workers
+
+For production deployments, Mastra can run workflow orchestration, cron scheduling, and background tool execution in dedicated worker processes separate from the API server. This lets you scale each concern independently and isolate failures. See [Workers](https://mastra.ai/docs/deployment/workers) for details.

package/.docs/docs/deployment/sandbox.md

@@ -82,7 +82,9 @@ API:    https://<sandbox-id>-4111.vercel.run/api
 Studio: https://<sandbox-id>-4111.vercel.run
 ```
 
-The manifest includes `expiresAt` when the sandbox provider reports an expiration time. Redeploys to the same sandbox skip the dependency install when the install inputs (`package.json`, bundled lockfiles, and the install command) are unchanged.
+The manifest includes `expiresAt` when the sandbox provider reports an expiration time.
+
+Redeploys to the same sandbox skip the dependency install when its inputs are unchanged. These inputs are `package.json`, the bundled lockfiles, and the install command.
 
 ### Using E2B