Your workflows don't just move data through, they often need a place to keep it: a file downloaded from an API, a database a step builds up over time, a report written on one run and read on the next. In Tines 3B, that place is storage, and the Browse storage view is your window into it.
Volumes are the unit of storage
Storage is made of volumes. A volume is a named, persistent folder that a step can mount into its sandbox. Once mounted, it appears at /storage/<name>, and anything a step writes there stays put: a volume persists across runs and across chat turns, so the next execution picks up right where the last one left off.
A step opts into a volume by declaring it in its code, and it can ask for a few different behaviors:
Read-only. A volume can be mounted so a step can read its contents but not change them, which is handy for sharing reference data without risk of overwriting it.
Run-scoped. Instead of persisting, a volume can be scoped to a single run, giving that run a clean scratch space. This option is only available in workflow steps.
Exclusive. A writable volume can require exclusive access, so only one execution writes to it at a time.
Learn how to pick the right storage for your workflow here.
When none of these are set, a volume is writable, shared, and tied to its branch, which is the common case.
How storage is organized
Volumes don't float free; they belong to something. Most belong to a space, and within a space they're organized by branch, so each branch of a workflow keeps its own set of files. That branch isolation means work in progress on one branch can't disturb the data your live version depends on.
Alongside space storage there's personal storage, tied to you rather than to a shared space. Files created by your personal chats and personal workflows live here, separate from anyone else's.
Browsing your storage
Browse storage opens a file browser you navigate column by column, drilling from a space into a branch, into a volume, and down through its folders to individual files. A breadcrumb across the top shows where you are. When you land on a file, you can see its size and when it was last changed, preview it in place, and download it. If a space has no stored files yet, the browser simply says so: files your workflows read and write will show up here once they exist.
Learn how to inspect your storage here.
Storage stays with your work
Because volumes persist and stay tied to their space and branch, storage behaves like a durable part of your workflow rather than a temporary side effect of a run. Tines 3B keeps track of how much space each of your spaces is using, so storage stays visible rather than growing silently in the background.