mirror of
https://github.com/mastra-ai/mastra.git
synced 2026-11-17 08:44:46 +00:00
914 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
d60ba71be0 | chore: version - exit prerelease mode | ||
|
|
5c87442ed7 |
chore: version packages (alpha) (#30203)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases > The changelog information of each package has been omitted from this message, as the content exceeds the size limit. ## @mastra/auth-auth0@1.3.0-alpha.0 ## @mastra/auth-clerk@1.4.0-alpha.0 ## @mastra/auth-okta@0.3.0-alpha.0 ## @mastra/auth-supabase@1.2.0-alpha.0 ## @mastra/client-js@1.60.0-alpha.13 ## @mastra/auth@1.2.0-alpha.0 ## @mastra/core@1.83.0-alpha.13 ## @mastra/playground-ui@69.0.0-alpha.15 ## @mastra/rag@2.8.0-alpha.3 ## @mastra/server@1.83.0-alpha.13 ## @mastra/server-adapters-test-suite@0.3.0-alpha.5 ## @mastra/auth-better-auth@1.1.11-alpha.2 ## @mastra/auth-cloud@1.2.9-alpha.0 ## @mastra/auth-neon@0.3.6-alpha.1 ## @mastra/auth-workos@1.6.9-alpha.0 ## @mastra/discord@1.3.4-alpha.0 ## @mastra/react@1.15.0-alpha.13 ## @mastra/deployer-cloud@1.83.0-alpha.13 ## @mastra/deployer-cloudflare@1.2.42-alpha.3 ## @mastra/deployer-netlify@1.2.42-alpha.1 ## @mastra/deployer-sandbox@0.3.27-alpha.1 ## @mastra/deployer-vercel@1.2.42-alpha.1 ## @mastra/longmemeval@1.1.42-alpha.13 ## @mastra/opencode@0.1.42-alpha.13 ## @mastra/factory@0.28.0-alpha.15 ## create-factory@0.4.3-alpha.15 ## @mastra/code-sdk@1.19.0-alpha.15 ## mastracode@0.50.0-alpha.14 ## @mastra/agent-builder@1.2.1-alpha.5 ## mastra@1.39.0-alpha.15 ## @mastra/connect@1.4.0-alpha.6 ## @mastra/deployer@1.83.0-alpha.13 ## @mastra/editor@0.17.1-alpha.7 ## @mastra/mcp@2.9.0-alpha.5 ## @mastra/mcp-docs-server@1.3.13-alpha.17 ## @mastra/memory@1.41.1-alpha.5 ## @mastra/schema-compat@1.4.0-alpha.2 ## @mastra/elysia@0.1.23-alpha.13 ## @mastra/express@1.5.27-alpha.13 ## @mastra/fastify@1.5.27-alpha.13 ## @mastra/hono@1.7.25-alpha.13 ## @mastra/koa@1.7.27-alpha.13 ## @mastra/nestjs@0.3.0-alpha.13 ## @mastra/next@0.2.41-alpha.13 ## @mastra/tanstack-start@0.2.41-alpha.13 ## @mastra/voice-google-gemini-live@0.14.19-alpha.2 ## @mastra/voice-openai-realtime@0.14.9-alpha.3 ## @mastra/voice-xai-realtime@0.2.18-alpha.2 ## @mastra/inngest@1.11.2-alpha.9 ## @mastra/temporal@0.6.0-alpha.13 ## create-mastra@1.39.0-alpha.15 ## @internal/playground@1.39.0-alpha.15 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
6ad8e7eb9d |
feat(ui): one settings layout across Studio, Factory and Platform (#29400)
## Description Settings pages in Studio, Factory and Platform each had their own layout: different widths, section headers with buttons, add rows at the bottom of lists, fields starting at different x positions. This gives all three one layout, built from reusable Playground UI components: - A 640px page column with the title above the sections. - Each section is a dimmed title above one borderless card. The card owns all row spacing (14px padding, inset hairlines), so rows carry no padding of their own. - Settings rows: label and description on the left, control on the right. Text fields share one width, selects hug their value up to that width, switches and buttons keep their size. - Lists: a count and the list's action in a header row at the top of the card, one empty row (text plus the same action) when there's nothing in it, and `SettingsItem` rows with one icon tile size, so every list lines up. - Input, InputGroup and select values use the regular-weight `text-body-sm`, like Textarea. This is the Playground UI, Studio and Factory half. The Platform half, mastra-ai/platform#4174, pins a snapshot of this branch. ## Before / After Every settings page in Studio and Factory, `origin/main` on the left and this branch on the right (1440×1800, dark). Platform's pages are in mastra-ai/platform#4174. | Before | After | | --- | --- | | <br>Studio · Settings | <br>Studio · Settings | | <br>Factory · My account | <br>Factory · My account | | <br>Factory · Preferences | <br>Factory · Preferences | | <br>Factory · Connections | <br>Factory · Connections | | <br>Factory · Models | <br>Factory · Models | | <br>Factory · Memory | <br>Factory · Memory | | <br>Factory · Skills | <br>Factory · Skills | | <br>Factory · Tools | <br>Factory · Tools | | <br>Factory · Behavior | <br>Factory · Behavior | | <br>Factory · Repositories | <br>Factory · Repositories | | <br>Factory · Work Intake | <br>Factory · Work Intake | | <br>Factory · Work board | <br>Factory · Work board | | <br>Factory · Manage Factory | <br>Factory · Manage Factory | One loading state everywhere (`SettingsSkeleton`, New/Settings Loading story), built from the real rows and list items:  ## What changed Playground UI (`@mastra/playground-ui/new/settings`): - `SettingsLayout`: the page column and title (`header` for an app's own header). - `SettingsTitle`: dimmed, inset to the card; `info` keeps a section description as a tooltip. - `SettingsContainer`: the card, owning row spacing. Rows with nothing in them take no space, so a list can always render its notice row. - `SettingsRow` / `SettingsFieldsetRow`: control column with shared field width; selects hug (`fieldTriggerWidthStyle` reads `--field-max-width`). With `controlPlacement="below"` the control fills the row. - New `SettingsListHeader`, `SettingsEmptyRow` (now takes an `action`), `SettingsItem`, `SettingsItemIcon`. `SettingsNoticeRow` stays. - New `SettingsSkeleton`: the one loading state for settings, placeholder rows (`variant="row"`) or list items (`variant="item"`) inside the same card. - Removed `SettingsAddRow` and `SettingsContainer`'s `variant`. `Section`'s deprecated rows keep their old look on their own code. Studio: the settings page uses `SettingsLayout` with its title in the column. URL, API prefix and request headers are one "Mastra connection" card. They only work as a set, so edits stay a draft: an "Unsaved changes · Discard · Save changes" row shows up once something changed, and saving applies all of it at once. This replaces "Save configuration", which sat under the headers and read as saving only them. The first-run connect screen keeps its own form. `@mastra/react`: `useAuthCapabilities` and `usePermissionPatterns` keep their last result while a new client loads (`keepPreviousData`). Before, every connection change gave them a new query key, and the auth and permission guards showed a full-page spinner until it answered, so the page went blank on each save. Factory: every settings page is on the shared components. Section stacks are fragments under `SettingsLayout`, lists with an action use the header or empty row (repositories, custom providers, speech-to-text keys, Connect, intake pickers), and logo and icon rows are `SettingsItem`s. Factory's own `SettingsAddRow`, `SettingsActionRow`, `SettingsSectionHeader` and `SettingsRowsSkeleton` are gone. Every settings loading state is `SettingsSkeleton` (Skills used to show plain "Loading skills…" text). Models keeps its routing diagram; its lane and defaults cards use the borderless settings surface. Work board keeps its form layout. Memory is split into Personal memory and Factory memory, and Build history is its own section. ## Testing 1. `mdev up storybook`: New/Settings, Page, Controls and Loading stories. 2. `mdev up studio`, open Settings: change the URL, prefix or a header and the unsaved row appears; Discard restores; Save applies everything without the page going blank. Change the theme. 3. Factory settings: every section, especially Models. Playground UI, Studio and Factory typecheck clean; the settings, Studio connection, Factory settings and Models tests pass, and CI is green. Not seen locally: a loading state on screen (they resolve too fast), Models with providers connected, and Factory's Memory form (no models in the local org). ## Related issue(s) Fixes PLTFRM-3135 ## Type of change - [ ] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [ ] Test update ## Checklist - [x] I have linked the related issue(s) in the description above - [ ] I have made corresponding changes to the documentation (if applicable) - [x] I have added tests that prove my fix is effective or that my feature works - [ ] I have addressed all Coderabbit comments on this PR <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 This PR makes settings pages in Playground UI, Studio, and Factory use a more consistent layout. It adds shared building blocks so settings and lists are easier to organize and read. ## Summary - Add shared settings components in Playground UI, including a centered 640px layout, consistent containers and rows, list headers, empty and notice rows, and settings items. - Update the Playground settings page and Studio connection form to use the shared layout. Add `CopyInput` for read-only values with a copy action. - Update Factory settings, workspace, and connection views to use the shared components. Separate Personal memory and Factory memory, and give Build history its own section. - Remove older layout helpers, including `SettingsAddRow`, `SettingsSectionHeader`, and the settings container variant. - Add or update component tests and Storybook examples for the new settings patterns. **Checks:** not available. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
05a6931471 |
chore: version packages (alpha) (#30172)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases ## @mastra/client-js@1.60.0-alpha.12 ### Minor Changes - Allow `querySpans()` to sort by `model` or `provider`. ([#30096](https://github.com/mastra-ai/mastra/pull/30096)) ```ts orderBy: [{ field: 'model', direction: 'asc' }]; ``` ### Patch Changes - The generated route types for scores now include the `SCORER` and `PROCESSOR` entity types, matching the entity types experiments can emit. ([#30145](https://github.com/mastra-ai/mastra/pull/30145)) - Add span-local error counts. ([#30088](https://github.com/mastra-ai/mastra/pull/30088)) - Updated dependencies [[`56f654f`]( |
||
|
|
a4258a989c |
chore: version packages (alpha) (#30127)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
055a8c3b82 | chore: version packages | ||
|
|
7c40bc84b6 |
fix(react): load the Studio review queue page by page (#29291)
Co-authored-by: mastra-platform[bot] <mastra-platform[bot]@users.noreply.github.com> Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com> |
||
|
|
9e82af0237 |
chore: version packages (alpha) (#30074)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
3a6ca42696 |
chore: version packages (alpha) (#30026)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
8bce7717eb |
chore: version packages (alpha) (#29986)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
23cc34a9c5 |
chore: version packages (alpha) (#29938)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases > The changelog information of each package has been omitted from this message, as the content exceeds the size limit. ## @mastra/factory@0.28.0-alpha.6 ## @mastra/code-sdk@1.19.0-alpha.6 ## @mastra/playground-ui@69.0.0-alpha.7 ## @mastra/client-js@1.60.0-alpha.6 ## @mastra/react@1.15.0-alpha.6 ## @mastra/deployer-cloud@1.83.0-alpha.6 ## @mastra/longmemeval@1.1.42-alpha.6 ## @mastra/opencode@0.1.42-alpha.6 ## create-factory@0.4.3-alpha.6 ## mastracode@0.50.0-alpha.6 ## @mastra/agent-builder@1.2.1-alpha.3 ## mastra@1.39.0-alpha.6 ## @mastra/core@1.83.0-alpha.6 ## @mastra/deployer@1.83.0-alpha.6 ## @mastra/editor@0.17.1-alpha.4 ## @mastra/mcp@2.9.0-alpha.3 ## @mastra/mcp-docs-server@1.3.13-alpha.9 ## @mastra/memory@1.41.1-alpha.3 ## @mastra/rag@2.7.3-alpha.2 ## @mastra/schema-compat@1.3.18-alpha.0 ## @mastra/server@1.83.0-alpha.6 ## @mastra/elysia@0.1.23-alpha.6 ## @mastra/express@1.5.27-alpha.6 ## @mastra/fastify@1.5.27-alpha.6 ## @mastra/hono@1.7.25-alpha.6 ## @mastra/koa@1.7.27-alpha.6 ## @mastra/nestjs@0.3.0-alpha.6 ## @mastra/next@0.2.41-alpha.6 ## @mastra/server-adapters-test-suite@0.3.0-alpha.3 ## @mastra/tanstack-start@0.2.41-alpha.6 ## @mastra/upstash@1.6.1-alpha.0 ## @mastra/vectorize@1.1.5-alpha.0 ## @mastra/voice-google-gemini-live@0.14.19-alpha.0 ## @mastra/voice-openai-realtime@0.14.9-alpha.0 ## @mastra/voice-xai-realtime@0.2.18-alpha.0 ## @mastra/inngest@1.11.2-alpha.4 ## @mastra/temporal@0.6.0-alpha.6 ## create-mastra@1.39.0-alpha.6 ## @internal/playground@1.39.0-alpha.6 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
779d2875b1 |
chore: version packages (alpha) (#29912)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases > The changelog information of each package has been omitted from this message, as the content exceeds the size limit. ## @mastra/auth-studio@1.4.0-alpha.1 ## @mastra/factory@0.28.0-alpha.5 ## @mastra/mcp-apps-components@0.1.0-alpha.5 ## @mastra/playground-ui@69.0.0-alpha.6 ## @mastra/client-js@1.60.0-alpha.5 ## @mastra/react@1.15.0-alpha.5 ## @mastra/deployer-cloud@1.83.0-alpha.5 ## @mastra/longmemeval@1.1.42-alpha.5 ## @mastra/opencode@0.1.42-alpha.5 ## create-factory@0.4.3-alpha.5 ## @mastra/code-sdk@1.19.0-alpha.5 ## mastracode@0.50.0-alpha.5 ## @mastra/agent-builder@1.2.1-alpha.2 ## mastra@1.39.0-alpha.5 ## @mastra/core@1.83.0-alpha.5 ## @mastra/deployer@1.83.0-alpha.5 ## @mastra/editor@0.17.1-alpha.3 ## @mastra/mcp@2.9.0-alpha.2 ## @mastra/mcp-docs-server@1.3.13-alpha.8 ## @mastra/memory@1.41.1-alpha.2 ## @mastra/rag@2.7.3-alpha.1 ## @mastra/server@1.83.0-alpha.5 ## @mastra/elysia@0.1.23-alpha.5 ## @mastra/express@1.5.27-alpha.5 ## @mastra/fastify@1.5.27-alpha.5 ## @mastra/hono@1.7.25-alpha.5 ## @mastra/koa@1.7.27-alpha.5 ## @mastra/nestjs@0.3.0-alpha.5 ## @mastra/next@0.2.41-alpha.5 ## @mastra/server-adapters-test-suite@0.3.0-alpha.2 ## @mastra/tanstack-start@0.2.41-alpha.5 ## @mastra/libsql@1.30.0-alpha.2 ## @mastra/turso@0.1.21-alpha.2 ## @mastra/inngest@1.11.2-alpha.3 ## @mastra/temporal@0.6.0-alpha.5 ## create-mastra@1.39.0-alpha.5 ## @internal/playground@1.39.0-alpha.5 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
7c4dd88400 |
chore: version packages (alpha) (#29889)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
6deb16047f |
chore: version packages (alpha) (#29719)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases > The changelog information of each package has been omitted from this message, as the content exceeds the size limit. ## @mastra/slack@1.9.0-alpha.0 ## @mastra/factory@0.28.0-alpha.3 ## @mastra/code-sdk@1.19.0-alpha.3 ## mastracode@0.50.0-alpha.3 ## @mastra/observability@1.24.0-alpha.2 ## @mastra/core@1.83.0-alpha.3 ## @mastra/mcp-apps-components@0.1.0-alpha.3 ## @mastra/playground-ui@69.0.0-alpha.4 ## @mastra/server@1.83.0-alpha.3 ## @mastra/server-adapters-test-suite@0.3.0-alpha.1 ## @mastra/platform-workspace@1.13.0-alpha.0 ## @mastra/auth-better-auth@1.1.11-alpha.1 ## @mastra/client-js@1.60.0-alpha.3 ## @mastra/react@1.15.0-alpha.3 ## @mastra/deployer-cloud@1.83.0-alpha.3 ## @mastra/longmemeval@1.1.42-alpha.3 ## @mastra/opencode@0.1.42-alpha.3 ## create-factory@0.4.3-alpha.3 ## @mastra/arize@1.3.30-alpha.2 ## @mastra/arthur@0.4.30-alpha.2 ## @mastra/braintrust@1.3.27-alpha.2 ## @mastra/datadog@1.4.22-alpha.2 ## @mastra/deepeval@0.1.24-alpha.2 ## @mastra/laminar@1.3.32-alpha.2 ## @mastra/langfuse@1.6.6-alpha.2 ## @mastra/langsmith@1.4.3-alpha.2 ## @mastra/otel-bridge@1.5.22-alpha.2 ## @mastra/otel-exporter@1.5.2-alpha.2 ## @mastra/posthog@1.4.7-alpha.2 ## @mastra/sentry@1.2.32-alpha.2 ## @mastra/agent-builder@1.2.1-alpha.1 ## mastra@1.39.0-alpha.3 ## @mastra/connect@1.3.2-alpha.2 ## @mastra/deployer@1.83.0-alpha.3 ## @mastra/editor@0.17.1-alpha.2 ## @mastra/fastembed@1.3.7-alpha.0 ## @mastra/mcp-docs-server@1.3.13-alpha.6 ## @mastra/memory@1.41.1-alpha.1 ## @mastra/elysia@0.1.23-alpha.3 ## @mastra/express@1.5.27-alpha.3 ## @mastra/fastify@1.5.27-alpha.3 ## @mastra/hono@1.7.25-alpha.3 ## @mastra/koa@1.7.27-alpha.3 ## @mastra/nestjs@0.3.0-alpha.3 ## @mastra/next@0.2.41-alpha.3 ## @mastra/tanstack-start@0.2.41-alpha.3 ## @mastra/convex@1.8.1-alpha.0 ## @mastra/pg@1.36.0-alpha.2 ## @mastra/inngest@1.11.2-alpha.2 ## @mastra/temporal@0.6.0-alpha.3 ## create-mastra@1.39.0-alpha.3 ## @internal/playground@1.39.0-alpha.3 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
7601d91220 |
fix(react): stop useChat sendMessage from rejecting when the user presses Stop (#29764)
## Summary In `@mastra/react`, pressing Stop (`cancelRun`) while a reply is streaming made `useChat`'s `sendMessage` reject with `AbortError: signal is aborted without reason`. Apps that call `void chat.sendMessage(...)` (the usual pattern) logged an unhandled rejection every time a user stopped a reply. This PR changes that: - `sendMessage` now **resolves** when the reply was ended by Stop or by a newer send replacing it. This applies to both the legacy `/stream` route (the default) and the thread-signal route. - Starting a new send while an older reply is still streaming no longer sets `isRunning` to `false` for the newer reply. Only the run that still owns the stream controller clears it. - If you abort **your own** `signal` passed to `sendMessage`, the send still rejects, same as `fetch`. This changes behavior for every `useChat` consumer, which is why it is split out of #29438 for its own review. ## Test plan - [x] New MSW tests in `client-sdks/react/src/agent/__tests__/cancel-run.msw.test.tsx`, under "when Stop cuts off a reply that is still streaming": - Stop resolves the send instead of rejecting it - a newer send keeps `isRunning` true when it replaces a streaming one (the second response's headers are held, so its `start` chunk cannot hide the bug) - aborting the caller's own signal still rejects - [x] Before the fix, 4 of these tests fail with 2 unhandled errors. Mutating each guard (`stoppedHere`, the caller-signal check, the `settleStopped` ownership check, the `settleStopped` call) fails at least one test. - [x] Full `@mastra/react` suite passes (1020 tests) on the branch this came from. The agent hook code is identical to `main` apart from this change. - [x] In the `examples/gen-ui` app (Playwright): stopped a streaming reply, saw no unhandled rejection, and the next message got its reply. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 When someone presses Stop, `sendMessage` now finishes normally instead of reporting an error. If a new message replaces a reply, the chat stays marked as running. Aborting with the caller’s own signal still reports an `AbortError`. ## Changes - Updated `useChat` to treat intentional stream cancellation as a normal end in both the legacy route and thread-signal route. - Prevented an older send from clearing `isRunning` when a newer send owns the stream. - Removed an unconfirmed pending message when Stop interrupts a thread-signal send. - Added tests for Stop, replacement sends, and caller-signal aborts, including thread-signal fallback routes. - Added a patch changeset for `@mastra/react`. ## Checks - Test and CI results: not available. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |
||
|
|
009f632534 | chore: version packages | ||
|
|
f21e0742ce | chore: version packages | ||
|
|
8d07b0b293 |
feat(factory): live Mistral dictation, Slack voice clip failure card, and voice fixes (#29573)
## Description **─────── TLDR ───────** > With Mistral, the Factory composer now writes your words while you speak, and a Slack voice clip that can't be transcribed tells its sender why instead of reaching the agent. This is the one follow-up to the voice stack (#29363, #29366, #29372): live dictation, the fixes the reviews turned up, and three dedups. It also brings `main`'s factory unit tests back: #29317 landed first with a test importing `factoryMemorySettingsUserId`, which #29366 renamed to `factoryProjectSettingsUserId`. ### Behavior changed composer mic, Mistral chosen ├─ **was** — records, and the text lands after you stop ├─ **now** — words appear in the draft as you speak ├─ **if Mistral won't mint a token for a key that still works** — records a clip with the same key, like before └─ **if the key is rejected or out of credit** — says so before the mic opens composer mic, any other provider └─ **unchanged** — records a clip and transcribes it on stop a Slack voice clip that can't be transcribed ├─ **was** — stays attached; the agent reads a note and may relay it └─ **now** — dropped; a card only the sender sees says why a Slack message that was only failed clips ├─ **was** — the agent runs, and a new thread starts a session └─ **now** — no run, just the card a member dictating more than 20 times in a minute └─ **new** — 429 `voice_rate_limited` with `Retry-After`, before the mic opens For a missing, rejected or out-of-credit key the card has an **Open voice settings** button to `/factories/<id>/settings/models#voice-input`; for a busy or slow provider it says to send the clip again shortly. A recorded dictation counts once against the limit: the live-session check for a batch provider doesn't charge. ### Fixes > speech-to-text calls stop after 1 minute and retry once, instead of up to 10 minutes and 2 retries > a stored OpenAI key no longer sends the server's `OPENAI_ORG_ID` / `OPENAI_PROJECT_ID` > picking Deepgram works: `@mastra/voice-deepgram` stopped sending `diarize=undefined` > `recordMicrophoneToFile` labels Safari clips `.m4a` and releases the mic when recording can't start > web transcription errors show the same fixed reason as Slack, never the provider's text ### Shape changed | | | | |---|---|---| | **+** | `POST /web/voice/live-session` | mints the Mistral token; answers `batch` for other providers | | **+** | `STTModel.realtimeModel` | only Mistral has one, so the registry decides live mode | | **−** | Factory's own recorder | `@mastra/react`'s `recordMicrophoneToFile`, fixed, replaces it | | **~** | thread → Factory lookup | 3 copies become `threadRunBinding` in `session-threads.ts` | | **~** | `loose()` | 26 copies become one in `routes/route.ts` | | **~** | drawer placement | 4 copies become `useSidePanelDrawer()` | new surface the browser and other packages now rely on `{ mode: 'batch' } | { mode: 'live', url, token, expiresAt }` · `transcriptionFailureReason(error)` · `voiceRateLimiter()` · `voiceClipFailureCard(report, retryHint)` ### Decisions - **the browser streams to Mistral directly** — a token keeps audio off Factory and the key on it; it lasts ~15 minutes, one model only - **the limit lives in memory per process** — nothing shared exists yet; each replica allows 20 a minute - **a stored OpenAI key drops the env org/project** — those vars belong to the `OPENAI_API_KEY` account; one comparison to undo ### Watch > [!WARNING] > Live dictation opens `wss://api.mistral.ai` and loads its capture worklet from a `blob:` URL. Nothing in `mastracode/` sets a Content-Security-Policy today, but <mark>a CSP added later has to allow both</mark> or the mic stops connecting. ### Not verified - [ ] the composer in a real browser — capture and live text run in MSW tests with a fake `AudioContext`; real Mistral ran from a script driving the same `liveDictation.ts`, 19 deltas and the exact sentence back - [ ] the card in a real Slack thread — rendered and unit-tested only - [ ] a real out-of-credit response — the wording comes from `classifyProviderError` on a simulated 429 `insufficient_quota` --- > ██████████████████ **tests** `+1095 −212` — 54% of the additions > ███████████████ **source** `+912 −376` > █ **changeset** `+24` > █ **docs** `+2 −2` ## Related issue(s) No issue. Follow-up to #29363, #29366 and #29372. ## Type of change - [x] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update - [x] Code refactoring - [ ] Performance improvement - [ ] Test update ## Checklist - [ ] I have linked the related issue(s) in the description above - [x] I have made corresponding changes to the documentation (if applicable) - [x] I have added tests that prove my fix is effective or that my feature works - [ ] I have addressed all Coderabbit comments on this PR <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 Factory can show words as someone speaks when they use a supported Mistral model. If transcription fails, Slack now tells the sender what happened and removes the failed clip so it does not reach the agent. ## What changed - Added live Mistral dictation to the Factory composer. Other providers use batch transcription. If live setup falls back, Mistral also uses batch transcription. - Added `POST /web/voice/live-session`. The server checks Mistral credentials before recording and applies a per-process limit of 20 voice requests per member per minute. Requests over the limit return `429` with `Retry-After`. - Changed Slack voice-clip failures to remove failed clips and send the sender a private failure card. Messages with no remaining content do not start an agent run. - Reduced speech-to-text timeouts to one minute and configured one retry. OpenAI organization and project IDs are omitted when the request uses a stored key. - Fixed Deepgram requests that included unset options. Improved recording MIME types, file extensions, and microphone cleanup. - Standardized web transcription error messages. Consolidated route context casting and thread-to-Factory lookup, and added a shared drawer configuration helper. ## Validation - Added or updated tests for live dictation, voice routes, Slack failure cards, rate limiting, transcription retries, Deepgram options, and microphone recording. - The author reports testing browser capture and live text with MSW and a fake `AudioContext`, and testing `liveDictation.ts` against Mistral. The live composer was not verified in a real browser. - A real Slack thread card and a real out-of-credit response were not verified. - Current-head build, test, and CI results: not available. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
25726091b3 |
feat(playground-ui): configure Platform feedback creation (#29528)
## Description
Platform uses the shared feedback composer but needs explicit context
mode and author fields, and cannot yet support its delete/review
actions. Add optional `feedbackOptions` across trace, span, and thread
composers: `{ contextMode: 'resolve', feedbackUserId: null, allowDelete:
false, allowReview: false }`. Omitted options preserve existing
behavior.
Failed submissions display an error and preserve the draft. Switching
traces resets composer state. The client continues generating stable
IDs/timestamps, and the hook returns the server response, including its
identity and timestamp, for later replacement writes. Includes separate
React/UI changesets. Inline feedback options use primitive dependencies
in the existing explorer config memo, and standalone composers re-export
`FeedbackOptions`.
Validated with 147 shared UI tests, 6 React hook tests, package builds,
typecheck, and scoped lint/format checks. Regression tests were also
checked against the original behavior. Platform will consume a new alpha
or snapshot after this merges; this PR does not publish one.
## Related issue(s)
Part of [OBS-827](https://linear.app/kepler-crm/issue/OBS-827), under
[OBS-792](https://linear.app/kepler-crm/issue/OBS-792). Platform
integration remains a separate draft PR.
## Type of change
- [x] New feature (non-breaking change that adds functionality)
- [x] Bug fix (non-breaking change that fixes an issue)
- [x] Test update
## Checklist
- [x] I have linked the related issue(s) in the description above
- [x] I have made corresponding changes to the documentation (if
applicable; usage examples are in the changesets)
- [x] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have addressed all Coderabbit comments on this PR
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
This PR lets the host application control who feedback is attributed to,
how its context is resolved, and whether users can delete or review
feedback. It also shows an error when saving fails, so users know their
feedback was not saved.
## Changes
- Added optional `feedbackOptions` to trace, span, thread, and explorer
feedback components. When omitted, existing action behavior remains
enabled.
- Added `contextMode` and `feedbackUserId` options to
`useCreateFeedback`.
- Added submission-error messages to trace and span feedback composers.
- Added tests for request options, disabled actions, failed submissions,
and composer state when switching traces.
- Added changesets for `@mastra/react` and `@mastra/playground-ui`.
Test and build results: not available.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
|
||
|
|
675caf0613 |
chore: version packages (alpha) (#29336)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases > The changelog information of each package has been omitted from this message, as the content exceeds the size limit. ## @mastra/client-js@1.60.0-alpha.0 ## @mastra/react@1.15.0-alpha.0 ## @mastra/factory@0.28.0-alpha.0 ## @mastra/code-sdk@1.19.0-alpha.0 ## mastra@1.39.0-alpha.0 ## @mastra/core@1.83.0-alpha.0 ## @mastra/mcp@2.9.0-alpha.0 ## @mastra/mcp-apps-components@0.1.0-alpha.0 ## @mastra/playground-ui@69.0.0-alpha.0 ## @mastra/server@1.83.0-alpha.0 ## @mastra/nestjs@0.3.0-alpha.0 ## @mastra/clickhouse@1.30.0-alpha.0 ## @mastra/duckdb@1.19.0-alpha.0 ## @mastra/libsql@1.30.0-alpha.0 ## @mastra/pg@1.36.0-alpha.0 ## @mastra/temporal@0.6.0-alpha.0 ## @mastra/auth-better-auth@1.1.11-alpha.0 ## @mastra/deployer-cloud@1.83.0-alpha.0 ## @mastra/deployer-cloudflare@1.2.42-alpha.0 ## @mastra/deployer-netlify@1.2.42-alpha.0 ## @mastra/deployer-sandbox@0.3.27-alpha.0 ## @mastra/deployer-vercel@1.2.42-alpha.0 ## @mastra/longmemeval@1.1.42-alpha.0 ## @mastra/opencode@0.1.42-alpha.0 ## create-factory@0.4.3-alpha.0 ## mastracode@0.49.1-alpha.0 ## @mastra/arize@1.3.30-alpha.0 ## @mastra/arthur@0.4.30-alpha.0 ## @mastra/braintrust@1.3.27-alpha.0 ## @mastra/datadog@1.4.22-alpha.0 ## @mastra/deepeval@0.1.24-alpha.0 ## @mastra/laminar@1.3.32-alpha.0 ## @mastra/langfuse@1.6.6-alpha.0 ## @mastra/langsmith@1.4.3-alpha.0 ## @mastra/observability@1.23.2-alpha.0 ## @mastra/otel-bridge@1.5.22-alpha.0 ## @mastra/otel-exporter@1.5.2-alpha.0 ## @mastra/posthog@1.4.7-alpha.0 ## @mastra/sentry@1.2.32-alpha.0 ## @mastra/agent-builder@1.2.1-alpha.0 ## @mastra/connect@1.3.2-alpha.0 ## create-mastra@1.39.0-alpha.0 ## @mastra/deployer@1.83.0-alpha.0 ## @mastra/editor@0.17.1-alpha.0 ## @mastra/mcp-docs-server@1.3.13-alpha.0 ## @mastra/memory@1.41.1-alpha.0 ## @mastra/rag@2.7.3-alpha.0 ## @mastra/redis-streams@0.8.1-alpha.0 ## @mastra/elysia@0.1.23-alpha.0 ## @mastra/express@1.5.27-alpha.0 ## @mastra/fastify@1.5.27-alpha.0 ## @mastra/hono@1.7.25-alpha.0 ## @mastra/koa@1.7.27-alpha.0 ## @mastra/next@0.2.41-alpha.0 ## @mastra/tanstack-start@0.2.41-alpha.0 ## @mastra/spanner@1.11.2-alpha.0 ## @mastra/turso@0.1.21-alpha.0 ## @mastra/inngest@1.11.2-alpha.0 ## @mastra/gcs@0.3.6-alpha.0 ## @internal/playground@1.39.0-alpha.0 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
8ad7773cd4 |
feat(observability): align signal writes and context modes (#29289) | ||
|
|
b28ed08077 |
feat(playground-ui): chat annotations for Studio and Factory (#29310)
**─────── TLDR ───────** > In Studio and Factory chat you can select part of a reply, comment on it, and the agent gets it quoted in your next message. Until now, asking about one sentence of a long reply meant copying it into the message box and quoting it by hand. A selection inside one message now offers **Add to chat**. Each passage gets a numbered bubble in the transcript, the message box counts them, and Send turns them into a numbered list ahead of what you typed. ### Behavior changed text selected inside one message, in Studio or Factory └─ **new** — **Add to chat** floats over it, and Tab reaches it an added passage └─ **new** — a numbered bubble that scrolls with it; select it to comment or remove Send with annotations waiting └─ **new** — each passage quoted with its comment, then your text, if any a send that fails └─ **new** — its annotations come back, ahead of any added since a slash command in Factory └─ **unchanged** — runs as before; annotations wait for the next message text typed after dictating, in Studio └─ **fixed** — stays; each keystroke used to bring the dictated text back dictating right after `useSpeechRecognition` gets a new `agentId` └─ **fixed** — uses the browser until the new agent's voice is checked, instead of the previous agent ### Shape changed | | | | |---|---|---| | **+** | `ChatShell.Transcript` | the positioned reading column the bubbles travel with | | **~** | `ChatShell.Dock` | its `ComposerInput` is the one an added passage focuses | | **~** | `escapeRegExp` | annotations needed a third copy, now one in `lib/string` | | **~** | `useSpeechRecognition().start` | takes an optional `onTranscript`, called as each transcript is recognized | what Studio and Factory now mount, from `@mastra/playground-ui/components/ai/annotations` `ChatAnnotationsProvider` · `TranscriptAnnotations` · `ComposerAnnotations` · `useChatAnnotations()` · `formatAnnotatedMessage(text, annotations)` ### Decisions - **the transcript finds its composer through `ChatShell`** — neither app passes refs; a ref prop is the way back if you disagree - **the tint uses the CSS Custom Highlight API** — message text gets no wrapper elements; browsers without it show only the bubbles - **switching threads drops waiting annotations** — each one points at rendered text the switch unmounts - **effects only where React can't reach** — Add to chat's keys and dictated text moved to the handlers that own them, the pending dot's delay to the CSS entrance the trace skeletons use, and the voice check's reset to a value derived in render; the effects left subscribe to the browser, measure layout, or wait on data ### Not verified - [ ] right-click on a selection in macOS: the menu reset is covered in jsdom only, since Playwright cannot open the native menu - [ ] Safari and Firefox: the live runs used Chromium only, and Firefox's multi-range selection is covered in jsdom only - [ ] Factory against a live agent session: its live run used the real app with a mocked agent backend - [ ] Studio dictation in a browser: checked in jsdom only, with a stubbed `SpeechRecognition` - [ ] the pending dot's delay in Studio: the same classes as the trace skeletons, checked in the built stylesheet only --- > ██████████████████████ **tests** `+1545 −11` — 49% of the additions > ███████████████████ **source** `+1333 −147` > ██ **storybook** `+156` > ██ **changeset** `+108` > █ **docs** `+2` --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|
|
6e8dfcb83f | chore: version - exit prerelease mode | ||
|
|
4bc3aa672f |
chore: version packages (alpha) (#29255)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases > The changelog information of each package has been omitted from this message, as the content exceeds the size limit. ## @mastra/factory@0.27.0-alpha.3 ## @mastra/agent-builder@1.2.0-alpha.3 ## @mastra/core@1.82.0-alpha.3 ## @mastra/mcp@2.8.0-alpha.2 ## @mastra/memory@1.41.0-alpha.3 ## @mastra/playground-ui@68.0.0-alpha.3 ## @mastra/ring-signals@0.1.0-alpha.0 ## @mastra/libsql@1.29.0-alpha.2 ## @mastra/mongodb@1.26.0-alpha.2 ## @mastra/mysql@0.16.0-alpha.3 ## @mastra/pg@1.35.0-alpha.3 ## @mastra/discord@1.3.3-alpha.0 ## @mastra/slack@1.8.1-alpha.0 ## @mastra/teams@0.1.4-alpha.0 ## @mastra/telegram@0.2.5-alpha.0 ## @mastra/client-js@1.59.0-alpha.3 ## @mastra/react@1.14.1-alpha.3 ## @mastra/deployer-cloud@1.82.0-alpha.3 ## @mastra/longmemeval@1.1.41-alpha.3 ## @mastra/opencode@0.1.41-alpha.3 ## create-factory@0.4.2-alpha.3 ## @mastra/code-sdk@1.18.0-alpha.3 ## mastracode@0.49.0-alpha.3 ## @mastra/arize@1.3.29-alpha.2 ## @mastra/arthur@0.4.29-alpha.2 ## @mastra/laminar@1.3.31-alpha.2 ## @mastra/langfuse@1.6.5-alpha.2 ## @mastra/otel-bridge@1.5.21-alpha.2 ## @mastra/otel-exporter@1.5.1-alpha.2 ## @mastra/sentry@1.2.31-alpha.3 ## mastra@1.38.0-alpha.3 ## @mastra/connect@1.3.1-alpha.1 ## @mastra/deployer@1.82.0-alpha.3 ## @mastra/editor@0.17.0-alpha.3 ## @mastra/evals@1.10.11-alpha.0 ## @mastra/mcp-docs-server@1.3.12-alpha.4 ## @mastra/server@1.82.0-alpha.3 ## @mastra/elysia@0.1.22-alpha.3 ## @mastra/express@1.5.26-alpha.3 ## @mastra/fastify@1.5.26-alpha.3 ## @mastra/hono@1.7.24-alpha.3 ## @mastra/koa@1.7.26-alpha.3 ## @mastra/nestjs@0.2.41-alpha.3 ## @mastra/next@0.2.40-alpha.3 ## @mastra/tanstack-start@0.2.40-alpha.3 ## @mastra/turso@0.1.20-alpha.2 ## @mastra/inngest@1.11.1-alpha.2 ## @mastra/temporal@0.5.0-alpha.3 ## create-mastra@1.38.0-alpha.3 ## @internal/playground@1.38.0-alpha.3 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
7ad1918a72 |
feat(playground-ui): readable failed Knowledge tool calls and linked knowledge_list cards in chat (#29215)
## Description
Two Knowledge tool cards in Studio chat were hard to read:
1. **Failed Knowledge calls showed `[object Object]`.** When a Knowledge
tool threw (for example, reading a page that does not exist), the error
crossed the wire as `{"name":"KnowledgeNotFoundError"}` with no message.
An `Error`'s `message` is non-enumerable, so serialising the stream
chunk dropped it, and the chat UI then stringified the object.
2. **`knowledge_list` results showed raw JSON**, and once they had a
card, the entries were plain text. In the same chat, `knowledge_search`
hits are links.
This PR fixes both:
- **Server (`@mastra/server`)**: when a stream chunk carries an `Error`
in `payload.error`, it is sent as a plain object that keeps `name` and
`message`. An error class's own `toJSON()` is used when it has one, so
curated fields like `code` and `cause` survive and private fields don't
leak (for example, a provider error's request body). Stacks are no
longer sent.
- **`@mastra/react`**: when a tool error has no usable message, it reads
as `"The tool call failed."`, never a JSON dump.
- **Knowledge cards (`@mastra/playground-ui`)**: a failed Knowledge call
gets its own card, such as "Couldn't read" with the page ref and the
message, instead of the generic failed row. `knowledge_list` results get
a card showing an indented tree with each entry's ref, child count and
description, plus a line when more entries exist. Each entry now links
to its page, the same way search hits do: scope roots (`site:mastra`,
`thread:…`) open their scope page, and nested `scope#path` entries open
at any depth.
- **Opening a page by reference (`@mastra/core`, `@mastra/server`)**:
list entries carry a ref, not a page id. `GET
/knowledge/:knowledgeKey/pages/:pageId` now also accepts a scope address
or a `scope#key/path` ref. It applies the same read check as an id
lookup, and an unknown or unreadable ref still returns 404. Studio's
Knowledge page then replaces the ref in the URL with the page id, so the
tree and graph can highlight the page.
- `KnowledgeLinksProvider` gets an optional `refHref`. Hosts that only
open pages by id leave it out, and list entries stay plain text there.
## Related issue(s)
Part of the Knowledge Studio alpha work (Knowledge tool cards in Studio
chat). Not tracked as a GitHub issue.
## Type of change
- [x] Bug fix (non-breaking change that fixes an issue)
- [x] New feature (non-breaking change that adds functionality)
## Checklist
- [x] I have added tests that prove my fix is effective or that my
feature works
## Test plan
- Server serialize and Knowledge handler tests: 445/445. These include
curating a provider error without leaking its request body, and a 404
for a ref outside the caller's read scope.
- `@mastra/react` accumulator: 195/195
- core `readKnowledgePage` by reference: 15/15. Two of these fail
without the change.
- playground-ui chat and Knowledge suites: 683/683. The list-link test
fails without the change.
- Studio Knowledge page: a ref in `?page=` opens the page and the URL
switches to its id.
- `pnpm --filter ./packages/playground-ui typecheck`: passes
- On the docs demo, a forced read of a missing page showed `[object
Object]` before and "Couldn't read" plus the message after. A
`knowledge_list` card had 0 of 3 scope entries and 0 of 50 page entries
linked before, and all 3 and all 50 linked after. No page errors at 390,
768 or 1440 px.
---------
Co-authored-by: remy-builder[bot] <324360501+remy-builder[bot]@users.noreply.github.com>
|
||
|
|
886679eb10 |
chore: version packages (alpha) (#29205)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases > The changelog information of each package has been omitted from this message, as the content exceeds the size limit. ## @mastra/client-js@1.59.0-alpha.2 ## @mastra/factory@0.27.0-alpha.2 ## @mastra/code-sdk@1.18.0-alpha.2 ## mastra@1.38.0-alpha.2 ## @mastra/core@1.82.0-alpha.2 ## @mastra/editor@0.17.0-alpha.2 ## @mastra/server@1.82.0-alpha.2 ## @mastra/clickhouse@1.29.0-alpha.1 ## @mastra/duckdb@1.18.0-alpha.1 ## @mastra/pg@1.35.0-alpha.2 ## @mastra/platform-workspace@1.12.0-alpha.1 ## @mastra/react@1.14.1-alpha.2 ## @mastra/deployer-cloud@1.82.0-alpha.2 ## @mastra/deployer-sandbox@0.3.26-alpha.1 ## @mastra/longmemeval@1.1.41-alpha.2 ## @mastra/opencode@0.1.41-alpha.2 ## @mastra/parallel@0.1.5-alpha.0 ## create-factory@0.4.2-alpha.2 ## mastracode@0.49.0-alpha.2 ## @mastra/arize@1.3.29-alpha.1 ## @mastra/arthur@0.4.29-alpha.1 ## @mastra/braintrust@1.3.26-alpha.1 ## @mastra/datadog@1.4.21-alpha.1 ## @mastra/deepeval@0.1.23-alpha.1 ## @mastra/laminar@1.3.31-alpha.1 ## @mastra/langfuse@1.6.5-alpha.1 ## @mastra/langsmith@1.4.2-alpha.1 ## @mastra/observability@1.23.1-alpha.1 ## @mastra/otel-bridge@1.5.21-alpha.1 ## @mastra/otel-exporter@1.5.1-alpha.1 ## @mastra/posthog@1.4.6-alpha.1 ## @mastra/sentry@1.2.31-alpha.2 ## @mastra/agent-builder@1.1.33-alpha.2 ## @mastra/deployer@1.82.0-alpha.2 ## @mastra/mcp@2.8.0-alpha.1 ## @mastra/mcp-docs-server@1.3.12-alpha.3 ## @mastra/memory@1.41.0-alpha.2 ## @mastra/playground-ui@68.0.0-alpha.2 ## @mastra/rag@2.7.2-alpha.0 ## @mastra/elysia@0.1.22-alpha.2 ## @mastra/express@1.5.26-alpha.2 ## @mastra/fastify@1.5.26-alpha.2 ## @mastra/hono@1.7.24-alpha.2 ## @mastra/koa@1.7.26-alpha.2 ## @mastra/nestjs@0.2.41-alpha.2 ## @mastra/next@0.2.40-alpha.2 ## @mastra/tanstack-start@0.2.40-alpha.2 ## @mastra/dsql@1.5.6-alpha.0 ## @mastra/libsql@1.29.0-alpha.1 ## @mastra/mongodb@1.26.0-alpha.1 ## @mastra/mssql@1.11.1-alpha.0 ## @mastra/mysql@0.16.0-alpha.2 ## @mastra/oracledb@0.5.6-alpha.0 ## @mastra/spanner@1.11.1-alpha.0 ## @mastra/turso@0.1.20-alpha.1 ## @mastra/voice-google@0.14.5-alpha.0 ## @mastra/inngest@1.11.1-alpha.1 ## @mastra/temporal@0.5.0-alpha.2 ## @mastra/e2b@0.16.1-alpha.1 ## create-mastra@1.38.0-alpha.2 ## @internal/playground@1.38.0-alpha.2 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
c7d27f650b |
feat(editor): make model fallback lists editable and persistent (#27287)
Adds opt-in Editor ownership for static model fallback lists on
code-defined agents.
```ts
new Agent({
id: 'support-agent',
model: [
{ id: 'primary', model: 'openai/gpt-5.4-mini' },
{ id: 'fallback', model: 'anthropic/claude-sonnet-4-5' },
],
editor: { model: true },
})
```
Studio can reorder models, change provider/model selections, and enable
or disable entries. These changes follow the configured Editor
persistence workflow:
- Database-backed Editor storage creates versioned drafts that can be
published.
- Code-backed Editor storage saves overrides to the filesystem or
through the configured pull-request workflow.
Persisted entries include their order, provider, model ID, enabled
state, and `maxRetries`. Immutable model IDs reconnect stored values to
code-defined entries while preserving non-serializable code
configuration.
Function-valued model configurations remain code-owned and read-only in
Studio.
This also adds storage support, model-list persistence through the
existing server mutation routes, generated client types, regression
coverage, documentation, and a changeset.
Closes #27089.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
This lets teams edit and save an agent’s model fallback list in Studio
without changing code. The feature is opt-in, so existing agents keep
their current behavior by default.
## Summary
- Added `editor: { model: true }` support for code-defined agents.
- Added persistent `modelList` storage with entry IDs, provider, model
ID, enabled state, and `maxRetries`.
- Applied stored overrides by matching immutable entry IDs while
preserving code-owned configuration.
- Persisted reorder and update actions through Editor drafts and
publishing workflows.
- Added filesystem, LibSQL, server route, export, versioning, and client
cache support.
- Kept function-valued model configurations code-owned and read-only in
Studio.
- Updated ownership logic, API schemas, client behavior, and
documentation.
- Added regression coverage for runtime overrides, persistence, exports,
ownership, draft activation, storage compatibility, and query
invalidation.
- Added changesets for the affected packages.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
|
||
|
|
30046969ad |
chore: version packages (alpha) (#29146)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases ## @mastra/client-js@1.59.0-alpha.1 ### Minor Changes - Added the `aggregateTimeToFirstMeasures` observability capability. Trace and span aggregate requests for `timeToFirstToken.*` or `timeToFirstChunk.*` measures now return `501` against stores that can't compute them, and field discovery omits those measures for such stores. ([#29055](https://github.com/mastra-ai/mastra/pull/29055)) ```typescript const { capabilities } = await mastraClient.getObservabilityCapabilities(); if (capabilities.traceAggregate && capabilities.aggregateTimeToFirstMeasures) { const { rows } = await mastraClient.aggregateTraces({ timeRange: { from: '2026-08-01T00:00:00.000Z', to: '2026-08-02T00:00:00.000Z' }, groupBy: ['entityName'], measures: ['timeToFirstChunk.p95', 'timeToFirstChunk.count'], }); } ``` ### Patch Changes - Updated dependencies [[`8751dd7`]( |
||
|
|
eed9cc214e | chore: version packages | ||
|
|
77076a1012 | chore: version - exit prerelease mode | ||
|
|
582ef17a2b |
chore: version packages (alpha) (#28888)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
5cc1e6a4cd |
fix(server): report resolver-backed workspace capabilities in workspace routes (#29027) | ||
|
|
655b19993f |
chore(security): Vanta 2026-10-30 - zod ^4.6.7, @hono/node-server 2.1.5 (direct bumps) (#28983)
## Vanta 2026-10-30 security fixes (consolidated)
Direct dependency bumps and lockfile updates only. **No
overrides/resolutions added or raised.** The earlier override-based
edits on this branch were reverted; those findings are deferred below.
| Package | From → To | Advisory | Where |
|---|---|---|---|
| zod | ^3.25.76 → ^4.6.7 | zod <4.6.6 (High; no fixed 3.x) |
`client-sdks/react` (dev), `deployers/cloudflare` (dev),
`server-adapters/nestjs` (dev), `packages/editor` (dev),
`packages/playground-ui` (dep), `packages/playground`,
`workflows/_test-utils`, `examples/{durable-agents,inngest}`,
`explorations/longmemeval`,
`observability/_examples/otel-bridge/agent-hub`, e2e fixtures/templates
(`experiment-worker/fixtures/*`, `deployers/template/cloudflare`,
`no-bundling/template`, agent-builder `minimal-mastra-project`) + root
`pnpm-lock.yaml` |
| @hono/node-server | 1.19.x / 2.1.1 → 2.1.5 | CVE-2026-118663 /
GHSA-rmxm-3fg6-px4f (Medium) | direct deps: `examples/agent-builder`,
`otel-bridge/hono-multi/service-{one,two,mastra}`,
`templates/template-customer-refund-agent/client-demo-ui`,
`templates/template-kyc-customer-onboarding`,
`templates/template-security-incident-triage` |
Peer ranges (`^3.25.0 || ^4.0.0`) are unchanged, so consumers are
unaffected. Changeset: patch for `@mastra/playground-ui` (runtime zod
dep).
Supersedes the zod parts of #28075 (that PR also raises a pnpm override
and rewrites the `zod-v3` compat aliases to v4, so it is left as-is for
maintainers).
### Deferred (needs override, upstream release, or is intentional)
- zod v3 compat aliases (`zod-v3` in `packages/core`,
`packages/schema-compat`, `e2e-tests/type-check/template`;
`e2e-tests/client-js/zod-v3`): intentional zod 3 test coverage; no fixed
3.x release. Needs a decision to drop/dismiss.
- zod 3.25.76 transitive via `@arcadeai/arcadejs`, `@mcp-ui/client`,
firecrawl, `agent-browser`, `zod-to-json-schema`, MCP SDK paths:
upstream pins; override-only.
- @hono/node-server 1.19.x transitive via `@modelcontextprotocol/sdk`
(root, `examples/agent`, `packages/mcp/integration-tests`), and npm
lockfiles of `scripts/gh-issue-triage` (existing override, left alone)
and the two templates: override-only.
- graphql-scalars, raw-body, jose (templates/scripts): override-only.
- @azure/msal-node <7.1.0: 6.0.1 via `@azure/identity@4.14.0` (fixed in
4.14.1, blocked by the 1-day `minimumReleaseAge`; lockfile refresh
tomorrow), 5.6.0 via `@microsoft/teams.apps` (no fixed release).
- @opentelemetry/core <2.8.0: via `@google-cloud/pubsub@5` (fix needs
pubsub 6 major).
- @ai-sdk/provider-utils 2.2.8 / ai 4.x: pinned vendored AI SDK v4 line;
no fixed release in that major.
- extract-zip, deepmerge: no patched version.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
This PR updates Zod and `@hono/node-server` versions in selected
packages, examples, and templates to address security advisories. It
also updates playground form code to work with Zod 4.
## Changes
- Updates selected `zod` dependencies to `^4.6.7`.
- Updates selected `@hono/node-server` dependencies to `2.1.5`.
- Updates the playground form’s IP address and record validators for Zod
4.
- Maps a specific Zod validation error to the message `Required`.
- Adds a patch changeset for `@mastra/playground-ui`.
## Validation
Test results are not provided in the supplied change summary.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Co-authored-by: shreyas-mastra <327047572+shreyas-mastra@users.noreply.github.com>
|
||
|
|
6e93079260 |
feat(playground-ui): add time to first chunk and token to observability lists and trace details (#28898)
Observability stores now record time to first token (TTFT) next to time
to first chunk (TTFC), but Studio only showed TTFC, and only on the
Traces list. This brings both timings to every observability list and to
trace details, so slow-starting model calls are easy to find wherever
you look.
**Lists**
- **Traces**: TTFT is a new optional column you can sort by, like TTFC,
and both timings can be used as filters on the trace or on any of its
spans.
- **Spans**: TTFC and TTFT are new optional columns, sortable and
filterable.
- **Threads**: now has its own column picker (messages, TTFC, TTFT…),
saved per project and in saved views, and both timings can be used as
filters.
Each timing only shows up when the store records it. That also applies
to the existing TTFC span/thread filters, which used to hit a 501 on
stores without it.
**Trace details**
- The span details Timing section shows TTFC and TTFT when the span
streamed.
- On the trace timeline, a "Metrics" row (closed by default) shows TTFC
and TTFT as dashed rows above the spans, both ending on the first chunk.
This shows how much of the wait came from the model and how much from
earlier steps. The values come from the listed trace row, so no extra
request is made; traces not in the list show no Metrics row.
**API change**: `useObservabilityListFilters` now keeps the sort as a
field and a direction:
```ts
const { sort, setSort } = useObservabilityListFilters(url, {
sortFields: ['startedAt', 'timeToFirstTokenMs'],
});
setSort({ field: 'timeToFirstTokenMs', direction: 'asc' });
```
**Tests**: MSW tests on the explorers and columns menu (capability
gating, sort requests, URL state, timeline metrics from the listed row)
plus unit tests on the filter, column and timeline helpers. Platform
side: mastra-ai/platform#3981.
Refs OBS-763
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
The observability lists can now show how long traces and spans take to
produce their first output. These timing columns and filters appear only
when the store supports them, and trace details can show the timings on
the timeline.
## Summary
- Added optional TTFC and TTFT columns, sorting, and filters for traces,
spans, and threads.
- Added a project- and saved-view-scoped column picker for threads.
- Gated timing columns and filters on store capabilities. Hidden
unsupported columns retain their saved preferences.
- Added TTFC and TTFT values to span details. Added a
collapsed-by-default Metrics section to the timeline, using timing data
from the listed trace row when available.
- Updated `useObservabilityListFilters` and URL sort state to represent
sorting as a field and direction.
## Testing
The changes include tests for capability gating, sorting, URL state,
filters, thread column preferences, and timeline metrics. Test execution
results were not provided.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
|
||
|
|
2e62b365e4 |
chore: version packages (alpha) (#28869) | ||
|
|
4f12792ed1 |
chore: version packages (alpha) (#28722)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
81cf36f60d |
feat(observability): record and query time to first token on spans, traces and threads (#28699)
## Description Fills the `timeToFirstTokenMs` span column that #28389 added empty, and lets trace, span and thread queries return, filter and sort by it. Time to first token is the time from the start of the model call (the `model_inference` span) to the first streamed chunk. Unlike `timeToFirstChunkMs`, it leaves out the work Mastra does before calling the model. - The tracker measures the value once, on the `model_inference` span, when its first chunk arrives, and copies that number up the agent's own chain (`model_step`, `model_generation`, `agent_run`) as a `timeToFirstTokenMs` attribute, first write wins, the same way `completionStartTime` is copied. Each step takes its own inference's value; the generation and agent run take the first step's. - Span export reads the attribute. Storage fills the column from it and drops the key from the attributes JSON. The Platform collector and the store row mappers already carry the column, so no DDL changes. - Durable agents (core and `@mastra/inngest`) carry the number through loop state beside `completionStartTime`, so a fresh tracker on another worker ends the generation and agent run with both. - Core contract, ClickHouse, Postgres and DuckDB return, filter and sort the field. Trace rows use the root span's value. Thread rows use the first trace's root when it is an agent run. Empty values sort last. Stores declare `trace-query-time-to-first-token` and `-sort`; the server returns 501 when a store lacks them. - A fallback model attempt opens its own `model_inference` span, named after the model it calls, so its value and label are its own, and a failed attempt's span ends with its error. Braintrust and LangSmith keep the attribute out of span metadata. - Client types regenerated, `useTraceQuery` keeps new traces in order under the new sort, docs and changesets added. No Studio changes. - Also fixes two gaps that already affected `timeToFirstChunkMs`: durable abort and tripwire exits now keep the clocks on the ended spans, and span aggregation gates the timing field instead of failing inside the store. - After a failed model call, in-process agents count the retry wait and durable agents do not. One test marked expected-to-fail pins that difference. Rebased on `main` after #28389 merged. ## Related Issue(s) N/A (OBS-722 follow-up) ## Type of Change - [ ] Bug fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [ ] Test update ## Checklist - [x] I have made corresponding changes to the documentation (if applicable) - [x] I have added tests that prove my fix is effective or that my feature works - [ ] I have addressed all Coderabbit comments on this PR 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 This change measures how long a model takes to send its first piece of a response. Supported storage systems can return, filter, and sort by this time, which helps teams find slow responses. ## Summary - Records `timeToFirstTokenMs` from the start of a model inference to its first streamed chunk. The value is added to inference spans and propagated to related model-step, generation, and agent-run spans. - Gives each fallback model attempt its own inference span and timing value. Carries timing across durable agent steps, including resumed runs and abort or tripwire exits. - Adds `timeToFirstTokenMs` to trace, span, and thread query results and predicates. Trace values use the root span. Thread values use the first trace’s root agent span. - Adds sorting by this field for trace and span queries in ClickHouse, PostgreSQL, and DuckDB. Missing values sort last. The server returns `501` when a store does not support a requested predicate or sort. - Updates client types, `useTraceQuery`, documentation, storage capability declarations, and changesets. Braintrust and LangSmith exporters exclude the field from span metadata. - Adds and updates tests across tracing, durable workflows, query handling, and storage conformance. Test execution results were not provided. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
|
f3abb9c940 |
fix(react): keep experiment details cached when navigating back (#28813)
## Description
Opening an experiment you'd already visited showed a loading state every
time, because the experiment query set `gcTime: 0`, which drops the
cache as soon as the page unmounts. `staleTime: 0` was also set, but
that's already TanStack Query's default, so it did nothing.
This PR removes both settings so the experiment query behaves like our
other queries (agents, workflows). When you go back to an experiment,
the cached data shows right away and refreshes in the background. The
refetch on mount still updates a stale `running` status and stops
polling once the experiment has finished.
```ts
// before
tanstackQueryOptions({
queryKey: ['dataset-experiment', datasetId, experimentId],
queryFn: () => client.getDatasetExperiment(datasetId, experimentId),
gcTime: 0,
staleTime: 0,
refetchInterval: query => (isInProgress(query.state.data?.status) ? POLL_INTERVAL_MS : false),
});
// after
tanstackQueryOptions({
queryKey: ['dataset-experiment', datasetId, experimentId],
queryFn: () => client.getDatasetExperiment(datasetId, experimentId),
refetchInterval: query => (isInProgress(query.state.data?.status) ? POLL_INTERVAL_MS : false),
});
```
I added two MSW tests for `useDatasetExperiment`. The first checks that
cached data renders without a loading state after an unmount and
remount. It fails without this fix. The second checks that a cached
`running` experiment switches to `completed` and polling stops.
## Related issue(s)
None. Found while reviewing experiments in Studio.
## Type of change
- [x] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [x] Test update
## Checklist
- [ ] I have linked the related issue(s) in the description above
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [x] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have addressed all Coderabbit comments on this PR
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
When you return to an experiment, the page can show the saved details
right away while it checks for updates. If the experiment is still
running, it keeps checking; when it completes, checking stops.
## Changes
- Removed the `gcTime: 0` and `staleTime: 0` settings from the
dataset-experiment query. Cached data can now remain available and
render while a mount refetch runs.
- Added tests for cached data on remount and for a cached running
experiment updating to completed, after which polling stops.
- Added a patch changeset for `@mastra/react`.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
|
||
|
|
6a191d46dc | chore: version - exit prerelease mode | ||
|
|
332eb25cdc |
chore: version packages (alpha) (#28647)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
e6764d26da |
chore: version packages (alpha) (#28625)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
a7cc444233 |
fix(core): expose recoverable run outcomes to thread subscribers (#28621)
Thread subscribers now receive an ordered `thread-run-status` frame for
success, failure, abort, or suspension without closing the subscription.
Initial history also reports `activeRunId`, so an idle snapshot no
longer has to stand in for a run outcome. Retained outcomes reach late
subscribers even after saved output has been trimmed, with execution
authority preserved to reject superseded attempts.
For example, a subscription opened after a run finishes now receives
`thread-history` followed by `thread-run-status` with `{ status:
"success" }`, rather than history alone. Recovery is bounded by PubSub
retention; upgrade both `@mastra/core` and `@mastra/redis-streams` for
recovery after trimming. Client callback types, documentation, and
package changesets are included.
Verified with core build and typecheck, 220 core tests across the
thread-stream suites and four execution engines, 91 client tests, 55
Redis integration tests, and three HTTP conformance cases covering
plain, durable, and evented agents. Real Redis regressions cover restart
after trimming and superseded completion/abort after registration
eviction. The live outcome scenario also passed 20 repeated four-engine
runs. Typed lint, formatting, MDX prose checks, and final adversarial
review passed.
Fixes COR-1500.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
A thread subscription can now tell clients when a run succeeds, fails,
stops, or pauses without ending the subscription. This helps clients
understand what happened after reconnecting, even when the run’s saved
output is no longer available.
## Summary
- Added opt-in `withRunStatus` support to core, server, and client
thread subscriptions. Enabled subscriptions can receive ordered
`thread-run-status` chunks for `success`, `failed`, `aborted`, or
`suspended` outcomes.
- Added `activeRunId` to initial thread history so clients can identify
the run that held the thread lease during history loading.
- Added terminal-event retention during output trimming. Recovery
depends on PubSub retention. Redis Streams users must upgrade
`@mastra/core` and `@mastra/redis-streams` together.
- Updated React `useChat` to request run statuses and apply outcomes to
the matching run. Added API types, documentation, and changesets.
## Validation
The PR objectives report passing core build and typecheck, core and
client tests, Redis integration tests, HTTP conformance cases, lint and
formatting checks, and documentation checks. They also report repeated
run-outcome checks and adversarial review. These results are
author-reported.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: mastra-platform[bot] <mastra-platform[bot]@users.noreply.github.com>
Co-authored-by: mastra-platform[bot] <284800079+mastra-platform[bot]@users.noreply.github.com>
|
||
|
|
ef92d71d94 |
chore: version packages (alpha) (#28499)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
852110d4ee |
Remove model and provider from thread rows and cap thread pages at 100 (#28595)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |
||
|
|
168e0abe68 |
feat(playground-ui): data layer for Metrics cards on trace and span aggregates (#27908)
## What The data layer for Metrics cards built on `aggregateTraces()` and `aggregateSpans()`, shared by Studio and Platform's Metrics pages. No visible change on its own: the cards that use it are in #28272. First of two playground-ui PRs for OBS-698 (#28062 is an independent fix that lands alongside). ## Why The new cards (Breakdown, Resources and threads) need trace and span aggregates, and two Metrics pages (Studio's project page, Platform's org page) must send the same requests from the same components. That takes a few shared pieces that are easier to review on their own than inside 3,000 lines of cards. ## Changes - **Hooks:** `useTraceAggregate` and `useSpanAggregate` in `@mastra/react`; `aggregateTraces()` in `@mastra/client-js` takes an abort signal. - **Layout gate:** `useMetricsLayout()` returns `unified` only when the server reports both `traceAggregate` and `spanAggregate`, else `legacy` (today's page, card for card). Someone can upgrade Studio without upgrading their storage, so the page never mixes layouts. - **One window per page:** `MetricsProvider` freezes "now" once per range change, so every card's request keys match and React Query dedups requests shared between cards. - **Scope:** `MetricsProvider` takes `scope: { projectLabel? }` for pages that span several projects; `DrilldownScope` gains `projectId`. - **One limiter for all aggregate requests:** at most 3 in flight, in page order with a priority (`first`/`normal`/`last`). It deliberately ignores React Query's abort signal: under StrictMode the mount/unmount/remount aborted and resent every first-wave request. A queued request nobody observes any more is skipped when it reaches the front. - **Request builders and gates:** `useMetricsTraceAggregate`/`useMetricsSpanAggregate` and `useTraceAggregateGate`/`useSpanAggregateGate`, which map the page filters into a `where` and report filters an aggregate can't apply, so a card says so instead of showing an unfiltered number. ## Test plan - [x] MSW tests through the real client for the limiter (never more than 3 in flight, priority order, started requests never aborted, unobserved queued requests skipped, nested providers share one cap), the layout gate (both capabilities / one / failing capabilities request), and both React hooks. - [x] Unit tests for the filter-to-`where` mapping and interval choice, checked against the server's own request schema and planner. - [x] typecheck, lint and tests for playground-ui, playground and @mastra/react. - [ ] X58 whole-page benchmark (run on the full stack with #28272). <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## ELI5 This PR adds a shared way for Metrics pages to request trace and span data. The new page layout is used only when the server supports both request types; older servers keep the existing layout. ## What changed - Added the `useTraceAggregate` and `useSpanAggregate` hooks to `@mastra/react`. - Added optional `AbortSignal` support to `aggregateTraces()` in `@mastra/client-js`. - Added filter builders, time-range conversion, interval selection, and trace bucket generation for aggregate requests. - Added capability checks that select the unified layout only when the server supports both trace and span aggregates. - Added a shared limiter for aggregate requests. It allows up to three requests at once, orders queued requests by priority, and skips queued requests that are no longer observed. Started requests continue after unmount. - Updated `MetricsProvider` to share query filters and project scope. Added `projectId` to `DrilldownScope`. ## Validation and status The PR description reports tests for the limiter, layout selection, React hooks, filter mapping, and interval selection. It also reports typecheck, lint, and tests for `playground-ui`, `playground`, and `@mastra/react`. The whole-page X58 benchmark remains unchecked. The PR description says it is planned alongside `#28272`. This PR adds the data layer; the cards that use it are planned for `#28272`. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |
||
|
|
355b5299b9 |
feat(playground-ui): add a Columns menu to the Spans page (#28562)
The Columns menu only existed on the Traces page, so the Spans list was
stuck with a fixed set of columns. This pulls the menu out into a
reusable `ColumnsMenu` that takes a scope and only offers the columns
that scope's rows actually have.
On Spans you can now show Model, Provider, End, Environment and the
Trace/Thread/Resource/Primitive ID columns. Usage and metadata columns
aren't offered there because span rows don't carry that data. Traces
behaves exactly as before, and Threads doesn't get a menu since there's
no discovery endpoint for it.
```tsx
const columns = useTraceColumnPreferences({ scope: 'spans' });
<ColumnsMenu scope="spans" value={columns.preferences} onChange={columns.setPreferences} />
```
Span column choices are saved under their own key
(`mastra:spans:columns:…`) via a new optional `scope` argument on
`useTraceColumnPreferencesStorageKey` in `@mastra/react`, so they never
overwrite trace choices. Existing trace preferences keep their key. The
column toggling logic moved into pure reducers shared by the menu and
the hook.
Testing: MSW tests for `ColumnsMenu` (capability loading, metadata
discovery, usage gating, threads firing no requests, per-scope
defaults/reset) and for the Spans body (Model/Provider offered and
rendered, persisted separately from traces). playground-ui traces +
spans suites pass (1230 tests), typecheck and lint clean for
playground-ui, @mastra/react and playground. Also checked by hand in
Studio with real agent runs (gpt-5.6, gpt-6-luna, plus failed
Anthropic/Gemini runs): every Traces and Spans column shows sensible
values, Model/Provider fill only on model spans, and the menu fits on
mobile, tablet and desktop.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## ELI5
The Spans page can now show extra details, such as the model and
provider, when you choose them from a Columns menu. Your span choices
are saved separately from your trace choices.
## Summary
- Added a reusable `ColumnsMenu` for traces and spans, with columns
based on the selected scope. Threads do not show the menu.
- Added Model and Provider columns to span rows and the shared traces
list view.
- Added span-specific defaults and storage keys. Existing trace
preferences remain under their current keys.
- Added tests for column choices, discovery behavior, persistence, and
reset behavior. Test results and manual validation status are not
established by the supplied evidence.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com>
|
||
|
|
2c646b53d0 |
chore: version packages (alpha) (#28399)
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. ⚠️⚠️⚠️⚠️⚠️⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`. ⚠️⚠️⚠️⚠️⚠️⚠️ # Releases > The changelog information of each package has been omitted from this message, as the content exceeds the size limit. ## @mastra/factory@0.25.0-alpha.5 ## @mastra/langsmith@1.4.0-alpha.2 ## @mastra/connect@1.2.0-alpha.2 ## @mastra/core@1.80.0-alpha.4 ## @mastra/playground-ui@66.0.0-alpha.4 ## @mastra/acp@0.4.4-alpha.0 ## @mastra/claude@0.3.4-alpha.0 ## @mastra/cursor@0.3.4-alpha.0 ## @mastra/openai@1.1.4-alpha.0 ## @mastra/auth-auth0@1.2.6-alpha.0 ## @mastra/auth-better-auth@1.1.9-alpha.0 ## @mastra/auth-clerk@1.3.2-alpha.0 ## @mastra/auth-cloud@1.2.8-alpha.0 ## @mastra/auth-firebase@1.1.5-alpha.0 ## @mastra/auth-google@0.1.7-alpha.0 ## @mastra/auth-neon@0.3.5-alpha.0 ## @mastra/auth-okta@0.2.6-alpha.0 ## @mastra/auth-studio@1.3.11-alpha.1 ## @mastra/auth-supabase@1.1.6-alpha.0 ## @mastra/auth-workos@1.6.8-alpha.0 ## @mastra/agent-browser@0.5.5-alpha.0 ## @mastra/browser-viewer@0.2.6-alpha.0 ## @mastra/browser-firecrawl@0.2.5-alpha.1 ## @mastra/stagehand@0.3.7-alpha.1 ## @mastra/discord@1.3.2-alpha.0 ## @mastra/slack@1.8.0-alpha.1 ## @mastra/teams@0.1.3-alpha.0 ## @mastra/telegram@0.2.4-alpha.0 ## @mastra/client-js@1.57.0-alpha.4 ## @mastra/react@1.13.0-alpha.4 ## @mastra/isolated-vm@0.1.4-alpha.0 ## @mastra/quickjs@0.1.5-alpha.0 ## @mastra/deployer-cloud@1.80.0-alpha.4 ## @mastra/deployer-cloudflare@1.2.39-alpha.1 ## @mastra/deployer-netlify@1.2.39-alpha.1 ## @mastra/deployer-sandbox@0.3.24-alpha.1 ## @mastra/deployer-vercel@1.2.39-alpha.1 ## @mastra/voyageai@0.4.3-alpha.0 ## @mastra/longmemeval@1.1.39-alpha.4 ## @mastra/livekit@0.5.2-alpha.0 ## @mastra/opencode@0.1.39-alpha.4 ## @mastra/parallel@0.1.4-alpha.0 ## create-factory@0.3.1-alpha.4 ## @mastra/code-sdk@1.15.1-alpha.5 ## mastracode@0.48.1-alpha.4 ## @mastra/arize@1.3.27-alpha.2 ## @mastra/arthur@0.4.27-alpha.2 ## @mastra/braintrust@1.3.24-alpha.2 ## @mastra/datadog@1.4.19-alpha.2 ## @mastra/deepeval@0.1.21-alpha.2 ## @mastra/laminar@1.3.29-alpha.2 ## @mastra/langfuse@1.6.3-alpha.2 ## @mastra/observability@1.21.1-alpha.2 ## @mastra/otel-bridge@1.5.19-alpha.2 ## @mastra/otel-exporter@1.4.10-alpha.2 ## @mastra/posthog@1.4.4-alpha.2 ## @mastra/sentry@1.2.29-alpha.2 ## @mastra/agent-builder@1.1.31-alpha.2 ## @mastra/auth@1.1.5-alpha.0 ## mastra@1.36.0-alpha.4 ## @mastra/codemod@1.1.8-alpha.0 ## create-mastra@1.36.0-alpha.4 ## @mastra/deployer@1.80.0-alpha.4 ## @mastra/editor@0.16.5-alpha.2 ## @mastra/evals@1.10.9-alpha.0 ## @mastra/fastembed@1.3.5-alpha.2 ## @mastra/loggers@1.3.10-alpha.1 ## @mastra/mcp@2.6.0-alpha.1 ## @mastra/mcp-docs-server@1.3.10-alpha.7 ## @mastra/mcp-registry-registry@1.1.7-alpha.0 ## @mastra/memory@1.39.1-alpha.2 ## @mastra/rag@2.7.1-alpha.0 ## @mastra/schema-compat@1.3.17-alpha.0 ## @mastra/server@1.80.0-alpha.4 ## @mastra/google-cloud-pubsub@1.1.5-alpha.1 ## @mastra/redis-streams@0.6.5-alpha.1 ## @mastra/valkey-streams@0.5.7-alpha.1 ## @mastra/elysia@0.1.20-alpha.4 ## @mastra/express@1.5.24-alpha.4 ## @mastra/fastify@1.5.24-alpha.4 ## @mastra/hono@1.7.22-alpha.4 ## @mastra/koa@1.7.24-alpha.4 ## @mastra/nestjs@0.2.39-alpha.4 ## @mastra/next@0.2.38-alpha.4 ## @mastra/server-adapters-test-suite@0.1.4-alpha.2 ## @mastra/tanstack-start@0.2.38-alpha.4 ## @mastra/astra@1.1.3-alpha.0 ## @mastra/azure-ai-search@0.1.2-alpha.1 ## @mastra/chroma@1.1.5-alpha.0 ## @mastra/clickhouse@1.27.0-alpha.1 ## @mastra/cloudflare@1.7.6-alpha.0 ## @mastra/cloudflare-d1@1.4.5-alpha.1 ## @mastra/convex@1.7.6-alpha.0 ## @mastra/couchbase@1.1.4-alpha.1 ## @mastra/dsql@1.5.5-alpha.0 ## @mastra/duckdb@1.16.0-alpha.1 ## @mastra/dynamodb@1.4.5-alpha.1 ## @mastra/elasticsearch@1.4.6-alpha.1 ## @mastra/lance@1.5.2-alpha.1 ## @mastra/libsql@1.27.1-alpha.0 ## @mastra/mongodb@1.24.1-alpha.1 ## @mastra/mssql@1.10.6-alpha.0 ## @mastra/mysql@0.14.1-alpha.0 ## @mastra/opensearch@1.1.4-alpha.1 ## @mastra/oracledb@0.5.5-alpha.0 ## @mastra/pg@1.33.0-alpha.2 ## @mastra/pinecone@1.1.3-alpha.0 ## @mastra/qdrant@1.1.6-alpha.0 ## @mastra/redis@1.4.12-alpha.1 ## @mastra/s3vectors@1.1.5-alpha.0 ## @mastra/spanner@1.10.1-alpha.1 ## @mastra/turbopuffer@1.2.3-alpha.0 ## @mastra/turso@0.1.18-alpha.0 ## @mastra/upstash@1.5.5-alpha.1 ## @mastra/valkey@0.2.8-alpha.1 ## @mastra/vectorize@1.1.4-alpha.0 ## @mastra/weaviate@0.1.4-alpha.0 ## @mastra/voice-aws-nova-sonic@0.2.6-alpha.0 ## @mastra/voice-azure@0.12.3-alpha.0 ## @mastra/voice-cloudflare@0.13.4-alpha.0 ## @mastra/voice-deepgram@0.13.3-alpha.0 ## @mastra/voice-elevenlabs@0.13.3-alpha.0 ## @mastra/voice-gladia@0.13.3-alpha.0 ## @mastra/voice-google@0.14.4-alpha.0 ## @mastra/voice-google-gemini-live@0.14.18-alpha.0 ## @mastra/voice-inworld@0.4.6-alpha.0 ## @mastra/voice-mistral@0.1.3-alpha.0 ## @mastra/voice-modelslab@0.2.3-alpha.0 ## @mastra/voice-murf@0.13.3-alpha.0 ## @mastra/voice-openai@0.13.4-alpha.0 ## @mastra/voice-openai-realtime@0.14.8-alpha.0 ## @mastra/voice-playai@0.13.3-alpha.0 ## @mastra/voice-sarvam@1.1.4-alpha.0 ## @mastra/voice-speechify@0.14.3-alpha.0 ## @mastra/voice-xai-realtime@0.2.17-alpha.0 ## @mastra/inngest@1.10.8-alpha.3 ## @mastra/temporal@0.4.18-alpha.4 ## @mastra/agentcore@0.5.3-alpha.0 ## @mastra/agentfs@0.2.3-alpha.0 ## @mastra/apple-container@0.5.2-alpha.0 ## @mastra/archil@0.3.2-alpha.0 ## @mastra/azure@0.3.3-alpha.1 ## @mastra/blaxel@0.10.2-alpha.0 ## @mastra/cloudflare-sandbox@0.5.4-alpha.0 ## @mastra/daytona@0.11.4-alpha.0 ## @mastra/docker@0.12.1-alpha.0 ## @mastra/e2b@0.15.1-alpha.1 ## @mastra/e2b-desktop@0.1.10-alpha.1 ## @mastra/files-sdk@0.3.3-alpha.0 ## @mastra/gcs@0.3.5-alpha.1 ## @mastra/google-drive@0.2.4-alpha.0 ## @mastra/mesa@0.3.3-alpha.0 ## @mastra/modal@0.7.3-alpha.0 ## @mastra/platform-workspace@1.10.0-alpha.1 ## @mastra/railway@0.10.2-alpha.1 ## @mastra/s3@0.6.5-alpha.1 ## @mastra/sprites@0.1.2-alpha.0 ## @mastra/vercel@1.6.2-alpha.0 ## @internal/playground@1.36.0-alpha.4 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|
|
ce5d4731ee |
chore(deps): update dependencies across the monorepo (#28417)
Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |
||
|
|
dac22288b0 | chore: version packages | ||
|
|
f9317a7150 |
chore: version packages (alpha) (#28265)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |