October 14, 2026
Mastra's October 14, 2026 update introduces the FactorySandbox provider contract with Docker, E2B, and Platform implementations, run fencing for distributed storage engines, concurrency hardening for observational memory, bidirectional trace linking via MCP, and several breaking API changes.
Why this signal matters
The October 14, 2026 Mastra release introduces major features and breaking changes across core packages. A primary addition is the FactorySandbox provider contract (@mastra/core/workspace), enabling sandbox settings schemas, repository templates, and prebuilt environment builds, with out-of-the-box implementations in @mastra/docker, @mastra/e2b, and @mastra/platform-workspace. Factory also supports multi-repo environments and scheduled/triggered builds to reduce cold starts. For distributed durability, multiple storage adapters (including Cloudflare DO/D1, DynamoDB, MongoDB, MySQL, Redis, and Spanner) now enforce run fencing to prevent recovered runs from overwriting state after ownership loss. Observational Memory introduces generation protection (supersededBy), reduced blocking intervals, and new commit/append write-result APIs to prevent race conditions across parallel processes. Additionally, AgentController steer and followUp actions now accept file attachments. Telemetry adds trace link support (including W3C traceparent helpers), with bidirectional linking between client tool calls and server requests in @mastra/mcp. Breaking changes include the deprecation of direct internal workflow HTTP invocations in @mastra/server (returning 404), AgentController suspension address claiming changes, and UI prop refactors.
Actionable summary
Mastra release (core@1.77.0) introduces the FactorySandbox contract in @mastra/core/workspace, run fencing in multiple storage adapters to block stale runs post-recovery, observational memory concurrency safeguards (supersededBy, write-result APIs), and W3C traceparent linking in @mastra/mcp. Breaking changes remove internal workflow invocation via @mastra/server HTTP routes, refactor AgentController suspension…
- Agent usefulness
- 94/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Switch internal workflow HTTP invocations to direct agent routes (e.g., POST /agents/:agentId/stream) as server workflow routes now return 404.
- Migrate sandbox integrations to the new FactorySandbox contract if settings, repository templates, or prebuilt template builds are required.
- Update code referencing deprecated SessionRecord fields (modeId, modelId, state, pending), HarnessStorage pending item methods, and SessionSuspensions.resolveToolCallId().
- Refactor @mastra/playground-ui Dialog and AlertDialog implementations to use controlled open and onOpenChange props.