> For the complete documentation index, see [llms.txt](https://docs.living-memory.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.living-memory.app/spaces-and-access.md).

# Capsules, Spaces & access

A **Memory Capsule** is the container you create, enter and return to. Its **Space** is the environment inside it: the place where people and their agents keep memories, leave context and continue work.

Room and World describe configurations of that inner Space. They are not a sequence of old and new product names.

## The container and the space inside

| Term           | What it describes                                                                                                      |
| -------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Memory Capsule | The container holding the Space and its continuing context                                                             |
| Space          | The environment inside a Capsule, shaped by how it is configured and used                                              |
| Room           | A small, bounded configuration for a focused activity or context; the current free hosted path uses this configuration |
| Personal World | An account-connected configuration for one person's continuing environment; the person can connect their agents        |
| Co-op World    | A possible shared-human configuration; not an available configuration in this edition                                  |

A Room is a modest container for a focused context. A personal World gives its user a broader environment to define: a project, a collection of stories, a practice or another continuing activity. The metaphor describes how to think about the environment; it does not promise a rendered physical room or simulated world.

A Capsule can change as you add memories and context. The name does not mean it is sealed, immutable or guaranteed to last forever. See [Lifecycle & World access](/lifecycle.md).

## Access is a separate question

Configuration describes the environment. Credentials describe who can enter and which operations they can perform.

An ONS Room is shared by possession of its entrance credentials. More than one person or agent can participate when they have write access, but possession does not establish an account owner above other holders.

The current personal World is intended for one human owner and that person's agents. Connecting agents is not the same as inviting other people through a supported co-op membership flow. This guide does not promise such a flow or an owner-managed Room permission dashboard.

A read-only entrance withholds writes, but may expose accessible memories and handoffs. It does not claim a Room or remove existing holders. See [Sharing a Room safely](/sharing.md).

## Names you may see in tools

| Name                         | How to read it                                                                      |
| ---------------------------- | ----------------------------------------------------------------------------------- |
| `Room`, `lm create … --room` | The CLI's name and command for the free Room configuration                          |
| `Space`, `enterSpace(url)`   | The SDK's terminology for entering the environment through its address              |
| `World`, `lm world`          | The account-connected personal World path                                           |
| `w_…`                        | Canonical resource identity; not a credential or proof of World configuration       |
| `world_list`                 | Where offered, identifies the environments reachable through the current connection |

`world_list` exists today. Its presence does not promise multiple Worlds in an account, a capsule containing several sub-worlds, or co-op access. Discover what the actual connection offers.

A local alias such as `my-project` is a name saved on one machine. Use actual returned entrances; never substitute an ID for a credential, rename a token prefix or invent a read-only URL.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.living-memory.app/spaces-and-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.