Persistent files & workspace
How an agent keeps source files, scripts, and results across conversations.
uploads downloads attachments artifacts filesOn this page
A filesystem that lasts beyond a chatInputs, scripts, and resultsAttach and inspect filesWorking files and business storageScope and lifecycleA filesystem that lasts beyond a chat
Each agent has its own persistent workspace. It can keep uploaded inputs, scripts, working notes, and generated files there, then use them again in another conversation with the same agent. Ordinary runtime restarts use the same workspace rather than starting with an empty directory.
A new conversation does not erase those files. It also does not automatically read all of them. Give the agent the filename or ask it to find the saved material when you want to continue earlier work.
Inputs, scripts, and results
The agent can read and write files and run code against them. It commonly uses workspace locations such as uploads/ for inputs, artifacts/ for results, and .tmp/ for scratch work. Exact filenames come from the task and its tools.
Use the source spreadsheet and comparison script we saved last week. Run the same checks on this new file and save this week's report separately.
Ask it to keep a reusable script when a task involves repeatable transformations or checks. A saved script gives a later run a concrete starting point; Code & scripts explains the execution environment.
Attach and inspect files
Attach a file to your message and explain which sheet, pages, columns, or records matter. Open the agent's Files area to browse its workspace. Results can also appear as file links in the conversation.
Open the actual output and check its values, formulas, and layout. If a tool fails, a message promising a file is not enough: ask for the saved result and verify it opens.
Working files and business storage
| Location | Use it for |
|---|---|
| Agent workspace | Source material, scripts, intermediate work, and artifacts for that agent |
| Workspace storage | Stored files and attachments referenced by business records |
| An installed app | Documents or records that need the app's organization, sharing, and workflow |
Keeping a file in an agent workspace does not publish it or make it a shared app record. Ask the agent to store the final file in the intended destination. The storage capability can move a file from the workspace into storage and fetch it back for later work.
When a recipient needs a link outside Opser, make that intent explicit. Supported sharing includes expiring links and public links that can be revoked. A public link is a separate sharing decision; do not confuse it with an ordinary in-app attachment.
Scope and lifecycle
The workspace belongs to the agent. Switching to a different agent means using a different filesystem. Shared-agent files belong to that shared workspace, so choose the agent with the intended team audience.
Persistence is not a backup policy. Files you delete are no longer available, scratch work should not be your only copy of an important result, and deleting an agent can remove its workspace. Store important deliverables in the appropriate business location before removing an agent. Storage allowances also apply to ongoing work.