Live data from Hacker News

Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

github.com

151–159 of 159 posts

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#151
post #53
post #39

I don’t really understand agents. I just don’t get why we need to pretend we have multiple personalities, especially when they’re all using the same model. Can anyone please give me a usecase, that couldn’t be solved with a single API call to a modern LLM (capable of multi-step planning/reasoning) and a proper prompt? Or is this really just about building the prompt, and giving the LLM closer guidance by splitting in…

https://aider.chat/2024/09/26/architect.html "Aider now has experimental support for using two models to complete each coding task: An Architect model is asked to describe how to solve the coding problem. An Editor model is given the Architect’s solution and asked to produce specific code editing instructions to apply those changes to existing source files. Splitting up “code reasoning” and “code editing” in this man…

Now next is to have a Senior Editor and Editor pair :)

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#153

Does Mastra support libraries of tools for agents like toolhouse.ai or https://github.com/transitive-bullshit/agentic

Agentic's tool library _should_ also work for Mastra via its AI SDK adapter. (We haven't tested this, so if you do try let us know if you see quirks!)

What about Toolhouse and/or composeio?

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#154

Earlier quoted context omitted.

What lock in? I use their AI SDK, but never touch vercel servers. It's just a unified interface.

The SDK is the lock in.

Same as any other open source framework or library.

Calling that "lock in" is a stretch, but you're free to write everything from scratch if that's the way you roll.

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#155

Earlier quoted context omitted.

I think the problem is that a 'fluent' chain of calls already expresses a sequence, so the way that 'after' resets the context to start a new branch feels very awkward ... like a GOTO or something It's telling that the example relies on arbitrary indentation (which a linter will get rid of) to have some hope of comprehending it Possibly this was all motivated by a desire to avoid nested structures above all? But for…

You’re right that the syntax was inspired by the desire to avoid nested structures. But the syntax here is interesting as well and fairly readable. Worth thinking about!

that example syntax is loosely based on CDK code for AWS Step Functions, since I had to write some recently

essentially you're building a DAG so it could be worth checking some other APIs which do a similar thing for inspiration

e.g. it looks like in Airflow you could write it as:

    chain(llm, decider, [agentOne, agentTwo], workflow)
https://airflow.apache.org/docs/apache-airflow/stable/core-c...

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#157

Earlier quoted context omitted.

Agentic's tool library _should_ also work for Mastra via its AI SDK adapter. (We haven't tested this, so if you do try let us know if you see quirks!)

What about Toolhouse and/or composeio?

in npm there's a mastra/composeio package that might work, they also seem to have some mcp support

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#158
post #30
post #27

This looks really nice. We've been considering developing something very similar in-house. Are you guys looking at supporting MLC Web LLM, or someother local models?

Yup! We rely on the AI SDK for model routing, and they have an Ollama provider, which will handle pretty much any local model.

can confirm this works well with any OpenAI like API endpoint, like ollama or LM studio's

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#159
post #119

The example from the landing page does not exactly spark joy: testWorkflow .step(llm) .then(decider) .then(agentOne) .then(workflow) .after(decider) .then(agentTwo) .then(workflow) .commit(); On a first glance, this looks like a very awkward way to represent the graph from the picture. And this is just a simple "workflow" (the structure of the graph does not depend on the results of the execution), not an agent.

Same frustration with frameworks like Langchain and Llama_Index let me to build a simple UI base Agentic freamwork that runs locally. https://github.com/ranjanprj/agentollama
Post reply on HN