0
Fork 0
mirror of https://github.com/mastra-ai/mastra.git synced 2026-11-17 08:44:46 +00:00

Compare commits

...

5 commits

Author SHA1 Message Date
Leo
9332137e3b Merge origin/main to pick up the goal-step test fix (#30571)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 23:00:10 -05:00
Leo
a2f1013b28 docs(core): guard the stepCount changeset example against a missing count
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 14:45:33 -05:00
Leo
192c968689 docs(core): show reading output.stepCount from a thread subscription
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 14:39:05 -05:00
Leo
2c8f6c72fb fix(core, playground): keep the step count on thread broadcast finish chunks
Studio's default signal transport reads a run's finish chunk from the thread
subscription, whose copies drop output.steps. The maxSteps check then never
saw a step count and missed real exhaustion. Broadcast finish copies now keep
output.stepCount (steps that count against maxSteps, retries excluded), and
Studio falls back to it when steps are absent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 12:04:11 -05:00
Leo
b1dd43256b fix(playground): show the maxSteps warning only when a run used every step
Studio warned "Agent stopped because it reached maxSteps" after any run
whose last step called a tool. Core also ends runs that way when a
stopWhen matches or a client tool ends the turn, so agents that end
each turn with a question tool saw the warning every turn.

The check now also requires a known maxSteps and that the run used at
least that many steps, not counting processor retry steps, which is how
core counts the step budget.

Fixes #29612

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 11:37:47 -05:00
11 changed files with 442 additions and 42 deletions