Mastra turns off automatic agent runs by default

Mastra's 1.59.0 release turns automatic agent runs off by default, requiring approval before a rule-proposed run executes. The change affects anyone running Mastra agents in production: workflows that used to fire automatically now wait on a person to approve them.

The mechanism is a new autoRunEnabled setting in Factory. When a rule proposes a run, that run gets parked as a "proposed" decision instead of firing immediately, per the GitHub release. Upgrading to 1.59.0 silently stops any workflow that depended on rules triggering runs on their own. Someone has to flip the flag back on or start approving proposed runs by hand.

Cost control got rebuilt too

The second breaking change replaces CostGuardProcessor with TokenCostControl. The new system adds a warnAtPercent threshold and per-request maxCost functions. It also splits spend limits into separate scopes for users, organizations, and sessions. That's a finer-grained way to catch spend before it runs away. It suggests the old blanket cost guard wasn't enough for teams running agents at scale.

A smaller change is worth flagging too. Trace redaction now uses indexed labels like [APIKEY_1] instead of one blanket [REDACTED] stamp. A trace with multiple secrets no longer hides which one is which.

The GitHub release doesn't say what specifically pushed the auto-run default to off, only that it happened.