Always local
The following work happens on the machine running Mneme:
- File discovery and parsing.
- Indexing, manifest updates, and cache management.
- Vector and BM25 retrieval.
- Source IDs, chunk IDs, and index fingerprints.
When an LLM-backed feature is used
Retrieved document snippets are sent to the endpoint you configure for answer generation, query decomposition, or Graph RAG entity extraction.
The exact handoff
Mneme does not choose an endpoint for you. Use a trusted endpoint, keep secrets out of indexed files, and check limits before indexing sensitive material.
Controls that narrow the boundary
| Control | Default | Why it matters |
|---|---|---|
| Remote endpoint transport | HTTPS required | Non-local HTTP requires an explicit development override. |
| Document size | 50 MiB | Bounds a single document. |
| PDF pages | 2,000 | Bounds extraction work. |
| Remote context | 60,000 characters | Bounds retrieved content sent to an endpoint. |
| Untrusted-document framing | Always on | Treats retrieved text as data rather than instructions. |
What you can inspect
Answers carry query-local citations, source paths, PDF pages, chunk IDs, and boundary framing. Safety is part of the product experience, not a promise hidden in the footer.