brain-memory 0.1.0-beta.3 → 0.1.0-beta.5

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.
@@ -0,0 +1,220 @@
1
+ # /brain:sync — Cloud Sync
2
+
3
+ You are managing cloud synchronization for the Brain Memory system. This enables manual push/pull of `.brain/` memories to Dropbox, Google Drive, or OneDrive.
4
+
5
+ **CRITICAL RULES:**
6
+ - NEVER auto-sync — always require explicit user action
7
+ - NEVER silently overwrite files — always show a preview first
8
+ - NEVER display OAuth tokens, credentials, or secrets in output
9
+ - ALWAYS show what will change before executing push/pull
10
+
11
+ ## Subcommands
12
+
13
+ Parse the user's input to determine the subcommand:
14
+ - `login [provider]` → Setup OAuth + configure sync
15
+ - `push` → Upload local changes to cloud
16
+ - `pull` → Download remote changes to local
17
+ - `status` → Show sync state and pending changes
18
+ - `logout` → Remove credentials and disconnect
19
+ - `resolve [file]` → Resolve a sync conflict
20
+
21
+ If no subcommand is given, show available subcommands.
22
+
23
+ ---
24
+
25
+ ## `/brain:sync login [provider]`
26
+
27
+ ### Steps
28
+
29
+ 1. **Check prerequisites:**
30
+ - Verify `.brain/` exists. If not, suggest `/brain:init` first.
31
+ - Check if sync is already configured (`.brain/.sync/config.json`). If so, ask if they want to reconfigure.
32
+
33
+ 2. **Select provider** (if not specified):
34
+ - Present options: `dropbox`, `google-drive`, `onedrive`
35
+ - Explain each briefly:
36
+ - **Dropbox**: Simplest setup, App Folder isolation
37
+ - **Google Drive**: Uses hidden appDataFolder (invisible in Drive UI)
38
+ - **OneDrive**: Microsoft Graph API, App Folder isolation
39
+
40
+ 3. **Get OAuth Client ID:**
41
+ - Explain that Brain Memory requires the user to register their own OAuth app
42
+ - Provide provider-specific instructions:
43
+
44
+ **Dropbox:**
45
+ - Go to https://www.dropbox.com/developers/apps
46
+ - Create app → Scoped access → App folder → Name it "BrainMemory"
47
+ - Under Permissions, enable: `files.metadata.read`, `files.metadata.write`, `files.content.read`, `files.content.write`
48
+ - Copy the App Key (this is the client ID)
49
+ - Add `http://127.0.0.1` to Redirect URIs (any port)
50
+
51
+ **Google Drive:**
52
+ - Go to https://console.cloud.google.com → Create project
53
+ - Enable "Google Drive API"
54
+ - Create OAuth 2.0 credentials → Desktop app
55
+ - Copy the Client ID
56
+ - Add `http://127.0.0.1` to Authorized redirect URIs
57
+
58
+ **OneDrive:**
59
+ - Go to https://portal.azure.com → App registrations
60
+ - New registration → Personal Microsoft accounts
61
+ - Add redirect URI: `http://localhost` (Mobile and desktop applications)
62
+ - Copy Application (client) ID
63
+
64
+ 4. **Ask for Client ID** from the user.
65
+
66
+ 5. **Ask about encryption** (optional):
67
+ - "Would you like to encrypt memories before uploading? (recommended for sensitive data)"
68
+ - If yes, ask for a passphrase (will be needed on every push/pull and on other devices)
69
+
70
+ 6. **Run OAuth flow:**
71
+ - Use `setupSync()` from `src/sync/sync-engine.js`
72
+ - This will open the browser for authorization
73
+ - If in SSH/headless environment, offer Device Code Flow as alternative
74
+
75
+ 7. **Show result:**
76
+ ```
77
+ ✓ Cloud sync configured!
78
+ Provider: [provider]
79
+ Account: [email/name]
80
+ Encryption: [enabled/disabled]
81
+ Remote files: [count]
82
+
83
+ Use /brain:sync push to upload your memories.
84
+ Use /brain:sync pull to download from cloud.
85
+ ```
86
+
87
+ ---
88
+
89
+ ## `/brain:sync push`
90
+
91
+ ### Steps
92
+
93
+ 1. **Check sync is configured.** If not, suggest `/brain:sync login`.
94
+
95
+ 2. **Preview changes** (always show before executing):
96
+ - Use `push()` with `{ dryRun: true }` from `src/sync/sync-engine.js`
97
+ - Display summary:
98
+ ```
99
+ 📤 Push Preview:
100
+ Upload: [count] files ([new] new, [modified] modified)
101
+ Delete: [count] files (deleted locally)
102
+ Skip: [count] unchanged
103
+ ⚠️ Conflicts: [count] (modified both locally and remotely)
104
+ ```
105
+ - If there are conflicts, list them and explain options
106
+
107
+ 3. **Ask for confirmation** before proceeding.
108
+
109
+ 4. **Execute push:**
110
+ - Use `push()` from `src/sync/sync-engine.js`
111
+ - Show progress for each file
112
+ - Show final results:
113
+ ```
114
+ ✓ Push complete!
115
+ Uploaded: [count] files
116
+ Deleted: [count] files
117
+ Conflicts: [count] (use /brain:sync resolve to fix)
118
+ Errors: [count]
119
+ ```
120
+
121
+ ---
122
+
123
+ ## `/brain:sync pull`
124
+
125
+ ### Steps
126
+
127
+ 1. **Check sync is configured.**
128
+
129
+ 2. **Preview changes** (always show before executing):
130
+ - Use `pull()` with `{ dryRun: true }`
131
+ - Display summary:
132
+ ```
133
+ 📥 Pull Preview:
134
+ Download: [count] files ([new] new, [modified] modified)
135
+ Delete: [count] files (deleted remotely)
136
+ Skip: [count] unchanged
137
+ ⚠️ Conflicts: [count]
138
+ ```
139
+
140
+ 3. **Ask for confirmation.**
141
+
142
+ 4. **Execute pull:**
143
+ - Use `pull()` from `src/sync/sync-engine.js`
144
+ - Show results:
145
+ ```
146
+ ✓ Pull complete!
147
+ Downloaded: [count] files
148
+ Deleted: [count] files
149
+ Conflicts: [count]
150
+ Errors: [count]
151
+ ```
152
+
153
+ ---
154
+
155
+ ## `/brain:sync status`
156
+
157
+ ### Steps
158
+
159
+ 1. **Read sync status** using `syncStatus()` from `src/sync/sync-engine.js`
160
+
161
+ 2. **Display dashboard:**
162
+ ```
163
+ ☁️ Cloud Sync Status
164
+ ─────────────────────
165
+ Provider: [provider]
166
+ Account: [account]
167
+ Connected: [yes/no]
168
+ Encryption: [enabled/disabled]
169
+ Last Sync: [timestamp or "never"]
170
+ Tracked Files: [count]
171
+ Pending Changes:[count] local files modified since last sync
172
+
173
+ Conflicts: [count]
174
+ [list conflict files if any]
175
+ ```
176
+
177
+ ---
178
+
179
+ ## `/brain:sync logout`
180
+
181
+ ### Steps
182
+
183
+ 1. **Show current config** (provider, account).
184
+ 2. **Ask for confirmation:** "This will remove stored credentials. Your cloud data will NOT be deleted."
185
+ 3. **Execute:** Use `logout()` from `src/sync/sync-engine.js`
186
+ 4. **Confirm:** "✓ Logged out from [provider]. Credentials removed."
187
+
188
+ ---
189
+
190
+ ## `/brain:sync resolve [file]`
191
+
192
+ ### Steps
193
+
194
+ 1. **List conflicts** if no file specified using `listConflicts()`.
195
+
196
+ 2. **For a specific file:**
197
+ - Show the conflict details (reason, local hash, remote hash)
198
+ - Present resolution options:
199
+ - **keep-local**: Push your local version (overwrites remote)
200
+ - **keep-remote**: Pull the remote version (overwrites local)
201
+ - **keep-both**: Save local as `filename.local.ext`, pull remote as `filename.ext`
202
+
203
+ 3. **Execute resolution** using `resolveConflict()` from `src/sync/sync-engine.js`
204
+
205
+ 4. **Show result:**
206
+ ```
207
+ ✓ Conflict resolved for [file]
208
+ Action: [description]
209
+ ```
210
+
211
+ ---
212
+
213
+ ## Key Implementation Notes
214
+
215
+ - All sync functions are in `src/sync/sync-engine.js`
216
+ - Crypto utilities in `src/sync/crypto-utils.js`
217
+ - OAuth in `src/sync/oauth.js`
218
+ - Provider implementations in `src/sync/providers/`
219
+ - Sync state stored in `.brain/.sync/` (never synced to cloud)
220
+ - Uses three-way diff: local state vs remote state vs last-known sync state
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "brain-memory",
3
- "version": "0.1.0-beta.3",
3
+ "version": "0.1.0-beta.5",
4
4
  "description": "A brain-inspired hierarchical memory system for AI coding agents. Deep nested file structure that mimics human memory with time-decay and strength-based recall.",
