tour

Mem0 Project Tour

Show the user what mem0 has stored for the current project.

Cross-project mode

When invoked with --all-projects (e.g., /mem0:tour --all-projects or /mem0:tour --all-projects auth middleware), search across ALL projects:

1. Call get_memories with filters={"AND": [{"user_id": "<active_user_id>"}]}, page_size=200 — no app_id filter.
2. If a search query was also provided, run search_memories with query=<query>, filters={"AND": [{"user_id": "<active_user_id>"}]}, top_k=20 — again no app_id.
3. Group results by app_id first, then by category within each project.
4. Display:

   ## <app_id_1> (<N> memories) ← current
   **Architecture Decisions** — <memory content>
   ...
   
   ## <app_id_2> (<N> memories)
   ...
   
   <N> memories across <M> projects
   

5. Mark the current project with ← (current) in the heading.

If --all-projects is NOT present, use the standard single-project flow below.

Peek mode (compact search)

When /mem0:tour receives a search query argument (e.g., /mem0:tour auth middleware) WITHOUT --all-projects, run in peek mode — compact one-liner results:

1. Run 2 parallel search_memories calls:
   • Broad: query=<query>, filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}]}, top_k=10, rerank=true
   • Targeted: query=<query>, filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}, {"metadata": {"type": "decision"}}]}, top_k=5, rerank=true
2. Deduplicate by ID, display compact results:

   ## mem0 search: "<query>" (<N> results)
   
   1. [decision] Auth module uses JWT with RS256 keys (2025-05-15) [mem0:a3f8b2c1]
   2. [anti_pattern] Don't use symmetric HS256 — leaked in env (2025-05-10) [mem0:7e2d9f4a]
   3. [convention] All middleware in src/middleware/ (2025-05-08) [mem0:c4d5e6f7]
   

   Format: <number>. [<type>] <content, 80 chars> (<date>) [mem0:<short_id>]
3. If no results: No memories matching "<query>" for project <project_id>.