Live data from Hacker News

Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs

github.com

31–40 of 72 posts

Re: Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs

#33
post #27
post #23

> a `.network()` method that turns any agent into a routing agent say more pls?

We've always supported letting folks specify their agent hierarchy, eg agent supervisor, workflow orchestrator, mix and match, etc. But people kept asking us for a multi-agent primitive out of the box so we shipped `agent.network()`, which is basically dynamic hierarchy decided at runtime, pass in an array of workflows and agents to the routing agent and let it decide what to do, how long to execute for, etc! https:/…

ty! btw your docs search is broken, as i tweeted to Ward.

Re: Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs

#34

I've been building with Mastra for a couple of weeks now and loving it, so congratulations on reaching 1.0! It's built on top of Vercel AI elements/SDK and it seems to me that was a good decision. My mental heuristic is: Vercel AI SDK = library, low level Mastra = framework Then Vercel AI Elements gives you an optional pre built UI. However, I read the blog post for the upcoming AI SDK 6.0 release last week, and it s…

Have a ton of respect for the AI SDK team. Initially we only used AI SDK model routing, but now we also have our own built-in model routing as well.

I see each of us having different architectures. AI SDK is more low-level, and Mastra is more integrated with storage powering our studio, evals, memory, workflow suspend/resume etc.

Re: Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs

#35
I worked with Mastra for three months and it is awesome. Thank you for making a great product.

One thing to consider is that it felt clunky working with workflows and branching logic with non LLM agents. I have a strong preference for using rules based logic and heuristics first. That way, if I do need to bring in the big gun LLM models, I already have the context engineering solved. To me, an agent means anything with agency. After a couple weeks of frustration, I started using my own custom branching workflows.

One reason to use rules, they are free and 10,000x faster, with an LLM agent fallback if validation rules were not passing. Instead of running an LLM agent to solve a problem every single time, I can have the LLM write the rules once. The whole thing got messy.

Otherwise, Mastra is best in class for working with TypeScript.

Re: Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs

#36

I worked with Mastra for three months and it is awesome. Thank you for making a great product. One thing to consider is that it felt clunky working with workflows and branching logic with non LLM agents. I have a strong preference for using rules based logic and heuristics first. That way, if I do need to bring in the big gun LLM models, I already have the context engineering solved. To me, an agent means anything wi…

Thank you for using us, and for the feedback!

Do you have code snippets you can share about how you wanted to write the rules? Want to understand desired grammar / syntax better.

Re: Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs

#37
post #33
post #27

Earlier quoted context omitted.

We've always supported letting folks specify their agent hierarchy, eg agent supervisor, workflow orchestrator, mix and match, etc. But people kept asking us for a multi-agent primitive out of the box so we shipped `agent.network()`, which is basically dynamic hierarchy decided at runtime, pass in an array of workflows and agents to the routing agent and let it decide what to do, how long to execute for, etc! https:/…

ty! btw your docs search is broken, as i tweeted to Ward.

ah crap, thanks for heads-up. looking into it.
Post reply on HN