Important updates: Python Framework, Monorepo & Agent Interoperability 🚀

[mmurad2]

Hey BeeAI Community! 👋

We've been listening to your feedback and reflecting on our journey so far. As we continue evolving the BeeAI project, we are implementing key changes that enhance the developer experience and enable an open and interoperable agent ecosystem.

🔍 Learnings & Community Feedback

Over the past few months, we've seen incredible engagement from developers, researchers, and companies building with BeeAI. Some key takeaways from your feedback:

• Python lovers, we hear you! We were late to release a Python version of the framework. We now have an alpha release of the Python Framework. Bringing it to feature parity with Typescript is our top priority.
• Too many repos, too little time? We get it. Finding where to start has been tricky, so we're consolidating repos for a smoother experience.
• Agent architectures exist on a spectrum. There is no one-size-fits-all approach to multi-agent architectures. Whether you need high control or full autonomy, a good framework should accommodate any architecture that best serves your use case—so you can focus on building while we handle the complexity.
• GUIs matter! Developers need delightful ways to consume and interact with the agents they are building, for testing and sharing.

📦 Moving to a Framework Monorepo

To streamline your experience building agents with BeeAI framework, we consolidated our repositories into a single monorepo. This currently includes:

• The existing Typescript library for building agents.
• A Python-equivalent version of the Typescript library. We are working rapidly towards achieving full parity with Typescript capabilities.
• Observability capabilities.
• Documentation and examples for both Typescript and Python libraries.

What does this mean for you?

• ⚠️ Repo name change. bee-agent-framework has become beeai-framework. This is mainly to keep consistent naming across our core repos going forward.
• ⚠️ Some repositories will eventually be deprecated. We’ll provide a migration guide and clear communication on where everything will live going forward. For now, we will maintain bee-api, bee-ui, bee-stack, and bee-python-sdk until we achieve feature parity with our new architecture. We know many of you found the GUI valuable, so we’re rebuilding it from the ground up to support more agentic capabilities and simplify setup.
• More cohesive development. One repo = faster updates, better documentation, and stronger integrations.

⏭️ Our Next Focus: Agent Interoperability

Today, most agent implementations exist in silos, limiting their potential. We believe the future lies in seamless interoperability, where agents—regardless of framework, language, or runtime—can collaborate effectively. If we get this right, this will be a major step toward new human-agent interaction modalities and allow us to double-down on GUI components for serving agents.

What does this mean for you?

• We are developing standards and protocols to enable BeeAI agents to communicate with agents from other frameworks.
• More updates coming soon on how we plan to bridge agent ecosystems and innovate on the agent consumption experience.

📢 Public Roadmap

In the spirit of transparency and open development, we have created a public roadmap to give you better visibility into our upcoming releases and priorities.

🔗 Link

---

We’d love your feedback—drop your thoughts below! 💬

And thanks for being part of this journey! 🚀🐝

[u007]

would love to see jsr based typescript package, make it easier to explore source code directly from vs code itself. dislike the types that been made, hiding behind the scene code on github

[mmurad2]

Thanks for your input @u007 -- could you speak more to why jsr is preferrable to npm? supporting two packages is extra overhead for the team, so trying to gather some more inputs to make the case.

[u007]

Hi, sorry for the late reply, yes, i think alike python its better for the community to easily browse the code under the hood of beeai agent framework. right now it is showing only types, the compiled version. best regards, James Tan

…

On Tue, Feb 25, 2025 at 4:49 AM Maya Murad ***@***.***> wrote: Thanks for your input @u007 <https://github.com/u007> -- could you speak more to why jsr is preferrable to npm? supporting two packages is extra overhead for the team, so trying to gather some more inputs to make the case. — Reply to this email directly, view it on GitHub <https://github.com/orgs/i-am-bee/discussions/349#discussioncomment-12305440>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC65TN3G7AUCT53XSX2OGD2ROAVVAVCNFSM6AAAAABXQ4ELAOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZQGU2DIMA> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>