Ok this is actually genius.
Let’s say I wanted an agent in my dashboard to have the same permissions as a user.
Well, it would look a lot like this!! Heavenly DX.
Better Agent v0.2 beta is finally out 🚀
This release includes:
- Native AG-UI event streaming
- AI SDK providers support
- Auth-aware agents
- Memory
- Storage adapters: Drizzle, Prisma, Redis, and more
- A bunch of improvements
better-agent.com/changelog
@vinpac_io@sseraphini Persistence is storage-agnostic. Better Agent gives you interfaces plus a memory store for debugging or simple in-memory apps. For Postgres, you implement the interfaces on your schema. It’s optional and flexible and we’re working to make it better:
better-agent.com/docs/concepts/…
@probiruk@sseraphini How does persistence in Postgres happen? I mean does it apply migrations on its own?
How hard is it to create a custom persistence ?
@deshiou0604 yeah, that’s big part of it. Better Agent treats state as explicit persistence for conversation history, stream resumption, and active-run state. It’s optional, and the contracts are small enough that you can plug into your own DB, extend them, or fully customize the setup.
@liran_tal Better Agent treats agents, plugins, providers, and persistence as one typed system from server to client. Rate limits and other reusable runtime behavior are packaged as plugins, durable runs are built in, and it works with your existing stack.
@PsudoMike Yeah, composability happens more at the orchestration level where agents combine into a better agent.
It mainly focuses on how agents, plugins, providers, persistence, and other runtime pieces fit together cleanly as one system, with end-to-end type safety from server to client.
@probiruk What's the key differentiator from LangChain.js or Mastra here? Curious whether the composability is at the tool binding layer or closer to the orchestration level where agents get composed into betterAgent.