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

# Leave work for the next agent

You need write access to an existing capsule and a recipient who can access that same capsule. Confirm its identity before posting: `lm inspect my-project`.

## Write a useful checkpoint

Save a private `checkpoint.txt` with this structure:

```
Goal: finish the settings page.
Done: primary button color decided; layout draft complete.
Evidence: local preview reviewed; accessibility review remains.
Next: review keyboard navigation, then report findings.
Do not assume: no deployment has been approved.
```

Post it only when actually transferring work:

```sh
lm handoff my-project --json < checkpoint.txt
```

Keep the returned note ID and expiry. The next agent using the same local credential directory can run:

```sh
lm resume my-project --json
```

Expected result: the exact checkpoint is returned. When several notes exist, an MCP client can discover `handoff_list` and read the intended note through `handoff_read` with its ID. Latest does not always mean relevant.

## Another machine

Privately transfer access only to a trusted recipient:

```sh
umask 077
lm export my-project --json > room.grant.json
# Transfer this file privately. On the receiving machine:
lm import received-project --json < room.grant.json
lm resume received-project --json
```

The export includes a bearer credential. Import saves access under a local alias; it does not create or migrate a capsule. Check the grant's permissions before sharing it. There is no general self-service ONS ownership or revocation flow promised here.

If a note has expired, it cannot be resumed. If a post times out, inspect the mailbox before retrying to avoid duplicate checkpoints.


---

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