agent-platform-state

This skill should be used when deciding where data lives on Gemini Enterprise Agent Platform, across Agent Platform Sessions and Agent Platform Memory Bank: "how do I persist X", "does this survive a restart", "should I use Sessions or Memory Bank", "can agents share state across users", "how do I share memories across users", "why is my state empty in a new conversation", "what does app: or user: prefixed state do", "how do I list every memory in a scope", "why did my tool write to the wrong scope", "why is the console's Sessions page blank", "why is my agent's whole run one event", "which location does VertexAiSessionService take", or when a value written by a tool is missing on the next turn or the next instance. Names each managed service, gives its scope and lifetime, and maps it to the ADK client that binds to it. Use agent-platform-architecture for choosing a host or identity mode, agent-platform-a2a for auth failures.

Version

0.9.0