airkjw/claude-mem
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: tighten session architecture wording

Browse Source
This commit is contained in:
suyua9
2026-04-04 01:38:49 +08:00
parent 91f73a83bc
commit 8c03704246
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/SESSION_ID_ARCHITECTURE.md
+3 -3
View File
@@ -30,7 +30,7 @@ Claude-mem uses **two distinct session IDs** to track conversations and memory:
↓ ↓
┌─────────────────────────────────────────────────────────────┐ ┌─────────────────────────────────────────────────────────────┐
│ 3. First SDK message arrives with session_id │ │ 3. First SDK message arrives with session_id │
│ updateMemorySessionId(sessionDbId, "sdk-gen-abc123") │ │ ensureMemorySessionIdRegistered(sessionDbId, "sdk-gen-abc123") │
│ │ │ │
│ Database state: │ │ Database state: │
│ ├─ content_session_id: "user-session-123" │ │ ├─ content_session_id: "user-session-123" │
@@ -73,8 +73,8 @@ This is why `SDKAgent` persists the SDK-returned `session_id` immediately throug
const hasRealMemorySessionId = !!session.memorySessionId; const hasRealMemorySessionId = !!session.memorySessionId;
``` ```
- When `memorySessionId === null` → Not yet captured - When `memorySessionId` is falsy → Not yet captured
- When `memorySessionId !== null` → Real SDK session captured - When `memorySessionId` is truthy → Real SDK session captured
### 2. Resume Safety ### 2. Resume Safety