Disk and files
How a plori agent's persistent disk works: the account disk pool, the files panel, what persists between sessions, and buying more space.
Every plori agent works on a real, persistent disk. Files it writes today are there next week, in the next conversation, without you doing anything. This page explains the disk model and the files panel.
One account disk, shared by your agents
Your account has one disk pool, and all your agents draw from it. The pool is your plan's included disk plus any extra you have bought:
| Plan | Included disk |
|---|---|
| Free | 1 GB |
| Pro | 20 GB |
| Power | 50 GB |
Disk within your plan is free, including while agents sleep. Need more? Buy extra by the gigabyte at 10 credits per GB per month from your dashboard, on any plan. It is billed from your credits a little each day, prorated, for as long as you keep it. Drop back down anytime and the charge stops.
The account disk is a hard cap. When your agents' files reach it, further writes stop, like any full disk, rather than running up a surprise bill. Free up space or buy more and they continue.
What persists between sessions
Everything on the disk. An agent that built you a report keeps the report, its notes, any repos it cloned, and any tools it installed for the job. When the agent wakes for the next conversation it opens the same disk. Deleting an agent permanently erases its files.
The files panel
Each agent's dashboard page has a Files panel where you can work with its disk directly:
- Browse the agent's directories.
- Open and edit text files in a built-in code editor. Saves are conflict-safe: if the agent changed the file while you had it open, you choose whether to reload, keep your version as a download, or overwrite.
- Upload files to the agent's disk, so you can hand it a spreadsheet or a codebase to work on.
- Download any file. Binary and oversized files are download-only.
Browsing never wakes a sleeping agent by itself; if the disk is asleep the panel offers to wake it. To delete files, ask the agent in chat, the same way you would ask a colleague to clean up a directory.
Why a real disk matters
Most agent sandboxes are ephemeral: the filesystem vanishes when the session ends, so every task starts from zero. A persistent disk changes what you can delegate. You can leave a half-finished job overnight, keep a growing dataset or codebase with the agent that owns it, and treat "ask the agent to open last week's file" as a normal thing to say.
Related
- Pricing and the disk cost estimator
- Agent memory, the other thing that survives between conversations