Lore
Documentation navigation
Docs/Use Lore/Write a durable memory

Write a durable memory

Save one useful memory with path, priority, disclosure, glossary, and content.

Write one durable memory for one future use case.

A useful memory is easy to find, easy to trust, and narrow enough that it does not pollute unrelated prompts.

Example

*.txt
Plaintext
URI: project://my_app/auth
Priority: 1
Disclosure: When working on authentication, login, refresh tokens, or session security for MyApp.
Glossary: MyApp auth, JWT, refresh token, login
Content: MyApp uses JWT access tokens with refresh-token rotation. Token refresh bugs must be checked against replay protection and server-side revocation state.

Checklist

  1. Choose the right domain: core://, preferences://, or project://.
  2. Keep the path short and specific.
  3. Write content as a fact, rule, decision, or workflow that should survive the session.
  4. Add a disclosure trigger that names the future task.
  5. Add glossary terms for aliases and likely prompt words.
  6. Set priority based on real importance.
  7. Run a recall query that should find the memory.

Avoid

  • saving secrets, tokens, credentials, or private keys;
  • combining unrelated project facts into one broad memory;
  • copying the same rule into local AGENTS.md, CLAUDE.md, and Lore;
  • using priority 0 or 1 for everything;
  • writing disclosure as a vague label instead of a future trigger.
Web ConsoleLearn what each main page in the Lore Web Console is used for.Recommended routineFollow a simple routine for memory review, recall checks, Dream, and backups.Use recall in chatRead the recall block as memory pointers and open useful memories before relying on them.Read recall resultsInterpret scores, candidates, query details, and usage state in the Recall UI.