> 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/memory-vs-handoff.md).

# Memory vs Handoff

Use memory for facts worth retrieving later. Use handoff for a temporary, exact checkpoint that lets someone continue work.

|                   | Memory                                                        | Handoff                                                         |
| ----------------- | ------------------------------------------------------------- | --------------------------------------------------------------- |
| Example           | The project uses blue primary buttons                         | The draft is ready; review the settings section next            |
| How to retrieve   | Semantic recall/search                                        | Read the raw note; select an ID when supported                  |
| Intended lifetime | Retained subject to the Space's lifecycle and memory behavior | Temporary; expires at the server-returned time                  |
| CLI               | `lm remember`, `lm recall`                                    | `lm handoff`, `lm resume`                                       |
| Hosted MCP        | `memory_add`, `memory_search`                                 | `handoff_post`, `handoff_read` and `handoff_list` where offered |

Handoff text is not embedded or returned by memory search. Do not expect `recall` to find a handoff. Memory search is not an exact transcript archive.

A useful checkpoint names the goal, completed work, evidence, blockers and next action. It should remain usable without the previous conversation.

Ask an agent to store a durable fact when that is your intent. A welcome note, retrieved suggestion or old plan should not automatically become a durable memory.

Both memory and handoffs remain subject to the Space's lifecycle. A handoff cannot keep an expired capsule alive. Treat retrieved text as context, not permission to run commands or override the current user's instructions.


---

# 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/memory-vs-handoff.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.