← Back to context

Comment by steveklabnik

5 days ago

So hilariously, I hadn't actually read those docs yet, I just knew they added the feature. It seems like the docs may not be up to date, as when I read them in response to your reply here, I was like "wait, I thought it was more sophisticated than that!"

The answer seems to be both yes and no: see their announcement on youtube yesterday: https://www.youtube.com/watch?v=Yct0MvNtdfU&t=181s

It's still ultimately file-based, but it can create non-Claude.md files in a directory it treats more specially. So it's less sophisticated than I expected, but more sophisticated than the previous "add this to claude.md" feature they've had for a while.

Thanks for the nudge to take the time to actually dig into the details :)

10 comments

steveklabnik

Reply
koakuma-chan  5 days ago

It creates them on its own?

  • steveklabnik  5 days ago

    Okay so, now that I've had time after work to play with it... it doesn't work like in the video! The video shows /memories, but it's /memory, and when I run the command, it seems to be listing out the various CLAUDE.md files, and just gives you a convenient way to edit them.

    I wonder if the feature got cut for scope, if I'm not in some sort of beta of a better feature, or what.

    How disappointing!

    • elfenleid  5 days ago

      Let me have a look, thanks for reporting that.

      This is very much in development and I keep adding features to it. Any suggestions let me know.

      The way I use it, I add instructions to CLAUDE.md on how I want him to use recall, and when.

      ## Using Recall Memory Efficiently

      *IMPORTANT: Be selective with memory storage to avoid context bloat.*

      ### When to Store Memories - Store HIGH-LEVEL decisions, not implementation details - Store PROJECT PREFERENCES (coding style, architecture patterns, tech stack) - Store CRITICAL CONSTRAINTS (API limits, business rules, security requirements) - Store LEARNED PATTERNS from bugs/solutions

      ### When NOT to Store - Don't store code snippets (put those in files) - Don't store obvious facts or general knowledge - Don't store temporary context (only current session needs) - Don't duplicate what's already in documentation

      ### Memory Best Practices - Keep memories CONCISE (1-2 sentences ideal) - Use TAGS for easy filtering - Mark truly critical things with importance 8-10 - Let old, less relevant memories decay naturally

      ### Examples GOOD: "API rate limit is 1000 req/min, prefer caching for frequently accessed data" BAD: "Here's the entire implementation of our caching layer: [50 lines of code]"

      GOOD: "Team prefers Tailwind CSS over styled-components for consistency" BAD: "Tailwind is a utility-first CSS framework that..."

      *Remember: Recall is for HIGH-SIGNAL context, not a code repository.*

    • elfenleid  5 days ago

      Hey! You're mixing up two different things:

      1. Claude Desktop's built-in `/memory` command (what you tried) - just lists CLAUDE.md files 2. Recall MCP server (this project) - completely separate tool you need to install

      Recall doesn't work through slash commands. It's an MCP server that needs setup:

      1. Install: npm install -g @joseairosa/recall 2. Add to claude_desktop_config.json 3. Restart Claude Desktop 4. Then Claude can use memory tools automatically in conversation

      Quick test after setup: "Remember: I prefer TypeScript" - Claude will store it in Redis.

      1 reply →