What is InMemorySessionService in google-adk?

InMemorySessionService stores session state in process memory. It resets on restart, making it ideal for unit tests and local development without a persistent backend.

How should I verify a running-total accumulator?

Test with multiple recorded values and assert both the total and count are correct. Also assert the empty-state case — when nothing is recorded, the summary should return total 0 and count 0.

What should the summarize function return?

A dict with 'total' (sum of all recorded values) and 'count' (number of records). When nothing has been recorded, it returns {'total': 0, 'count': 0}.

Remembering the running summary

Your task

Build a helper that keeps a running summary of what it has processed so far. Each time you record a value, it folds into the summary; ask for the summary any time and it reflects everything recorded so far. Complete record_item and summarize. Note: uses google-adk session state. record_item(service, app_name, user_id, session_id, value) records one processed value. summarize(service, app_name, user_id, session_id) returns the running summary {"total": ..., "count": ...}, or {"total": 0, "count": 0} when nothing was recorded.

Ground rules

•use google-adk's InMemorySessionService for session management.
•summarize returns a dict with "total" and "count".

Not required

•the actual domain action (confirming a booking, charging payment).
•persistent session services such as a database.

▶About this challenge

This challenge asks you to complete two helper functions that keep a running summary (total and count) across conversation turns using google-adk session state. The helper relies on InMemorySessionService and must correctly reflect every recorded value in the summary at any point, including the empty-state boundary condition.

Uses google-adk session state to keep a running total and count across a conversation. A google-adk agent holds a session per conversation, and values that must persist between turns are stored in session state. The habit that matters is verifying it on the boundary cases — nothing recorded yet, one value, several values — not just the single-value happy path.

What is InMemorySessionService in google-adk?: InMemorySessionService stores session state in process memory. It resets on restart, making it ideal for unit tests and local development without a persistent backend.
How should I verify a running-total accumulator?: Test with multiple recorded values and assert both the total and count are correct. Also assert the empty-state case — when nothing is recorded, the summary should return total 0 and count 0.
What should the summarize function return?: A dict with 'total' (sum of all recorded values) and 'count' (number of records). When nothing has been recorded, it returns {'total': 0, 'count': 0}.

Remembering the running summary

Your task

Ground rules

•use google-adk's InMemorySessionService for session management.
•summarize returns a dict with "total" and "count".

Not required

•the actual domain action (confirming a booking, charging payment).
•persistent session services such as a database.

▶About this challenge

What is InMemorySessionService in google-adk?: InMemorySessionService stores session state in process memory. It resets on restart, making it ideal for unit tests and local development without a persistent backend.
How should I verify a running-total accumulator?: Test with multiple recorded values and assert both the total and count are correct. Also assert the empty-state case — when nothing is recorded, the summary should return total 0 and count 0.
What should the summarize function return?: A dict with 'total' (sum of all recorded values) and 'count' (number of records). When nothing has been recorded, it returns {'total': 0, 'count': 0}.