> ## 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.

# Managing Spaces

> Switch between Spaces, create new ones, assign experts and environments, and control who can manage them.

Use the **Space picker** at the top-left of the Cosmos sidebar to switch the current Space, create new ones, and search across them. Your selection persists, and it drives which Space new experts, environments, and sessions default into.

## Switch Spaces

<Steps>
  <Step title="Open the Space picker">
    Click the Cosmos button in the sidebar to view all the Spaces for your organization.
  </Step>

  <Step title="Choose a Space">
    Select the Default space or any named Space.
  </Step>

  <Step title="Work within the Space">
    Only the sessions, experts, environments, secrets, and MCP servers that belong to that Space are available.
  </Step>
</Steps>

## Search through Spaces

As your organization grows, use the search field at the top of the Space picker to filter the list. The list narrows as you type. Press **Enter** to select the first visible match.

## Create a Space

Open the Space picker, type a name, and press **Enter**. The new Space becomes the current selection, and the **Create expert** and **Create environment** forms will default new resources into it.

Space names must be unique within your organization. Creating a Space is open to any member of your organization, and the creator becomes the Space's owner.

## Assign resources to a Space

**Experts and environments** default into the currently-selected Space when you create them, and the create form lets you override that choice. Once assigned, expert and environment cards show a Space pill so you can see where each one lives. You can move a resource by clearing or changing its Space assignment; leaving it unassigned returns it to the Default space.

**Sessions** are assigned to a Space automatically when they start. Cosmos resolves a session's Space using the following order of precedence:

1. **Manager's Space**: a worker launched by a manager agent inherits the manager's Space, so an entire worker subtree stays together.
2. **Expert's Space**: the Space the launching expert is pinned to.
3. **Selected Space**: the Space selected when the session was launched, such as in the home-page launcher.
4. **Daemon's Space**: for daemon-routed sessions, the Space declared by the daemon.

If none of these applies, the session isn't scoped to a named Space and lives in the Default space.

<Note>An expert's pinned Space wins over the Space you have selected at launch. If an expert is pinned to a different Space, launching it from another Space still runs the session in the expert's Space.</Note>

## Delete a Space

Deleting a Space does **not** delete the resources inside it. When you delete a Space, its experts, environments, projects, daemon pools, sessions, secrets, and MCP servers are **reassigned**, either to another Space you choose or to the Default space. Webhooks are the exception: they return to the Default-space view rather than being reassigned.

Before you confirm, the webapp shows a preview of what will be affected, counting the live resources still associated with the Space. Terminated, completed, and archived sessions are not counted.

## Permissions

* **Creating** a Space is open to any member of your organization. The creator becomes the Space's owner.
* **Renaming, deleting, setting defaults, and changing membership** require an organization admin, or ownership (or the equivalent permission) on the Space and the resource being changed.

All Space operations apply only within your own organization.