feat(projects): Add Mastra, Flue, and Eve platforms - #125015
Merged
obostjancic merged 10 commits intoSep 24, 2026
Merged
obostjancic merged 10 commits into
obostjancic merged 10 commits into
Conversation
github-actions
Bot
added
Scope: Frontend
obostjancic
changed the title
github-actions
Bot
removed
the
Scope: Backend
obostjancic
marked this pull request as ready for review
September 21, 2026 07:53
shellmayr
approved these changes
Sep 21, 2026
ArthurKnaus
approved these changes
Sep 21, 2026
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
obostjancic
added a commit
that referenced
this pull request
Sep 21, 2026
Project creation now accepts `node-mastra`, `node-flue`, and `node-eve` as valid platform IDs. This PR must merge and deploy before the frontend picker change in #125015 can merge. Refs TET-2969
obostjancic
changed the title
Add createable Node platforms for Mastra, Flue, and Eve with framework-specific setup guides, Node product onboarding, and matching defaults in Explore Agent Monitoring. Refs TET-2969
obostjancic
force-pushed
the
ognjenbostjancic/tet-2969-add-mastra-flue-eve-as-project-platforms
branch
from
September 23, 2026 13:57
255b0f6 to
ee86b6d
Compare
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ee86b6d. Configure here.
Treat Mastra, Flue, and Eve project platforms as authoritative in Agent onboarding so their integration and deployment selectors stay hidden and query overrides cannot select conflicting setup instructions. Refs TET-2969
Framework-specific Mastra, Flue, and Eve projects already handle conversation correlation, so omit the generic manual conversation ID guidance for those platforms. Refs TET-2969
Use the project platform to select Mastra, Flue, or Eve setup in Conversations, hide redundant selectors, and keep conversation-specific user guidance on top of the shared framework setup. Refs TET-2969
Contributor
📊 Type Coverage Diff✅ no issues found |
Place Conversations copy instructions in the Install step and use app.ts as the Flue entry point in its generated setup guidance. Refs TET-2969
Avoid an AgentIntegration assertion by using a string-keyed set for integrations that supply conversation IDs automatically, and remove redundant UI tests. Refs TET-2969
Move active Mastra, Flue, and Eve setup definitions into their platform directories and centralize project-platform option selection across Agents and Conversations. Include Flue input and output recording environment variables in its generated setup. Refs TET-2969
Remove the broad data-structure parity test for agent framework product onboarding. Refs TET-2969
…eve-as-project-platforms
Advertise SDK 11.0.0 as the minimum for integrations that rely on the v11 Eve and Mastra APIs while retaining existing defaults for other integrations. Refs TET-2969
obostjancic
deleted the
ognjenbostjancic/tet-2969-add-mastra-flue-eve-as-project-platforms
branch
September 24, 2026 07:33
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mastra, Flue, and Eve are now available as Node server platforms when creating a project. They use their native icons from
platformicons9.7.0 and expose the same Tracing, Profiling, Logs, and Metrics product choices as Node.Each platform has framework-specific setup shared by regular project onboarding, Explore > Agents, and Explore > Conversations: Mastra installs the v11 Node SDK with
@mastra/observabilityand preloads its instrument file, Flue uses its official Sentry blueprint, and Eve createsagent/instrumentation/sentry.tswith the v11Sentry.eveInstrumentationprovider. Agents shows the base framework setup, while Conversations layers on conversation-specific user guidance.For framework-specific projects, both Explore onboarding surfaces use the known integration directly and hide redundant integration/runtime selectors, including when conflicting query parameters are present. They also omit generic manual conversation-ID guidance because these frameworks correlate conversations automatically.
This work assumes Sentry JavaScript SDK v11 is the released baseline. Blocked by #125016: the backend platform allowlist must merge and deploy before this frontend PR merges, otherwise project creation will reject the new platform IDs.
Closes TET-2969