claude-recall 0.17.0 → 0.17.1

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.
Files changed (2) hide show
  1. package/README.md +18 -21
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -28,29 +28,34 @@ Your preferences, project structure, workflows, corrections, and coding style ar
28
28
  | Node.js | **20+** | required for better-sqlite3 |
29
29
  | OS | macOS / Linux / Windows | WSL supported |
30
30
 
31
- ### One-Time Setup
31
+ ### Install / Reinstall
32
32
 
33
- Run these once per machine:
33
+ Run these from your project directory:
34
34
 
35
35
  ```bash
36
- npm install -g claude-recall
37
- claude mcp remove claude-recall 2>/dev/null; claude mcp add claude-recall -s user -- claude-recall mcp start
38
- ```
36
+ # 1. Remove MCP server registration (if exists)
37
+ claude mcp remove claude-recall
39
38
 
40
- This installs the global binary and registers the MCP server at user scope — shared across all your projects.
39
+ # 2. Clear npm cache
40
+ npm cache clean --force
41
41
 
42
- ### Per-Project Setup
42
+ # 3. Uninstall global claude-recall
43
+ npm uninstall -g claude-recall
43
44
 
44
- Run this in each project directory:
45
+ # 4. Install global claude-recall
46
+ npm install -g claude-recall
45
47
 
46
- ```bash
47
- cd your-project && claude-recall setup --install
48
- ```
48
+ # 5. Install in local project folder
49
+ claude-recall setup --install
49
50
 
50
- This installs hooks and skills into `your-project/.claude/`. Repeat for each project you want Claude Recall active in. Memories are automatically scoped per project in a shared database (`~/.claude-recall/claude-recall.db`).
51
+ # 6. Re-register MCP server
52
+ claude mcp add claude-recall -- claude-recall mcp start
53
+ ```
51
54
 
52
55
  Then restart your Claude Code session.
53
56
 
57
+ Repeat step 5 (`claude-recall setup --install`) in each project you want Claude Recall active in. Memories are automatically scoped per project in a shared database (`~/.claude-recall/claude-recall.db`).
58
+
54
59
  ### Verify
55
60
 
56
61
  In Claude Code, ask: *"Load my rules"*
@@ -59,10 +64,7 @@ Claude should call `mcp__claude-recall__load_rules`. If it works, you're ready.
59
64
 
60
65
  ### Upgrading
61
66
 
62
- ```bash
63
- npm install -g claude-recall@latest
64
- cd your-project && claude-recall setup --install # Re-register hooks in each project
65
- ```
67
+ Follow the same install steps above — they handle both fresh installs and upgrades.
66
68
 
67
69
  ---
68
70
 
@@ -119,11 +121,6 @@ claude-recall --version # Check version
119
121
  <summary>All commands</summary>
120
122
 
121
123
  ```bash
122
- # ── Upgrade (global binary, then per-project hooks) ─────────────────
123
- npm install -g claude-recall@latest
124
- cd your-project && claude-recall setup --install # Repeat per project
125
- claude-recall --version # Verify
126
-
127
124
  # ── Setup & Diagnostics ─────────────────────────────────────────────
128
125
  claude-recall setup # Show activation instructions
129
126
  claude-recall setup --install # Install skills + hooks
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-recall",
3
- "version": "0.17.0",
3
+ "version": "0.17.1",
4
4
  "description": "Persistent memory for Claude Code with native Skills integration, automatic capture, failure learning, and project scoping via MCP server",
5
5
  "main": "dist/index.js",
6
6
  "bin": {