calcsam

7 ms·

31.
Mastra is now Apache 2.0 licensed(mastra.ai)
2 points by calcsam 1y ago|0 comments
32.
by calcsam 1y ago
interesting idea, this benchmark maps fairly closely to the types of output I typically ask LLMs to generate for me day-to-day
33.
Mastra is now Apache 2.0 licensed(mastra.ai)
1 points by calcsam 1y ago|0 comments
34.
by calcsam 2y ago
We have a ticket to allow this actually!
35.
by calcsam 2y ago
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!
36.
by calcsam 2y ago
awesome! let us know how it goes
37.
by calcsam 2y ago
1. what are you wanting to create? currently agents and workflow endpoints are created at `/api/workflows/workflow-id` and `/api/agents/agent-id/` for workers and agents 2. we are thinking about it -- curi
38.
by calcsam 2y ago
https://www.artifact.engineer/
39.
by calcsam 2y ago
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!)
40.
by calcsam 2y ago
Thanks! The conditional `when` clauses live on the steps, rather than being represented in the workflow, and in fact when we built this for an example, the last step being called depended on the results of the previous two steps. How would
41.
by calcsam 2y ago
Some people don't like frameworks. Some people do. We have a little bit of experience building frameworks, so we figured we'd build a good one.
42.
by calcsam 2y ago
thanks!!
43.
by calcsam 2y ago
thank you!
44.
by calcsam 2y ago
let us know what you think!
45.
by calcsam 2y ago
If you watch the demo video you will see the cloud platform we are building at the end. Right now it’s in beta.
46.
by calcsam 2y ago
thank you!
47.
by calcsam 2y ago
It’s not. It’s on top of AI SDK, which is a popular open source library maintained by Vercel.
48.
by calcsam 2y ago
I mentioned that in the comment. We’re using Elastic v2 for now because we want users to be able to do anything with us, but protect from eg AWS
49.
by calcsam 2y ago
Not planning on it — we think frameworks should be single-language
50.
by calcsam 2y ago
I could be wrong but don't think OpenAI wants to be opinionated about that, except maybe the OpenAI solutions engineers :)
51.
by calcsam 2y ago
Yup! We rely on the AI SDK for model routing, and they have an Ollama provider, which will handle pretty much any local model.
52.
by calcsam 2y ago
100% and agree with this, we saw the langmem stuff last night imho getting some sort of hierarchical memory is conceptually fairly straightforward, the tricky part is having the storage and vector db pieces well integrated so that the apis
53.
by calcsam 2y ago
demo: https://x.com/calcsam/status/1889856384549982419
54.
by calcsam 2y ago
We're just starting to do that and have a few TTS providers: ElevenLabs, OpenAI, PlayAI. We hear a lot from people who are outgrowing the voice agent platforms and moving to something like pipecat (in Python), and we'd love to be
55.
by calcsam 2y ago
that's awesome!
56.
by calcsam 2y ago
Yeah, this is something we've heard as well. No particular feature right now but we did ship an agent in local dev to help people improve their prompts.
57.
by calcsam 2y ago
Kyle started the project, I started helping pretty shortly thereafter, then he and I cofounded the company together. Kyle's working on ElectricSQL now but is using us, we're doing a meetup together next month, etc.
58.
by calcsam 2y ago
lol thanks
59.
by calcsam 2y ago
that's great to hear!!
60.
by calcsam 2y ago
We originally were wrapping AI SDK, but that confused people who wanted to use both, so we decided to make the API more explicit, eg: import { Agent } from "@mastra/core/agent"; import { openai } from "@ai-sdk/

More ›