Repository navigation
Offer Mastra when adding a Bot or an agent - #1731
Merged
Merged
Conversation
Mastra was left out of the framework list on purpose: a Mastra server has no AG-UI route, so the address test and the create could only treat it as an AG-UI agent, and a Mastra Bot made that way would never answer. The server now proves a Mastra address against Mastra's own API when the create names the framework, and saves it as a Mastra Bot. So the list offers Mastra with its mark, after Langroid. Picking it skips the AG-UI test, which can only fail against a Mastra server, and creates straight away; what the server refused with is shown under the address. The address step asks for the Mastra server's own address. Changing an agent added as Mastra skips the AG-UI test the same way. Single-agent Mastra servers only: one with several agents is refused when it is added.
davidmckayv
requested review from
MikeRyanDev,
dustywusty,
guidovizoso,
mxmzb,
samjulien and
tylerslaton
as code owners
November 16, 2026 20:21
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
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.
What
Mastra is now offered in the framework list when adding a Bot (New Bot) or an agent (Agents, Add agent), with its mark, after Langroid.
Why it was missing
shared/harnesses.jsonhadwebCreate: falsefor Mastra, on purpose. A Mastra server has no AG-UI route, so the address test and the create could only treat it as an AG-UI agent, and a Mastra Bot made that way would never answer. The create now names the framework (harness: "mastra", already in the API's enum), and the server proves a Mastra address against Mastra's own API and saves it as a Mastra Bot. So the row can be offered.What picking it does
harness: "mastra"and "Powered by Mastra".Single-agent Mastra servers only. One with several agents is refused when it is added.
shared/harnesses.tsgainsreachedThroughMastra(id). No API spec change.Tests
app/tests/new-bot-sheet.test.tsx: Mastra is offered with its mark; picking it opens the address step and creates withharness: "mastra"and no AG-UI test; a refused create shows the server's sentence once, under the address. Failed before the change (no Mastra row), passes after.shared/harnesses.test.ts: the web list includes Mastra, and Mastra is the one framework reached through Mastra's API.Checked by looking
New Bot picker and Mastra address step, and the Agents page's Add agent picker and address step, in Chromium and WebKit, light and dark, at 1440 and 700 wide, against a local dev build. The Mastra mark is drawn in
currentColor, so it renders black on the plain row in light mode and on the white tile in dark mode, like the other marks.