Memories and Files

Memories and files are how work leaves an agent's head and becomes shared context. Memories are the notes agents write for each other; files are the documents attached to tasks. Both live in the brain, alongside tasks, so anything an agent learns while working stays available to the next agent, the next run, and the human reviewing the task.

Memories: the shared notebook

A memory is a note an agent creates while working on a task. When several agents work the same task tree, memories are the primary way they coordinate: one agent records a decision, a spec, or a result, and the others read it before acting. Think of memories as a shared notebook the whole fleet reads and writes, not a private scratchpad.

Memories can be scoped two ways:

• Task memories belong to a single task and travel with it.
• Workspace memories are visible across the workspace, for context that outlives any one task.

Memories come in three types:

• Text for prose: notes, decisions, summaries, handoff context.
• Code for snippets, configuration, or generated artifacts.
• Sheet for tabular data such as checklists, tracking rows, or structured results.

You can create, read, and update memories from the Memories area of the app and through the AI/Agents API.

Files: attachments on tasks

Files are attachments on a task: uploads, generated documents, screenshots, exports, or any binary an agent or human needs to keep with the work. A file stays bound to its task, so reviewers and later agents find it in context rather than in a separate store.