Hi team,
Do we have support for event trigger handling. Basically, if some external event is triggered, then our agent should respond to it i.e event listening and subscribing feature just like CrewAI.
@monalisha @Monali could you guys assist me with this please ?
Hey @MahorShekhar,
Just wanted to say how lovely it is to see you actively exploring our product and engaging with the community — we really appreciate it! 
At the moment, we’re a bit swamped with support requests, but I’ve shared your message with the team. We’re working through each one carefully and will get back to you as soon as we can.
Thanks so much for your patience and for being part of the journey with us 
@Dirk Could I please request you to respond to this one. Seems this ticket of mine got pushed down in the queue 
Let me reiterate what I meant. I’m looking something like Google ADK’s Long Running Function Tool. But this solves only one part of my request.
Let me explain the requirement - Suppose our team has made a tool call. But that tool call involves submitting a asynchronous request to some third party tool whose response will be received 2 days later. Upon receiving the response later, there should be some capability to inject the response received in history or tool call response, whatever you see right.
Could you please share if Agno has this functionality already in the place or it is in framwork’s future plan ?
Hey @MahorShekhar — thanks for the detailed note.
What you’re describing is a more advanced Human-in-the-Loop pattern, We don’t support it yet, but it’s definitely on our radar.
Appreciate you pushing the edge here. Keep the ideas coming.
Hi @MahorShekhar
Really interesting idea.
This is not something we support right now, but we are actively working on human-in-the-loop features. In this case I would imagine the 2-day request to be kicked off with a normal function that is non-blocking. We should have the ability for this function call then to exit straight after without the model responding (we already have this functionality on our @tool decorator). The crucial missing part then is to “continue” this run at a later stage by simply adding that result to the message history and continuing the run.
This is really cool and we will work on enabling this.