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
{{ message }}
This repository was archived by the owner on Apr 20, 2026. It is now read-only.
it felt more honest to prove one tiny handoff than to talk about a big adapter
CrewAI already has a real event surface, so sample-first seemed like the right move
it keeps the observed vs derived boundary very explicit
I am not assuming this belongs in crewAI-examples as-is.
The real question is smaller:
would you be open to a trimmed version of this as an example or integration pattern here, or is there another repo / event surface you would consider the better home for it?
Happy to reshape it if there is a more natural CrewAI-native way to present the same idea.
I wanted to share a small CrewAI-focused sample we just cut on the Assay side.
Instead of opening with a broad integration pitch, we started from CrewAI's local event-listener seam and kept the whole thing intentionally small:
BaseEventListenerexportSample:
A couple of reasons we cut it this way:
I am not assuming this belongs in
crewAI-examplesas-is.The real question is smaller:
would you be open to a trimmed version of this as an example or integration pattern here, or is there another repo / event surface you would consider the better home for it?
Happy to reshape it if there is a more natural CrewAI-native way to present the same idea.