This page used to describe "Spaces". Spaces no longer exist: files live in ordinary folders and agents belong to your whole organization. The page address is unchanged so older links keep working.

Folders and Files

Everything your agents read and write lives in one file tree that belongs to your organization. Folders in that tree are ordinary folders: nest them as deep as you like, name them however you like, and move things around when your needs change. Nothing is special about a top-level folder, and there is no separate container to create before an agent can start work.

Key Ideas

Term	Meaning
Organization	Your account. Everyone and every agent in it shares one file tree and one set of secrets, MCP connections, and repositories.
Folder	An ordinary folder in that tree, such as `/product` or `/marketing/blog`.
Working directory	The folder a chat, job, process, or app works from. You choose it when you create the item.
Path	The address of a file or folder from the organization root, for example `/marketing/blog/launch.md`.

Agents and Folders

Agents belong to your organization. Each agent carries its own instructions, skills, tools, and MCP connections, and brings the same equipment to whatever folder it works in. There are no per-folder copies of an agent and nothing to "assign" before it can work somewhere.

When you start a chat you choose two things: the agent and the folder it should work from. The same agent can work in /product in one chat and in /finance/q3 in another, with the same skills and connections in both.

To control which agent can reach which folders, use the agent's working-folder settings. See Agent Configuration.

The Working Directory

Every chat, job, process (mission), and app has an explicit working directory, chosen when it is created. It is an absolute path in your organization, such as /product.

Relative paths in instructions ("save it to reports/") resolve from the working directory.
Browsing a different folder on the Files page later does not change the working directory of an existing chat or job.
To work somewhere else, start a new chat or job with the other folder as its working directory.

This keeps work predictable: you always know where an agent will read from and write to.

What Lives in Your Folders

Content	Notes
Files	Documents, data, code, images, video. Uploaded from the Files page or written by agents.
Knowledge	Markdown files agents read repeatedly. Conventionally under `/knowledge`, but any folder works.
Media	Images, video, and audio uploaded from the Files page land under `/media` by default.
Repositories	Connected Git repositories, managed with `teamday repositories ...`. See Git Integration.
Projects and apps	Projects and apps are created from a folder; that folder is their working directory.
`CLAUDE.md`	Persistent instructions read from the working directory at the start of a run.

Secrets (API keys, tokens) are organization-owned and are not stored in folders. See Org Secrets.

Browse and Manage Files

Via Web App

Open Files in the sidebar. You can create folders, upload files, move and rename items, and open Markdown files as Knowledge articles. See Files for uploads and size limits.

Via CLI

teamday files ls /
teamday files ls /marketing
teamday files read /marketing/blog/launch.md
teamday files write /marketing/blog/launch.md --from=launch.md
teamday files mkdir /marketing/blog
teamday files mv /marketing/blog/draft.md /marketing/blog/final.md
teamday files rm /marketing/blog/old.md

Knowledge uses the same shape:

teamday knowledge list
teamday knowledge search "pricing"
teamday knowledge write /knowledge/pricing.md --from=pricing.md

Via API

# List a folder
curl "https://app.teamday.ai/api/files?path=/marketing" \
  -H "Authorization: Bearer $TEAMDAY_API_TOKEN"

# Read and write file content
curl "https://app.teamday.ai/api/files/content?path=/marketing/blog/launch.md" \
  -H "Authorization: Bearer $TEAMDAY_API_TOKEN"

# Create a folder
curl -X POST "https://app.teamday.ai/api/files/directory" \
  -H "Authorization: Bearer $TEAMDAY_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"path": "/marketing/blog"}'

The full route list is in API Endpoints.

Start Work in a Folder

Chat

In the web app, start a chat, pick the agent, and choose the folder it should work from. From the CLI:

teamday chats new --agent-id=<agent-id> --cwd=/marketing/blog

Scheduled work

A mission (process) has a working directory too:

teamday missions create \
  --title="Weekly blog audit" \
  --agent-id=<agent-id> \
  --cwd=/marketing/blog \
  --schedule-cron="0 9 * * MON"

See Missions.

Apps

teamday apps create --cwd=/product/dashboard

Organizing Your Tree

A simple structure that works for most companies:

/knowledge        Reference material agents read repeatedly
/marketing        Content, campaigns, SEO reports
/product          Specs, roadmaps, app folders
/finance          Reports and analysis
/media            Uploaded images, video, audio

These are suggestions, not requirements. Pick folders that match how your team already thinks about its work, and give each chat or mission the narrowest folder that contains what it needs.

Next Steps

Setting Up Your Company Folders — Step-by-step recipes
Files — Uploading and managing files
Agent Configuration — Working folders, skills, and MCP connections
Git Integration — Connected repositories