Menu

Your agent's session store is a database nobody designed. Audit the five gaps.
📰

Your agent's session store is a database nobody designed. Audit the five gaps.

DEV Community: security·Dekita·4 days ago
#lk1KbA1L
#devtosecurity#devto#dev#session#store
Reading 0:00
15s threshold

A developer deleted a session from a Google ADK Go agent. The framework returned no error. The session row was gone. The password the agent had read from a config file was still sitting in the events table, in plain text, attached to nothing.

That is not a hypothetical. It is the opening of a post by davideimola on dev.to (2026-11-11), with a public reproduction: no model, no API key, just the session service doing what its runner does after a tool call. You delete, it returns nil, the events survive. The interesting part is not the bug. It is what the bug is a symptom of.

Your agent's session store is a database. Nobody designed it as one, and your compliance obligations have already classified it as one.

A session is a database, whether you meant it or not

Frameworks made persistence convenient, and convenience made the storage invisible. In Genkit's Agents API, after every turn the session is replaced with the model's full history, including tool calls and, more importantly, tool responses.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.