search

i-am-bee / bee-ui

Web application (UI) for Bee Stack.
Apache License 2.0
37 stars 5 forks source link

Exposing custom Bee Agents and Tools to the UI #85

Open nneubacher opened 1 week ago

nneubacher commented 1 week ago

Description

It would be great to leverage the UI built here for custom agentic flows. As of my understanding, while the bee-ui requires to be connected to a bee-api instance, it is not possible to expose custom code to the UI. Further, the integration of assets like the one found in the /examples/agents/ directory of the framework repo into a bee-api instance is complicated, or rather requires fully rewriting the application. Developers using the framework would be able to increase the visibility of their agent apps hugely and profit from the existing features of bee-ui.

For our specific case, the desired and optimal feature would allow users to follow the agents "chain of thought" just like the chain of tool calls shown in this picture.

Open questions

Additional context

For specifics on our application, please take a look at the repo and if you like, give it a try. We appreciate your feedback!

mmurad2 commented 3 days ago

Related ticket (internal) @matoushavlena

geneknit commented 1 day ago

Thanks you so much for this this @nneubacher. A "bring your own agent" feature is absolutely on our radar.

Today the bee-api module is rather opinionated and was built specifically to serve the bee-ui layer we developed for a general purpose Bee Assistant that followed a ReAct (or ReWoo) architecture. But from early feedback, it's clear there could be a lot more value here by enabling the top of the stack (API and GUI) to expose a diversity of agent architectures created further down the stack at the agent architecture layer. We want the Bee to serve as a unifying home for rapid innovation in agent architecture happening as developers tackle various use cases and are working to architect a scalable way to achieve this. cc: @ismaelfaro

Re:

How can we help?

Would love to follow up to get even more details on the use case you're tackling, the architecture you are using to solve it (what's the shape of the custom agentic flow you have built), where you are seeing value in bee today for creating it (what works), and your main friction points (what needs to change!) for adopting it. I realize you've enunciated a lot of this in the ticket, but digging a bit deeper. I set up some time to connect.