Lore
Documentation navigation
Docs/Troubleshooting/Memory writing tips

Memory writing tips

Use a practical checklist and example for durable memory shape.

Use this checklist when writing or reviewing memory.

Good memory shape

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

Review checklist

  1. One memory, one topic.
  2. Path names the topic directly.
  3. Disclosure names the future situation.
  4. Glossary uses words the user or agent will actually type.
  5. Priority reflects real importance.
  6. Content is current and verified.
  7. The memory is not duplicated in local agent files.
  8. The memory can be opened and understood without reading unrelated nodes.

Split when needed

Split a memory when it contains multiple independent triggers. For example, deployment commands, database migration rules, and design preferences should usually be separate nodes because they are recalled in different situations.

Setup issuesCheck server address, setup status, health, migrations, and auth problems.Recall issuesFix missing memories, noisy results, slow recall, and confusing query output.Agent issuesFix boot context, recall hooks, MCP tools, and stale agent memory.Common questionsShort answers for everyday Lore usage decisions.