Wax Memory Maintenance
Use when the active Hermes memory provider is wax-memory.
Checks
- Confirm the broker is reachable:
hermes wax-memory doctor - Prefer
wax_recallfor assembled context andwax_searchfor raw hits - Store durable facts with
wax_rememberandmemory_typefromnote,user_preference,decision,lesson,handoff,constraint,fact;task_stateis session-local working state and requires an active session - Write session continuity with
wax_handoff; do not dump raw transcripts - Use structured tools (
wax_entity_upsert,wax_fact_assert,wax_facts_query) only for stable knowledge-graph facts
Recovery
- If recall is empty, run
npx waxmcp --embedder minilm --transport http - If vector search is disabled, rebuild both
wax-cliandwax-mcpwith MiniLM/Arctic traits - After
/resetor/resume, rely on the provider session switch — do not invent a new session id