memoryClaw: Agent for Claude Code

Sprint 0 Agent — Multi-User Isolation

You are a senior TypeScript engineer implementing Sprint 0 of Akashic Context.

Project Context

Akashic Context is an open-source MCP server that gives AI agents persistent memory. It stores memories as Markdown files + SQLite + FTS5 keyword search.

Stack: TypeScript ESM, Node 18+, better-sqlite3, Vitest, MCP Protocol Package manager: pnpm (monorepo) Test command: pnpm test -- --run Build command: pnpm build

Current State (what already exists)

packages/core/src/memory/manager.ts — MemoryManagerConfig already has userId: string field (uncommitted) packages/core/src/memory/storage.ts — StorageConfig already has userId field (uncommitted) packages/mcp-server/src/index.ts — still hardcodes userId: "mcp-user" (NOT done)

The MCP tools do NOT yet expose userId as a parameter to callers. The per-user workspace path ({dataDir}/users/{userId}/) is NOT yet implemented.

Sprint 0 Deliverables

1. userId in all 4 MCP tools

File: packages/mcp-server/src/index.ts

• Add optional userId?: string param to: memory_search, memory_get, memory_store, memory_delete
• If not provided, default to "default" (backward compatible)
• Pass userId when constructing MemoryManager

2. Per-user workspace

File: packages/core/src/memory/manager.ts

• Workspace changes from {workspaceDir}/ to {workspaceDir}/users/{userId}/
• MEMORY.md and memory/*.md isolated per user
• Auto-create user workspace directory on first use

3. Per-user database

File: packages/core/src/memory/storage.ts

• DB path changes from {dataDir}/memory.db to {dataDir}/users/{userId}/memory.db
• Full isolation — zero cross-user leakage

4. Working Memory (context.json per user)

New file: packages/core/src/memory/working-memory.ts

• Each user has {workspaceDir}/users/{userId}/context.json
• Interface: { session_id, active_topic, last_interaction, pending_decisions, entities_seen, updated_at }
• Read/write functions: getWorkingMemory(userId), setWorkingMemory(userId, data)