Skip to content
← Writing
Writing · October 2026 · 2 min read

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

The Logic Atelier logo above the words: Where your agents keep their work.

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

  1. 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.
  2. 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.
  3. 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.

New articles by email

I will never sell your details, for any reason, and I never send spam.

How I use your details
  • I, Abhijit Chatterjee Chattopadhyay of The Logic Atelier, hold them, in my own newsletter system hosted on Fly.io. Emails go out through Resend.
  • Your name is for greeting you, your email is for sending new articles, and your phone number, if you give it, is so I can reach you directly about my work.
  • If you do not confirm your email within 7 days, I delete the sign-up. If you unsubscribe, I delete your details 30 days later.
  • If Google Analytics is running on your visit, it is told that a sign-up was made, and nothing you typed.
  • To see or delete what I hold about you at any time, email hello@thelogicatelier.com.
  • The full detail is on the privacy page.
NextAn agent that works all day will be interrupted
← cd ../writing

Where your agents keep their work

agent-workspace.mdfront matter
title: Where your agents keep their work
date: 2026-10-28
reading_time: 2 min
author: Abhijit Chatterjee Chattopadhyay
agent_workspace_cover_29a89e01_5683aadd91.pngcover
The Logic Atelier logo above the words: Where your agents keep their work.

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

  1. 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.
  2. 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.
  3. 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.

subscribeemail

// I will never sell your details, for any reason, and I never send spam.

How I use your details
  • I, Abhijit Chatterjee Chattopadhyay of The Logic Atelier, hold them, in my own newsletter system hosted on Fly.io. Emails go out through Resend.
  • Your name is for greeting you, your email is for sending new articles, and your phone number, if you give it, is so I can reach you directly about my work.
  • If you do not confirm your email within 7 days, I delete the sign-up. If you unsubscribe, I delete your details 30 days later.
  • If Google Analytics is running on your visit, it is told that a sign-up was made, and nothing you typed.
  • To see or delete what I hold about you at any time, email hello@thelogicatelier.com.
  • The full detail is on the privacy page.

vi.Contact

06 · contact

Talk to me.

Talk to me.

Production AI and software architecture. Based in Dubai, working with teams in the Emirates and Ireland.

I work Dubai hours, Monday to Friday, the same week you do. Dubai is three hours ahead of Dublin in summer and four in winter, so my afternoon is your morning.

I will never sell your details, for any reason, and I never send spam.

How I use your enquiry
  • Your enquiry comes to me, Abhijit Chatterjee Chattopadhyay of The Logic Atelier. The form is handled by Formspree, which passes it to my inbox and keeps a copy in my Formspree account.
  • I use it to read your enquiry and reply. If no work follows, I delete it within 12 months, and sooner whenever you ask.
  • If Google Analytics is running on your visit, it is told that an enquiry was sent, and nothing you typed.
  • To see or delete what I hold about you, email hello@thelogicatelier.com.
  • The full detail is on the privacy page.