Workspace files

Every workspace has a file store with folders. It holds what users sent, what workflows generated, and what you uploaded by hand on the Files tab.

Nodes

• file_read — read a file;
• file_write — write a file;
• file_glob — find files by pattern;
• file_tool — the same operations as an agent tool.

Where they actually go is decided by the store node wired into them: the workspace store, a local directory, or WebDAV. The same graph therefore works against the built-in store and against someone else’s disk — only the attached node changes.

References, not bytes

Files travel through the graph as filestore://… references, not as content. The reason is plain: a ten-megabyte image placed in a node’s output would go into the database, into the SSE stream and into the chat history — one copy per step.

The reference is resolved to bytes where bytes are genuinely needed: sending to a model, attaching to a message, writing into another store. From your side it looks like an ordinary file being passed between nodes.

Quota

Space is counted per owner, not per workspace: extra workspaces do not add room. There is also a separate cap on a single upload. Both are in the plan limits.

What next

• The Files tab — working with the store by hand.
• Knowledge bases — when the file is needed for search, not as a whole.