> 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/troubleshooting.md).

# Troubleshooting

First identify the intended Space and the actual door you are using. Keep credential-bearing output private.

| Symptom                       | What to check                                                                         |
| ----------------------------- | ------------------------------------------------------------------------------------- |
| `lm` is not found             | Open a new terminal after installation; verify the installer completed                |
| Wrong or missing memories     | Confirm the alias/capsule ID, then query a harmless known fact                        |
| A write tool is unavailable   | Discover tools; you may be using a read-only door                                     |
| SDK returns `ENTER_FAILED`    | Check the address privately; SDK 0.1.0 also refuses read-only doors                   |
| HTTP 401                      | Check account OAuth/consent on the account route; do not attach unrelated credentials |
| HTTP 404                      | The door may be invalid, revoked or unavailable; do not assume data was deleted       |
| HTTP 410                      | Access has expired; creating another capsule does not recover the old one             |
| `ROOM_FULL`                   | Existing memories remain readable; see lifecycle guidance                             |
| HTTP 429                      | Read the response: it can be a daily operation or creation limit                      |
| HTTP 502/503 or timeout       | The outcome may be uncertain; check state before retrying a write                     |
| Resume returns the wrong note | Discover `handoff_list`, then read the intended ID through MCP                        |
| A handoff is missing          | Check expiry and Space identity; handoffs are not found by memory search              |

`lm inspect` can preserve saved identity while reporting a live failure. That does not establish that the capsule is gone. The CLI reports failures without automatically retrying or replacing capsules.

For support, include interface, version, time, action and sanitized error code. Exclude tokens, grant files, full credential URLs and unrelated memory contents. Treat debug output as private until reviewed.


---

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