Disk and files
How a Workspace's files and the account disk work: the disk pool, the files panel, what persists between runs, and buying more space.
A plori Workspace keeps a project's files. Files that a run saves are there next week,
in the next conversation, without you doing anything. The agent works on them with a
shell under /workspace, and Plori saves versions of them.
One account disk, shared by your Workspaces
Your account has one disk, and all your Workspaces draw from it. Its size 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 $0.10 per GB per month from your dashboard, on any plan. It is billed daily from your balance, prorated. Drop it anytime and the charge stops.
The account disk is a hard cap. When your Workspace 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?
Only the Workspace files persist. An agent that built you a report keeps the report, its notes, and the repositories it cloned into the Workspace. The next conversation starts from the Workspace's current saved files. Software that a run installs outside the Workspace files is not there in the next run. A process that a run starts does not continue either.
A completed run is not proof that its files are saved. See Workspaces for saves and recovery. Deleting a Workspace erases its files and history in a background cleanup.
The files panel
Open Files in a Workspace conversation to browse its directories and preview supported files. You can download any file, including files without a preview.
To delete a file, open the ⋯ menu beside its name and select Delete. Select OK in the browser confirmation dialog. The file moves to the trash. Select Undo in the “Deleted” message that follows to restore it. The menu is available on file rows, but not directories. Viewers cannot delete files.
Files in the trash still count toward your disk usage. To remove them, select
Empty trash above the file tree, beside /, and confirm with OK. Older
saved versions can still use space until they are removed. You cannot delete files
or empty the trash while a run uses the Workspace files.
You can also publish a directory as a website at your-name.plori.site. See
Publish a site.
Use the paperclip beside the message box to attach PDFs, images, text, or code.
Sending the message starts an agent run and saves the attachments under
.plori/attachments, with names based on their contents. See
attachment types and filenames.
For other file types or a path you choose, use
uploads over MCP.
Ask the agent in chat to edit files.
Attach a PDF in chat
Use the paperclip in an agent conversation to attach a PDF and ask questions about it. The file is stored with the Workspace files, so you can refresh the page or ask a follow-up without uploading it again. The agent can inspect selected text, tables, charts, and scanned pages.
Files and chat serve different purposes. In Files, PDFs are download-only and never open as an inline preview. In chat, the agent reads the attached document with a restricted local tool. The original PDF is not copied into the conversation or published at a public URL.
Why saved files matter
A repository or report saved in the Workspace remains available in a later conversation. Save intermediate results there if another task will need them. File persistence does not preserve a running process or its RAM. See what persists between tasks for the difference between saved files, memory notes, and process state.
Related
- Pricing and the disk cost estimator
- Agent memory, the other thing that survives between conversations
- Workspaces, saved versions and several agents at once
- How we store AI agent files, the storage design behind Workspaces
- Workspace save time, measured on production: how long saving a Workspace takes by size, and disk throughput inside the VM