# Agent Storage: files your agents keep between runs > Agent Storage gives each Nebula agent its own persistent files. Learn how agents keep notes, state and reports between runs and move files to any device. Source: https://docs.nebula.gg/docs/workspace/agent-storage Last updated: 2026-11-09 Agents you create in Nebula each have their own Agent Storage: a persistent set of files that survives across runs, threads and devices. Ask an agent to keep something for next time, such as notes, state between scheduled runs or a generated report, and it saves it there and finds it again later. **[Download Nebula](https://nebula.gg/download)**. Free account first: you sign up on nebula.gg, then the download starts. Desktop for Mac, Windows and Linux, the iPhone, iPad and Android apps, and the CLI. > **You:** @Market Analyst, keep each week's competitor pricing table so you can tell me what changed next Monday. > > **Market Analyst:** Saved this week's table as pricing/2026-10-26.csv in my storage. Next Monday I'll compare the new prices against it and list every change. ## What agents keep in storage Storage belongs to the agent, not to a channel or a device. Whatever channel runs the agent and whichever device it works on, it opens the same files. Nothing else in Nebula writes to them. | Keep | Example | | ---------------------------- | ---------------------------------------------------------------------- | | Working notes | What a research agent has already checked, so it doesn't repeat itself | | State between scheduled runs | The last invoice number a weekly job processed | | Generated reports | Each month's summary, kept so the next one can compare | | Caches and datasets | A cleaned customer list it reuses instead of rebuilding | Agents are told to keep it findable: a short `README.md` at the top saying what each folder holds, files grouped by purpose (`state/`, `reports/`, `cache/`), and anything stale deleted. ## Everyone who runs an agent shares its files An agent's storage isn't split per person. Everyone who can run the agent reads and writes the same files, so anything you ask it to keep, the other people who use it can read and change through it. > **Warning:** Don't ask an agent to store passwords, tokens or one person's private details unless everyone who uses that agent should have them. Keep account access in [Connections](https://docs.nebula.gg/docs/workspace/connections) and sign-ins in a [password manager](https://docs.nebula.gg/docs/workspace/password-managers). ## How an agent reaches its storage Each agent comes with the **agent-storage** skill, which tells it when and how to use its storage. You don't need to set anything up. The agent picks one of two ways in, depending on the file. **Storage tools:** For small text files up to 256 KiB, such as notes, JSON state or Markdown. In a task's activity log these show as **List Stored Files**, **Read Stored File**, **Store File** and **Delete Stored File**. Storing a file replaces the whole file at that path. **nebula-storage on a device:** For binary or large files, up to 100 MiB each, and files the agent makes or uses on a [device](https://docs.nebula.gg/docs/channels/devices). The agent installs the small `nebula-storage` command-line tool on the device it's working on (it needs only Python 3), then moves files in and out: ```bash nebula-storage ls [PREFIX] # list stored files nebula-storage get PATH [DEST|-] # download a stored file nebula-storage put SRC|- PATH # upload a file, replacing PATH nebula-storage rm PATH # delete a stored file ``` It works only inside commands the agent runs. A terminal you open on the same device can't use it. Paths are relative to the agent's storage, separated by `/`, like `reports/2026-10.csv`. ## Ask an agent to use its storage Mention storage when you want something kept, or ask the agent what it already has. For example: - "Save the cleaned lead list to your storage so tomorrow's run starts from it." - "What's in your storage? Delete anything older than this quarter." - "Put the exported dashboard PDF from the device into your storage as reports/october.pdf." ## Common questions **Which agents have Agent Storage?** The agents you create in Nebula. [App agents](https://docs.nebula.gg/docs/computer-use/app-agents) and [website agents](https://docs.nebula.gg/docs/channels/agents#website-agents) each have one fixed job and only the tool for it, so they don't. Coding agents such as Claude Code and Codex run on their own runtime and don't use it either. **Can I browse an agent's files in the app?** On desktop, yes. Open the agent's page and, under **Files**, click **View files** to preview, download or delete what it stored. Everyone who can run the agent sees the same files and can delete them. The mobile app has no such screen yet, so there ask the agent to list its storage, read a file back to you, or copy one onto a device you can open. **Does storage follow the agent to other channels and devices?** Yes. The files belong to the agent within your workspace, so it reaches the same storage from every channel it works in and from any device it runs commands on. **What happens to the files when an agent is deleted?** They're deleted with it. Taking an agent off a channel's team keeps the agent, so its storage stays too. See [Delete an agent](https://docs.nebula.gg/docs/channels/agents#delete-an-agent). **Can I use nebula-storage from my own terminal?** No. It signs in with credentials Nebula gives the agent's own commands, and those never reach a terminal a person opens. Ask the agent to move the file instead. > **Note:** Unsure what an agent has kept? Ask it, or ask Nebula. For anything else, email . ## Related - [Agents and your channel's team](https://docs.nebula.gg/docs/channels/agents): Create agents and see what they've learned. - [Skills and slash commands](https://docs.nebula.gg/docs/workspace/skills): Reusable procedures your agents follow. - [Devices](https://docs.nebula.gg/docs/channels/devices): Where agents run commands and work with files. - [Tasks](https://docs.nebula.gg/docs/channels/tasks): Scheduled work that picks up where it left off.