Where your agents keep their work
Agent storage is now a product you can set up. Before you use it, decide what your agents keep between runs, who can change it and when it is deleted.
Abhijit Chatterjee Chattopadhyay

On 15 October, Vercel made Drives generally available. In its words: "We built Vercel Drives to keep an agent's files independent of its execution environment."
That is from Vercel's post introducing Drives (opens in a new tab). The detail matters less than the direction. Where an agent keeps its work is now something you choose and set up, not something that happens by accident.
Two kinds of agent state
Most agents run in a temporary environment that is thrown away when the run ends. That is fine for the tools and the scratch work. It is not fine for the work itself: the files, the notes, the half-finished report. If those live in the environment, they go when it goes, and the next run starts from nothing.
In Vercel's example, the line is simple: "everything under /workspace persists on the drive. Everything else belongs to the sandbox." Whatever tools you use, your agents need the same line. Some things are kept. Everything else is thrown away.
Three decisions before an agent keeps anything
- What it keeps. Its working files and its notes on the task. Not secrets, and not customer data it only needed for one step. Anything kept is something you now have to protect.
- Who can read it and who can change it. Vercel lets other agents mount read-only copies, and lets agents fork a drive to work in parallel. Forks do not merge back into the original. So decide in advance whose changes count, and who copies a good result back. I wrote about checking what an agent can reach, and stored work belongs on that list.
- When it is deleted, and by whom. Storage that outlives the run also outlives the reason for it. Give each store an owner and a rule for when it goes.
Do this today
- Pick one agent and write down what it keeps between runs, and where.
- Check whether any of it is a secret or customer data that did not need to be kept.
- Give that storage a named owner and a date or rule for deleting it.
Your next step
I write one practical note like this every day. Sign up just below to get them by email.
Drafted with AI help, edited and approved by me.