eagle-mem 2.0.3 → 2.0.4

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 +12 -28
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -9,49 +9,33 @@ Persistent memory for [Claude Code](https://docs.anthropic.com/en/docs/claude-co
9
9
 
10
10
  **Zero per-instance overhead.** No daemon, no vector DB, no MCP server. Just bash scripts, sqlite3, and jq.
11
11
 
12
- ## Install
12
+ ## Getting started
13
+
14
+ **1. Install** (once — this is the only setup step):
13
15
 
14
16
  ```bash
15
17
  npm install -g eagle-mem
16
18
  eagle-mem install
17
19
  ```
18
20
 
19
- That's it. Eagle Mem registers 5 lifecycle hooks in Claude Code and is fully automatic from here.
20
-
21
- ## New project
22
-
23
- Open Claude Code in your project. Eagle Mem activates and shows:
21
+ **2. Open Claude Code** in any project directory. Eagle Mem activates automatically:
24
22
 
25
23
  ```
26
24
  █▀▀ ▄▀█ █▀▀ █ █▀▀ █▀▄▀█ █▀▀ █▀▄▀█
27
25
  ██▄ █▀█ █▄█ █▄▄ ██▄ █ ▀ █ ██▄ █ ▀ █
28
26
 
29
27
  Project: my-app
30
- Sessions: 0 recent | Memories: 0 | Tasks: 0 pending
31
- ```
32
-
33
- Since no overview exists, Eagle Mem prompts Claude to build one on your first message. After that, every session starts with full context — you don't do anything.
34
-
35
- **What happens automatically:**
36
- - Every Claude turn end: session summary saved
37
- - Every tool use: file touches recorded, Claude's memories/plans/tasks mirrored
38
- - Every session start (including after `/compact`): overview + summaries + memories + tasks injected
39
- - Every prompt: FTS5 searches past sessions for relevant context
40
-
41
- ## Existing project
42
-
43
- If you've been using Claude Code on a project and want to backfill everything:
44
-
45
- ```bash
46
- eagle-mem refresh .
28
+ Sessions: 5 recent | Memories: 3 | Tasks: 2 pending
29
+ Last: Added auth middleware with JWT validation
47
30
  ```
48
31
 
49
- This runs three steps:
50
- 1. **Scan** analyzes your codebase structure (languages, frameworks, entry points)
51
- 2. **Index** chunks source files into FTS5-searchable pieces
52
- 3. **Memory sync** imports all existing Claude Code memories, plans, and tasks
32
+ **3. That's it.** Everything else is automatic:
33
+ - Session summaries captured on every Claude turn
34
+ - Claude's memories, plans, and tasks mirrored into Eagle Mem
35
+ - Full context re-injected after every `/compact`, `/clear`, or new session
36
+ - Past sessions searched on every prompt via FTS5
53
37
 
54
- Now open Claude Code. Eagle Mem injects your full history from the start.
38
+ > **Have existing Claude Code history?** Run `eagle-mem refresh` inside your project directory to backfill — it scans your codebase, indexes source files, and imports all existing memories, plans, and tasks.
55
39
 
56
40
  ## Day-to-day usage
57
41
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "eagle-mem",
3
- "version": "2.0.3",
3
+ "version": "2.0.4",
4
4
  "description": "Persistent memory for Claude Code — SQLite + FTS5, no daemon, no bloat",
5
5
  "bin": {
6
6
  "eagle-mem": "bin/eagle-mem"