Paths and where files land

Path resolution

Relative paths start in the caller's folder; absolute paths start at the shared Workspace root. A path changes location, never permission. Agents still need access to shared destinations.

Path	Agent	Workflow
`./reports/q3.md`	reports/q3.md in its Home.	reports/q3.md in its workflow folder.
`reports/q3.md`	Same as `./reports/q3.md`.	Same as `./reports/q3.md`.
`/reports/q3.md`	Shared root's reports folder, if granted.	Shared root's reports folder.
`{{workflow.tmp}}/rows.csv`	Workflow-only variable.	This run's Temporary files folder.

The dashboard Assistant works at the root, so these relative and absolute forms resolve there. Use explicit ./ or / paths in instructions and steps. Tools return reusable paths in the same form.

Homes and workflow folders

Location	Contents and access
Agent Home under Agents/	Fixed read-and-write access for that agent; dashboard operators can manage it. Other agents cannot browse it.
AGENTS.md	Operator-owned identity; read every run and conversation.
MEMORY.md	Agent-owned memory; read when needed.
Skills/	Procedures; read when their descriptions match a task.
Scripts/	Reusable code run with Code Executor.
Chats/	One folder per agent chat, labelled for the member; account-owned original attachments.
tmp/	The agent's scratch files. Files the agent writes here are never attached to its answers; files it writes elsewhere are.
Workflow folder under Workflows/	Persistent outputs and state; Workflow folder variable or `./` paths.
Temporary files / Run	Separate scratch folder per workflow run; Temporary files (this run) variable.

Homes contain readable instructions: never store secrets there. Workflows have folders, not agent Homes. An agent step keeps its own Home as its relative-path base and gains access to the workflow folder for that run.

Renaming a workflow does not move its folder. Deleting a workflow keeps its persistent folder and files; temporary files move to Trash. Archived automations/ and hidden .runs/ remain read-only for operators.

Where outputs land

Source	Default destination
File with a bare filename	Caller's folder: agent Home, workflow folder or dashboard root.
Generated images, videos or documents	images/, videos/ or documents/ beneath the caller's folder.
External download or saved email attachment	downloads/ beneath the caller's folder; root downloads/ for the dashboard Assistant.
Workflow tool result saved without a path	This run's temporary folder; kept results go to the workflow's folder. An agent step saves to the agent's Home instead.
Agent-chat attachment	The chat's folder under the agent Home's Chats/. Deleting the conversation leaves the file.
Dashboard-chat upload	Your own folder under chat-attachments/ in account Workspace.
Member's personal-assistant file	That member's personal Files.

Account agents, workflows and the dashboard Assistant always save to account Workspace. A failed or denied write does not fall back to personal Files.

Retention

Material or action	Retention effect
Saved large tool result outside temporary folders	Temporary by default; expires after 24 hours unless kept.
File in an agent's tmp/ or a workflow's temporary folder	Expires seven days after its last write; another write restarts the clock.
Expiration	Hourly cleanup moves the file to Trash.
Trash	Recoverable for seven days, then permanently removed; still counts toward storage until removal.
Keep, rename or move	Makes a temporary file permanent.
Move or rename into a temporary folder	Refused; write a new file there instead.
Later agent edit outside temporary folders	Makes the temporary file permanent.
Write inside a temporary folder	Applies seven-day expiration again, even if previously kept.

Save deliverables and state needed by later runs outside temporary folders.

Paths and where files land

Path resolution

Homes and workflow folders

Where outputs land

Retention

Related