September 29, 2026
Mastra's September 29, 2026 update introduces breaking changes to tool approval APIs, adds multi-worker background task leasing, dynamic live channel resolvers, trace aggregation, and a new Microsoft Teams integration.
Why this signal matters
Mastra released updates across its ecosystem, notably @mastra/core@1.72.0. Key changes include: 1. Breaking Changes: - session.respondToToolApproval(...) now requires a toolCallId; calls lacking it are rejected. Approval APIs now key gates per thread/run with updated grant scoping. - @mastra/playground-ui removed and renamed several components and props, including ScrollArea and PageHeader props, renaming ToolCall to Activity, and updating color tokens. 2. Background Tasks & Concurrency: - Background task executions now support persisted, expiring ownership leases using ownerId and leaseDurationMs, preventing duplicate runs and overwrites across multi-worker environments. Storage adapters must be updated alongside core to enforce conditional writes. 3. Dynamic Channels & Connect Ecosystem: - Mastra constructor's channels field supports a resolver function (via @mastra/connect) allowing dynamic runtime channel additions without server redeploys, accessed via mastra.resolveChannels(). - Introduced @mastra/teams with 25 tools in @mastra/connect, multi-connection naming support, and bundled Slack/Telegram/Discord dependencies. 4. Engine Durability & Memory: - Observational memory now supports maxRetries and failurePolicy (e.g., continue), preventing agent turn termination on observer/reflector failures. - Improved durability and crash recovery for agents and workflows, preserving timeouts across serialization and restoring EventedAgent on the built-in evented engine. - PubSub.trimTopic() added to prune thread topics in @mastra/redis-streams; subscribeToThread({…
Actionable summary
Mastra core 1.72.0 introduces breaking changes to session.respondToToolApproval (now strictly requiring toolCallId) and UI component APIs. New capabilities include lease-fenced multi-worker background tasks via ownerId/lease expiration, runtime channel resolution via @mastra/connect, observational memory failure policies, trace aggregation storage APIs, and @mastra/teams integration.
- Agent usefulness
- 89/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Update any invocations of session.respondToToolApproval(...) to supply the required toolCallId.
- Upgrade storage adapter packages alongside @mastra/core to ensure conditional write checks and lease fencing are enforced for background tasks.
- Adjust imports and props in projects using @mastra/playground-ui to handle removed/renamed components (e.g., ToolCall to Activity) and color tokens.