5
5
  "keywords": [
6
6
  "claude-code",
@@ -9,7 +9,11 @@
9
9
  "memory",
10
10
  "ai-agent",
11
11
  "context-engineering",
12
- "hierarchical-memory"
12
+ "hierarchical-memory",
13
+ "neuroscience",
14
+ "spaced-repetition",
15
+ "file-based",
16
+ "slash-commands"
13
17
  ],
14
18
  "author": {
15
19
  "name": "Onur Karali",
@@ -27,7 +31,6 @@
27
31
  "commands/",
28
32
  "prompts/",
29
33
  "templates/",
30
- "hooks/",
31
34
  "src/",
32
35
  "README.md",
33
36
  "LICENSE"
@@ -37,7 +40,12 @@
37
40
  "url": "git+https://github.com/onurkarali/brain.git"
38
41
  },
39
42
  "scripts": {
40
- "test": "node --test test/index-manager.test.js test/scorer.test.js test/functional.test.js test/sunshine.test.js test/stress.test.js"
43
+ "test": "node --test test/index-manager.test.js test/scorer.test.js test/functional.test.js test/sunshine.test.js test/stress.test.js test/oauth.test.js test/sync-provider.test.js test/sync-engine.test.js test/install.test.js test/prompts.test.js",
44
+ "prerelease": "npm test",
45
+ "release:beta": "npm version prerelease --preid beta && npm publish --tag beta && npm dist-tag add brain-memory@$(node -p \"require('./package.json').version\") latest",
46
+ "release:patch": "npm version patch && npm publish",
47
+ "release:minor": "npm version minor && npm publish",
48
+ "release:major": "npm version major && npm publish"
41
49
  },
