{}state button coming along with chats when running adk-web locally

[Heenasharma]

I ran my backend locally and connected the adk-web UI(which is also running locally), and I am able to query my backend using adk-web. Almost everytime, I am getting a button of {}state in that chat area.

[Harshk133]

This is expected behavior and a built-in feature of the Google Agent Development Kit (ADK) Dev UI, rather than an error.

In ADK, conversations are tracked via Sessions, which maintain two separate logs:

Events: The immutable chronological transcript of the conversation (user inputs, agent outputs, and tool calls).

State: A mutable, key-value scratchpad used by the agent to read/write structured context dynamically during execution (e.g., tracking current variables, session scopes, or user preferences like user:dietary_preferences).

Why is the button appearing?
When a tool function (like your call_db_agent) runs, it can interact with the session state via tool_context.state. Every time a state change occurs, ADK records it as a state_delta tied to that specific execution event.

The {} State button is provided in the local web console specifically for debugging and state inspection.

What it does: Clicking that button will expand a JSON-like view showing the exact snapshot of the session state variables or state_delta immediately after that specific tool call executed.

Production vs. Local Dev: Because adk-web is strictly a local developer environment meant for tracing under-the-hood LLM orchestration, it exposes these buttons to make debugging easier. This UI component will not appear to end-users in a production deployment.

If your backend is responding properly and your tool calls are successful, everything is working exactly as designed!