Mastra 1.80.0 adds per-user OAuth connections for agent tools

Mastra Core 1.80.0 adds end-user OAuth connections scoped through a resource ID. Applications can request tools for that resource and expose user connection routes, while global connections remain a separate option.

Ask for a connection when needed

A missing integration can produce a structured connection prompt through request_connection. This gives an application a defined state to display instead of treating every missing authorization as an ordinary tool failure.

Observability gains span aggregation, and provider failures retain structured details such as status, request ID and recovery information. Thread subscriptions expose run status, while run abortion is explicit; disconnecting an observer no longer aborts durable or evented work.

Review changed interfaces

Connection sessions use launchUrl in place of connectUrl. Trace-thread query results and pagination also change, and built-in Code SDK subagents are no longer enabled by default.

These are integration and lifecycle changes. They do not supply users’ OAuth consent, provider accounts or inference credits. Existing applications should check the migration details against the interfaces they actually use.

See the mastra hub.