> 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/sharing.md). # Sharing a capsule safely A capsule entrance grants access to anyone who possesses it. Before sharing, decide what its recipient should be able to read or change. ## Choose an actual door * A write-capable MCP entrance permits the writes registered for that connection. Share it privately only with collaborators who should have that access. * A server-issued read-only entrance permits its offered reads and withholds writes. It is still a credential: anyone holding it may read accessible memories and handoffs. * A capsule ID identifies the resource. It does not grant access. The hosted creation path issued separate write and read-only URLs in the CLI verification on 2 October 2026. The CLI can expose the returned read-only entrance as Open/Guide. The Web mint path also accepts a returned read-only URL; available sharing controls can differ by deployed version. If your grant has no read-only door, do not invent one or substitute the write door. For grants supported by the CLI, use `lm inspect my-project` privately and share its actual Open/Guide entrance only when that reading access is intended. A Theatre visit link uses the door token after `#`; do not move it into a query string or substitute the capsule ID. ## Understand the limits Read-only access is not per-note privacy. Avoid mixing public reading material and private checkpoints in the same shared capsule. Taking down a link does not remove credentials already copied by another person. There is no general self-service claim/protect/revoke flow for an existing ONS capsule documented here. Receiving a read-only door does not establish ownership over other credential holders. Use harmless example data in public demos. For current service disclosures, read [Privacy](https://living-memory.app/documents#privacy) and [Terms](https://living-memory.app/documents#terms). --- # 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/sharing.md?ask=&goal= ``` `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.