Editorial illustration for Google open-sources Always On Memory Agent, using SQLite over vector DBs
Google's Always On Memory Agent Redefines AI Data
Google open-sources Always On Memory Agent, using SQLite over vector DBs
Google just released an agent with no vector database. None. Its memory is a single SQLite file and the model's own decisions.
The Always On Memory Agent swallows files and API calls, writes structured entries to that local database, and tidies everything up every thirty minutes. The design is aggressively simple. It suggests most of the infrastructure we bolt onto large language models is optional.
For anyone building AI assistants, this is either a revelation or a provocation. The standard approach involves embedding pipelines, vector storage, indexing layers, and sync logic. It's a sprawling, expensive stack.
Google's engineer Shreyas Saboo cut it all out. His agent uses the model to read, think about, and directly write its own memory. You get a local HTTP API and a Streamlit dashboard for viewing it.
The system handles text, images, audio, video, and PDFs.
Google senior AI product manager Shubham Saboo has turned one of the thorniest problems in agent design into an open-source engineering exercise: persistent memory.
This flips the script. The model becomes the librarian, not just the book. It decides what's important and how to find it later.
The appeal is obvious for prototypes. You skip the infrastructure hell. The cost is control.
You exchange the predictable, if heavy, mechanics of vector search for the opaque reasoning of a language model. Latency shifts from database queries to model calls. Stability depends on the model not inventing memories during its half-hourly clean-ups.
It works until it doesn't. That's the trade. For small, persistent desktop agents, this is a clean solution.
For large-scale production systems, it introduces a new kind of risk. The project doesn't solve the problem of AI memory. It just offers a radically different answer.
The answer is on your local machine, updating every thirty minutes, and asking how much you really trust the model in charge.
Common Questions Answered
How does the Always On Memory Agent differ from traditional vector database approaches?
The Always On Memory Agent uniquely uses SQLite for data storage instead of a dedicated vector database, prioritizing simplicity and direct data ingestion. This approach allows for continuous memory capture and consolidation every 30 minutes, without the complexity of traditional retrieval stacks.
What types of data can the Always On Memory Agent ingest and store?
The agent supports multi-modal data ingestion, including text, image, audio, video, and PDF files. It can pull these files or API payloads directly into a SQLite storage system, creating a flexible and comprehensive memory management solution.
What are the key technical components of Google's Always On Memory Agent?
The agent is built with the 2025 Agent Development Kit and Gemini 3.1 Flash-Lite, runs as a continuous background service, and includes a local HTTP API and Streamlit dashboard for memory inspection. It consolidates memories every 30 minutes by default and is released under an MIT open-source license.
Further Reading
- Papers with Code - Latest NLP Research — Papers with Code
- Hugging Face Daily Papers — Hugging Face
- ArXiv CS.CL (Computation and Language) — ArXiv