Agent - Connect query to invoke / query to get Logs

💬 Agents
1

Hi team,

Following up to these two threads: Agent chat credit issue - #2 by MiguelOrtiz and Passing context to AI Agents in Apps (similar to what is done in Cursor)

I kind of realized yesterday that the agent chat component is somehow designed to re-trigger the linked query until it gets the results.

I guess another way of approaching the challenge of passing context from apps to agents would be to enable the option to link 2 queries, one for invoke and for getLogs. As such, we could then manipulate the invoke query and pass in additional context from the apps.

I'm aware Kent already suggested this other solution, but just wanted to share my thoughts in case it helps.

3

Hi @MiguelOrtiz!

Interesting idea, it would make sense to better break up the logic of 'what' the LLM behind the agent should be trying to do and 'what' the agent has to work with to unterstand context and make decisions.

How are you imagining the breakdown of inputs/outputs for the 'invoke' query and the 'getLogs' query to look?

4

Hi @MiguelOrtiz,

Just wanted to close the loop on this as Kent answered the question how to pass additional params into an Agent query in this thread here.

Are you thinking we need additional support for getting logs from the agent's own run to be able to give the agent contextual understanding of why a query or tool it is invoking may not be working?