@mastra/mcp-docs-server 1.2.26-alpha.3 → 1.2.26-alpha.7

package/.docs/docs/agents/overview.md

@@ -76,7 +76,7 @@ Short list of known model IDs are:
 
 Go to <https://mastra.ai/models> for a full list of supported models.
 
-Add a tool an agent by importing the tool and passing it to the agent constructor as a tools object.
+Add a tool to an agent by importing the tool and passing it to the agent constructor as a tools object.
 
 Example:
 

package/.docs/docs/agents/processors.md

@@ -976,6 +976,27 @@ export class ContextLengthHandler implements Processor {
 
 Mastra includes a built-in [`PrefillErrorHandler`](https://mastra.ai/reference/processors/prefill-error-handler) that automatically handles the Anthropic "assistant message prefill" error. This processor is auto-injected and requires no configuration.
 
+## Receive background work notifications
+
+Use `createBackgroundWorkSignalProcessor()` to retain the active caller's signal capability for eligible background tool calls:
+
+```typescript
+import { Agent } from '@mastra/core/agent'
+import { createBackgroundWorkSignalProcessor } from '@mastra/core/processors'
+
+const agent = new Agent({
+  id: 'background-agent',
+  name: 'Background agent',
+  instructions: 'Complete tasks using the available tools.',
+  model: 'openai/gpt-5.6-sol',
+  inputProcessors: [createBackgroundWorkSignalProcessor()],
+})
+```
+
+Mastra's background runtime remains responsible for execution, persistence, retries, result reconciliation, and continuation. The processor only retains caller-scoped notification access. When background work starts, it emits `work-deferred` or `work-awaited` with `status: 'running'`. After the authoritative tool result is reconciled, it emits `work-completed` or `work-failed`.
+
+Notifications are process-local and best-effort. If the originating run has already ended or the signal can't be delivered (for example, because the task resumed on another process), Mastra preserves the authoritative result without recreating the run or retrying the notification. Foreground calls never emit background work notifications because there is no detached work to report.
+
 ## Related documentation
 
 - [Agent lifecycle](https://mastra.ai/docs/guides/agent-lifecycle): Full-run ordering and `RequestContext` visibility

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

@@ -143,9 +143,15 @@ To add your own endpoints, see [Custom API Routes](https://mastra.ai/docs/server
 
 ## Graceful shutdown and rolling deploys
 
-By default, the generated server handles `SIGINT` and `SIGTERM`. It stops accepting connections, waits up to [`server.drainTimeout`](https://mastra.ai/reference/configuration) for active requests and streams, then runs `mastra.shutdown()`. The drain timeout defaults to 5 seconds. A second signal terminates the process immediately. See [`server.handleShutdownSignals`](https://mastra.ai/reference/configuration) if you need to manage signals yourself.
+By default, the generated server handles `SIGINT` and `SIGTERM`. It stops accepting connections, waits up to [`server.drainTimeout`](https://mastra.ai/reference/configuration) for active requests and streams, then runs `mastra.shutdown()`. Shutdown gives in-flight workflow runs (including durable agent runs) the same drain window to finish before workers and pub/sub subscriptions are torn down. The drain timeout defaults to 5 seconds. A second signal terminates the process immediately. See [`server.handleShutdownSignals`](https://mastra.ai/reference/configuration) if you need to manage signals yourself.
 
-Increase `drainTimeout` when your hosting platform's termination grace period can accommodate longer turns. Keep enough time after the drain for shutdown cleanup.
+Increase `drainTimeout` when your hosting platform's termination grace period can accommodate longer turns. The HTTP drain and the workflow drain run one after the other, so keep enough time for both plus shutdown cleanup.
+
+If you call `mastra.shutdown()` yourself, pass `drainTimeout` to control how long it waits for in-flight workflow runs:
+
+```typescript
+await mastra.shutdown({ drainTimeout: 30_000 })
+```
 
 ```typescript
 import { Mastra } from '@mastra/core/mastra'

package/.docs/docs/guides/context-engineering.md

@@ -178,7 +178,7 @@ await assistant.generate('Help me plan the next project milestone.', {
 
 The example assumes storage is configured on the registered Mastra instance or directly on `Memory`. `lastMessages` controls how many recent messages Mastra loads from the thread. The default is 10.
 
-Message history works well for shorter conversations where recent turns contain the context the agent needs. For long-running conversations, Mastra recommends [Observational Memory](https://mastra.ai/docs/memory/observational-memory), which keeps recent conversation available and turns older history into a dense observation log.
+Message history works well for shorter conversations where recent turns contain the context the agent needs. Because the `lastMessages` window slides forward on every request, each turn past the limit removes the oldest message from the start of the prompt and invalidates the provider prompt cache. For long-running conversations, Mastra recommends [Observational Memory](https://mastra.ai/docs/memory/observational-memory), which keeps recent conversation available and turns older history into a dense observation log while keeping the prompt prefix stable for caching.
 
 ## Observational Memory
 

package/.docs/docs/harness/background-tasks.md

@@ -44,16 +44,16 @@ The full set of options is listed in the [backgroundTasks configuration referenc
 
 ## Run a tool in the background
 
-Enabling the manager doesn't run anything in the background by itself as every tool defaults to foreground execution. Tools opt in at one of two layers:
+Enabling the manager doesn't run anything in the background by itself. Tools become eligible at one of two layers:
 
 1. **Tool-level config**: the tool itself declares it as background-eligible.
 2. **Agent-level config**: the agent declares which of its tools are background-eligible.
 
-Once a tool has opted in, the LLM can optionally include a `_background` field in the tool arguments to override the resolved config for a specific call (timeout, retries, or to flip the call back to foreground).
+Eligible tools default to `deferred` execution. Set `defaultDisposition: 'foreground'` at either layer when eligibility should only give the LLM the option to run a call in the background. The LLM can include a `_background` field in the tool arguments to select `foreground`, `deferred`, or `awaited` execution for a specific call and override its timeout or retries.
 
 ### Tool-level
 
-Set `background.enabled: true` on the tool definition. Tools opted in at this layer run in the background whenever called by an agent that has the manager enabled.
+Set `background.enabled: true` on the tool definition. Tools opted in at this layer are eligible for background execution when called by an agent that has the manager enabled. Their configured default disposition determines whether each call runs inline or in the background unless the call includes a `_background` override.
 
 ```typescript
 import { createTool } from '@mastra/core/tools'
@@ -65,6 +65,7 @@ export const researchTool = createTool({
   inputSchema: z.object({ topic: z.string() }),
   background: {
     enabled: true,
+    defaultDisposition: 'deferred',
     timeoutMs: 600_000,
     maxRetries: 1,
   },
@@ -104,20 +105,23 @@ When a tool is registered on an agent that has background tasks enabled, the mod
 ```json
 {
   "topic": "solana",
-  "_background": { "enabled": true, "timeoutMs": 900_000 }
+  "_background": { "disposition": "awaited", "timeoutMs": 900000 }
 }
 ```
 
-The `_background` override is a _modifier_ on tools the developer has already opted in at the tool or agent layer, it's not a standalone opt-in. If a tool hasn't been opted in, `_background.enabled: true` from the model is ignored and the tool runs in the foreground. This keeps deterministic, foreground-only tools (calculators, lookups, schema validators) from being silently dispatched as tasks.
+The available dispositions are:
 
-### Resolution order
+- `foreground`: Run the tool synchronously without background-work lifecycle signals.
+- `deferred`: Dispatch the tool and let the agent continue. The task remains attached to the run, and streams using `untilIdle` wait for it to reconcile.
+- `awaited`: Dispatch the tool through the background task manager, but hold the current branch until its authoritative result has been reconciled.
+
+For compatibility, `_background.enabled: true` selects `deferred`, and `_background.enabled: false` selects `foreground`. An explicit `disposition` takes precedence over `enabled`.
 
-When a tool call is dispatched, the resolved background config is computed in this priority order:
+The `_background` override only _modifies_ tools the developer has already opted in at the tool or agent layer. If a tool hasn't been opted in, a model-selected background disposition is ignored and the tool runs in the foreground. This keeps deterministic, foreground-only tools (calculators, lookups, schema validators) from being silently dispatched as tasks.
 
-1. Agent-level `backgroundTasks.tools` entry for the tool.
-2. Tool-level `background` config.
-3. LLM `_background.enabled` override (only used to enable background dispatch when the tool was opted in at one of the layers above).
-4. Manager defaults (`defaultTimeoutMs`, `defaultRetries`).
+### Resolution order
+
+When a tool call is dispatched, agent-level and tool-level settings determine eligibility and fallback values. For an eligible tool, the LLM `_background` fields override the corresponding values for that call. Manager defaults fill timeout and retry values that remain unset. An `_background` field can't enable a tool that's not eligible.
 
 If the agent has `backgroundTasks.disabled: true`, every tool call runs synchronously regardless of the layers above.
 
@@ -204,7 +208,7 @@ const stream = await supervisor.stream('Research AI in education and write an ar
 
 ### Inheriting from the subagent
 
-If a subagent isn't listed under the supervisor's `backgroundTasks.tools` but has background-eligible tools of its own (either via tool-level `background.enabled: true` or its own `backgroundTasks.tools` entry) the framework still dispatches the entire subagent invocation as a background task. The supervisor inherits the subagent's intent: the subagent itself becomes the background task, and its inner tools run in the foreground inside the subagent's loop.
+If a subagent isn't listed under the supervisor's `backgroundTasks.tools` but has background-eligible tools of its own (either via tool-level `background.enabled: true` or its own `backgroundTasks.tools` entry) the framework still dispatches the entire subagent invocation as a background task. The supervisor inherits the subagent's intent: the subagent itself becomes the background task, and it can dispatch its eligible ordinary tools in the background inside its loop. Further delegated-agent calls run in the foreground.
 
 The background config used for the inherited dispatch (for example `waitTimeoutMs`) is derived from the subagent's own `backgroundTasks` config.
 
@@ -223,9 +227,11 @@ const researchAgent = new Agent({
 })
 ```
 
-When this `researchAgent` is delegated to from a supervisor that has no backgroundTask configuration for the `researchAgent`, the supervisor still dispatches the whole `researchAgent` invocation as a background task, and `deepResearchTool` runs in the foreground inside that invocation, instead of dispatching its own nested background task.
+When this `researchAgent` is delegated to from a supervisor that has no background task configuration for the `researchAgent`, the supervisor still dispatches the whole `researchAgent` invocation as a background task.
+
+Mastra supports one nested background-tool level inside a delegated run: a root agent can delegate to a subagent, and that subagent can dispatch an eligible ordinary tool in the background. A second delegated-agent edge runs in the foreground and doesn't receive nested background guidance. This limit is execution-scoped and doesn't mutate the shared subagent configuration.
 
-Use this pattern when you want a subagent to behave consistently in the background regardless of which supervisor invokes it. Use the supervisor-side opt-in (above) when you want to tune background behavior centrally per supervisor.
+Which layer to use depends on where consistency matters: subagent-level configuration travels with the agent, so its background behavior stays the same under every supervisor, whereas the supervisor-side opt-in above centralizes that tuning in one place. This boundary stops at a single nested delegation level and has no workflow integration.
 
 ## Suspending and resuming
 
@@ -315,23 +321,23 @@ export const mastra = new Mastra({
 Calling `stream()` with no filter returns a stream of every task event in the system. On connection, the stream emits a snapshot of all currently running tasks, then forwards live events as they happen.
 
 ```typescript
-const bgManager = mastra.backgroundTaskManager
-if (!bgManager) throw new Error('Background tasks are not enabled')
+const bgManager = mastra.backgroundTaskManager;
+if (!bgManager) throw new Error('Background tasks are not enabled');
 
-const controller = new AbortController()
-const stream = bgManager.stream({ abortSignal: controller.signal })
+const controller = new AbortController();
+const stream = bgManager.stream({ abortSignal: controller.signal });
 
 for await (const chunk of stream) {
   switch (chunk.type) {
     case 'background-task-running':
-      console.log('started', chunk.payload.taskId, chunk.payload.toolName)
-      break
+      console.log('started', chunk.payload.taskId, chunk.payload.toolName);
+      break;
     case 'background-task-completed':
-      console.log('done', chunk.payload.taskId, chunk.payload.result)
-      break
+      console.log('done', chunk.payload.taskId, chunk.payload.result);
+      break;
     case 'background-task-failed':
-      console.error('failed', chunk.payload.taskId, chunk.payload.error)
-      break
+      console.error('failed', chunk.payload.taskId, chunk.payload.error);
+      break;
   }
 }
 ```

package/.docs/docs/harness/signals.md

@@ -318,6 +318,45 @@ Use `createNotificationInboxTool()` to give agents one tool for inbox actions in
 
 `sendNotificationSignal()` requires a storage domain with `notifications` support. Use `sendSignal({ type: 'notification' })` only for lower-level notification-shaped context that should bypass inbox storage.
 
+## Cross-agent connections in Mastra Code
+
+Cross-agent communication is experimental and off by default. Enable it in Mastra Code with the `/settings` toggle "Experimental cross-agent communication" and restart. Embedded clients can set `crossAgentSignals: true` when calling `createMastraCode()`. The setting enables thread ownership advertisements and peer discovery. It also makes the agent connection tools available. It doesn't affect the pub/sub transport itself.
+
+```typescript
+import { createMastraCode } from 'mastracode'
+
+const mastraCode = await createMastraCode({
+  crossAgentSignals: true,
+})
+```
+
+Mastra Code can use notification signals to communicate between agent threads. A peer is an exact `{ agentId, resourceId, threadId }` endpoint. Discovery is a point-in-time advertisement that the exact endpoint is available now. It isn't a durable connection or a guarantee that delivery will succeed.
+
+`agent_connections_list` returns one `peers` collection. Each peer includes:
+
+- `relationship`: `none` or `saved`. This is the authoritative durable state for the current sender thread.
+- `presence`: `advertised` or `absent`. This reflects the current discovery pass.
+- `displayStatus`: A derived, presentational value: `discovered`, `connected`, or `saved`.
+- `canAttemptSend`: `true` only when the peer is both saved and currently advertised.
+
+The displayed statuses mean:
+
+| Status         | Meaning                                                     | Can attempt a send? |
+| -------------- | ----------------------------------------------------------- | ------------------- |
+| `[discovered]` | Advertised now, but not saved by the current sender thread. | No                  |
+| `[connected]`  | Saved by the current sender thread and advertised now.      | Yes                 |
+| `[saved]`      | Saved by the current sender thread, but not advertised now. | No                  |
+
+Use the connection tools for distinct operations:
+
+- `agent_connect` saves a freshly discovered exact peer in the current sender thread.
+- `agent_disconnect` removes a saved peer from the current sender thread. The peer doesn't need to be currently advertised, and repeated disconnects are safe.
+- `agent_signal_send` requires the exact peer to remain saved and freshly advertised at send time. A previously discovered or recently seen peer that's absent from the current discovery pass isn't sendable.
+
+Saved connections remain in the sender thread until explicitly disconnected. Every send independently refreshes discovery and verifies the exact endpoint before routing begins. A saved connection therefore records collaboration intent. It doesn't indicate current presence.
+
+After a send attempt reaches Core routing, the routing result is authoritative. The result can be `wake`, `deliver`, `persist`, `blocked`, or `discard`, depending on the target thread and notification policy. A send that isn't acknowledged by the advertised thread owner returns an error and doesn't consume its `messageId`, so the sender can retry it.
+
 ## Distributed and serverless deployments
 
 Signals coordinate runs through a pub/sub backend. When a signal arrives on a backend that implements `LeaseProvider`, Mastra acquires a lease on the target thread so a single process owns the conversation at a time, then either wakes the agent or routes the input into the running loop. Backends without leasing fall back to a no-op that always grants ownership, which is fine in a single process but not across instances.

package/.docs/docs/index.md

@@ -74,7 +74,7 @@ Short list of known model IDs are:
 
 Go to <https://mastra.ai/models> for a full list of supported models.
 
-Add a tool an agent by importing the tool and passing it to the agent constructor as a tools object.
+Add a tool to an agent by importing the tool and passing it to the agent constructor as a tools object.
 
 Example:
 

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

@@ -122,6 +122,8 @@ You can use this history in two ways:
 - **Automatic inclusion**: Mastra automatically includes recent messages in the context window. The default of 10 messages keeps agents grounded in the conversation. Adjust it with `lastMessages` when needed.
 - [**Manual querying**](#querying): For more control, query threads and messages directly with `recall()`. Use the results to choose which memories enter the context window or to render conversation history in your UI.
 
+> **Note:** `lastMessages` counts every stored message, including tool calls, tool results, and [signals](https://mastra.ai/docs/harness/signals) of any kind, so a single turn can add several messages to the count. The window also slides forward on every request: once a thread grows past the limit, the oldest message leaves context on each turn, which changes the start of the prompt and invalidates the provider prompt cache. For long-running conversations, use [Observational Memory](https://mastra.ai/docs/memory/observational-memory), which keeps the prompt prefix stable.
+
 > **Tip:** When memory is enabled, [Studio](https://mastra.ai/docs/studio/overview) uses message history to display past conversations in the chat sidebar.
 
 ## Thread title generation
@@ -343,7 +345,9 @@ const { thread, clonedMessages } = await memory.cloneThread({
 
 You can filter cloned messages by count or date range and specify custom thread IDs. Utility methods are also available to inspect clone relationships.
 
-See [`cloneThread()`](https://mastra.ai/reference/memory/cloneThread) and [clone utilities](https://mastra.ai/reference/memory/clone-utilities) for the full API.
+If you don't need the copied messages returned, for example when forking a long thread, use `copyThread()`. It never returns message payloads, and on LibSQL and PostgreSQL the rows are copied inside the database. When semantic recall is enabled, the copied messages are still read back in batches to generate embeddings.
+
+See [`cloneThread()`](https://mastra.ai/reference/memory/cloneThread), [`copyThread()`](https://mastra.ai/reference/memory/copyThread), and [clone utilities](https://mastra.ai/reference/memory/clone-utilities) for the full API.
 
 ## Deleting messages
 

package/.docs/integrations/agentic-ui/ai-sdk-ui.md

@@ -1362,6 +1362,11 @@ export function NestedAgentChat() {
                 <div key={index} className="nested-agent">
                   <strong>Nested Agent: {id}</strong>
                   {data.text && <p>{data.text}</p>}
+                  {data.toolErrors?.map(toolError => (
+                    <p key={toolError.toolCallId} className="nested-agent-error">
+                      {toolError.toolName} failed: {toolError.errorText}
+                    </p>
+                  ))}
                 </div>
               )
             }
@@ -1388,6 +1393,8 @@ Key points:
 - Piping `fullStream` to `context.writer` creates `data-tool-agent` parts
 - Read `data-tool-agent-step` when you need the full payload for the nested step that finished
 - The `AgentDataPart` has `id` (on the part) and `data.text` (the current nested-agent text snapshot)
+- A tool that throws inside the nested agent is reported in `data.toolErrors`, each entry `{ toolCallId, toolName, args?, errorText, providerExecuted? }`. `errorText` is a JSON-safe string, so the failure survives serialization to the client instead of arriving as `{}`
+- `toolErrors` resets at each nested step boundary, like `toolCalls` and `toolResults`. For a finished step, read it from `data-tool-agent-step` (`data.step.toolErrors`) or from `data.steps[]` on the final snapshot
 - The tool still returns its own output after the stream completes
 
 For a complete implementation, see the [tool-nested-streams example](https://github.com/mastra-ai/ui-dojo/blob/main/src/pages/ai-sdk/tool-nested-streams.tsx) in UI Dojo.

package/.docs/integrations/file-storage/archil.md

@@ -4,7 +4,7 @@
 
 # Archil
 
-Stores files on [Archil](https://docs.archil.com) elastic, serverless disks. Combines an S3-compatible object API for fast reads/writes with `exec()` for POSIX shell operations and `grep()` for parallel server-side search. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files on [Archil](https://docs.archil.com) elastic, serverless disks. Combines an S3-compatible object API for fast reads/writes with `exec()` for POSIX shell operations and `diskGrep()` for parallel server-side search. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Installation
 
@@ -173,12 +173,12 @@ const result = await filesystem.exec('ls -la /data')
 // { exitCode: 0, stdout: '...', stderr: '' }
 ```
 
-#### `grep(options)`
+#### `diskGrep(options)`
 
 Run a parallel server-side search across files on the disk.
 
 ```typescript
-const results = await filesystem.grep({
+const results = await filesystem.diskGrep({
   directory: '/logs',
   pattern: 'ERROR',
   recursive: true,

package/.docs/integrations/frameworks/electron.md

@@ -430,7 +430,7 @@ export default function App(): React.JSX.Element {
 }
 ```
 
-This connects [`useChat()`](https://ai-sdk.dev/docs/reference/ai-sdk-ui/use-chat) to the `/chat/weather-agent` endpoint, sending propmts there and streaming the response back in chunks.
+This connects [`useChat()`](https://ai-sdk.dev/docs/reference/ai-sdk-ui/use-chat) to the `/chat/weather-agent` endpoint, sending prompts there and streaming the response back in chunks.
 
 ## Test your agent
 

package/.docs/integrations/sandboxes/cloudflare-sandbox.md

@@ -82,6 +82,8 @@ const result = await workspace.sandbox?.executeCommand?.('npm', ['test'], {
 
 Relative paths are resolved under `/workspace`. Absolute paths must also resolve within `/workspace`. Each file is sent as its own bridge request, and the bridge caps a single file at 32 MiB.
 
+The Cloudflare sandbox cannot set per-file permissions, so a `writeFiles` call that includes a `mode` is rejected rather than silently ignored.
+
 ```typescript
 await workspace.sandbox?.writeFiles?.([
   { path: 'src/index.ts', content: "console.log('hello')\n" },

package/.docs/integrations/sandboxes/docker.md

@@ -162,6 +162,19 @@ const sandbox = new DockerSandbox({
 })
 ```
 
+## Write files
+
+Upload multiple files in one call with `writeFiles`. Relative paths resolve under the working directory. Set an optional per-file `mode` to control POSIX permissions; it must be an integer between `0o001` and `0o777`. When `mode` is omitted, new files are created with `0644`.
+
+```typescript
+await sandbox.writeFiles([
+  { path: 'src/index.js', content: "console.log('hello')\n" },
+  { path: 'run.sh', content: '#!/bin/sh\n', mode: 0o755 },
+])
+```
+
+Docker is the only built-in sandbox that applies an explicit `mode`. Providers that cannot honor per-file permissions (Vercel, E2B, Daytona, Cloudflare) reject a `writeFiles` call that includes a `mode` instead of silently dropping it.
+
 ## Bind mounts
 
 Mount host directories into the container using the `volumes` option:

package/.docs/models/gateways/merge-gateway.md

@@ -4,7 +4,7 @@
 
 # ![Merge Gateway logo](https://models.dev/logos/merge-gateway.svg)Merge Gateway
 
-Merge Gateway aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 182 models through Mastra's model router.
+Merge Gateway aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 187 models through Mastra's model router.
 
 Learn more in the [Merge Gateway documentation](https://docs.merge.dev/merge-gateway).
 
@@ -67,6 +67,7 @@ ANTHROPIC_API_KEY=ant-...
 | `deepseek/deepseek-v3.1`                         |
 | `deepseek/deepseek-v3.2`                         |
 | `deepseek/deepseek-v4-flash`                     |
+| `deepseek/deepseek-v4-flash-0423`                |
 | `deepseek/deepseek-v4-flash-0731`                |
 | `deepseek/deepseek-v4-flash-0731-fast`           |
 | `deepseek/deepseek-v4-pro`                       |
@@ -94,6 +95,9 @@ ANTHROPIC_API_KEY=ant-...
 | `google/gemini-embedding-001`                    |
 | `google/gemini-flash-latest`                     |
 | `google/gemini-flash-lite-latest`                |
+| `google/gemma-3-12b-it`                          |
+| `google/gemma-3-27b-it`                          |
+| `google/gemma-3-4b-it`                           |
 | `google/gemma-4-26b-a4b-it`                      |
 | `google/gemma-4-31b-it`                          |
 | `meta/llama-3.1-70b-instruct`                    |
@@ -160,6 +164,7 @@ ANTHROPIC_API_KEY=ant-...
 | `openai/gpt-oss-120b`                            |
 | `openai/gpt-oss-20b`                             |
 | `openai/gpt-oss-safeguard-120b`                  |
+| `openai/gpt-oss-safeguard-20b`                   |
 | `openai/o1`                                      |
 | `openai/o3`                                      |
 | `openai/o3-mini`                                 |

package/.docs/models/gateways/netlify.md

@@ -4,7 +4,7 @@
 
 # Netlify
 
-Netlify AI Gateway provides unified access to multiple providers with built-in caching and observability. Access 252 models through Mastra's model router.
+Netlify AI Gateway provides unified access to multiple providers with built-in caching and observability. Access 253 models through Mastra's model router.
 
 Learn more in the [Netlify documentation](https://docs.netlify.com/build/ai-gateway/overview/).
 
@@ -161,6 +161,7 @@ ANTHROPIC_API_KEY=ant-...
 | `openrouter/inclusionai/ling-3.0-flash-fin`                           |
 | `openrouter/inclusionai/ling-3.0-flash-fin:free`                      |
 | `openrouter/inclusionai/ling-3.0-flash-sante:free`                    |
+| `openrouter/inclusionai/ling-3.0-flash-vl`                            |
 | `openrouter/inclusionai/ling-3.0-flash-vl:free`                       |
 | `openrouter/mancer/weaver`                                            |
 | `openrouter/meta-llama/llama-3.1-70b-instruct`                        |

package/.docs/models/gateways/openrouter.md

@@ -4,7 +4,7 @@
 
 # ![OpenRouter logo](https://models.dev/logos/openrouter.svg)OpenRouter
 
-OpenRouter aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 359 models through Mastra's model router.
+OpenRouter aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 365 models through Mastra's model router.
 
 Learn more in the [OpenRouter documentation](https://openrouter.ai/models).
 
@@ -46,8 +46,11 @@ ANTHROPIC_API_KEY=ant-...
 | `~google/gemini-flash-latest`                              |
 | `~google/gemini-pro-latest`                                |
 | `~moonshotai/kimi-latest`                                  |
-| `~openai/gpt-latest`                                       |
+| `~openai/gpt-astra-latest`                                 |
+| `~openai/gpt-luna-latest`                                  |
 | `~openai/gpt-mini-latest`                                  |
+| `~openai/gpt-sol-latest`                                   |
+| `~openai/gpt-terra-latest`                                 |
 | `~x-ai/grok-latest`                                        |
 | `~z-ai/glm-flash-latest`                                   |
 | `~z-ai/glm-latest`                                         |
@@ -147,6 +150,7 @@ ANTHROPIC_API_KEY=ant-...
 | `inclusionai/ling-3.0-flash-fin`                           |
 | `inclusionai/ling-3.0-flash-fin:free`                      |
 | `inclusionai/ling-3.0-flash-sante:free`                    |
+| `inclusionai/ling-3.0-flash-vl`                            |
 | `inclusionai/ling-3.0-flash-vl:free`                       |
 | `kwaipilot/kat-coder-pro-v2`                               |
 | `kwaipilot/kat-coder-pro-v2.5`                             |
@@ -350,7 +354,9 @@ ANTHROPIC_API_KEY=ant-...
 | `rekaai/reka-flash-3`                                      |
 | `relace/relace-apply-3`                                    |
 | `relace/relace-search`                                     |
+| `sakana/fugu-max`                                          |
 | `sakana/fugu-ultra`                                        |
+| `sakana/fugu-ultra-v2`                                     |
 | `sakana/sakana-namazu`                                     |
 | `sao10k/l3-lunaris-8b`                                     |
 | `sao10k/l3.1-euryale-70b`                                  |

package/.docs/models/index.md

@@ -4,7 +4,7 @@
 
 # Model Providers
 
-Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 7171 models from 200 providers through a single API.
+Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 7245 models from 200 providers through a single API.
 
 ## Features
 

package/.docs/models/providers/above.md

@@ -38,7 +38,7 @@ for await (const chunk of stream) {
 
 | Model                                | Context | Tools | Reasoning | Image | Audio | Video | Input $/1M | Output $/1M |
 | ------------------------------------ | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
-| `above/deepseek-v4-flash`            | 1.0M    |       |           |       |       |       | $0.24      | $0.73       |
+| `above/deepseek-v4-flash`            | 1.0M    |       |           |       |       |       | $0.17      | $0.66       |
 | `above/deepseek-v4-flash-vision-exp` | 1.0M    |       |           |       |       |       | $0.24      | $0.73       |
 | `above/deepseek-v4-pro`              | 1.0M    |       |           |       |       |       | $0.73      | $2          |
 | `above/glm-5.2`                      | 1.0M    |       |           |       |       |       | $2         | $5          |

package/.docs/models/providers/baseten.md

@@ -4,7 +4,7 @@
 
 # ![Baseten logo](https://models.dev/logos/baseten.svg)Baseten
 
-Access 22 Baseten models through Mastra's model router. Authentication is handled automatically using the `BASETEN_API_KEY` environment variable.
+Access 23 Baseten models through Mastra's model router. Authentication is handled automatically using the `BASETEN_API_KEY` environment variable.
 
 Learn more in the [Baseten documentation](https://docs.baseten.co).
 
@@ -41,6 +41,7 @@ for await (const chunk of stream) {
 | `baseten/deepseek-ai/DeepSeek-V4-Flash-0731`       | 1.0M    |       |           |       |       |       | $0.13      | $0.26       |
 | `baseten/deepseek-ai/DeepSeek-V4-Pro`              | 1.0M    |       |           |       |       |       | $2         | $3          |
 | `baseten/deepseek-ai/DeepSeek-V4-Pro-0813`         | 1.0M    |       |           |       |       |       | $1         | $4          |
+| `baseten/deepseek-ai/DeepSeek-V4.1-Flash`          | 1.0M    |       |           |       |       |       | $0.30      | $1          |
 | `baseten/moonshotai/Kimi-K2.5`                     | 262K    |       |           |       |       |       | $0.60      | $3          |
 | `baseten/moonshotai/Kimi-K2.6`                     | 262K    |       |           |       |       |       | $0.95      | $4          |
 | `baseten/moonshotai/Kimi-K2.7-Code`                | 262K    |       |           |       |       |       | $0.95      | $4          |

package/.docs/models/providers/bothub.md

@@ -4,7 +4,7 @@
 
 # ![Bothub logo](https://models.dev/logos/bothub.svg)Bothub
 
-Access 7 Bothub models through Mastra's model router. Authentication is handled automatically using the `BOTHUB_API_KEY` environment variable.
+Access 8 Bothub models through Mastra's model router. Authentication is handled automatically using the `BOTHUB_API_KEY` environment variable.
 
 Learn more in the [Bothub documentation](https://bothub.ru/models).
 
@@ -44,6 +44,7 @@ for await (const chunk of stream) {
 | `bothub/glm-5.3`                         | 1.0M    |       |           |       |       |       | $2         | $5          |
 | `bothub/glm-5.3-flash`                   | 1.0M    |       |           |       |       |       | $0.12      | $0.44       |
 | `bothub/gpt-5.6-luna`                    | 1.1M    |       |           |       |       |       | $0.06      | $0.37       |
+| `bothub/muse-spark-1.3-contributor`      | 1.0M    |       |           |       |       |       | $0.10      | $0.20       |
 | `bothub/nemotron-3-ultra-550b-a55b:free` | 1.0M    |       |           |       |       |       | —          | —           |
 
 Model availability, capabilities, context windows, and pricing are sourced from [models.dev](https://models.dev) and may change.

package/.docs/models/providers/cline-pass.md

@@ -4,7 +4,7 @@
 
 # ![ClinePass logo](https://models.dev/logos/cline-pass.svg)ClinePass
 
-Access 14 ClinePass models through Mastra's model router. Authentication is handled automatically using the `CLINE_API_KEY` environment variable.
+Access 15 ClinePass models through Mastra's model router. Authentication is handled automatically using the `CLINE_API_KEY` environment variable.
 
 Learn more in the [ClinePass documentation](https://docs.cline.bot/getting-started/clinepass).
 
@@ -36,22 +36,23 @@ for await (const chunk of stream) {
 
 ## Models
 
-| Model                                     | Context | Tools | Reasoning | Image | Audio | Video | Input $/1M | Output $/1M |
-| ----------------------------------------- | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
-| `cline-pass/cline-pass/deepseek-v4-flash` | 1.0M    |       |           |       |       |       | $0.14      | $0.28       |
-| `cline-pass/cline-pass/deepseek-v4-pro`   | 1.0M    |       |           |       |       |       | $2         | $3          |
-| `cline-pass/cline-pass/glm-5.2`           | 1.0M    |       |           |       |       |       | $1         | $4          |
-| `cline-pass/cline-pass/glm-5.3`           | 1.0M    |       |           |       |       |       | $1         | $4          |
-| `cline-pass/cline-pass/glm-5.3-flash`     | 1.0M    |       |           |       |       |       | $0.15      | $0.50       |
-| `cline-pass/cline-pass/kimi-k2.6`         | 262K    |       |           |       |       |       | $0.95      | $4          |
-| `cline-pass/cline-pass/kimi-k2.7-code`    | 262K    |       |           |       |       |       | $0.95      | $4          |
-| `cline-pass/cline-pass/kimi-k3`           | 1.0M    |       |           |       |       |       | $3         | $15         |
-| `cline-pass/cline-pass/mimo-v2.5`         | 1.0M    |       |           |       |       |       | $0.14      | $0.28       |
-| `cline-pass/cline-pass/mimo-v2.5-pro`     | 1.0M    |       |           |       |       |       | $2         | $3          |
-| `cline-pass/cline-pass/minimax-m3`        | 1.0M    |       |           |       |       |       | $0.30      | $1          |
-| `cline-pass/cline-pass/qwen3.7-max`       | 1.0M    |       |           |       |       |       | $3         | $8          |
-| `cline-pass/cline-pass/qwen3.7-plus`      | 1.0M    |       |           |       |       |       | $0.40      | $2          |
-| `cline-pass/cline-pass/qwen3.8-max`       | 1.0M    |       |           |       |       |       | $2         | $6          |
+| Model                                       | Context | Tools | Reasoning | Image | Audio | Video | Input $/1M | Output $/1M |
+| ------------------------------------------- | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
+| `cline-pass/cline-pass/deepseek-v4-flash`   | 1.0M    |       |           |       |       |       | $0.14      | $0.28       |
+| `cline-pass/cline-pass/deepseek-v4-pro`     | 1.0M    |       |           |       |       |       | $2         | $3          |
+| `cline-pass/cline-pass/deepseek-v4.1-flash` | 1.0M    |       |           |       |       |       | $0.15      | $0.60       |
+| `cline-pass/cline-pass/glm-5.2`             | 1.0M    |       |           |       |       |       | $1         | $4          |
+| `cline-pass/cline-pass/glm-5.3`             | 1.0M    |       |           |       |       |       | $1         | $4          |
+| `cline-pass/cline-pass/glm-5.3-flash`       | 1.0M    |       |           |       |       |       | $0.15      | $0.50       |
+| `cline-pass/cline-pass/kimi-k2.6`           | 262K    |       |           |       |       |       | $0.95      | $4          |
+| `cline-pass/cline-pass/kimi-k2.7-code`      | 262K    |       |           |       |       |       | $0.95      | $4          |
+| `cline-pass/cline-pass/kimi-k3`             | 1.0M    |       |           |       |       |       | $3         | $15         |
+| `cline-pass/cline-pass/mimo-v2.5`           | 1.0M    |       |           |       |       |       | $0.14      | $0.28       |
+| `cline-pass/cline-pass/mimo-v2.5-pro`       | 1.0M    |       |           |       |       |       | $2         | $3          |
+| `cline-pass/cline-pass/minimax-m3`          | 1.0M    |       |           |       |       |       | $0.30      | $1          |
+| `cline-pass/cline-pass/qwen3.7-max`         | 1.0M    |       |           |       |       |       | $3         | $8          |
+| `cline-pass/cline-pass/qwen3.7-plus`        | 1.0M    |       |           |       |       |       | $0.40      | $2          |
+| `cline-pass/cline-pass/qwen3.8-max`         | 1.0M    |       |           |       |       |       | $2         | $6          |
 
 Model availability, capabilities, context windows, and pricing are sourced from [models.dev](https://models.dev) and may change.
 

package/.docs/models/providers/cortecs.md

@@ -52,7 +52,7 @@ for await (const chunk of stream) {
 | `cortecs/codestral-2508`                      | 256K    |       |           |       |       |       | $0.33      | $1          |
 | `cortecs/deepseek-r1-0528`                    | 164K    |       |           |       |       |       | $0.65      | $3          |
 | `cortecs/deepseek-v3.2`                       | 164K    |       |           |       |       |       | $0.30      | $0.49       |
-| `cortecs/deepseek-v4-flash-0731`              | 1.0M    |       |           |       |       |       | $0.13      | $0.28       |
+| `cortecs/deepseek-v4-flash-0731`              | 1.0M    |       |           |       |       |       | $0.09      | $0.17       |
 | `cortecs/deepseek-v4-pro`                     | 1.0M    |       |           |       |       |       | $2         | $3          |
 | `cortecs/deepseek-v4-pro-0813`                | 1.0M    |       |           |       |       |       | $2         | $4          |
 | `cortecs/devstral-2512`                       | 256K    |       |           |       |       |       | $0.48      | $2          |
@@ -73,7 +73,7 @@ for await (const chunk of stream) {
 | `cortecs/glm-5.1`                             | 203K    |       |           |       |       |       | $1         | $4          |
 | `cortecs/glm-5.2`                             | 1.0M    |       |           |       |       |       | $1         | $4          |
 | `cortecs/glm-5.3`                             | 1.0M    |       |           |       |       |       | $1         | $4          |
-| `cortecs/glm-5.3-flash`                       | 1.0M    |       |           |       |       |       | $0.20      | $0.50       |
+| `cortecs/glm-5.3-flash`                       | 1.0M    |       |           |       |       |       | $0.10      | $0.35       |
 | `cortecs/glm-5v-turbo`                        | 203K    |       |           |       |       |       | $1         | $4          |
 | `cortecs/gpt-4.1`                             | 1.0M    |       |           |       |       |       | $2         | $9          |
 | `cortecs/gpt-4.1-mini`                        | 1.0M    |       |           |       |       |       | $0.43      | $2          |
@@ -139,7 +139,7 @@ for await (const chunk of stream) {
 | `cortecs/qwen3.6-27b`                         | 262K    |       |           |       |       |       | $0.45      | $3          |
 | `cortecs/qwen3.6-35b-a3b`                     | 262K    |       |           |       |       |       | $0.17      | $0.56       |
 | `cortecs/qwen3.8-2.4t-a95b`                   | 262K    |       |           |       |       |       | $3         | $6          |
-| `cortecs/qwen3.8-27b`                         | 262K    |       |           |       |       |       | $0.33      | $2          |
+| `cortecs/qwen3.8-27b`                         | 262K    |       |           |       |       |       | $0.10      | $0.40       |
 | `cortecs/qwen3.8-flash-next`                  | 262K    |       |           |       |       |       | $0.20      | $0.50       |
 | `cortecs/qwen3guard-gen-0.6b`                 | 32K     |       |           |       |       |       | —          | —           |
 | `cortecs/qwen3guard-gen-8b`                   | 32K     |       |           |       |       |       | —          | —           |