42
50
  "license": "MIT",
43
51
  "engines": {
package/prompts/claude.md CHANGED
@@ -58,10 +58,59 @@ Memories store their encoding context (project, topics, task type). During recal
58
58
  - `/brain:sunshine [target]` — Deep forensic erasure — trace and remove all references to a memory
59
59
  - `/brain:sleep [scope]` — Full maintenance cycle: replay, synaptic homeostasis, knowledge propagation, semantic crystallization, reorganize, consolidate, prune, REM dreaming, and expertise detection
60
60
  - `/brain:status` — Dashboard with brain health overview
61
+ - `/brain:sync [subcommand]` — Cloud sync: push/pull memories to Dropbox, Google Drive, or OneDrive
61
62
 
62
- ## Auto-Memorize Guidance
63
+ ## Session Start Behavior
63
64
 
64
- At the end of significant sessions, consider suggesting `/brain:memorize` to the user if important decisions, learnings, or insights occurred during the conversation. Do NOT automatically memorize without the user's awareness.
65
+ **IMPORTANT: Perform these steps automatically at the beginning of every session.**
66
+
67
+ If `.brain/index.json` exists in the current project:
68
+
69
+ 1. **Read the index** to understand the current brain state (memory count, categories)
70
+ 2. **Identify high-value memories** — the top 3-5 memories by effective strength that are relevant to the current project context
71
+ 3. **Silently internalize** these memories so you can reference them naturally during the session — do NOT dump memory contents
72
+ 4. **Check review queue** — read `.brain/review-queue.json` if it exists for memories due for review
73
+ 5. **Capture session context** — note the current project name, inferred topics, and task type for context-dependent recall
74
+ 6. **Output a brief status** (1-3 lines):
75
+
76
+ If memories are due for review:
77
+ ```
78
+ 🧠 Brain active — <N> memories loaded (<M> in current project context)
79
+ 📋 <X> memories due for review — run /brain:review
80
+ ```
81
+
82
+ Otherwise:
83
+ ```
84
+ 🧠 Brain active — <N> memories loaded (<M> in current project context)
85
+ ```
86
+
87
+ If any frequently-used memories (access_count >= 3) have confidence < 0.5:
88
+ ```
89
+ ⚠️ <N> frequently-used memories have low confidence — consider verifying
90
+ ```
91
+
92
+ **The goal is ambient awareness** — know about past decisions, learnings, and preferences without reciting them. When a situation arises where a past memory is relevant, naturally reference it.
93
+
94
+ ## Session End Behavior
95
+
96
+ When a session is ending or the user signals they are done, evaluate whether the session contained:
97
+ - **Decisions** — Architecture choices, technology selections, trade-off resolutions
98
+ - **Learnings** — New patterns, debugging insights, API discoveries
99
+ - **Insights** — Realizations about the codebase, project, or process
100
+ - **Experiences** — Significant events like incidents, deployments, milestones
101
+ - **Goals** — New objectives discussed or planned
102
+
103
+ If the session contained meaningful content in any of these categories, suggest:
104
+ ```
105
+ 💡 This session contained notable <type(s)>. Would you like to store them as brain memories?
106
+ Run /brain:memorize to capture them before this context is lost.
107
+ ```
108
+
109
+ **Rules:**
110
+ - Do NOT auto-memorize without user consent
111
+ - Do NOT prompt for trivial sessions (quick fixes, typo corrections, simple questions)
112
+ - Only suggest when there is genuinely valuable context worth preserving
113
+ - Always save session context to `.brain/contexts.json` regardless (append a session summary, keep last 20 entries)
65
114
 
66
115
  ## When Recalling Memories
67
116
 
@@ -73,3 +122,7 @@ When the user asks you to "remember" something, or when context from past sessio
73
122
  5. Apply spaced reinforcement (spacing-aware boost) and improve decay rate
74
123
  6. Strengthen Hebbian links between co-retrieved memories
75
124
  7. If no active matches, search the archive (`.brain/_archived/`)
125
+
126
+ ## Cloud Sync
127
+
128
+ Brain memories can be synced across devices via `/brain:sync`. Supports Dropbox, Google Drive, and OneDrive with optional AES-256-GCM encryption. Sync is always manual (push/pull) — never automatic. Run `/brain:sync login` to set up, then use `/brain:sync push` and `/brain:sync pull` to keep memories in sync.
package/prompts/gemini.md CHANGED
@@ -59,10 +59,59 @@ Commands are available via `/brain:` prefix:
59
59
  - `/brain:sunshine [target]` — Deep forensic erasure — trace and remove all references to a memory
60
60
  - `/brain:sleep [scope]` — Full maintenance cycle: replay, synaptic homeostasis, knowledge propagation, semantic crystallization, reorganize, consolidate, prune, REM dreaming, and expertise detection
61
61
  - `/brain:status` — Dashboard with brain health overview
62
+ - `/brain:sync [subcommand]` — Cloud sync: push/pull memories to Dropbox, Google Drive, or OneDrive
62
63
 
63
- ## Auto-Memorize Guidance
64
+ ## Session Start Behavior
64
65
 
65
- At the end of significant sessions, consider suggesting `/brain:memorize` to the user if important decisions, learnings, or insights occurred during the conversation. Do NOT automatically memorize without the user's awareness.
66
+ **IMPORTANT: Perform these steps automatically at the beginning of every session.**
67
+
68
+ If `.brain/index.json` exists in the current project:
69
+
70
+ 1. **Read the index** to understand the current brain state (memory count, categories)
71
+ 2. **Identify high-value memories** — the top 3-5 memories by effective strength that are relevant to the current project context
72
+ 3. **Silently internalize** these memories so you can reference them naturally during the session — do NOT dump memory contents
73
+ 4. **Check review queue** — read `.brain/review-queue.json` if it exists for memories due for review
74
+ 5. **Capture session context** — note the current project name, inferred topics, and task type for context-dependent recall
75
+ 6. **Output a brief status** (1-3 lines):
76
+
77
+ If memories are due for review:
78
+ ```
79
+ 🧠 Brain active — <N> memories loaded (<M> in current project context)
80
+ 📋 <X> memories due for review — run /brain:review
81
+ ```
82
+
83
+ Otherwise:
84
+ ```
85
+ 🧠 Brain active — <N> memories loaded (<M> in current project context)
86
+ ```
87
+
88
+ If any frequently-used memories (access_count >= 3) have confidence < 0.5:
89
+ ```
90
+ ⚠️ <N> frequently-used memories have low confidence — consider verifying
91
+ ```
92
+
93
+ **The goal is ambient awareness** — know about past decisions, learnings, and preferences without reciting them. When a situation arises where a past memory is relevant, naturally reference it.
94
+
95
+ ## Session End Behavior
96
+
97
+ When a session is ending or the user signals they are done, evaluate whether the session contained:
98
+ - **Decisions** — Architecture choices, technology selections, trade-off resolutions
99
+ - **Learnings** — New patterns, debugging insights, API discoveries
100
+ - **Insights** — Realizations about the codebase, project, or process
101
+ - **Experiences** — Significant events like incidents, deployments, milestones
102
+ - **Goals** — New objectives discussed or planned
103
+
104
+ If the session contained meaningful content in any of these categories, suggest:
105
+ ```
106
+ 💡 This session contained notable <type(s)>. Would you like to store them as brain memories?
107
+ Run /brain:memorize to capture them before this context is lost.
108
+ ```
109
+
110
+ **Rules:**
111
+ - Do NOT auto-memorize without user consent
112
+ - Do NOT prompt for trivial sessions (quick fixes, typo corrections, simple questions)
113
+ - Only suggest when there is genuinely valuable context worth preserving
114
+ - Always save session context to `.brain/contexts.json` regardless (append a session summary, keep last 20 entries)
66
115
 
67
116
  ## When Recalling Memories
68
117
 
@@ -74,3 +123,7 @@ When the user asks you to "remember" something, or when context from past sessio
74
123
  5. Apply spaced reinforcement (spacing-aware boost) and improve decay rate
75
124
  6. Strengthen Hebbian links between co-retrieved memories
76
125
  7. If no active matches, search the archive (`.brain/_archived/`)
126
+
127
+ ## Cloud Sync
128
+
129
+ Brain memories can be synced across devices via `/brain:sync`. Supports Dropbox, Google Drive, and OneDrive with optional AES-256-GCM encryption. Sync is always manual (push/pull) — never automatic. Run `/brain:sync login` to set up, then use `/brain:sync push` and `/brain:sync pull` to keep memories in sync.
package/prompts/openai.md CHANGED
@@ -59,10 +59,59 @@ Brain skills are available via `/brain-` prefix:
59
59
  - `/brain-sunshine [target]` — Deep forensic erasure — trace and remove all references to a memory
60
60
  - `/brain-sleep [scope]` — Full maintenance cycle: replay, synaptic homeostasis, knowledge propagation, semantic crystallization, reorganize, consolidate, prune, REM dreaming, and expertise detection
61
61
  - `/brain-status` — Dashboard with brain health overview
62
+ - `/brain-sync [subcommand]` — Cloud sync: push/pull memories to Dropbox, Google Drive, or OneDrive
62
63
 
63
- ## Auto-Memorize Guidance
64
+ ## Session Start Behavior
64
65
 
65
- At the end of significant sessions, consider suggesting `/brain-memorize` to the user if important decisions, learnings, or insights occurred during the conversation. Do NOT automatically memorize without the user's awareness.
66
+ **IMPORTANT: Perform these steps automatically at the beginning of every session.**
67
+
68
+ If `.brain/index.json` exists in the current project:
69
+
70
+ 1. **Read the index** to understand the current brain state (memory count, categories)
71
+ 2. **Identify high-value memories** — the top 3-5 memories by effective strength that are relevant to the current project context
72
+ 3. **Silently internalize** these memories so you can reference them naturally during the session — do NOT dump memory contents
73
+ 4. **Check review queue** — read `.brain/review-queue.json` if it exists for memories due for review
74
+ 5. **Capture session context** — note the current project name, inferred topics, and task type for context-dependent recall
75
+ 6. **Output a brief status** (1-3 lines):
76
+
77
+ If memories are due for review:
78
+ ```
79
+ 🧠 Brain active — <N> memories loaded (<M> in current project context)
80
+ 📋 <X> memories due for review — run /brain-review
81
+ ```
82
+
83
+ Otherwise:
84
+ ```
85
+ 🧠 Brain active — <N> memories loaded (<M> in current project context)
86
+ ```
87
+
88
+ If any frequently-used memories (access_count >= 3) have confidence < 0.5:
89
+ ```
90
+ ⚠️ <N> frequently-used memories have low confidence — consider verifying
91
+ ```
92
+
93
+ **The goal is ambient awareness** — know about past decisions, learnings, and preferences without reciting them. When a situation arises where a past memory is relevant, naturally reference it.
94
+
95
+ ## Session End Behavior
96
+
97
+ When a session is ending or the user signals they are done, evaluate whether the session contained:
98
+ - **Decisions** — Architecture choices, technology selections, trade-off resolutions
99
+ - **Learnings** — New patterns, debugging insights, API discoveries
100
+ - **Insights** — Realizations about the codebase, project, or process
101
+ - **Experiences** — Significant events like incidents, deployments, milestones
102
+ - **Goals** — New objectives discussed or planned
103
+
104
+ If the session contained meaningful content in any of these categories, suggest:
105
+ ```
106
+ 💡 This session contained notable <type(s)>. Would you like to store them as brain memories?
107
+ Run /brain-memorize to capture them before this context is lost.
108
+ ```
109
+
110
+ **Rules:**
111
+ - Do NOT auto-memorize without user consent
112
+ - Do NOT prompt for trivial sessions (quick fixes, typo corrections, simple questions)
113
+ - Only suggest when there is genuinely valuable context worth preserving
114
+ - Always save session context to `.brain/contexts.json` regardless (append a session summary, keep last 20 entries)
66
115
 
67
116
  ## When Recalling Memories
68
117
 
@@ -74,3 +123,7 @@ When the user asks you to "remember" something, or when context from past sessio
74
123
  5. Apply spaced reinforcement (spacing-aware boost) and improve decay rate
75
124
  6. Strengthen Hebbian links between co-retrieved memories
76
125
  7. If no active matches, search the archive (`.brain/_archived/`)
126
+
127
+ ## Cloud Sync
128
+
129
+ Brain memories can be synced across devices via `/brain-sync`. Supports Dropbox, Google Drive, and OneDrive with optional AES-256-GCM encryption. Sync is always manual (push/pull) — never automatic. Run `/brain-sync login` to set up, then use `/brain-sync push` and `/brain-sync pull` to keep memories in sync.