You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tracing between javascript and Python languages will be unified. In the python version of bee-hive, the emitter principle is already used. TODO: It will be necessary to provide the same trace interface -> so that the same thing is sent in both languages.
@tomas.dvorak
Single-agent support = We will use external frameworks (CrewAI, Atogen, AWS labs) and for each framework, we will need to make a "wrapper" that will compile events compatible with our framework from the internal emitter/log. For some frameworks, this will not even work, for example in AWS labs. => It will not work for those that do not support the emitter pattern (there will be more of these).
In terms of compatibility of basic events, we will be able to provide most event names, but not data. So we will not be able to select specific data, such as rawPrompt now (an internal thing)
MULTI agent
for support in the framework for "multi-agent systems" we will only support input/output in the first version. (for example -> now I started agent xx from crewUI, and now agent xx from crewAI has finished).
"multi-agent approach" => We will support both (agent/workflow). This means that for example in aws-lab we can export a single agent and then use it within the workflow in bee, but we can also export the entire orchestration (multi-agent) and then use it in our bee. So we will have to provide instrumentation at both levels.
How to implement our observability to external tools/frameworks like:
multi-agent-system:
Call
bee-agent-framework + observabilita
SINGLE agent
@tomas.dvorak
MULTI agent
Autogen
AUTOGEN ANALYSIS 👁
Aws labs
Multi-Agent (awslabs) ANALYSIS
The text was updated successfully, but these errors were encountered: