# Workspaces and sessions

> A workspace holds files. A session is an agent working with them.

Source: https://usefiretower.com/docs/concepts-work

One workspace can hold several sessions

Workspace **Checkout fix** Example: one repository and shared branch

**Lead session** Coordinates the fix

**Reviewer session** Reads the same files

↳

Sub-workspace · separate placement **Test the checkout fix** QA session · separate working files and branch

Example with a repository. The reviewer shares the lead’s workspace; QA runs in a sub-workspace.

## The four concepts

**Workspace**

A working directory on a machine, with its files and associated sessions. It can have a repository or contain work without git.

**Session**

One agent conversation and execution context. It can contain several turns, tool calls and approvals. Several sessions can work in one workspace.

**Subagent**

An agent session started by a lead to handle part of the task. It returns its result to the lead.

**Sub-workspace**

A separate workspace created for delegated work. It appears beneath the lead’s work and has its own files and, for git-backed work, branch.

## Two places for delegated work

| Placement | What it means |
| --- | --- |
| Same workspace | A separate session uses the lead’s files and branch. Changes are shared immediately. |
| Its own workspace | A separate workspace holds the delegated work. Its changes may need to be integrated. |

A subagent does not always create a sub-workspace. A sub-workspace is also not a folder nested inside the lead’s files.

See delegated work in the redesigned app

 ![Lead and delegated work](https://usefiretower.com/product/team-light.webp)

Lead and delegated work · supplied redesign prototype, not a release screenshot

Put it into practice [Create a workspace](https://usefiretower.com/docs/workspaces) [Manage a run](https://usefiretower.com/docs/runs) [Build an agent team](https://usefiretower.com/docs/teams)