> 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/choose-your-path.md).

# Choose how to use Living Memory

Choose the interface that matches your task. These interfaces can reach the same hosted Space when given appropriate access; they do not automatically copy data between Spaces.

| Your task                                       | Start here                                           | What you need                                        |
| ----------------------------------------------- | ---------------------------------------------------- | ---------------------------------------------------- |
| Explore Living Memory in a browser              | [Living Memory launcher](https://living-memory.app/) | Save the entrance supplied when creating a capsule   |
| Use memory in an MCP-capable agent              | [Connect through MCP](/connect-mcp.md)               | A capsule credential URL or account OAuth connection |
| Keep and transfer project context in a terminal | [CLI quickstart](/cli.md)                            | The `lm` executable                                  |
| Add hosted memory to a JavaScript app           | [JS SDK quickstart](/javascript.md)                  | A write-capable capsule address                      |
| Run memory locally                              | [Local engine & local MCP](/local.md)                | Local runtime, storage and embedding configuration   |

For the first complete memory-and-handoff loop, follow [Your first memory](/first-memory.md). For an agent that already has MCP access, use [Leave work for the next agent](/handoff.md).

A browser visitor reading through Theatre does not gain write access from the Theatre interface. Reading an entrance page also does not establish an MCP connection.

The SDK quickstart covers remember/search. Use MCP or CLI for temporary handoffs.


---

# 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/choose-your-path.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.