2025-05-08 - Mastra Release

CLI / Playground

• A new '--mcp' option to the mastra project setup command. #4072
• Fix default value handling for number fields in the playground's autoform component. #4119
• Fix tool calls would disappear from the streaming UI during sessions. #4145

Workflows

• The ability to view inner nested workflows within multi-layered nested vNext workflows by updating the serializedStepGraph to return only serializedStepFlow for steps created from a workflow. #4115
• Alpha version of the Inngest runtime, including modifications to the default execution engine to enhance extensibility for the Inngest implementation. #4066
• Error handling by providing a clear, self-explanatory error message when a workflow's execution flow is not defined, and updates related tests. #4141
• Fixes and improvements in using Inngest playground. #4143

Client SDK - JS

• Agent runtimeContext in Client SDK, and adds server-side parsing and related updates. #4117
• AGUI text component fix. #4151
• Copilot Kit. #4127

Server

• A new feature that allows overriding the server body size limit. #4137

Memory

• Fix naming scheme for embedding indexes and adds duplicate index creation checks across various vector stores. #4107
• Message persistence to store all user messages, refactors assistant response extraction to handle both text and structured outputs, and simplifies the getResponseMessages function to accept a direct messages array. #4155

Observability

• Fix setBaggage implementation for tracing to use createBaggage, resolving an issue with Sentry tracing where baggage was not properly defined. #4128
• Fix excessive logging and telemetry updates when retrieving the LLM component for agents by filtering out logger and telemetry settings during this process. #4133

Storage

• Add OpenSearch as a new vector storage backend for Mastra, supporting multiple similarity metrics, metadata filtering, and robust error handling, with full unit and integration test coverage. #2964

Tools

• A tool schema compatibility layer to standardize tool behavior across different model providers by removing incompatible schema properties and appending necessary instructions, ensuring consistent tool usage regardless of the underlying model. #4027