claude-recall 0.2.7 → 0.2.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -45,11 +45,12 @@ Launch Claude Code and your memories will be captured automatically. Claude Reca
45
45
 
46
46
  Claude Recall uses the Model Context Protocol to integrate directly with Claude Code.
47
47
 
48
- ### Automatic Memory Capture (v0.2.5+)
48
+ ### Automatic Memory System (v0.2.8+)
49
49
 
50
- Claude Recall ensures memories are captured reliably by:
51
- 1. **Instructing Claude via CLAUDE.md** - Installation adds instructions so Claude always calls the MCP tool when you use memory-related keywords
52
- 2. **Automatic pattern detection** - When Claude does use tools, additional patterns are detected
50
+ Claude Recall creates a seamless memory experience:
51
+ 1. **Automatic Context Loading** - Claude searches memory on EVERY prompt to provide context-aware responses
52
+ 2. **Silent Memory Storage** - Memories are stored without mentioning it
53
+ 3. **Natural Integration** - Retrieved information is used as if Claude always knew it
53
54
 
54
55
  **Memory storage is triggered by:**
55
56
  - "recall" (when used for storing, e.g., "for recall later")
@@ -80,10 +81,15 @@ You can also explicitly ask Claude to store memories using the MCP tools:
80
81
  ## Real-World Example
81
82
 
82
83
  ```
83
- Monday: "For recall: we're using PostgreSQL for our database and YAML for configs"
84
- Tuesday: "Recall what database we decided on"
85
- Claude: "Based on our stored memories, you're using PostgreSQL for the database
86
- and YAML for configuration files."
84
+ Monday: "Remember: all tests go in the tests/ directory"
85
+ Claude: "Understood!"
86
+
87
+ Tuesday: "Create a test for user authentication"
88
+ Claude: [automatically searches memory, finds test location preference]
89
+ "I'll create the authentication test in tests/auth.test.js"
90
+
91
+ Wednesday: "Where should tests go?"
92
+ Claude: "Tests go in the tests/ directory."
87
93
  ```
88
94
 
89
95
  ## Architecture
@@ -251,7 +251,7 @@ async function main() {
251
251
  program
252
252
  .name('claude-recall')
253
253
  .description('Memory-enhanced Claude Code via MCP')
254
- .version('0.2.7')
254
+ .version('0.2.8')
255
255
  .option('--verbose', 'Enable verbose logging')
256
256
  .option('--config <path>', 'Path to custom config file');
257
257
  // MCP command
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-recall",
3
- "version": "0.2.7",
3
+ "version": "0.2.8",
4
4
  "description": "MCP server for persistent memory in Claude Code conversations",
5
5
  "main": "dist/index.js",
6
6
  "bin": {
@@ -94,16 +94,27 @@ When you see these words/phrases, ALWAYS call \`mcp__claude-recall__search\` or
94
94
  - "what did we discuss about"
95
95
  - "do you remember"
96
96
 
97
- ## Important
98
- - When storing memories, just briefly acknowledge (e.g., "Got it!" or "Noted.")
99
- - When retrieving memories, integrate the information naturally into your response
100
- - Don't elaborate on the tool usage - keep responses concise and natural
101
- - These instructions ensure your memory system works reliably
102
-
103
- ## Response Guidelines
104
- - For storage: Simple acknowledgment like "I'll remember that" or "Stored!"
105
- - For retrieval: Just answer with the information, don't explain the search process
106
- - Keep the conversation flow natural and unobtrusive
97
+ ## Critical Behavior Rules
98
+
99
+ ### 1. ALWAYS Search Memory First
100
+ Before responding to ANY user prompt, ALWAYS call \`mcp__claude-recall__search\` with relevant keywords from the prompt. This ensures you have context from previous conversations.
101
+
102
+ Examples:
103
+ - User: "create a test script" → Search for: "test script location test directory testing"
104
+ - User: "what's the API endpoint?" Search for: "API endpoint URL base"
105
+ - User: "build the project" Search for: "build command compile"
106
+
107
+ ### 2. Silent Memory Storage
108
+ When storing memories, NEVER mention that you're saving anything. Just acknowledge the information naturally.
109
+
110
+ BAD: "I'll remember that" / "Storing in memory" / "Saved!"
111
+ GOOD: "Vanilla it is!" / "Understood" / Continue conversation naturally
112
+
113
+ ### 3. Natural Information Integration
114
+ When retrieving memories, integrate them seamlessly into your response without mentioning the search.
115
+
116
+ BAD: "According to my memory..." / "I found in my memory that..."
117
+ GOOD: Just use the information as if you always knew it
107
118
  `;
108
119
 
109
120
  // Always use global CLAUDE.md since claude-recall is a global tool