Drive & Memory
An agent's memory is just files — and they live in its Drive. Feed it your materials and it stops starting from zero: it remembers you, and gets more like you over time.
Most AI forgets you the moment a chat ends. No memory, no progress, no idea who you are — every conversation starts from zero. Buda's answer is simple: an agent's memory is just files, and those files live in its Drive. The more you put there, the less it starts over — and the more it works like you.
Memory is just files
There's nothing mystical about agent memory. Open any agent, click Drive, and you're looking at a real file system — its memory laid out as files and folders. Because it's plain files, your agent's memory is portable and yours: it isn't locked inside a model or a vendor. You can copy the whole working directory and take it with you.
That reframes the core skill of working with agents: managing memory is managing files. Get the files right and everything else follows.
The three layers of memory
Buda keeps memory in three layers, from fleeting to permanent:
| Layer | What it holds | Lifecycle |
|---|---|---|
| Session memory | the back-and-forth of the current job | Ephemeral — each new session starts fresh |
MEMORY.md | a compact index the agent skims before each task | Persists — the summary, not the whole story |
| Drive | the full archive: documents, past work, transcripts, notes, memory fragments | Durable and versioned |
The key insight is that MEMORY.md is not all of your agent's memory — it's the condensed table of contents. The real long-term memory is the body of files in Drive; MEMORY.md is what the agent reads first to know where to look. Think of Drive as the full archive and MEMORY.md as the highlight reel that points back into it.
How memory grows
- Tell it to remember. Say "remember this" and the agent writes a memory file — no fixed format, capture a moment whenever it's worth keeping.
- Feed it your materials. Pour in past articles, recordings and transcripts, a case library, prior projects. The more context an agent accumulates, the more its output sounds like yours.
- Shape who it is. A few standing files define the agent itself:
AGENTS.mdholds its role and rules;MEMORY.mdholds what it remembers about you and your work.
This is what "AI that evolves" actually means in Buda. The model doesn't change — the files improve. Clearer Drive materials, a sharper MEMORY.md, better rules in AGENTS.md, and reusable Skills are what turn a generic Claw into something that behaves like a seasoned teammate who knows your business.
Agent Drive vs Space Drive
- Agent Drive — private to one agent: its own memory and working files.
- Space Drive — shared across a Space, so multiple agents and people hand work off to each other.
Persistent and versioned
Drive persists across sessions and tasks — close everything, come back, and the files (the memory) are still there. Buda keeps file history so you can see how a document changed and recover earlier states, and snapshots let you capture a known-good point to return to.
What to keep in Drive
Policies and SOPs · brand guidelines · product specs and FAQs · contracts and templates · research notes and datasets · drafts and project briefs · generated assets and past work. When an agent answers, it opens the relevant files and grounds its reply in your documents — updating a file is often faster and more reliable than rewriting a prompt.
File hygiene
- Use clear, business-oriented folder and file names.
- Separate drafts from approved source-of-truth files.
- Prune outdated documents instead of letting them pile up — clean memory is good memory.