MastraAI
The TypeScript Agent FrameworkFrom the team that brought you Gatsby: prototype and productionize AI features with a modern JavaScript stack.
JoinMastraAI
The TypeScript Agent FrameworkFrom the team that brought you Gatsby: prototype and productionize AI features with a modern JavaScript stack.
JoinInput processor can't add non user role message
Dependecy update inconsistency
Playground throws use of streamVNext.
ERROR [2025-10-08 11:49:24.392 +0530] (Mastra): Error in streamVNext generate: streamVNext has been renamed to stream. Please use stream instead.
ERROR [2025-10-08 11:49:24.392 +0530] (Mastra): Error in streamVNext generate: streamVNext has been renamed to stream. Please use stream instead.
@mastra/ai-sdk chatRoute with middleware context
Message Persistence using CopilotRuntime

Workflow execution strangeness

Lazy load Tools
Error saveMessagetoMemory
await client.saveMessageToMemory()
await client.saveMessageToMemory()
Why in @ag-ui/mastra has no exported member 'registerCopilotKit'?

Can you wait to update docs until you cut a release
Workflow runId in logs
calling default*Options dynamic configuration option is not logical
defaultVNextStreamOptions is called nevertheless agent.generate or agent.stream were called.
```
gitlabAgent.generate
defaultVNextStreamOptions called
...Integration Home Assistant with Mastra?
There is no way to use RuntimeContext as actual DI with playground
const gitlabClient = runtimeContext.get("gitlabClient") as GitLabClient;
const gitlabClient = runtimeContext.get("gitlabClient") as GitLabClient;
createTool only uses inputSchema for validation
runtimeContext type safety
Pass runtime configuration variables to tools through a type-safe runtimeContext.I may be missing something but I can't see how it is type safe. Type definition for
execute option of createTool is defined as RuntimeContext without any generics making it affectively to store everything as unknown....How to achieve LLM structured output in Mastra ai-sdk compatible streaming.
Tools getting called sequentially
workflow.agentic-loop.step.executionWorkflow with each calling a tool (see screenshot). In cases where the same agent runs the tools in parallel, I see a single workflow.agentic-loop.step.executionWorkflow that calls multiple tools (workflow.executionWorkflow.step.toolCallStep).
I was hoping there was a flag I could set to force parallel tool calls within my workflow step. I know maxSteps is an option on an agent, but it defaults to 1 anyways so that probably isn't it.
Any advice here would be amazing!...
Stream order issue in nested agent via tool call
Playground incorrect rendering for workflow execution
.map() step calls are rendered as mapping_undefined. If workflow has several mapping steps they render same execution state at the same time. Let's imagine I have workflow:
```
workflow...