> ## Documentation Index
> Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cosmos Spaces

> Spaces group the experts, environments, sessions, and settings for a team or workstream so everyone works from a shared, focused set of resources.

## About spaces

A **Space** is a grouping of the experts, environments, sessions, secrets, and integrations your team uses in Cosmos. Each Space is a dedicated area of Cosmos for one team or workstream, where you only see the resources that belong to it.

Most organizations create one Space per team, such as Engineering, Data Science, Marketing, DevOps, IT, or Design. Each team sees only its own experts and environments, keeps its own secrets and integrations separate, and sets sensible defaults for new sessions, without the clutter of every other team's resources.

A Space is the boundary that scopes what you see and what agents can use. Switching Spaces switches the entire context: the sessions, experts, environments, secrets, and MCP servers available to you all change to match the selected Space.

## What belongs to a Space

A Space can group most of the resources you configure in Cosmos:

| Resource         | In a Space                                                                  |
| ---------------- | --------------------------------------------------------------------------- |
| **Experts**      | The agents your team runs, pinned to the Space so launches stay in context. |
| **Environments** | Cloud environments and daemon pools available for the Space's sessions.     |
| **Sessions**     | Interactive and automation sessions started while the Space is selected.    |
| **Secrets**      | Tenant-scoped secrets scoped to the Space's experts and sessions.           |
| **MCP servers**  | MCP server configurations available to the Space.                           |
| **Webhooks**     | Inbound webhooks that trigger work within the Space.                        |
| **Projects**     | Project groupings associated with the Space.                                |

A Space also shows how many experts and environments belong to it, so you can see at a glance how much each team has configured.

## The Default space

Every organization has a **Default space**. Any resource that hasn't been assigned to a named Space automatically belongs to the Default space. It always exists, and it can't be renamed or deleted.

Until you create a named Space, every expert, environment, and session lives in the Default space. You can start there and add named Spaces to organize your work as your team grows.

## When to use spaces

Use Spaces when more than one team or workstream shares a Cosmos organization and you want to:

* **Keep surfaces focused**: each team sees only its own experts, environments, and sessions instead of a shared, crowded list.
* **Separate configuration**: secrets, MCP servers, and integrations stay scoped to the team that owns them.
* **Set team defaults**: a Space can define a default expert and default environment, so new sessions started in that Space begin with the right setup.

A single team getting started can stay in the Default space. As you add more teams, create a Space for each one.

Read more about [managing spaces](/cosmos/spaces/managing) to switch, create, assign resources, and manage access.