Separate session for each agent in a multi-agent design

[naitik-parekh]

Problem definition
I have designed a multi-agent system where some agents are transactional and others are informational. Transactional agents do not need to retain context once a transaction is complete, whereas informational agents need to retain longer context to provide a better user experience. In my design, I clear the session once a transaction is completed, which clears the context for all agents. However, if I choose not to clear the session in order to enhance the performance of informational agents, the transactional agents may become confused by the context from previous transactions.

Desired solution

1. Is there a way to clear the context of selected agents? If yes, how to implement it?
2. Is there a way to manage separate sessions for each agent under one root agent? If yes, how to implement it?

Additional context
I am using google-adk 1.2.1

[Thongnguyentam]

did you try to ParallelAgent from google.adk.agents to create child session for transactional agents, then run transactional agents in isolated session. And finally, use context.session_service.delete_session(), to delete that session?

Is this what you meant, or do you need to delete the prior whole chat session?

[naitik-parekh]

I have not tried ParallelAgent as my use case does not need parallel execution of sub agents. Rather, only one of the sub agents should be invoked at a time.

Are you suggesting to use ParallelAgent because it facilitates creation of child session?

I do not want to deleted the whole chat session. I just want to clear the context of specific agent.

[naitik-parekh]

Is there a possible solution other than using PrallelAgent?

[klateefa]

Hi @naitik-parekh and thanks to everyone who participated in this thread.

We're currently doing some housekeeping on our issue tracker. Given the rapid pace of development and the number of updates since this was last active, there's a good chance this issue has been resolved in a newer version. To help us keep our backlog focused on current issues, we are closing this as stale.

If you're still facing this problem, could you please update to the very latest version of the library and confirm the issue still exists? If it does, please comment here, and we will be happy to reopen this issue and investigate further.

Thanks for your contribution and understanding!