This page's address still says "workspace-files" from an earlier version of Teamday. Files now live in ordinary organization folders; the content below reflects that.

Files

Your organization has one persistent file tree that agents read from and write to. You can upload files directly from the Files page into any folder, and any agent working in that folder (or with access to it) can use them.

---

Uploading Files

1. Click Files in the left sidebar and open the folder you want.
2. Click Upload (or drag files onto the file browser).
3. Select one or more files from your device.
4. The upload completes automatically. Large files (images, video, audio) upload directly to object storage and appear in the /media folder.

Supported file types: Any file type can be uploaded. Agents can read text-based files (.txt, .csv, .md, .json, etc.) and images directly. Video and audio files are placed in /media for agent pipelines that process media. Markdown files (.md) open directly as Knowledge articles when you click them in the file browser.

Size limits: Small files (under ~5 MB) upload via the standard path. Larger media files use a direct upload to object storage with no practical browser timeout — multi-gigabyte video files are supported.

---

Where Files Live

Folders are ordinary folders; nest them however suits your team. A few conventional locations:

Image, video, and audio uploads land under /media/<filename> by default. Other file types are placed in the folder you are viewing, or at the path you specify.

Files are addressed by their path from the organization root, for example /marketing/blog/launch.md.

---

Agents Reading Files

An agent reads files with the Read tool and other filesystem tools. Relative paths resolve from the chat's or job's working directory; absolute paths (/media/report.csv) work from anywhere the agent has access. To point an agent at a file:

1. Upload the file via the Files page.
2. In chat, reference it by path: "Analyze the data in /media/report.csv" or "Process the video at /media/campaign.mp4."
3. The agent reads the file and uses it as part of its task.

Files persist across conversations — unlike chat attachments, which are scoped to a single conversation.

---

Chat Attachments vs Files Page

Use the Files page for assets agents need across multiple runs — CRM exports, brand assets, large media, or reference documents.

---

Managing Files from the CLI and API

teamday files ls /media
teamday files read /media/report.csv
teamday files write /marketing/brief.md --from=brief.md
teamday files mkdir /marketing/assets
teamday files mv /media/old-name.png /marketing/assets/logo.png
teamday files rm /media/unused.mp4

The same operations are available over the API: GET /api/files?path=, GET/PUT /api/files/content, POST /api/files/directory, POST /api/files/move, and DELETE /api/files?path=. See API Endpoints.

---

Troubleshooting

Upload fails immediately

• Check your internet connection. For very large files, a stable connection is required for the direct upload handshake.
• If the organization is new, wait a few seconds and retry — object storage may still be initializing.

File does not appear in the file browser

• Refresh the Files page after uploading.
• If the upload was interrupted, try again — partial uploads are not committed until complete.

Agent cannot find the file

• Ask the agent: "List all files available to you."
• Verify the path — media files land under /media/<filename>, not in the folder you were viewing.
• Check the chat's working directory. A relative path like report.csv resolves from that folder; use the absolute path if the file is elsewhere.

Large video upload shows a provider configuration error

• The hosted Teamday deployment includes object storage. Self-hosted deployments require Tigris or S3-compatible storage configured with TIGRIS_BUCKET (or S3_BUCKET) and matching access credentials. Contact your operator if you manage your own instance.