Challenge 3: Sticky Notes

Challenge 3: Sticky Notes

Previous Challenge Next Challenge

Introduction

Meaningful, multi-turn conversations require agents to understand context. Just like humans, they need to recall the conversation history: what’s been said and done to maintain continuity and avoid repetition. The Agent Development Kit (ADK) provides structured ways to manage this context through Session, State, and (Long Term) Memory.

In this challenge we’ll focus on the session state. Within each Session (our conversation thread), the state attribute acts like the agent’s dedicated scratchpad for that specific interaction. While session events hold the full history, session state is where the agent stores and updates dynamic details needed during the conversation.

Description

Modify the resource_scanner_agent to save the list of all virtual machines in the session state. The list should adhere to the output schema VMInstanceList and should be stored in the session state under the name resources.

Success Criteria

• The Agent has been configured to store the list of virtual machines in the session state.
• The session state contains the same set of virtual machines using the correct schema when prompted to list the resources.
• The changes have been pushed to the remote Git repository.

Learning Resources

• Session state in ADK
• Updating state
• Output schemas

Tips

• You can use adk web UI to inspect the session state (and to verify that everything works as expected).

Previous Challenge Next Challenge