chore: bump version to 10.2.5

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
   "plugins": [
     {
       "name": "claude-mem",
-      "version": "9.0.17",
+      "version": "10.2.5",
       "source": "./plugin",
       "description": "Persistent memory system for Claude Code - context compression across sessions"
     }

.claude-plugin/plugin.json

@@ -0,0 +1,17 @@
+{
+  "name": "claude-mem",
+  "version": "9.0.6",
+  "description": "Persistent memory system for Claude Code - seamlessly preserve context across sessions",
+  "author": {
+    "name": "Alex Newman"
+  },
+  "repository": "https://github.com/thedotmack/claude-mem",
+  "license": "AGPL-3.0",
+  "keywords": [
+    "memory",
+    "context",
+    "persistence",
+    "hooks",
+    "mcp"
+  ]
+}

.claude/plans/2026-01-05-fix-81-test-failures.md

@@ -1,299 +0,0 @@
-# Plan: Fix 81 Test Failures from Incomplete Logger Mocks
-
-## Problem Summary
-
-**Root Cause**: NOT circular dependency (which is handled gracefully), but **incomplete logger mocks** that pollute across test files when Bun runs tests in alphabetical order.
-
-When `tests/context/` runs before `tests/utils/`, the incomplete mocks replace the real logger module globally, causing subsequent tests to fail with `TypeError: logger.formatTool is not a function`.
-
-## Phase 0: Documentation Discovery (COMPLETED)
-
-### Sources Consulted
-- `src/utils/logger.ts` - Full logger interface (lines 136, 289-373)
-- `tests/context/context-builder.test.ts` - Mock pattern (lines 22-29)
-- `tests/context/observation-compiler.test.ts` - Mock pattern (lines 4-10)
-- `tests/server/server.test.ts` - Mock pattern (lines 4-11)
-- `tests/server/error-handler.test.ts` - Mock pattern (lines 5-12)
-- `tests/worker/agents/response-processor.test.ts` - Mock pattern (lines 32-39)
-
-### Logger Methods (Complete List)
-All 11 methods that must be in any logger mock:
-1. `formatTool(toolName: string, toolInput?: any): string` (line 136)
-2. `debug(component, message, context?, data?): void` (line 289)
-3. `info(component, message, context?, data?): void` (line 293)
-4. `warn(component, message, context?, data?): void` (line 297)
-5. `error(component, message, context?, data?): void` (line 301)
-6. `dataIn(component, message, context?, data?): void` (line 308)
-7. `dataOut(component, message, context?, data?): void` (line 315)
-8. `success(component, message, context?, data?): void` (line 322)
-9. `failure(component, message, context?, data?): void` (line 329)
-10. `timing(component, message, durationMs, context?): void` (line 336)
-11. `happyPathError<T>(message, context?): T` (line 362)
-
-### Files Requiring Updates
-1. `tests/context/observation-compiler.test.ts` (lines 4-10)
-2. `tests/context/context-builder.test.ts` (lines 22-29)
-3. `tests/server/server.test.ts` (lines 4-11)
-4. `tests/server/error-handler.test.ts` (lines 5-12)
-5. `tests/worker/agents/response-processor.test.ts` (lines 32-39)
-
----
-
-## Phase 1: Create Shared Logger Mock Utility
-
-### Objective
-Create a reusable complete logger mock to avoid duplication and ensure consistency.
-
-### Implementation
-
-**Create new file**: `tests/test-utils/mock-logger.ts`
-
-```typescript
-/**
- * Complete logger mock for tests.
- * Includes ALL logger methods to prevent mock pollution across test files.
- */
-import { mock } from 'bun:test';
-
-export function createMockLogger() {
-  return {
-    logger: {
-      // Core logging methods
-      debug: mock(() => {}),
-      info: mock(() => {}),
-      warn: mock(() => {}),
-      error: mock(() => {}),
-
-      // Data flow logging
-      dataIn: mock(() => {}),
-      dataOut: mock(() => {}),
-
-      // Status logging
-      success: mock(() => {}),
-      failure: mock(() => {}),
-
-      // Performance logging
-      timing: mock(() => {}),
-
-      // Tool formatting - returns string
-      formatTool: mock((toolName: string, _toolInput?: any) => toolName),
-
-      // Error helper - returns the message
-      happyPathError: mock((message: string, _context?: any) => message),
-    },
-  };
-}
-```
-
-### Verification Checklist
-- [ ] File created at `tests/test-utils/mock-logger.ts`
-- [ ] All 11 logger methods included
-- [ ] `formatTool` returns string (not void)
-- [ ] `happyPathError` returns the message (not void)
-- [ ] File compiles without errors: `bunx tsc --noEmit tests/test-utils/mock-logger.ts`
-
-### Anti-Patterns to Avoid
-- ❌ Don't forget `formatTool` - it returns a string, not void
-- ❌ Don't forget `happyPathError` - it's generic and returns the message
-- ❌ Don't use `() => {}` for methods that return values
-
----
-
-## Phase 2: Update Affected Test Files
-
-### Objective
-Replace incomplete logger mocks with the complete shared mock.
-
-### Files to Update (5 total)
-
-#### 2.1 `tests/context/observation-compiler.test.ts`
-
-**Current (lines 4-10)**:
-```typescript
-mock.module('../../src/utils/logger.js', () => ({
-  logger: {
-    debug: mock(() => {}),
-    failure: mock(() => {}),
-    error: mock(() => {}),
-  },
-}));
-```
-
-**Replace with**:
-```typescript
-import { createMockLogger } from '../test-utils/mock-logger.js';
-
-mock.module('../../src/utils/logger.js', () => createMockLogger());
-```
-
-#### 2.2 `tests/context/context-builder.test.ts`
-
-**Current (lines 22-29)**:
-```typescript
-mock.module('../../src/utils/logger.js', () => ({
-  logger: {
-    debug: mock(() => {}),
-    failure: mock(() => {}),
-    error: mock(() => {}),
-    info: mock(() => {}),
-  },
-}));
-```
-
-**Replace with**:
-```typescript
-import { createMockLogger } from '../test-utils/mock-logger.js';
-
-mock.module('../../src/utils/logger.js', () => createMockLogger());
-```
-
-#### 2.3 `tests/server/server.test.ts`
-
-**Current (lines 4-11)**:
-```typescript
-mock.module('../../src/utils/logger.js', () => ({
-  logger: {
-    info: () => {},
-    debug: () => {},
-    warn: () => {},
-    error: () => {},
-  },
-}));
-```
-
-**Replace with**:
-```typescript
-import { createMockLogger } from '../test-utils/mock-logger.js';
-
-mock.module('../../src/utils/logger.js', () => createMockLogger());
-```
-
-#### 2.4 `tests/server/error-handler.test.ts`
-
-**Current (lines 5-12)**:
-```typescript
-mock.module('../../src/utils/logger.js', () => ({
-  logger: {
-    info: () => {},
-    debug: () => {},
-    warn: () => {},
-    error: () => {},
-  },
-}));
-```
-
-**Replace with**:
-```typescript
-import { createMockLogger } from '../test-utils/mock-logger.js';
-
-mock.module('../../src/utils/logger.js', () => createMockLogger());
-```
-
-#### 2.5 `tests/worker/agents/response-processor.test.ts`
-
-**Current (lines 32-39)**:
-```typescript
-mock.module('../../../src/utils/logger.js', () => ({
-  logger: {
-    info: () => {},
-    debug: () => {},
-    warn: () => {},
-    error: () => {},
-  },
-}));
-```
-
-**Replace with**:
-```typescript
-import { createMockLogger } from '../../test-utils/mock-logger.js';
-
-mock.module('../../../src/utils/logger.js', () => createMockLogger());
-```
-
-### Verification Checklist
-- [ ] All 5 files updated with import statement
-- [ ] All 5 files use `createMockLogger()` instead of inline mock
-- [ ] Import paths are correct (relative to each file's location)
-- [ ] Each file still has `mock.module` BEFORE the module imports it mocks
-
-### Anti-Patterns to Avoid
-- ❌ Don't place import AFTER the mock.module call
-- ❌ Don't use wrong relative path (../test-utils vs ../../test-utils)
-- ❌ Don't forget the .js extension in imports
-
----
-
-## Phase 3: Verification
-
-### Objective
-Confirm all 81 failures are fixed.
-
-### Test Commands
-
-```bash
-# 1. Run individual test groups first
-bun test tests/context/
-bun test tests/server/
-bun test tests/utils/
-bun test tests/shared/
-bun test tests/worker/
-
-# 2. Run full suite
-bun test
-
-# 3. Verify specific test counts
-# Expected: 733+ tests pass (was 652 before)
-```
-
-### Verification Checklist
-- [ ] `bun test tests/context/` - all pass
-- [ ] `bun test tests/server/` - all pass
-- [ ] `bun test tests/utils/` - all pass (including 56 formatTool tests)
-- [ ] `bun test tests/shared/` - all pass (including 27 settings tests)
-- [ ] `bun test` - 730+ tests pass, 0 failures
-- [ ] No `TypeError: logger.formatTool is not a function` errors
-
-### Anti-Pattern Grep Checks
-
-```bash
-# Check no incomplete logger mocks remain
-grep -r "logger: {" tests/ --include="*.ts" | grep -v mock-logger
-
-# Verify all test files use createMockLogger
-grep -r "createMockLogger" tests/ --include="*.ts"
-```
-
----
-
-## Phase 4: Commit
-
-### Commit Message
-
-```
-fix(tests): complete logger mocks to prevent cross-test pollution
-
-The 81 test failures were caused by incomplete logger mocks that
-polluted the module cache when tests ran in alphabetical order.
-
-Changes:
-- Create shared mock-logger.ts with all 11 logger methods
-- Update 5 test files to use complete mock
-- Fix TypeError: logger.formatTool is not a function
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-
-Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
-```
-
----
-
-## Summary
-
-| Phase | Files Changed | Purpose |
-|-------|--------------|---------|
-| 1 | 1 new file | Create shared mock utility |
-| 2 | 5 files | Update to use shared mock |
-| 3 | 0 files | Verification only |
-| 4 | 0 files | Commit |
-
-**Total**: 6 files changed, fixing all 81 test failures.

.claude/plans/animated-installer.md

@@ -0,0 +1,371 @@
+# Comprehensive Claude-Mem Installer with @clack/prompts
+
+## Overview
+
+Build a beautiful, animated CLI installer for claude-mem using `@clack/prompts` (v1.0.1). Distributable via `npx claude-mem-installer` and `curl -fsSL https://install.cmem.ai | bash`. Replaces the need for users to manually clone, build, configure settings, and start the worker.
+
+**Worktree**: `feat/animated-installer` at `.claude/worktrees/animated-installer`
+
+---
+
+## Phase 0: Documentation & API Reference
+
+### Allowed APIs (@clack/prompts v1.0.1, ESM-only)
+
+| API | Signature | Use Case |
+|-----|-----------|----------|
+| `intro(title?)` | `void` | Opening banner |
+| `outro(message?)` | `void` | Completion message |
+| `cancel(message?)` | `void` | User cancelled |
+| `isCancel(value)` | `boolean` | Check if user pressed Ctrl+C |
+| `text(opts)` | `Promise<string \| symbol>` | API key input, port, data dir |
+| `password(opts)` | `Promise<string \| symbol>` | API key input (masked) |
+| `select(opts)` | `Promise<Value \| symbol>` | Provider, model, auth method |
+| `multiselect(opts)` | `Promise<Value[] \| symbol>` | IDE selection, observation types |
+| `confirm(opts)` | `Promise<boolean \| symbol>` | Enable Chroma, start worker |
+| `spinner()` | `SpinnerResult` | Installing deps, building, starting worker |
+| `progress(opts)` | `ProgressResult` | Multi-step installation progress |
+| `tasks(tasks[])` | `Promise<void>` | Sequential install steps |
+| `group(prompts, opts)` | `Promise<Results>` | Chain prompts with shared results |
+| `note(message, title)` | `void` | Display settings summary, next steps |
+| `log.info/success/warn/error(msg)` | `void` | Status messages |
+| `box(message, title, opts)` | `void` | Welcome box, completion summary |
+
+### Anti-Patterns
+- Do NOT use `require()` — package is ESM-only
+- Do NOT call prompts without TTY check first — hangs indefinitely in non-TTY
+- Do NOT forget `isCancel()` check after every prompt (or use `group()` with `onCancel`)
+- Do NOT use `chalk` — use `picocolors` (clack's dep) for consistency
+- `text()` has no numeric mode — validate manually for port numbers
+- `spinner.stop()` does not accept status codes — use `spinner.error()` for failures
+
+### Distribution Patterns
+- **npx**: `package.json` `bin` field → `"./dist/index.js"`, file needs `#!/usr/bin/env node`
+- **curl|bash**: Shell bootstrap downloads JS, runs `node script.js` directly (preserves TTY)
+- **esbuild**: Bundle to single ESM file, `platform: 'node'`, `banner` for shebang
+
+### Key Source Files to Reference
+- Settings defaults: `src/shared/SettingsDefaultsManager.ts` (lines 73-125)
+- Settings validation: `src/services/server/SettingsRoutes.ts`
+- Worker startup: `src/services/worker-service.ts` (lines 337-359)
+- Health check: `src/services/infrastructure/HealthMonitor.ts`
+- Plugin registration: `plugin/.claude-plugin/plugin.json`, `.claude-plugin/marketplace.json`
+- Marketplace sync: `scripts/sync-marketplace.cjs`
+- Cursor integration: `src/services/integrations/CursorHooksInstaller.ts`
+- Existing OpenClaw installer: `install/public/openclaw.sh` (reference for logic, not code to copy)
+
+---
+
+## Phase 1: Project Scaffolding
+
+**Goal**: Set up the installer package structure with build tooling.
+
+### Tasks
+
+1. **Create directory structure** in the worktree:
+   ```
+   installer/
+   ├── src/
+   │   ├── index.ts              # Entry point with TTY guard
+   │   ├── steps/
+   │   │   ├── welcome.ts        # intro + version check
+   │   │   ├── dependencies.ts   # bun, uv, git checks
+   │   │   ├── ide-selection.ts  # IDE picker + registration
+   │   │   ├── provider.ts       # AI provider + API key
+   │   │   ├── settings.ts       # Additional settings config
+   │   │   ├── install.ts        # Clone, build, register plugin
+   │   │   ├── worker.ts         # Start worker + health check
+   │   │   └── complete.ts       # Summary + next steps
+   │   └── utils/
+   │       ├── system.ts         # OS detection, command runner
+   │       ├── dependencies.ts   # bun/uv/git install helpers
+   │       └── settings-writer.ts # Write ~/.claude-mem/settings.json
+   ├── build.mjs                 # esbuild config
+   ├── package.json              # bin, type: module, deps
+   └── tsconfig.json
+   ```
+
+2. **Create `package.json`**:
+   ```json
+   {
+     "name": "claude-mem-installer",
+     "version": "1.0.0",
+     "type": "module",
+     "bin": { "claude-mem-installer": "./dist/index.js" },
+     "files": ["dist"],
+     "scripts": {
+       "build": "node build.mjs",
+       "dev": "node build.mjs && node dist/index.js"
+     },
+     "dependencies": {
+       "@clack/prompts": "^1.0.1",
+       "picocolors": "^1.1.1"
+     },
+     "devDependencies": {
+       "esbuild": "^0.24.0",
+       "typescript": "^5.7.0",
+       "@types/node": "^22.0.0"
+     },
+     "engines": { "node": ">=18.0.0" }
+   }
+   ```
+
+3. **Create `build.mjs`**:
+   - esbuild bundle: `entryPoints: ['src/index.ts']`, `format: 'esm'`, `platform: 'node'`, `target: 'node18'`
+   - Banner: `#!/usr/bin/env node`
+   - Output: `dist/index.js`
+
+4. **Create `tsconfig.json`**:
+   - `module: "ESNext"`, `target: "ES2022"`, `moduleResolution: "bundler"`
+
+5. **Run `npm install`** in installer/ directory
+
+### Verification
+- [ ] `node build.mjs` succeeds
+- [ ] `dist/index.js` exists with shebang
+- [ ] `node dist/index.js` runs (even if empty installer)
+
+---
+
+## Phase 2: Entry Point + Welcome Screen
+
+**Goal**: Create the main entry point with TTY detection and a beautiful welcome screen.
+
+### Tasks
+
+1. **`src/index.ts`** — Entry point:
+   - TTY guard: if `!process.stdin.isTTY`, print error directing user to `npx claude-mem-installer`, exit 1
+   - Import and call `runInstaller()` from steps
+   - Top-level catch → `p.cancel()` + exit 1
+
+2. **`src/steps/welcome.ts`** — Welcome step:
+   - `p.intro()` with styled title using picocolors: `" claude-mem installer "`
+   - Display version info via `p.log.info()`
+   - Check if already installed (detect `~/.claude-mem/settings.json` and `~/.claude/plugins/marketplaces/thedotmack/`)
+   - If upgrade detected, `p.confirm()`: "claude-mem is already installed. Upgrade?"
+   - `p.select()` for install mode: Fresh Install vs Upgrade vs Configure Only
+
+3. **`src/utils/system.ts`** — System utilities:
+   - `detectOS()`: returns 'macos' | 'linux' | 'windows'
+   - `commandExists(cmd)`: checks if command is in PATH
+   - `runCommand(cmd, args)`: executes shell command, returns { stdout, stderr, exitCode }
+   - `expandHome(path)`: resolves `~` to home directory
+
+### Verification
+- [ ] Running `node dist/index.js` shows intro banner
+- [ ] Ctrl+C triggers cancel message
+- [ ] Non-TTY (piped) shows error and exits
+
+---
+
+## Phase 3: Dependency Checks
+
+**Goal**: Check and install required dependencies (Bun, uv, git, Node.js version).
+
+### Tasks
+
+1. **`src/steps/dependencies.ts`** — Dependency checker:
+   - Use `p.tasks()` to check each dependency sequentially with animated spinners:
+     - **Node.js**: Verify >= 18.0.0 via `process.version`
+     - **git**: `commandExists('git')`, show install instructions per OS if missing
+     - **Bun**: Check PATH + common locations (`~/.bun/bin/bun`, `/usr/local/bin/bun`, `/opt/homebrew/bin/bun`). Min version 1.1.14. Offer to auto-install from `https://bun.sh/install`
+     - **uv**: Check PATH + common locations (`~/.local/bin/uv`, `~/.cargo/bin/uv`). Offer to auto-install from `https://astral.sh/uv/install.sh`
+   - For missing deps: `p.confirm()` to auto-install, or show manual instructions
+   - After install attempts, re-verify each dep
+
+2. **`src/utils/dependencies.ts`** — Install helpers:
+   - `installBun()`: downloads and runs bun install script
+   - `installUv()`: downloads and runs uv install script
+   - `findBinary(name, extraPaths[])`: searches PATH + known locations
+   - `checkVersion(binary, minVersion)`: parses `--version` output
+
+### Verification
+- [ ] Shows green checkmarks for found dependencies
+- [ ] Shows yellow warnings for missing deps with install option
+- [ ] Auto-install actually installs bun/uv when confirmed
+- [ ] Fails gracefully if git is missing (can't auto-install)
+
+---
+
+## Phase 4: IDE Selection & Provider Configuration
+
+**Goal**: Let user choose IDEs and configure AI provider with API keys.
+
+### Tasks
+
+1. **`src/steps/ide-selection.ts`** — IDE picker:
+   - `p.multiselect()` with options:
+     - Claude Code (default selected, hint: "recommended")
+     - Cursor
+     - Windsurf (hint: "coming soon", disabled: true)
+   - For Claude Code: explain plugin will be registered via marketplace
+   - For Cursor: explain hooks will be installed via CursorHooksInstaller pattern
+   - Store selections for later installation steps
+
+2. **`src/steps/provider.ts`** — AI provider configuration:
+   - `p.select()` for provider:
+     - **Claude** (hint: "recommended — uses your Claude subscription")
+     - **Gemini** (hint: "free tier available")
+     - **OpenRouter** (hint: "free models available")
+   - **If Claude selected**:
+     - `p.select()` for auth method: "CLI (Max Plan subscription)" vs "API Key"
+     - If API key: `p.password()` for key input
+   - **If Gemini selected**:
+     - `p.password()` for API key (required)
+     - `p.select()` for model: gemini-2.5-flash-lite (default), gemini-2.5-flash, gemini-3-flash-preview
+     - `p.confirm()` for rate limiting (default: true)
+   - **If OpenRouter selected**:
+     - `p.password()` for API key (required)
+     - `p.text()` for model (default: `xiaomi/mimo-v2-flash:free`)
+   - Validate API keys where possible (non-empty, format check)
+
+### Verification
+- [ ] Multiselect allows picking multiple IDEs
+- [ ] Provider selection shows correct follow-up prompts
+- [ ] API keys are masked during input
+- [ ] Cancel at any step triggers graceful exit
+
+---
+
+## Phase 5: Settings Configuration
+
+**Goal**: Configure additional settings with sensible defaults.
+
+### Tasks
+
+1. **`src/steps/settings.ts`** — Settings wizard:
+   - `p.confirm()`: "Use default settings?" (recommended) — if yes, skip detailed config
+   - If customizing, use `p.group()` for:
+     - **Worker port**: `p.text()` with default 37777, validate 1024-65535
+     - **Data directory**: `p.text()` with default `~/.claude-mem`
+     - **Context observations**: `p.text()` with default 50, validate 1-200
+     - **Log level**: `p.select()` — DEBUG, INFO (default), WARN, ERROR
+     - **Python version**: `p.text()` with default 3.13
+     - **Chroma vector search**: `p.confirm()` (default: true)
+       - If yes, `p.select()` mode: local (default) vs remote
+       - If remote: `p.text()` for host, port, `p.confirm()` for SSL
+   - Show settings summary via `p.note()` before proceeding
+
+2. **`src/utils/settings-writer.ts`** — Write settings:
+   - Build flat key-value settings object matching SettingsDefaultsManager schema
+   - Merge with existing settings if upgrading (preserve user customizations)
+   - Write to `~/.claude-mem/settings.json`
+   - Create `~/.claude-mem/` directory if it doesn't exist
+
+### Verification
+- [ ] Default settings mode skips all detailed prompts
+- [ ] Custom settings validates all inputs
+- [ ] Settings file written matches SettingsDefaultsManager schema exactly
+- [ ] Existing settings preserved on upgrade
+
+---
+
+## Phase 6: Installation Execution
+
+**Goal**: Clone repo, build plugin, register with IDEs, start worker.
+
+### Tasks
+
+1. **`src/steps/install.ts`** — Installation runner:
+   - Use `p.tasks()` for visual progress:
+     - **"Cloning claude-mem repository"**: `git clone --depth 1 https://github.com/thedotmack/claude-mem.git` to temp dir
+     - **"Installing dependencies"**: `npm install` in cloned repo
+     - **"Building plugin"**: `npm run build` in cloned repo
+     - **"Registering plugin"**: Copy plugin files to `~/.claude/plugins/marketplaces/thedotmack/`
+       - Create marketplace.json, plugin.json structure
+       - Register in `~/.claude/plugins/known_marketplaces.json`
+       - Add to `~/.claude/plugins/installed_plugins.json`
+       - Enable in `~/.claude/settings.json` under `enabledPlugins`
+     - **"Installing dependencies"** (in marketplace dir): `npm install`
+   - For Cursor (if selected):
+     - **"Configuring Cursor hooks"**: Run Cursor hooks installer logic
+     - Write hooks.json to `~/.cursor/` or project-level `.cursor/`
+     - Configure MCP in `.cursor/mcp.json`
+
+2. **`src/steps/worker.ts`** — Worker startup:
+   - Use `p.spinner()` for worker startup:
+     - Start worker: `bun plugin/scripts/worker-service.cjs` (from marketplace dir)
+     - Write PID file to `~/.claude-mem/worker.pid`
+   - Two-stage health check (copy pattern from OpenClaw installer):
+     - Stage 1: Poll `/api/health` — spinner message: "Starting worker service..."
+     - Stage 2: Poll `/api/readiness` — spinner message: "Initializing database..."
+     - Budget: 30 attempts, 1 second apart
+     - On success: `spinner.stop("Worker running on port {port}")`
+     - On failure: `spinner.error("Worker failed to start")`, show log path
+
+### Verification
+- [ ] Plugin files exist at `~/.claude/plugins/marketplaces/thedotmack/`
+- [ ] known_marketplaces.json updated
+- [ ] installed_plugins.json updated
+- [ ] settings.json has enabledPlugins entry
+- [ ] Worker responds to `/api/health` with 200
+- [ ] Worker responds to `/api/readiness` with 200
+
+---
+
+## Phase 7: Completion & Summary
+
+**Goal**: Show success screen with configuration summary and next steps.
+
+### Tasks
+
+1. **`src/steps/complete.ts`** — Completion screen:
+   - `p.note()` with configuration summary:
+     - Provider + model
+     - IDEs configured
+     - Data directory
+     - Worker port
+     - Chroma enabled/disabled
+   - `p.note()` with next steps:
+     - "Open Claude Code and start a conversation — memory is automatic!"
+     - "View your memories: http://localhost:{port}"
+     - "Search past work: use /mem-search in Claude Code"
+     - If Cursor: "Open Cursor — hooks are active in your projects"
+   - `p.outro()` with styled completion message
+
+### Verification
+- [ ] Summary accurately reflects chosen settings
+- [ ] URLs use correct port from settings
+- [ ] Next steps are relevant to selected IDEs
+
+---
+
+## Phase 8: curl|bash Bootstrap Script
+
+**Goal**: Create the shell bootstrap script for `curl -fsSL https://install.cmem.ai | bash`.
+
+### Tasks
+
+1. **`install/public/install.sh`** — Bootstrap script:
+   - Check for Node.js >= 18 (required to run the installer)
+   - Download bundled installer JS to temp file
+   - Execute with `node` directly (preserves TTY for @clack/prompts)
+   - Cleanup temp file on exit (trap)
+   - Support `--non-interactive` flag passthrough
+   - Support `--provider=X --api-key=Y` flag passthrough
+
+2. **Update `install/vercel.json`** to serve `install.sh` alongside `openclaw.sh`
+
+### Verification
+- [ ] `curl -fsSL https://install.cmem.ai | bash` downloads and runs installer
+- [ ] Interactive prompts work after curl download
+- [ ] Temp file cleaned up on success and failure
+- [ ] Flags pass through correctly
+
+---
+
+## Phase 9: Final Verification
+
+### Checks
+- [ ] `npm run build` in installer/ produces single-file `dist/index.js`
+- [ ] `node dist/index.js` runs full wizard flow
+- [ ] Fresh install on clean system works end-to-end
+- [ ] Upgrade path preserves existing settings
+- [ ] Ctrl+C at any step exits cleanly
+- [ ] Non-TTY shows error message
+- [ ] All settings written match SettingsDefaultsManager.ts defaults schema
+- [ ] Worker health check succeeds after install
+- [ ] Plugin appears in Claude Code plugin list
+- [ ] grep for deprecated/non-existent APIs returns 0 results
+- [ ] No `require()` calls in source (ESM-only)
+- [ ] No `chalk` imports (use picocolors)

.claude/plans/bugfix-env-auth.md

@@ -1,176 +0,0 @@
-# Bugfix Plan: Observer Sessions Authentication Failure
-
-## Problem Summary
-
-Observer sessions fail with "Invalid API key · Please run /login" because the `CLAUDE_CONFIG_DIR` environment variable is being set to an isolated directory (`~/.claude-mem/observer-config/`) that lacks authentication credentials.
-
-## Root Cause
-
-**File:** `src/services/worker/ProcessRegistry.ts` (lines 207-211)
-
-```typescript
-const isolatedEnv = {
-  ...spawnOptions.env,
-  CLAUDE_CONFIG_DIR: OBSERVER_CONFIG_DIR  // <-- This isolates auth credentials!
-};
-```
-
-This was added in Issue #832 to prevent observer sessions from polluting the `claude --resume` list. However, it also isolates the authentication credentials, breaking the SDK's ability to authenticate with the Anthropic API.
-
-## Evidence
-
-1. Running Claude with alternate config dir reproduces the error:
-   ```bash
-   CLAUDE_CONFIG_DIR=/tmp/test-claude claude --print "hello"
-   # Output: Invalid API key · Please run /login
-   ```
-
-2. The observer config directory exists but only has cached feature flags, no authentication:
-   - `~/.claude-mem/observer-config/.claude.json` - feature flags only
-   - No credentials copied from main `~/.claude/` directory
-
-## Solution
-
-The fix must allow authentication while still isolating session history. Claude Code stores different data types in `CLAUDE_CONFIG_DIR`:
-- Authentication credentials (needed)
-- Session history/resume list (should be isolated)
-- Feature flags and settings (can be shared or isolated)
-
-**Approach:** Do NOT override `CLAUDE_CONFIG_DIR`. Instead, find an alternative solution for Issue #832.
-
-### Alternative Approaches for Session Isolation
-
-1. **Use `--no-resume` flag** (if SDK supports it) - Prevent observer sessions from being resumable
-2. **Accept pollution** - Observer sessions in resume list may be acceptable tradeoff
-3. **Post-hoc cleanup** - Clean up observer session entries from history after completion
-4. **SDK parameter** - Check if SDK has a session isolation option that doesn't affect auth
-
----
-
-## Phase 0: Documentation Discovery
-
-### Objective
-Understand SDK options for session isolation without breaking authentication.
-
-### Tasks
-1. Read SDK documentation/source for:
-   - Available `query()` options
-   - Session isolation mechanisms
-   - Authentication handling
-
-2. Read Issue #832 context:
-   - What was the original problem?
-   - How bad was the pollution?
-   - Are there alternative solutions mentioned?
-
-### Verification
-- [ ] List all `query()` options available
-- [ ] Identify if `--no-resume` or equivalent exists
-- [ ] Document the tradeoffs
-
----
-
-## Phase 1: Fix Authentication
-
-### Objective
-Remove the `CLAUDE_CONFIG_DIR` override to restore authentication.
-
-### File to Modify
-`src/services/worker/ProcessRegistry.ts`
-
-### Change
-Remove lines 207-211 that override `CLAUDE_CONFIG_DIR`:
-
-**Before:**
-```typescript
-const isolatedEnv = {
-  ...spawnOptions.env,
-  CLAUDE_CONFIG_DIR: OBSERVER_CONFIG_DIR
-};
-```
-
-**After:**
-```typescript
-const isolatedEnv = {
-  ...spawnOptions.env
-  // CLAUDE_CONFIG_DIR removed - observer sessions need access to auth credentials
-  // Session isolation addressed via [alternative approach]
-};
-```
-
-### Verification
-- [ ] Build succeeds: `npm run build`
-- [ ] Observer sessions authenticate successfully
-- [ ] Observations are saved to database
-
----
-
-## Phase 2: Address Session Isolation (Issue #832)
-
-### Objective
-Find alternative solution to prevent observer sessions from polluting `claude --resume` list.
-
-### Options to Evaluate
-
-1. **Option A: Accept the tradeoff**
-   - Observer sessions appear in resume list but users can ignore them
-   - No code changes needed beyond Phase 1
-
-2. **Option B: Use isSynthetic flag**
-   - If SDK has a flag to mark sessions as non-resumable, use it
-   - Requires SDK documentation review
-
-3. **Option C: Post-processing cleanup**
-   - After session ends, remove observer entries from history
-   - More complex, may have race conditions
-
-### Decision Point
-After Phase 0 documentation review, choose the appropriate option.
-
-### Verification
-- [ ] Chosen approach documented
-- [ ] If code changes made, tests pass
-- [ ] Observer sessions either isolated OR tradeoff accepted
-
----
-
-## Phase 3: Testing
-
-### Manual Tests
-1. Start a new Claude Code session with the plugin
-2. Verify observations are being saved (check logs)
-3. Check that no "Invalid API key" errors appear
-4. Verify `claude --resume` behavior (acceptable level of observer entries)
-
-### Verification Checklist
-- [ ] `npm run build` succeeds
-- [ ] Worker service starts without errors
-- [ ] Observations save to database
-- [ ] No authentication errors in logs
-- [ ] Issue #832 regression acceptable or addressed
-
----
-
-## Anti-Patterns to Avoid
-
-1. **DO NOT** add `ANTHROPIC_API_KEY` to environment - authentication is handled by Claude Code's built-in credential management
-2. **DO NOT** copy credential files to observer config dir - credentials may be in keychain or other secure storage
-3. **DO NOT** try to "fix" authentication by adding API key loading - that creates Issue #588 (unexpected API charges)
-
----
-
-## Files Involved
-
-| File | Purpose |
-|------|---------|
-| `src/services/worker/ProcessRegistry.ts` | Contains the problematic `CLAUDE_CONFIG_DIR` override |
-| `src/shared/paths.ts` | Defines `OBSERVER_CONFIG_DIR` constant |
-| `src/services/worker/SDKAgent.ts` | Uses `createPidCapturingSpawn` which sets the env |
-
----
-
-## Risk Assessment
-
-**Low Risk:** Removing the `CLAUDE_CONFIG_DIR` override is a simple, targeted change.
-
-**Regression Risk (Issue #832):** Observer sessions may appear in `claude --resume` list again. This is a cosmetic issue vs. complete authentication failure, so the tradeoff favors removing the override.

.claude/plans/claude-md-path-validation-fix.md

@@ -1,262 +0,0 @@
-# CLAUDE.md Path Validation Bug Fix
-
-## Problem Summary
-
-Claude-Mem 9.0's distributed CLAUDE.md feature has a **critical path validation bug** that creates invalid directories when Claude SDK agent outputs non-path strings in file tracking XML tags (`<files_read>`, `<files_modified>`).
-
-### Root Cause
-
-In `src/utils/claude-md-utils.ts:234-239`:
-```typescript
-if (projectRoot && !path.isAbsolute(filePath)) {
-  absoluteFilePath = path.join(projectRoot, filePath);
-}
-```
-
-- `path.isAbsolute('~/.claude-mem/logs')` returns `false` (Node.js doesn't recognize `~`)
-- Code joins: `path.join(projectRoot, '~/.claude-mem/logs')` → `/project/~/.claude-mem/logs`
-- `mkdirSync` creates literal directories
-
-### Invalid Directories Currently in Repo
-
-```
-./~/                              ← literal tilde directory
-./PR #610 on thedotmack/          ← GitHub PR reference
-./git diff for src/               ← git command text
-./https:/code.claude.com/docs/en/ ← URL
-```
-
----
-
-## Implementation Plan
-
-### Phase 1: Add Path Validation Function
-
-**File:** `src/utils/claude-md-utils.ts`
-
-Add new validation function after the imports (around line 16):
-
-```typescript
-/**
- * Validate that a file path is safe for CLAUDE.md generation.
- * Rejects tilde paths, URLs, command-like strings, and paths with invalid chars.
- *
- * @param filePath - The file path to validate
- * @param projectRoot - Optional project root for boundary checking
- * @returns true if path is valid for CLAUDE.md processing
- */
-function isValidPathForClaudeMd(filePath: string, projectRoot?: string): boolean {
-  // Reject empty or whitespace-only
-  if (!filePath || !filePath.trim()) return false;
-
-  // Reject tilde paths (Node.js doesn't expand ~)
-  if (filePath.startsWith('~')) return false;
-
-  // Reject URLs
-  if (filePath.startsWith('http://') || filePath.startsWith('https://')) return false;
-
-  // Reject paths with spaces (likely command text or PR references)
-  if (filePath.includes(' ')) return false;
-
-  // Reject paths with # (GitHub issue/PR references)
-  if (filePath.includes('#')) return false;
-
-  // If projectRoot provided, ensure resolved path stays within project
-  if (projectRoot) {
-    const resolved = path.resolve(projectRoot, filePath);
-    const normalizedRoot = path.resolve(projectRoot);
-    if (!resolved.startsWith(normalizedRoot + path.sep) && resolved !== normalizedRoot) {
-      return false;
-    }
-  }
-
-  return true;
-}
-```
-
-### Phase 2: Integrate Validation in updateFolderClaudeMdFiles
-
-**File:** `src/utils/claude-md-utils.ts`
-
-Modify the file path loop in `updateFolderClaudeMdFiles` (around line 232):
-
-```typescript
-for (const filePath of filePaths) {
-  if (!filePath || filePath === '') continue;
-
-  // VALIDATE PATH BEFORE PROCESSING
-  if (!isValidPathForClaudeMd(filePath, projectRoot)) {
-    logger.debug('FOLDER_INDEX', 'Skipping invalid file path', {
-      filePath,
-      reason: 'Failed path validation'
-    });
-    continue;
-  }
-
-  // ... rest of existing logic unchanged
-}
-```
-
-### Phase 3: Add Unit Tests
-
-**File:** `tests/utils/claude-md-utils.test.ts`
-
-Add new test block after existing tests:
-
-```typescript
-describe('path validation in updateFolderClaudeMdFiles', () => {
-  it('should reject tilde paths', async () => {
-    const fetchMock = mock(() => Promise.resolve({ ok: true } as Response));
-    global.fetch = fetchMock;
-
-    await updateFolderClaudeMdFiles(
-      ['~/.claude-mem/logs/worker.log'],
-      'test-project',
-      37777,
-      tempDir
-    );
-
-    expect(fetchMock).not.toHaveBeenCalled();
-  });
-
-  it('should reject URLs', async () => {
-    const fetchMock = mock(() => Promise.resolve({ ok: true } as Response));
-    global.fetch = fetchMock;
-
-    await updateFolderClaudeMdFiles(
-      ['https://example.com/file.ts'],
-      'test-project',
-      37777,
-      tempDir
-    );
-
-    expect(fetchMock).not.toHaveBeenCalled();
-  });
-
-  it('should reject paths with spaces', async () => {
-    const fetchMock = mock(() => Promise.resolve({ ok: true } as Response));
-    global.fetch = fetchMock;
-
-    await updateFolderClaudeMdFiles(
-      ['PR #610 on thedotmack/CLAUDE.md'],
-      'test-project',
-      37777,
-      tempDir
-    );
-
-    expect(fetchMock).not.toHaveBeenCalled();
-  });
-
-  it('should reject paths with hash symbols', async () => {
-    const fetchMock = mock(() => Promise.resolve({ ok: true } as Response));
-    global.fetch = fetchMock;
-
-    await updateFolderClaudeMdFiles(
-      ['issue#123/file.ts'],
-      'test-project',
-      37777,
-      tempDir
-    );
-
-    expect(fetchMock).not.toHaveBeenCalled();
-  });
-
-  it('should reject path traversal outside project', async () => {
-    const fetchMock = mock(() => Promise.resolve({ ok: true } as Response));
-    global.fetch = fetchMock;
-
-    await updateFolderClaudeMdFiles(
-      ['../../../etc/passwd'],
-      'test-project',
-      37777,
-      tempDir
-    );
-
-    expect(fetchMock).not.toHaveBeenCalled();
-  });
-
-  it('should accept valid relative paths', async () => {
-    const apiResponse = {
-      content: [{ text: '| #123 | 4:30 PM | 🔵 | Test | ~100 |' }]
-    };
-    const fetchMock = mock(() => Promise.resolve({
-      ok: true,
-      json: () => Promise.resolve(apiResponse)
-    } as Response));
-    global.fetch = fetchMock;
-
-    await updateFolderClaudeMdFiles(
-      ['src/utils/logger.ts'],
-      'test-project',
-      37777,
-      tempDir
-    );
-
-    expect(fetchMock).toHaveBeenCalledTimes(1);
-  });
-});
-```
-
-### Phase 4: Update .gitignore
-
-**File:** `.gitignore`
-
-Add at end of file:
-
-```gitignore
-# Prevent literal tilde directories (path validation bug artifacts)
-~*/
-
-# Prevent other malformed path directories
-http*/
-https*/
-```
-
-### Phase 5: Clean Up Invalid Directories
-
-**Command sequence:**
-```bash
-rm -rf "~/."
-rm -rf "PR #610 on thedotmack"
-rm -rf "git diff for src"
-rm -rf "https:"
-```
-
-### Phase 6: Verify and Commit
-
-1. Run test suite: `npm test`
-2. Run build: `npm run build`
-3. Verify no invalid directories remain
-4. Commit with message: `fix: Add path validation to CLAUDE.md distribution to prevent invalid directory creation`
-
----
-
-## Files Modified
-
-| File | Change |
-|------|--------|
-| `src/utils/claude-md-utils.ts` | Add `isValidPathForClaudeMd()` function + integrate in loop |
-| `tests/utils/claude-md-utils.test.ts` | Add 6 new path validation tests |
-| `.gitignore` | Add `~*/`, `http*/`, `https*/` patterns |
-
-## Files Deleted
-
-| Path | Reason |
-|------|--------|
-| `~/` (directory tree) | Invalid literal tilde directory |
-| `PR #610 on thedotmack/` | Invalid PR reference directory |
-| `git diff for src/` | Invalid git command directory |
-| `https:/` | Invalid URL directory |
-
----
-
-## Risk Assessment
-
-**Low Risk:**
-- Validation is additive (only skips invalid paths, doesn't change valid path handling)
-- Existing tests remain unchanged
-- Fire-and-forget design means failures are logged but don't break hooks
-
-**Testing Coverage:**
-- 6 new unit tests covering all rejection cases
-- Existing 27 tests verify valid path behavior unchanged

.claude/plans/cleanup-worker-service-nonsense-logic.md

@@ -1,314 +0,0 @@
-# Plan: Cleanup worker-service.ts Unjustified Logic
-
-**Created:** 2026-01-13
-**Source:** `docs/reports/nonsense-logic.md`
-**Target:** `src/services/worker-service.ts` (813 lines)
-**Goal:** Address 23 identified issues, prioritizing safe deletions first
-
----
-
-## Phase 0: Documentation Discovery (COMPLETED)
-
-### Evidence Gathered
-
-**Exit Code Strategy (CLAUDE.md:44-54):**
-```
-- Exit 0: Success or graceful shutdown (Windows Terminal closes tabs)
-- Exit 1: Non-blocking error
-- Exit 2: Blocking error
-Philosophy: Exit 0 prevents Windows Terminal tab accumulation
-```
-
-**Signal Handler Pattern (ProcessManager.ts:294-317):**
-- Uses mutable reference object `isShuttingDownRef`
-- Factory function `createSignalHandler()` returns handler with embedded state
-- Current implementation has 3-hop indirection
-
-**MCP Client Pattern (worker-service.ts:157-160, ChromaSync.ts:124-136):**
-```typescript
-this.mcpClient = new Client({
-  name: 'worker-search-proxy',
-  version: '1.0.0'
-}, { capabilities: {} });
-```
-
-**Verification Results:**
-- `runInteractiveSetup` (lines 439-639): **NEVER CALLED** - grep shows only definition
-- `import * as fs from 'fs'` (line 13): **UNUSED** - no `fs.` usage found
-- `import { spawn } from 'child_process'` (line 14): **UNUSED** - no `spawn(` calls
-- `homedir` (line 15): Only used in `runInteractiveSetup` (dead code)
-- `processPendingQueues` default `= 10`: Never used, all callers pass explicit args
-
----
-
-## Phase 1: Safe Deletions (Dead Code & Unused Imports)
-
-### 1.1 Delete `runInteractiveSetup` Function
-
-**What:** Delete lines 435-639 (~201 lines)
-**Why:** Function is defined but never called. Setup happens via `handleCursorCommand()`.
-**Evidence:** `grep -n "runInteractiveSetup" src/services/worker-service.ts` returns only definition
-
-**Pattern to follow:** N/A - straight deletion
-
-**Steps:**
-1. Read worker-service.ts lines 435-650
-2. Delete the entire function including section comment (lines 435-639)
-3. Run `npm run build` to verify no compile errors
-
-**Verification:**
-- `grep "runInteractiveSetup" src/` returns nothing
-- Build succeeds
-
-### 1.2 Remove Unused Imports
-
-**What:** Delete lines 13, 14, 17
-
-**Current (delete these):**
-```typescript
-import * as fs from 'fs';           // Line 13 - UNUSED
-import { spawn } from 'child_process';  // Line 14 - UNUSED
-import * as readline from 'readline';   // Line 17 - Only in dead code
-```
-
-**Keep:**
-```typescript
-import { homedir } from 'os';  // Line 15 - DELETE (only in dead code)
-import { existsSync, writeFileSync, readFileSync, mkdirSync } from 'fs';  // Line 16 - CHECK USAGE
-```
-
-**Steps:**
-1. After deleting `runInteractiveSetup`, grep for remaining usages:
-   - `grep "homedir" src/services/worker-service.ts`
-   - `grep "readline" src/services/worker-service.ts`
-   - `grep "detectClaudeCode\|findCursorHooksDir\|installCursorHooks\|configureCursorMcp" src/services/worker-service.ts`
-2. Delete imports with zero usages
-3. Run `npm run build`
-
-**Verification:**
-- No TypeScript unused import warnings
-- Build succeeds
-
-### 1.3 Clean Up Cursor Integration Imports
-
-After deleting `runInteractiveSetup`, some CursorHooksInstaller imports become unused:
-- `detectClaudeCode` - only in runInteractiveSetup
-- `findCursorHooksDir` - only in runInteractiveSetup
-- `installCursorHooks` - only in runInteractiveSetup
-- `configureCursorMcp` - only in runInteractiveSetup
-
-**Steps:**
-1. Grep each import after dead code removal
-2. Remove any that are now unused
-3. Keep `updateCursorContextForProject` (re-exported) and `handleCursorCommand` (used in main)
-
-**Verification:**
-- `grep "detectClaudeCode\|findCursorHooksDir\|installCursorHooks\|configureCursorMcp" src/services/worker-service.ts` returns nothing
-- Build succeeds
-
----
-
-## Phase 2: Low-Risk Simplifications
-
-### 2.1 Remove Unused Default Parameter
-
-**What:** Line 350 - `async processPendingQueues(sessionLimit: number = 10)`
-**Why:** Default never used. All callers pass explicit args (50 in startup, dynamic in HTTP)
-
-**Change from:**
-```typescript
-async processPendingQueues(sessionLimit: number = 10): Promise<{...}>
-```
-
-**Change to:**
-```typescript
-async processPendingQueues(sessionLimit: number): Promise<{...}>
-```
-
-**Verification:**
-- Build succeeds
-- All call sites provide explicit values
-
-### 2.2 Simplify onRestart Callback
-
-**Location:** Lines 395-396 (approximate, find exact)
-**Issue:** `onShutdown` and `onRestart` both call `this.shutdown()`
-
-**Find pattern:**
-```typescript
-onShutdown: () => this.shutdown(),
-onRestart: () => this.shutdown()
-```
-
-**Options:**
-1. **Keep as-is** if restart semantically differs from shutdown (future-proofing)
-2. **Add comment** explaining intentional parity
-3. **Remove onRestart** if never used differently
-
-**Investigation needed:** Grep for `onRestart` usage in Server.ts to understand contract
-
-**Steps:**
-1. Grep `onRestart` in `src/services/server/`
-2. If Server.ts treats them identically, add clarifying comment
-3. If different, document why both map to shutdown
-
-### 2.3 Fix Over-Commented Lines (Sample Only)
-
-**Strategy:** Do NOT strip all comments. Only remove comments that describe obvious code.
-
-**Anti-pattern (remove):**
-```typescript
-// WHAT: Imports centralized logging utility with structured output
-// WHY: All worker logs go through this for consistent formatting
-import { logger } from '../utils/logger.js';
-```
-
-**Pattern to follow:** Remove WHAT/WHY on simple imports. Keep architectural comments.
-
-**Scope:** Sample 5-10 obvious comment removals to demonstrate approach, not exhaustive
-
----
-
-## Phase 3: Medium-Risk Improvements
-
-### 3.1 Simplify Signal Handler Pattern
-
-**Current (worker-service.ts:180-192 + ProcessManager.ts:294-317):**
-```typescript
-// 3-hop indirection with mutable reference
-const shutdownRef = { value: this.isShuttingDown };
-const handler = createSignalHandler(() => this.shutdown(), shutdownRef);
-process.on('SIGTERM', () => {
-  this.isShuttingDown = shutdownRef.value;  // Sync back
-  handler('SIGTERM');
-});
-```
-
-**Simplified approach:**
-```typescript
-private registerSignalHandlers(): void {
-  const handler = async (signal: string) => {
-    if (this.isShuttingDown) {
-      logger.warn('SYSTEM', `Received ${signal} but shutdown already in progress`);
-      return;
-    }
-    this.isShuttingDown = true;
-    logger.info('SYSTEM', `Received ${signal}, shutting down...`);
-    try {
-      await this.shutdown();
-      process.exit(0);
-    } catch (error) {
-      logger.error('SYSTEM', 'Error during shutdown', {}, error as Error);
-      process.exit(0);
-    }
-  };
-
-  process.on('SIGTERM', () => handler('SIGTERM'));
-  process.on('SIGINT', () => handler('SIGINT'));
-}
-```
-
-**Decision needed:** Does `createSignalHandler` serve other callers? If yes, keep factory but simplify worker usage.
-
-**Steps:**
-1. Grep `createSignalHandler` usage across codebase
-2. If only worker-service uses it, inline and simplify
-3. If shared, simplify worker's usage while keeping factory
-
-### 3.2 Unify Dual Initialization Tracking
-
-**Current (lines 111, 129-130):**
-```typescript
-private initializationCompleteFlag: boolean = false;
-private initializationComplete: Promise<void>;
-```
-
-**Recommendation:** Keep both but add clarifying comments:
-- Promise: For async waiters (HTTP handlers)
-- Flag: For sync checks (status endpoints)
-
-**Alternative:** Use Promise with inspection pattern:
-```typescript
-private initializationComplete = false;
-private initializationPromise: Promise<void>;
-// Flag derived from promise state via finally() callback
-```
-
-**Steps:**
-1. Add documentation comment explaining dual tracking purpose
-2. Consider if flag can be derived from promise state instead
-
-### 3.3 Reduce 5-Minute Timeout
-
-**Location:** Lines 464-478 (approximate)
-**Current:** `const timeoutMs = 300000; // 5 minutes`
-**Recommendation:** Reduce to 30-60 seconds for HTTP handler, keep 5min for MCP init
-
-**Caution:** MCP initialization can legitimately be slow (ChromaDB, model loading). May need different timeouts per use case.
-
-**Steps:**
-1. Find exact line for context inject timeout
-2. Verify this is separate from MCP init timeout
-3. Reduce HTTP handler timeout to 30-60 seconds
-4. Keep MCP init timeout at 5 minutes
-
----
-
-## Phase 4: Deferred / Low Priority
-
-These items are noted but NOT part of this cleanup:
-
-| Issue | Reason to Defer |
-|-------|-----------------|
-| Exit code 0 always | Documented Windows Terminal workaround - intentional |
-| Re-export for circular import | Works correctly, architectural fix is separate work |
-| Fallback agent verification | Behavioral change, needs feature design |
-| MCP version hardcoding | Low impact, separate version management issue |
-| Empty capabilities | Documentation issue only |
-| Unsafe `as Error` casts | Common TS pattern, low risk |
-
----
-
-## Phase 5: Verification
-
-### 5.1 Build Verification
-```bash
-npm run build
-```
-Expected: No errors
-
-### 5.2 Test Suite
-```bash
-npm test
-```
-Expected: All tests pass
-
-### 5.3 Grep for Anti-patterns
-```bash
-# Verify dead code removed
-grep -r "runInteractiveSetup" src/
-
-# Verify unused imports removed
-grep "import \* as fs from 'fs'" src/services/worker-service.ts
-grep "import { spawn }" src/services/worker-service.ts
-```
-Expected: No matches
-
-### 5.4 Runtime Check
-```bash
-npm run build-and-sync
-# Start worker and verify basic operation
-```
-
----
-
-## Summary
-
-| Phase | Items | Estimated Reduction |
-|-------|-------|---------------------|
-| Phase 1 | Dead code + unused imports | ~210 lines |
-| Phase 2 | Low-risk simplifications | ~5 lines + clarity |
-| Phase 3 | Medium-risk improvements | ~30 lines |
-| Total | | ~245 lines (~30% reduction) |
-
-**Execution Order:** Phase 1 → Phase 2 → Phase 3 → Phase 5 (verification after each)

.claude/plans/fix-claudemd-worktree-bug.md

@@ -1,516 +0,0 @@
-# Fix CLAUDE.md Worktree Bug - Implementation Plan
-
-## Problem Statement
-
-CLAUDE.md files are being written to the wrong directory when using git worktrees. The worker service writes files relative to its own `process.cwd()` instead of the project's working directory (`cwd`) from the observation.
-
-**Reproduction scenario:**
-1. Start Claude Code in `budapest` worktree → worker starts with `cwd=budapest`
-2. Run Claude Code in `~/Scripts/claude-mem/` (main repo)
-3. Observations created with relative file paths (e.g., `src/utils/foo.ts`)
-4. `updateFolderClaudeMdFiles` writes to `budapest/src/utils/CLAUDE.md` instead of main repo
-
-## Root Cause Analysis
-
-The `cwd` (project root path) IS captured and stored:
-- `SessionRoutes.ts:309,403` - receives `cwd` from hooks
-- `PendingMessageStore.ts:70` - stores `cwd` in database
-- `SDKAgent.ts:295` - passes `cwd` to prompt builder
-
-But `cwd` is NOT passed to file writing:
-- `ResponseProcessor.ts:222-225` - calls `updateFolderClaudeMdFiles(allFilePaths, session.project, port)` without `cwd`
-- `claude-md-utils.ts:219` - uses `path.dirname(filePath)` which produces relative paths
-- Relative paths resolve against worker's `process.cwd()`, not project root
-
----
-
-## Phase 0: Documentation & API Inventory
-
-### Allowed APIs (from codebase analysis)
-
-**File: `src/utils/claude-md-utils.ts`**
-```typescript
-export async function updateFolderClaudeMdFiles(
-  filePaths: string[],
-  project: string,
-  port: number
-): Promise<void>
-```
-
-**File: `src/sdk/parser.ts`**
-```typescript
-export interface ParsedObservation {
-  type: string;
-  title: string | null;
-  subtitle: string | null;
-  facts: string[];
-  narrative: string | null;
-  concepts: string[];
-  files_read: string[];
-  files_modified: string[];
-  // NOTE: Does NOT include cwd
-}
-```
-
-**File: `src/services/worker-types.ts`**
-```typescript
-export interface PendingMessage {
-  type: 'observation' | 'summarize';
-  tool_name?: string;
-  tool_input?: unknown;
-  tool_response?: unknown;
-  prompt_number?: number;
-  cwd?: string;  // <-- Source of project root
-  last_assistant_message?: string;
-}
-```
-
-**File: `src/shared/paths.ts`** - Path utilities
-```typescript
-import path from 'path';
-// Standard pattern: path.join(baseDir, relativePath)
-```
-
-### Anti-Patterns to Avoid
-
-1. **DO NOT** add `cwd` to `ParsedObservation` - it comes from message, not agent response
-2. **DO NOT** use `process.cwd()` for project-specific paths
-3. **DO NOT** assume file paths are absolute - they are relative from agent response
-4. **DO NOT** modify the parser - file paths come from agent XML output
-
----
-
-## Phase 1: Add `projectRoot` Parameter to `updateFolderClaudeMdFiles`
-
-### What to implement
-
-Modify the function signature to accept an optional `projectRoot` parameter for resolving relative paths to absolute paths.
-
-### Files to modify
-
-**File: `src/utils/claude-md-utils.ts`**
-
-**Location: Lines 206-210 (function signature)**
-
-Current:
-```typescript
-export async function updateFolderClaudeMdFiles(
-  filePaths: string[],
-  project: string,
-  port: number
-): Promise<void>
-```
-
-New:
-```typescript
-export async function updateFolderClaudeMdFiles(
-  filePaths: string[],
-  project: string,
-  port: number,
-  projectRoot?: string
-): Promise<void>
-```
-
-**Location: Lines 215-228 (folder extraction logic)**
-
-Current:
-```typescript
-const folderPaths = new Set<string>();
-for (const filePath of filePaths) {
-  if (!filePath || filePath === '') continue;
-  const folderPath = path.dirname(filePath);
-  if (folderPath && folderPath !== '.' && folderPath !== '/') {
-    if (isProjectRoot(folderPath)) {
-      logger.debug('FOLDER_INDEX', 'Skipping project root CLAUDE.md', { folderPath });
-      continue;
-    }
-    folderPaths.add(folderPath);
-  }
-}
-```
-
-New:
-```typescript
-const folderPaths = new Set<string>();
-for (const filePath of filePaths) {
-  if (!filePath || filePath === '') continue;
-
-  // Resolve relative paths to absolute using projectRoot
-  let absoluteFilePath = filePath;
-  if (projectRoot && !path.isAbsolute(filePath)) {
-    absoluteFilePath = path.join(projectRoot, filePath);
-  }
-
-  const folderPath = path.dirname(absoluteFilePath);
-  if (folderPath && folderPath !== '.' && folderPath !== '/') {
-    if (isProjectRoot(folderPath)) {
-      logger.debug('FOLDER_INDEX', 'Skipping project root CLAUDE.md', { folderPath });
-      continue;
-    }
-    folderPaths.add(folderPath);
-  }
-}
-```
-
-### Documentation references
-
-- Pattern for `path.isAbsolute()`: Standard Node.js path module
-- Pattern for `path.join(base, relative)`: Used throughout `src/shared/paths.ts`
-
-### Verification checklist
-
-1. [ ] `grep -n "updateFolderClaudeMdFiles" src/utils/claude-md-utils.ts` shows new signature
-2. [ ] `grep -n "path.isAbsolute" src/utils/claude-md-utils.ts` confirms new check added
-3. [ ] `grep -n "projectRoot" src/utils/claude-md-utils.ts` shows parameter usage
-4. [ ] Existing callers still compile (optional param is backward compatible)
-
-### Anti-pattern guards
-
-- **DO NOT** make `projectRoot` required - breaks existing callers
-- **DO NOT** use `process.cwd()` as default - defeats purpose of fix
-- **DO NOT** modify the API endpoint format - path resolution is caller's responsibility
-
----
-
-## Phase 2: Pass `cwd` from Message to `updateFolderClaudeMdFiles`
-
-### What to implement
-
-Extract `cwd` from the original messages being processed and pass it to `updateFolderClaudeMdFiles`.
-
-### Challenge
-
-The `syncAndBroadcastObservations` function receives `ParsedObservation[]` which does NOT include `cwd`. The `cwd` is in the original `PendingMessage` but is consumed during prompt generation.
-
-### Solution
-
-Add `projectRoot` parameter to `syncAndBroadcastObservations` and `processAgentResponse`, sourced from `session` or passed through from message processing.
-
-### Files to modify
-
-**File: `src/services/worker/agents/ResponseProcessor.ts`**
-
-**Step 1: Update `processAgentResponse` signature (lines 46-55)**
-
-Current:
-```typescript
-export async function processAgentResponse(
-  text: string,
-  session: ActiveSession,
-  dbManager: DatabaseManager,
-  sessionManager: SessionManager,
-  worker: WorkerRef | undefined,
-  discoveryTokens: number,
-  originalTimestamp: number | null,
-  agentName: string
-): Promise<void>
-```
-
-New:
-```typescript
-export async function processAgentResponse(
-  text: string,
-  session: ActiveSession,
-  dbManager: DatabaseManager,
-  sessionManager: SessionManager,
-  worker: WorkerRef | undefined,
-  discoveryTokens: number,
-  originalTimestamp: number | null,
-  agentName: string,
-  projectRoot?: string
-): Promise<void>
-```
-
-**Step 2: Pass `projectRoot` to `syncAndBroadcastObservations` (line 101-109)**
-
-Current:
-```typescript
-await syncAndBroadcastObservations(
-  observations,
-  result,
-  session,
-  dbManager,
-  worker,
-  discoveryTokens,
-  agentName
-);
-```
-
-New:
-```typescript
-await syncAndBroadcastObservations(
-  observations,
-  result,
-  session,
-  dbManager,
-  worker,
-  discoveryTokens,
-  agentName,
-  projectRoot
-);
-```
-
-**Step 3: Update `syncAndBroadcastObservations` signature (lines 153-161)**
-
-Current:
-```typescript
-async function syncAndBroadcastObservations(
-  observations: ParsedObservation[],
-  result: StorageResult,
-  session: ActiveSession,
-  dbManager: DatabaseManager,
-  worker: WorkerRef | undefined,
-  discoveryTokens: number,
-  agentName: string
-): Promise<void>
-```
-
-New:
-```typescript
-async function syncAndBroadcastObservations(
-  observations: ParsedObservation[],
-  result: StorageResult,
-  session: ActiveSession,
-  dbManager: DatabaseManager,
-  worker: WorkerRef | undefined,
-  discoveryTokens: number,
-  agentName: string,
-  projectRoot?: string
-): Promise<void>
-```
-
-**Step 4: Update `updateFolderClaudeMdFiles` call (lines 222-229)**
-
-Current:
-```typescript
-if (allFilePaths.length > 0) {
-  updateFolderClaudeMdFiles(
-    allFilePaths,
-    session.project,
-    getWorkerPort()
-  ).catch(error => {
-    logger.warn('FOLDER_INDEX', 'CLAUDE.md update failed (non-critical)', { project: session.project }, error as Error);
-  });
-}
-```
-
-New:
-```typescript
-if (allFilePaths.length > 0) {
-  updateFolderClaudeMdFiles(
-    allFilePaths,
-    session.project,
-    getWorkerPort(),
-    projectRoot
-  ).catch(error => {
-    logger.warn('FOLDER_INDEX', 'CLAUDE.md update failed (non-critical)', { project: session.project }, error as Error);
-  });
-}
-```
-
-### Verification checklist
-
-1. [ ] `grep -n "projectRoot" src/services/worker/agents/ResponseProcessor.ts` shows parameter throughout
-2. [ ] `grep -n "processAgentResponse" src/services/worker/*.ts` to find all callers
-3. [ ] TypeScript compiles without errors
-
-### Anti-pattern guards
-
-- **DO NOT** extract `cwd` from `ParsedObservation` - it doesn't have one
-- **DO NOT** store `cwd` on session globally - messages may come from different cwds (edge case)
-
----
-
-## Phase 3: Update Agent Callers to Pass `cwd`
-
-### What to implement
-
-Update SDKAgent, GeminiAgent, and OpenRouterAgent to pass `message.cwd` to `processAgentResponse`.
-
-### Files to modify
-
-**File: `src/services/worker/SDKAgent.ts`**
-
-Find the `processAgentResponse` call and add the `projectRoot` parameter from `message.cwd`.
-
-**Pattern to follow (from SDKAgent.ts:289-296):**
-```typescript
-const obsPrompt = buildObservationPrompt({
-  id: 0,
-  tool_name: message.tool_name!,
-  tool_input: JSON.stringify(message.tool_input),
-  tool_output: JSON.stringify(message.tool_response),
-  created_at_epoch: Date.now(),
-  cwd: message.cwd  // <-- This is available
-});
-```
-
-**Challenge:** `processAgentResponse` is called after the SDK response, not in the message loop. Need to track `lastCwd` from messages.
-
-**Solution:** Store `lastCwd` from messages being processed and pass to `processAgentResponse`.
-
-**File: `src/services/worker/GeminiAgent.ts`** - Same pattern
-**File: `src/services/worker/OpenRouterAgent.ts`** - Same pattern
-
-### Implementation pattern for each agent
-
-Add tracking variable:
-```typescript
-let lastCwd: string | undefined;
-```
-
-In message loop, capture cwd:
-```typescript
-if (message.cwd) {
-  lastCwd = message.cwd;
-}
-```
-
-In `processAgentResponse` call:
-```typescript
-await processAgentResponse(
-  responseText,
-  session,
-  this.dbManager,
-  this.sessionManager,
-  worker,
-  discoveryTokens,
-  originalTimestamp,
-  'SDK',  // or 'Gemini' or 'OpenRouter'
-  lastCwd
-);
-```
-
-### Verification checklist
-
-1. [ ] `grep -n "lastCwd" src/services/worker/SDKAgent.ts` shows tracking
-2. [ ] `grep -n "lastCwd" src/services/worker/GeminiAgent.ts` shows tracking
-3. [ ] `grep -n "lastCwd" src/services/worker/OpenRouterAgent.ts` shows tracking
-4. [ ] `grep -n "processAgentResponse.*lastCwd" src/services/worker/` shows all calls updated
-
-### Anti-pattern guards
-
-- **DO NOT** use `session.cwd` - sessions can have messages from multiple cwds
-- **DO NOT** default to `process.cwd()` - defeats the fix
-
----
-
-## Phase 4: Update Tests
-
-### What to implement
-
-Update existing tests and add new tests for the `projectRoot` functionality.
-
-### Files to modify
-
-**File: `tests/utils/claude-md-utils.test.ts`**
-
-Add test cases for:
-1. Relative paths with `projectRoot` resolve correctly
-2. Absolute paths ignore `projectRoot`
-3. Missing `projectRoot` maintains backward compatibility
-
-### Test pattern to copy
-
-From `tests/utils/claude-md-utils.test.ts:245-266` (folder deduplication test):
-```typescript
-it('should deduplicate folders from multiple files', async () => {
-  mockFetch.mockResolvedValue({
-    ok: true,
-    json: () => Promise.resolve({ content: [{ text: mockApiResponse }] })
-  });
-
-  await updateFolderClaudeMdFiles(
-    ['/project/src/utils/file1.ts', '/project/src/utils/file2.ts'],
-    'test-project',
-    37777
-  );
-
-  // Should only call API once for the deduplicated folder
-  expect(mockFetch).toHaveBeenCalledTimes(1);
-});
-```
-
-### New test to add
-
-```typescript
-it('should resolve relative paths using projectRoot', async () => {
-  mockFetch.mockResolvedValue({
-    ok: true,
-    json: () => Promise.resolve({ content: [{ text: mockApiResponse }] })
-  });
-
-  await updateFolderClaudeMdFiles(
-    ['src/utils/file.ts'],  // relative path
-    'test-project',
-    37777,
-    '/home/user/my-project'  // projectRoot
-  );
-
-  // Should write to absolute path /home/user/my-project/src/utils/CLAUDE.md
-  expect(mockWriteClaudeMd).toHaveBeenCalledWith(
-    '/home/user/my-project/src/utils',
-    expect.any(String)
-  );
-});
-```
-
-### Verification checklist
-
-1. [ ] `bun test tests/utils/claude-md-utils.test.ts` passes
-2. [ ] New test case for `projectRoot` exists and passes
-
----
-
-## Phase 5: Final Verification
-
-### Verification commands
-
-```bash
-# 1. Confirm new parameter exists
-grep -n "projectRoot" src/utils/claude-md-utils.ts
-grep -n "projectRoot" src/services/worker/agents/ResponseProcessor.ts
-grep -n "lastCwd" src/services/worker/SDKAgent.ts
-
-# 2. Confirm path.isAbsolute check added
-grep -n "path.isAbsolute" src/utils/claude-md-utils.ts
-
-# 3. Confirm all agents updated
-grep -n "processAgentResponse.*lastCwd" src/services/worker/*.ts
-
-# 4. Run tests
-bun test tests/utils/claude-md-utils.test.ts
-
-# 5. Build and verify no TypeScript errors
-npm run build
-```
-
-### Anti-pattern grep checks
-
-```bash
-# Should NOT find process.cwd() in updateFolderClaudeMdFiles path logic
-grep -n "process.cwd" src/utils/claude-md-utils.ts
-
-# Should NOT find cwd in ParsedObservation interface
-grep -A 10 "interface ParsedObservation" src/sdk/parser.ts | grep cwd
-```
-
-### Manual testing
-
-1. Start worker in one directory
-2. Run Claude Code in a different directory (worktree)
-3. Make a code change that creates an observation
-4. Verify CLAUDE.md is written to the correct project directory
-
----
-
-## Summary of Changes
-
-| File | Change |
-|------|--------|
-| `src/utils/claude-md-utils.ts` | Add `projectRoot` param, resolve relative paths |
-| `src/services/worker/agents/ResponseProcessor.ts` | Pass `projectRoot` through call chain |
-| `src/services/worker/SDKAgent.ts` | Track `lastCwd`, pass to `processAgentResponse` |
-| `src/services/worker/GeminiAgent.ts` | Track `lastCwd`, pass to `processAgentResponse` |
-| `src/services/worker/OpenRouterAgent.ts` | Track `lastCwd`, pass to `processAgentResponse` |
-| `tests/utils/claude-md-utils.test.ts` | Add tests for `projectRoot` behavior |

.claude/plans/fix-empty-claude-md-files.md

@@ -1,266 +0,0 @@
-# Plan: Fix Empty CLAUDE.md File Generation
-
-## Problem Statement
-
-Currently the CLAUDE.md generator creates files with wasteful content:
-1. **Empty files with "No recent activity"** - Files are created even when there are zero observations for a folder
-2. **Redundant HTML comment** - "<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->" is unnecessary since the `<claude-mem-context>` tag already conveys this information
-
-These issues create noisy, wasteful context that loads automatically and provides no value.
-
-## Phase 0: Documentation Discovery
-
-### Allowed APIs (from code analysis)
-- `formatTimelineForClaudeMd(timelineText: string): string` - src/utils/claude-md-utils.ts:139
-- `formatObservationsForClaudeMd(observations, folderPath): string` - scripts/regenerate-claude-md.ts:238
-- `writeClaudeMdToFolder(folderPath, newContent): void` - src/utils/claude-md-utils.ts:94
-- `updateFolderClaudeMdFiles(filePaths, project, port, projectRoot): Promise<void>` - src/utils/claude-md-utils.ts:257
-- `replaceTaggedContent(existingContent, newContent): string` - src/utils/claude-md-utils.ts:64
-
-### Key Locations
-| File | Lines | Purpose |
-|------|-------|---------|
-| `src/utils/claude-md-utils.ts` | 139-235 | Main formatting function |
-| `src/utils/claude-md-utils.ts` | 143 | HTML comment generation |
-| `src/utils/claude-md-utils.ts` | 209-211 | "No recent activity" handling |
-| `src/utils/claude-md-utils.ts` | 322-323 | Write decision point |
-| `scripts/regenerate-claude-md.ts` | 238-286 | Regeneration script formatting |
-| `scripts/regenerate-claude-md.ts` | 242 | HTML comment generation (duplicate) |
-| `scripts/regenerate-claude-md.ts` | 245-247 | "No recent activity" handling |
-| `scripts/regenerate-claude-md.ts` | 452-453 | Write decision point |
-| `tests/utils/claude-md-utils.test.ts` | 96-109 | Tests for "No recent activity" behavior |
-
-### Anti-patterns to avoid
-- Do NOT add new configuration options for this behavior - just fix it
-- Do NOT add logging for skipped files (unnecessary noise)
-
----
-
-## Phase 1: Modify formatTimelineForClaudeMd to Return Empty on No Observations
-
-### Task 1.1: Update formatTimelineForClaudeMd return behavior
-**File:** `src/utils/claude-md-utils.ts`
-**Lines:** 139-235
-
-**Changes:**
-1. Remove HTML comment line at line 143
-2. Change the empty observations case (lines 209-211) to return an empty string instead of "No recent activity"
-
-**Before (lines 141-144):**
-```typescript
-lines.push('# Recent Activity');
-lines.push('');
-lines.push('<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->');
-lines.push('');
-```
-
-**After:**
-```typescript
-lines.push('# Recent Activity');
-lines.push('');
-```
-
-**Before (lines 209-212):**
-```typescript
-if (observations.length === 0) {
-  lines.push('*No recent activity*');
-  return lines.join('\n');
-}
-```
-
-**After:**
-```typescript
-if (observations.length === 0) {
-  return '';
-}
-```
-
-### Verification
-- Run `bun test tests/utils/claude-md-utils.test.ts`
-- Tests at lines 96-109 will FAIL (expected - they test for "No recent activity")
-- Update tests to expect empty string for empty input
-
----
-
-## Phase 2: Update updateFolderClaudeMdFiles to Skip Empty Content
-
-### Task 2.1: Add empty content check before writing
-**File:** `src/utils/claude-md-utils.ts`
-**Lines:** 322-323
-
-**Changes:**
-After formatting, check if result is empty and skip writing if so.
-
-**Before (lines 321-325):**
-```typescript
-const formatted = formatTimelineForClaudeMd(result.content[0].text);
-writeClaudeMdToFolder(folderPath, formatted);
-
-logger.debug('FOLDER_INDEX', 'Updated CLAUDE.md', { folderPath });
-```
-
-**After:**
-```typescript
-const formatted = formatTimelineForClaudeMd(result.content[0].text);
-if (!formatted) {
-  logger.debug('FOLDER_INDEX', 'No observations for folder, skipping', { folderPath });
-  continue;
-}
-writeClaudeMdToFolder(folderPath, formatted);
-
-logger.debug('FOLDER_INDEX', 'Updated CLAUDE.md', { folderPath });
-```
-
-### Verification
-- Grep for files containing "No recent activity": should find none after running
-
----
-
-## Phase 3: Update Regeneration Script
-
-### Task 3.1: Remove HTML comment from formatObservationsForClaudeMd
-**File:** `scripts/regenerate-claude-md.ts`
-**Lines:** 238-286
-
-**Changes:**
-1. Remove HTML comment line at line 242
-2. Change empty observations case (lines 245-247) to return empty string
-
-**Before (lines 240-244):**
-```typescript
-lines.push('# Recent Activity');
-lines.push('');
-lines.push('<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->');
-lines.push('');
-```
-
-**After:**
-```typescript
-lines.push('# Recent Activity');
-lines.push('');
-```
-
-**Before (lines 245-248):**
-```typescript
-if (observations.length === 0) {
-  lines.push('*No recent activity*');
-  return lines.join('\n');
-}
-```
-
-**After:**
-```typescript
-if (observations.length === 0) {
-  return '';
-}
-```
-
-### Task 3.2: Update regenerateFolder to handle empty formatted content
-**File:** `scripts/regenerate-claude-md.ts`
-**Lines:** 432-459
-
-The script already skips folders with no observations (lines 443-444), so this change is already compatible. The `formatObservationsForClaudeMd` returning empty string doesn't change behavior since observations are checked before calling it.
-
-### Verification
-- Run `bun scripts/regenerate-claude-md.ts --dry-run` in the project
-- Should NOT show any folders with 0 observations
-
----
-
-## Phase 4: Update Tests
-
-### Task 4.1: Update tests for new empty behavior
-**File:** `tests/utils/claude-md-utils.test.ts`
-**Lines:** 96-109
-
-**Changes:**
-Update the two tests that expect "No recent activity" to expect empty string instead.
-
-**Before (lines 96-101):**
-```typescript
-it('should return "No recent activity" for empty input', () => {
-  const result = formatTimelineForClaudeMd('');
-
-  expect(result).toContain('# Recent Activity');
-  expect(result).toContain('*No recent activity*');
-});
-```
-
-**After:**
-```typescript
-it('should return empty string for empty input', () => {
-  const result = formatTimelineForClaudeMd('');
-
-  expect(result).toBe('');
-});
-```
-
-**Before (lines 103-109):**
-```typescript
-it('should return "No recent activity" when no table rows exist', () => {
-  const input = 'Just some plain text without table rows';
-
-  const result = formatTimelineForClaudeMd(input);
-
-  expect(result).toContain('*No recent activity*');
-});
-```
-
-**After:**
-```typescript
-it('should return empty string when no table rows exist', () => {
-  const input = 'Just some plain text without table rows';
-
-  const result = formatTimelineForClaudeMd(input);
-
-  expect(result).toBe('');
-});
-```
-
-### Task 4.2: Remove HTML comment assertions from any other tests
-Search for tests that assert on "auto-generated" comment and update accordingly.
-
-### Verification
-- Run full test suite: `bun test`
-- All tests should pass
-
----
-
-## Phase 5: Cleanup Existing Empty Files
-
-### Task 5.1: Run cleanup to remove existing empty CLAUDE.md files
-**Command:**
-```bash
-bun scripts/regenerate-claude-md.ts --clean
-```
-
-This will:
-- Find all CLAUDE.md files with `<claude-mem-context>` tags
-- Strip the tagged section
-- Delete files that become empty after stripping
-- Preserve files that have user content outside the tags
-
-### Verification
-- `grep -r "No recent activity" . --include="CLAUDE.md"` should return no results
-- `grep -r "auto-generated by claude-mem" . --include="CLAUDE.md"` should return no results
-
----
-
-## Summary of Changes
-
-| File | Change |
-|------|--------|
-| `src/utils/claude-md-utils.ts:143` | Remove HTML comment line |
-| `src/utils/claude-md-utils.ts:209-211` | Return empty string instead of "No recent activity" |
-| `src/utils/claude-md-utils.ts:322` | Skip writing if formatted content is empty |
-| `scripts/regenerate-claude-md.ts:242` | Remove HTML comment line |
-| `scripts/regenerate-claude-md.ts:245-247` | Return empty string instead of "No recent activity" |
-| `tests/utils/claude-md-utils.test.ts:96-109` | Update tests to expect empty string |
-
-## Final Verification Checklist
-- [ ] `bun test` passes
-- [ ] No "No recent activity" CLAUDE.md files exist
-- [ ] No "auto-generated" comments in CLAUDE.md files
-- [ ] Build succeeds: `npm run build-and-sync`
-- [ ] New observations correctly generate CLAUDE.md files with content
-- [ ] Folders without observations get no CLAUDE.md file created

.claude/plans/fix-stale-session-resume-crash.md

@@ -1,252 +0,0 @@
-# Plan: Fix Stale Session Resume Crash
-
-## Problem Summary
-
-The worker crashes repeatedly with "Claude Code process exited with code 1" when attempting to resume into a stale/non-existent SDK session.
-
-**Root Cause:** In `SDKAgent.ts:94`, the resume parameter is passed whenever `memorySessionId` exists in the database, regardless of whether this is an INIT prompt or CONTINUATION prompt. When a worker restarts or re-initializes a session, it loads a stale `memorySessionId` from a previous SDK session and tries to resume into a session that no longer exists in Claude's context.
-
-**Evidence from logs:**
-```
-[17:30:21.773] Starting SDK query {
-  hasRealMemorySessionId=true,           ← DB has old memorySessionId
-  resume_parameter=5439891b-...,         ← Trying to resume with it
-  lastPromptNumber=1                     ← But this is a NEW SDK session!
-}
-[17:30:24.450] Generator failed {error=Claude Code process exited with code 1}
-```
-
----
-
-## Phase 0: Documentation Discovery (COMPLETED)
-
-### Allowed APIs (from subagent research)
-
-**V1 SDK API (currently used):**
-```typescript
-// From @anthropic-ai/claude-agent-sdk
-function query(options: {
-  prompt: string | AsyncIterable<SDKUserMessage>;
-  options: {
-    model: string;
-    resume?: string;  // SESSION ID - only use for CONTINUATION
-    disallowedTools?: string[];
-    abortController?: AbortController;
-    pathToClaudeCodeExecutable?: string;
-  }
-}): AsyncIterable<SDKMessage>
-```
-
-**Resume Parameter Rules (from docs/context/agent-sdk-v2-preview.md and SESSION_ID_ARCHITECTURE.md):**
-- `resume` should only be used when continuing an existing SDK conversation
-- For INIT prompts (first prompt in a fresh SDK session), no resume parameter should be passed
-- Session ID is captured from first SDK message and stored for subsequent prompts
-
-### Anti-Patterns to Avoid
-- Passing `resume` parameter with INIT prompts (causes crash)
-- Using `contentSessionId` for resume (contaminates user session)
-- Assuming memorySessionId validity without checking prompt context
-
----
-
-## Phase 1: Fix the Resume Parameter Logic
-
-### What to Implement
-
-Modify `src/services/worker/SDKAgent.ts` line 94 to check BOTH conditions:
-1. `hasRealMemorySessionId` - memorySessionId exists and is non-null
-2. `session.lastPromptNumber > 1` - this is a CONTINUATION, not an INIT prompt
-
-### Current Code (line 89-99):
-```typescript
-const queryResult = query({
-  prompt: messageGenerator,
-  options: {
-    model: modelId,
-    // Resume with captured memorySessionId (null on first prompt, real ID on subsequent)
-    ...(hasRealMemorySessionId && { resume: session.memorySessionId }),
-    disallowedTools,
-    abortController: session.abortController,
-    pathToClaudeCodeExecutable: claudePath
-  }
-});
-```
-
-### Fixed Code:
-```typescript
-const queryResult = query({
-  prompt: messageGenerator,
-  options: {
-    model: modelId,
-    // Only resume if BOTH: (1) we have a memorySessionId AND (2) this isn't the first prompt
-    // On worker restart, memorySessionId may exist from a previous SDK session but we
-    // need to start fresh since the SDK context was lost
-    ...(hasRealMemorySessionId && session.lastPromptNumber > 1 && { resume: session.memorySessionId }),
-    disallowedTools,
-    abortController: session.abortController,
-    pathToClaudeCodeExecutable: claudePath
-  }
-});
-```
-
-### Also Update the Comment at Line 66-68:
-```typescript
-// CRITICAL: Only resume if:
-// 1. memorySessionId exists (was captured from a previous SDK response)
-// 2. lastPromptNumber > 1 (this is a continuation within the same SDK session)
-// On worker restart or crash recovery, memorySessionId may exist from a previous
-// SDK session but we must NOT resume because the SDK context was lost.
-// NEVER use contentSessionId for resume - that would inject messages into the user's transcript!
-```
-
-### Verification Checklist
-- [ ] `grep "hasRealMemorySessionId && session.lastPromptNumber > 1" src/services/worker/SDKAgent.ts` returns the fix
-- [ ] Build succeeds: `npm run build`
-- [ ] No TypeScript errors
-
----
-
-## Phase 2: Add Logging for Debugging
-
-### What to Implement
-
-Enhance the alignment log at line 81-85 to clearly indicate when resume is skipped due to INIT prompt:
-
-```typescript
-// Debug-level alignment logs for detailed tracing
-if (session.lastPromptNumber > 1) {
-  const willResume = hasRealMemorySessionId;
-  logger.debug('SDK', `[ALIGNMENT] Resume Decision | contentSessionId=${session.contentSessionId} | memorySessionId=${session.memorySessionId} | prompt#=${session.lastPromptNumber} | hasRealMemorySessionId=${hasRealMemorySessionId} | willResume=${willResume} | resumeWith=${willResume ? session.memorySessionId : 'NONE'}`);
-} else {
-  // INIT prompt - never resume even if memorySessionId exists (stale from previous session)
-  const hasStaleMemoryId = hasRealMemorySessionId;
-  logger.debug('SDK', `[ALIGNMENT] First Prompt (INIT) | contentSessionId=${session.contentSessionId} | prompt#=${session.lastPromptNumber} | hasStaleMemoryId=${hasStaleMemoryId} | action=START_FRESH | Will capture new memorySessionId from SDK response`);
-  if (hasStaleMemoryId) {
-    logger.warn('SDK', `Skipping resume for INIT prompt despite existing memorySessionId=${session.memorySessionId} - SDK context was lost (worker restart or crash recovery)`);
-  }
-}
-```
-
-### Verification Checklist
-- [ ] Build succeeds: `npm run build`
-- [ ] Log message appears when running with stale session scenario
-
----
-
-## Phase 3: Add Unit Tests
-
-### What to Implement
-
-Create tests in `tests/sdk-agent-resume.test.ts` following patterns from `tests/session_id_usage_validation.test.ts`:
-
-```typescript
-import { describe, it, expect, beforeEach, afterEach, mock } from 'bun:test';
-
-describe('SDKAgent Resume Parameter Logic', () => {
-  describe('hasRealMemorySessionId check', () => {
-    it('should NOT pass resume parameter when lastPromptNumber === 1 even if memorySessionId exists', () => {
-      // Scenario: Worker restart with stale memorySessionId
-      const session = {
-        memorySessionId: 'stale-session-id-from-previous-run',
-        lastPromptNumber: 1,  // INIT prompt
-      };
-
-      const hasRealMemorySessionId = !!session.memorySessionId;
-      const shouldResume = hasRealMemorySessionId && session.lastPromptNumber > 1;
-
-      expect(hasRealMemorySessionId).toBe(true);  // memorySessionId exists
-      expect(shouldResume).toBe(false);  // but should NOT resume
-    });
-
-    it('should pass resume parameter when lastPromptNumber > 1 AND memorySessionId exists', () => {
-      // Scenario: Normal continuation within same SDK session
-      const session = {
-        memorySessionId: 'valid-session-id',
-        lastPromptNumber: 2,  // CONTINUATION prompt
-      };
-
-      const hasRealMemorySessionId = !!session.memorySessionId;
-      const shouldResume = hasRealMemorySessionId && session.lastPromptNumber > 1;
-
-      expect(hasRealMemorySessionId).toBe(true);
-      expect(shouldResume).toBe(true);
-    });
-
-    it('should NOT pass resume parameter when memorySessionId is null', () => {
-      // Scenario: Fresh session, no captured ID yet
-      const session = {
-        memorySessionId: null,
-        lastPromptNumber: 1,
-      };
-
-      const hasRealMemorySessionId = !!session.memorySessionId;
-      const shouldResume = hasRealMemorySessionId && session.lastPromptNumber > 1;
-
-      expect(hasRealMemorySessionId).toBe(false);
-      expect(shouldResume).toBe(false);
-    });
-  });
-});
-```
-
-### Documentation Reference
-- Pattern: `tests/session_id_usage_validation.test.ts` lines 1-50 for test structure
-- Mock pattern: `tests/worker/agents/response-processor.test.ts` for session mocking
-
-### Verification Checklist
-- [ ] Tests pass: `bun test tests/sdk-agent-resume.test.ts`
-- [ ] Test file follows project conventions
-
----
-
-## Phase 4: Build and Deploy
-
-### What to Implement
-
-1. Build the plugin: `npm run build-and-sync`
-2. Verify worker restarts with fix applied
-
-### Verification Checklist
-- [ ] `npm run build-and-sync` succeeds
-- [ ] Worker health check passes: `curl http://localhost:37777/api/health`
-- [ ] No "Claude Code process exited with code 1" errors in logs after restart
-
----
-
-## Phase 5: Final Verification
-
-### Verification Commands
-
-```bash
-# 1. Verify fix is in place
-grep -n "hasRealMemorySessionId && session.lastPromptNumber > 1" src/services/worker/SDKAgent.ts
-
-# 2. Verify no crashes in recent logs
-tail -100 ~/.claude-mem/logs/claude-mem-$(date +%Y-%m-%d).log | grep -c "exited with code 1"
-
-# 3. Run tests
-bun test tests/sdk-agent-resume.test.ts
-
-# 4. Check for anti-patterns (should return 0 results)
-grep -n "hasRealMemorySessionId && { resume" src/services/worker/SDKAgent.ts
-```
-
-### Success Criteria
-- [ ] Fix in place at SDKAgent.ts:94
-- [ ] Zero "exited with code 1" errors related to stale resume
-- [ ] All tests pass
-- [ ] Worker stable for 10+ minutes without crash loop
-
----
-
-## Files to Modify
-
-1. `src/services/worker/SDKAgent.ts` - Fix resume logic (Phase 1 & 2)
-2. `tests/sdk-agent-resume.test.ts` - New test file (Phase 3)
-
-## Estimated Complexity
-
-- **Phase 1**: Low - Single line change with updated condition
-- **Phase 2**: Low - Enhanced logging
-- **Phase 3**: Medium - New test file following existing patterns
-- **Phase 4-5**: Low - Standard build/verify process

.claude/plans/folder-claude-md-generator.md

@@ -1,298 +0,0 @@
-# Folder CLAUDE.md Generator
-
-## CORE DIRECTIVE (NON-NEGOTIABLE)
-
-**EXTEND THE EXISTING CURSOR RULES TIMELINE GENERATION SYSTEM TO ALSO WRITE CLAUDE.MD FILES**
-
-- DO NOT create new services
-- DO NOT create new orchestrators
-- DO NOT create new HTTP routes
-- DO NOT create new database query functions
-- EXTEND existing functions to add folder-level output
-
----
-
-## Approved Directives (From Planning Conversation)
-
-### Trigger Mechanism
-- Observation save triggers folder CLAUDE.md regeneration **INLINE**
-- NO batching
-- NO debouncing
-- NO Set-based queuing
-- NO session-end hook
-- Synchronous: `observation.save()` → update folder CLAUDE.md files → done
-
-### Tag Strategy
-- Wrap ONLY auto-generated content with `<claude-mem-context>` tags
-- Everything outside tags is untouched (user's manual content preserved)
-- If tags are deleted, just regenerate them
-- NO backup system
-- NO manual content markers
-
-### Git Behavior
-- CLAUDE.md files SHOULD be committed (intentional)
-- `<claude-mem-context>` tag is searchable fingerprint for GitHub analytics
-- NO .gitignore for these files
-
-### Phasing
-- **Phase 1**: CLAUDE.md generation only (THIS PLAN)
-- **Phase 2**: IDE symlinks (FUTURE)
-
-### REJECTED
-- Cross-folder linking — NO
-- Semantic grouping — deferred enhancement only
-- Team sync — future phase
-
-### DEFERRED
-- Priority weighting by observation type
-- IDE-specific template refinements
-
----
-
-## Phase 0: Documentation Discovery (COMPLETED)
-
-### Existing APIs to USE (Not Rebuild)
-
-| Function | Location | Purpose |
-|----------|----------|---------|
-| `findByFile(filePath, options)` | `src/services/sqlite/SessionSearch.ts:342` | Query observations by folder prefix (already supports LIKE wildcards) |
-| `updateCursorContextForProject()` | `src/services/integrations/CursorHooksInstaller.ts:98` | Write context files after observation save |
-| `writeContextFile()` | `src/utils/cursor-utils.ts:97` | Atomic file write with temp file + rename |
-| `extractFirstFile()` | `src/shared/timeline-formatting.ts` | Extract file paths from JSON arrays |
-| `groupByDate()` | `src/shared/timeline-formatting.ts` | Group items chronologically |
-| `formatTime()`, `formatDate()` | `src/shared/timeline-formatting.ts` | Time formatting |
-
-### Existing Integration Points
-
-| Location | What Happens | Extension Point |
-|----------|--------------|-----------------|
-| `ResponseProcessor.ts:266` | Calls `updateCursorContextForProject()` after summary save | Add folder CLAUDE.md update here |
-| `CursorHooksInstaller.ts:98` | `updateCursorContextForProject()` fetches context and writes file | Add sibling function for folder updates |
-
-### Anti-Patterns to AVOID
-- Creating `FolderIndexOrchestrator.ts` — NO
-- Creating `FolderTimelineCompiler.ts` — NO
-- Creating `FolderDiscovery.ts` — NO
-- Creating `ClaudeMdGenerator.ts` — NO
-- Creating `FolderIndexRoutes.ts` — NO
-- Adding new HTTP endpoints — NO
-- Adding new settings in `SettingsDefaultsManager.ts` — NO (use sensible defaults inline)
-
----
-
-## Phase 1: Extend CursorHooksInstaller
-
-### What to Implement
-
-Add ONE new function to `src/services/integrations/CursorHooksInstaller.ts`:
-
-```typescript
-/**
- * Update CLAUDE.md files for folders touched by an observation.
- * Called inline after observation save, similar to updateCursorContextForProject.
- */
-export async function updateFolderClaudeMd(
-  workspacePath: string,
-  filesModified: string[],
-  filesRead: string[],
-  project: string,
-  port: number
-): Promise<void>
-```
-
-### Implementation Pattern (Copy From)
-
-Follow the EXACT pattern of `updateCursorContextForProject()` at line 98:
-1. Extract unique folder paths from filesModified and filesRead
-2. For each folder, fetch timeline via existing `/api/search/file?files=<folderPath>` endpoint
-3. Format as simple timeline (reuse existing formatters)
-4. Write to `<folder>/CLAUDE.md` preserving content outside `<claude-mem-context>` tags
-
-### Tag Preservation Logic
-
-```typescript
-function replaceTaggedContent(existingContent: string, newContent: string): string {
-  const startTag = '<claude-mem-context>';
-  const endTag = '</claude-mem-context>';
-
-  // If no existing content, wrap new content in tags
-  if (!existingContent) {
-    return `${startTag}\n${newContent}\n${endTag}`;
-  }
-
-  // If existing has tags, replace only tagged section
-  const startIdx = existingContent.indexOf(startTag);
-  const endIdx = existingContent.indexOf(endTag);
-
-  if (startIdx !== -1 && endIdx !== -1) {
-    return existingContent.substring(0, startIdx) +
-           `${startTag}\n${newContent}\n${endTag}` +
-           existingContent.substring(endIdx + endTag.length);
-  }
-
-  // If no tags exist, append tagged content at end
-  return existingContent + `\n\n${startTag}\n${newContent}\n${endTag}`;
-}
-```
-
-### Verification Checklist
-- [ ] Function added to CursorHooksInstaller.ts
-- [ ] Uses existing `findByFile` endpoint (no new database queries)
-- [ ] Preserves content outside `<claude-mem-context>` tags
-- [ ] Atomic writes (temp file + rename)
-- [ ] Build passes: `npm run build`
-
----
-
-## Phase 2: Hook Into ResponseProcessor
-
-### What to Implement
-
-Add call to `updateFolderClaudeMd()` in `src/services/worker/agents/ResponseProcessor.ts`, right after the existing `updateCursorContextForProject()` call at line 266.
-
-### Code Location
-
-In `syncAndBroadcastSummary()` function, after line 269:
-
-```typescript
-// EXISTING: Update Cursor context file for registered projects (fire-and-forget)
-updateCursorContextForProject(session.project, getWorkerPort()).catch(error => {
-  logger.warn('CURSOR', 'Context update failed (non-critical)', { project: session.project }, error as Error);
-});
-
-// NEW: Update folder CLAUDE.md files for touched folders (fire-and-forget)
-// Extract file paths from the saved observations
-updateFolderClaudeMd(
-  workspacePath,  // From registry lookup
-  filesModified,  // From observations
-  filesRead,      // From observations
-  session.project,
-  getWorkerPort()
-).catch(error => {
-  logger.warn('FOLDER_INDEX', 'CLAUDE.md update failed (non-critical)', { project: session.project }, error as Error);
-});
-```
-
-### Data Flow
-1. `processAgentResponse()` saves observations → gets back `observationIds`
-2. Fetch observation records to get `files_read` and `files_modified`
-3. Pass to `updateFolderClaudeMd()`
-
-### Verification Checklist
-- [ ] Call added to ResponseProcessor.ts
-- [ ] Fire-and-forget pattern (non-blocking, errors logged)
-- [ ] Uses existing observation data (no new queries)
-- [ ] Build passes: `npm run build`
-
----
-
-## Phase 3: Timeline Formatting
-
-### What to Implement
-
-Create a minimal timeline formatter for CLAUDE.md output. This can be:
-1. A simple function in CursorHooksInstaller.ts, OR
-2. Reuse existing `ResultFormatter.formatSearchResults()` from `src/services/worker/search/ResultFormatter.ts`
-
-### Output Format
-
-```markdown
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-<claude-mem-context>
-
-### 2026-01-04
-
-| Time | Type | Title |
-|------|------|-------|
-| 4:30pm | feature | Added folder index support |
-| 3:15pm | bugfix | Fixed file path handling |
-
-### 2026-01-03
-
-| Time | Type | Title |
-|------|------|-------|
-| 11:00am | refactor | Cleaned up cursor utils |
-
-</claude-mem-context>
-```
-
-### Key Points
-- Compact format (time, type emoji, title only)
-- Grouped by date
-- Limited to last N days or observations (sensible default: 10)
-- NO token counts
-- NO file columns (redundant - we're IN the folder)
-
-### Verification Checklist
-- [ ] Formatter produces clean markdown
-- [ ] Output is concise (not verbose)
-- [ ] Grouped by date
-- [ ] Build passes: `npm run build`
-
----
-
-## Phase 4: Verification
-
-### Functional Tests
-
-1. **Manual Test**:
-   - Start worker: `npm run dev`
-   - Create a test observation touching `src/services/sqlite/`
-   - Verify `src/services/sqlite/CLAUDE.md` is created/updated
-   - Verify `<claude-mem-context>` tags are present
-   - Verify manual content outside tags is preserved
-
-2. **Build Check**:
-   ```bash
-   npm run build
-   ```
-
-3. **Grep for Anti-Patterns**:
-   ```bash
-   # Should find NOTHING
-   grep -r "FolderIndexOrchestrator" src/
-   grep -r "FolderTimelineCompiler" src/
-   grep -r "FolderDiscovery" src/
-   grep -r "ClaudeMdGenerator" src/
-   grep -r "FolderIndexRoutes" src/
-   ```
-
-4. **Grep for Correct Implementation**:
-   ```bash
-   # Should find the new function
-   grep -r "updateFolderClaudeMd" src/
-   ```
-
-### Tag Preservation Test
-
-1. Create `src/test-folder/CLAUDE.md` with manual content:
-   ```markdown
-   # My Notes
-   This is manual content I wrote.
-   ```
-
-2. Trigger observation save touching files in `src/test-folder/`
-
-3. Verify result:
-   ```markdown
-   # My Notes
-   This is manual content I wrote.
-
-   <claude-mem-context>
-   ### 2026-01-04
-   | Time | Type | Title |
-   ...
-   </claude-mem-context>
-   ```
-
----
-
-## Summary
-
-This is a **~100 line change** spread across 2 files:
-1. `CursorHooksInstaller.ts` — Add `updateFolderClaudeMd()` function (~60 lines)
-2. `ResponseProcessor.ts` — Add call to the new function (~10 lines)
-
-NO new files. NO new services. NO new routes. Just extending existing patterns.

.claude/plans/folder-claude-md-refactor.md

@@ -1,378 +0,0 @@
-# Folder CLAUDE.md Refactor - Extract to Shared Utils
-
-## CORE DIRECTIVE
-
-**DECOUPLE FOLDER CLAUDE.MD WRITING FROM CURSOR INTEGRATION**
-
-The current implementation incorrectly couples folder-level CLAUDE.md generation to Cursor-specific registry lookups. The file paths from observations are already absolute - no workspace registry lookup is needed.
-
----
-
-## Phase 0: Documentation Discovery (COMPLETED)
-
-### Current Implementation Location
-
-| Function | Location | Lines | Purpose |
-|----------|----------|-------|---------|
-| `updateFolderClaudeMd` | CursorHooksInstaller.ts | 128-199 | Orchestrates folder CLAUDE.md updates |
-| `formatTimelineForClaudeMd` | CursorHooksInstaller.ts | 221-295 | Parses API response to markdown |
-| `replaceTaggedContent` | CursorHooksInstaller.ts | 300-321 | Preserves user content outside tags |
-| `writeFolderClaudeMd` | CursorHooksInstaller.ts | 326-353 | Atomic file write |
-
-### Integration Point
-
-**File:** `src/services/worker/agents/ResponseProcessor.ts:274-298`
-
-Current (problematic) code:
-```typescript
-const registry = readCursorRegistry();
-const registryEntry = registry[session.project];
-
-if (registryEntry && (filesModified.length > 0 || filesRead.length > 0)) {
-  updateFolderClaudeMd(
-    registryEntry.workspacePath,  // <-- PROBLEM: Needs Cursor registry
-    filesModified,
-    filesRead,
-    session.project,
-    getWorkerPort()
-  ).catch(error => { ... });
-}
-```
-
-### The Problem
-
-1. `filesModified` and `filesRead` already contain **absolute paths**
-2. We don't need `workspacePath` - just extract folder from file path directly
-3. Cursor registry is only populated when Cursor hooks are installed
-4. This makes folder CLAUDE.md a Cursor-only feature (unintended)
-
-### Project Utils Pattern
-
-**From `src/utils/cursor-utils.ts:97-122`:**
-- Pure functions with paths as parameters
-- Atomic write pattern: temp file + rename
-- `mkdirSync(dir, { recursive: true })` for directory creation
-
-### Related Utils
-
-**`src/utils/tag-stripping.ts`** - Handles *stripping* tags (input filtering)
-- `stripMemoryTagsFromJson()` - removes `<claude-mem-context>` content
-- `stripMemoryTagsFromPrompt()` - removes `<private>` content
-
-Our `replaceTaggedContent` handles *preserving/replacing* (output writing) - complementary, not duplicative.
-
----
-
-## Phase 1: Create Shared Utils File
-
-### What to Implement
-
-Create `src/utils/claude-md-utils.ts` with extracted and simplified functions.
-
-### File Structure
-
-```typescript
-/**
- * CLAUDE.md File Utilities
- *
- * Shared utilities for writing folder-level CLAUDE.md files with
- * auto-generated context sections. Preserves user content outside
- * <claude-mem-context> tags.
- */
-
-import { existsSync, readFileSync, writeFileSync, renameSync, mkdirSync } from 'fs';
-import path from 'path';
-import { logger } from './logger.js';
-
-/**
- * Replace tagged content in existing file, preserving content outside tags.
- *
- * Handles three cases:
- * 1. No existing content → wraps new content in tags
- * 2. Has existing tags → replaces only tagged section
- * 3. No tags in existing content → appends tagged content at end
- */
-export function replaceTaggedContent(existingContent: string, newContent: string): string {
-  // Copy from CursorHooksInstaller.ts:300-321
-}
-
-/**
- * Write CLAUDE.md file to folder with atomic writes.
- * Creates directory structure if needed.
- *
- * @param folderPath - Absolute path to the folder
- * @param newContent - Content to write inside tags
- */
-export function writeClaudeMdToFolder(folderPath: string, newContent: string): void {
-  // Simplified from writeFolderClaudeMd - no workspacePath needed
-  // Copy atomic write pattern from CursorHooksInstaller.ts:326-353
-}
-
-/**
- * Format timeline text from API response to compact CLAUDE.md format.
- *
- * @param timelineText - Raw API response text
- * @returns Formatted markdown with date headers and compact table
- */
-export function formatTimelineForClaudeMd(timelineText: string): string {
-  // Copy from CursorHooksInstaller.ts:221-295
-}
-```
-
-### Key Simplification
-
-**OLD `writeFolderClaudeMd` signature:**
-```typescript
-async function writeFolderClaudeMd(
-  workspacePath: string,  // <-- REMOVE
-  folderPath: string,
-  newContent: string
-): Promise<void>
-```
-
-**NEW `writeClaudeMdToFolder` signature:**
-```typescript
-export function writeClaudeMdToFolder(
-  folderPath: string,     // Must be absolute path
-  newContent: string
-): void                   // Sync is fine, atomic anyway
-```
-
-### Verification Checklist
-- [ ] File created at `src/utils/claude-md-utils.ts`
-- [ ] `replaceTaggedContent` exported and handles all 3 cases
-- [ ] `writeClaudeMdToFolder` exported with atomic writes
-- [ ] `formatTimelineForClaudeMd` exported
-- [ ] Build passes: `npm run build`
-
----
-
-## Phase 2: Create Folder Index Service Function
-
-### What to Implement
-
-Create a new orchestrating function that replaces `updateFolderClaudeMd`. This should NOT be in CursorHooksInstaller - it's a general feature.
-
-**Option A:** Add to `src/utils/claude-md-utils.ts` (keeps it simple)
-**Option B:** Create `src/services/folder-index-service.ts` (follows service pattern)
-
-Recommend **Option A** for simplicity - it's just one function.
-
-### New Function
-
-```typescript
-/**
- * Update CLAUDE.md files for folders containing the given files.
- * Fetches timeline from worker API and writes formatted content.
- *
- * @param filePaths - Array of absolute file paths (modified or read)
- * @param project - Project identifier for API query
- * @param port - Worker API port
- */
-export async function updateFolderClaudeMdFiles(
-  filePaths: string[],
-  project: string,
-  port: number
-): Promise<void> {
-  // Extract unique folder paths from file paths
-  const folderPaths = new Set<string>();
-  for (const filePath of filePaths) {
-    if (!filePath || filePath === '') continue;
-    const folderPath = path.dirname(filePath);
-    if (folderPath && folderPath !== '.' && folderPath !== '/') {
-      folderPaths.add(folderPath);
-    }
-  }
-
-  if (folderPaths.size === 0) return;
-
-  logger.debug('FOLDER_INDEX', 'Updating CLAUDE.md files', {
-    project,
-    folderCount: folderPaths.size
-  });
-
-  // Process each folder
-  for (const folderPath of folderPaths) {
-    try {
-      // Fetch timeline via existing API
-      const response = await fetch(
-        `http://127.0.0.1:${port}/api/search/by-file?filePath=${encodeURIComponent(folderPath)}&limit=10&project=${encodeURIComponent(project)}`
-      );
-
-      if (!response.ok) {
-        logger.warn('FOLDER_INDEX', 'Failed to fetch timeline', { folderPath, status: response.status });
-        continue;
-      }
-
-      const result = await response.json();
-      if (!result.content?.[0]?.text) {
-        logger.debug('FOLDER_INDEX', 'No content for folder', { folderPath });
-        continue;
-      }
-
-      const formatted = formatTimelineForClaudeMd(result.content[0].text);
-      writeClaudeMdToFolder(folderPath, formatted);
-
-      logger.debug('FOLDER_INDEX', 'Updated CLAUDE.md', { folderPath });
-    } catch (error) {
-      logger.warn('FOLDER_INDEX', 'Failed to update CLAUDE.md', { folderPath }, error as Error);
-    }
-  }
-}
-```
-
-### Verification Checklist
-- [ ] `updateFolderClaudeMdFiles` function added
-- [ ] Takes only `filePaths`, `project`, `port` (no workspacePath)
-- [ ] Extracts folder paths from absolute file paths
-- [ ] Uses `writeClaudeMdToFolder` for atomic writes
-- [ ] Build passes: `npm run build`
-
----
-
-## Phase 3: Update ResponseProcessor Integration
-
-### What to Implement
-
-Simplify the call site in `src/services/worker/agents/ResponseProcessor.ts`.
-
-### Current Code (lines 274-298)
-```typescript
-// Update folder CLAUDE.md files for touched folders (fire-and-forget)
-const filesModified: string[] = [];
-const filesRead: string[] = [];
-
-for (const obs of observations) {
-  filesModified.push(...(obs.files_modified || []));
-  filesRead.push(...(obs.files_read || []));
-}
-
-// Get workspace path from project registry
-const registry = readCursorRegistry();
-const registryEntry = registry[session.project];
-
-if (registryEntry && (filesModified.length > 0 || filesRead.length > 0)) {
-  updateFolderClaudeMd(
-    registryEntry.workspacePath,
-    filesModified,
-    filesRead,
-    session.project,
-    getWorkerPort()
-  ).catch(error => {
-    logger.warn('FOLDER_INDEX', 'CLAUDE.md update failed (non-critical)', { project: session.project }, error as Error);
-  });
-}
-```
-
-### New Code
-```typescript
-// Update folder CLAUDE.md files for touched folders (fire-and-forget)
-const allFilePaths: string[] = [];
-for (const obs of observations) {
-  allFilePaths.push(...(obs.files_modified || []));
-  allFilePaths.push(...(obs.files_read || []));
-}
-
-if (allFilePaths.length > 0) {
-  updateFolderClaudeMdFiles(
-    allFilePaths,
-    session.project,
-    getWorkerPort()
-  ).catch(error => {
-    logger.warn('FOLDER_INDEX', 'CLAUDE.md update failed (non-critical)', { project: session.project }, error as Error);
-  });
-}
-```
-
-### Import Changes
-
-**Remove:**
-```typescript
-import { updateFolderClaudeMd, readCursorRegistry } from '../../integrations/CursorHooksInstaller.js';
-```
-
-**Add:**
-```typescript
-import { updateFolderClaudeMdFiles } from '../../../utils/claude-md-utils.js';
-```
-
-**Keep (if still needed for Cursor context):**
-```typescript
-import { updateCursorContextForProject } from '../../worker-service.js';
-```
-
-### Verification Checklist
-- [ ] Import updated to use `claude-md-utils.ts`
-- [ ] `readCursorRegistry` import removed (if no longer needed)
-- [ ] Call site simplified - no registry lookup
-- [ ] Fire-and-forget pattern preserved
-- [ ] Build passes: `npm run build`
-
----
-
-## Phase 4: Clean Up CursorHooksInstaller
-
-### What to Implement
-
-Remove the extracted functions from `src/services/integrations/CursorHooksInstaller.ts`.
-
-### Functions to Remove
-- `updateFolderClaudeMd` (lines 128-199)
-- `formatTimelineForClaudeMd` (lines 221-295)
-- `replaceTaggedContent` (lines 300-321)
-- `writeFolderClaudeMd` (lines 326-353)
-
-### Verification Checklist
-- [ ] All 4 functions removed from CursorHooksInstaller.ts
-- [ ] No dangling references to removed functions
-- [ ] CursorHooksInstaller still exports what it needs for Cursor integration
-- [ ] Build passes: `npm run build`
-- [ ] Grep shows no references to old function locations
-
----
-
-## Phase 5: Verification
-
-### Build Check
-```bash
-npm run build
-```
-
-### Anti-Pattern Grep (should find NOTHING in CursorHooksInstaller)
-```bash
-grep -n "updateFolderClaudeMd\|formatTimelineForClaudeMd\|replaceTaggedContent\|writeFolderClaudeMd" src/services/integrations/CursorHooksInstaller.ts
-```
-
-### Correct Location Grep (should find in claude-md-utils)
-```bash
-grep -rn "updateFolderClaudeMdFiles\|writeClaudeMdToFolder\|formatTimelineForClaudeMd" src/utils/
-```
-
-### Integration Check
-```bash
-grep -n "updateFolderClaudeMdFiles" src/services/worker/agents/ResponseProcessor.ts
-```
-
-### No Cursor Registry Dependency
-```bash
-grep -n "readCursorRegistry" src/services/worker/agents/ResponseProcessor.ts
-# Should return nothing (or only for Cursor context, not folder index)
-```
-
----
-
-## Summary
-
-**~150 lines moved** from CursorHooksInstaller.ts to claude-md-utils.ts with simplification:
-
-| Before | After |
-|--------|-------|
-| 4 functions in CursorHooksInstaller | 4 functions in claude-md-utils |
-| Requires Cursor registry lookup | Works with absolute paths directly |
-| `updateFolderClaudeMd(workspacePath, ...)` | `updateFolderClaudeMdFiles(filePaths, ...)` |
-| Coupled to Cursor integration | Independent utility |
-
-**Files Changed:**
-1. `src/utils/claude-md-utils.ts` - NEW (create)
-2. `src/services/worker/agents/ResponseProcessor.ts` - UPDATE (simplify call site)
-3. `src/services/integrations/CursorHooksInstaller.ts` - UPDATE (remove extracted functions)

.claude/plans/folder-claude-md-timeline-format.md

@@ -1,186 +0,0 @@
-# Plan: Change Folder CLAUDE.md to Timeline Format
-
-## Goal
-
-Replace the simple table format in folder-level CLAUDE.md files with the timeline format used by search results.
-
-## Current vs Target Format
-
-### Current Format (Simple)
-```markdown
-# Recent Activity
-
-### Recent
-
-| Time | Type | Title |
-|------|------|-------|
-| 6:33pm | feature | Multiple CLAUDE.md files generated |
-| 6:32pm | feature | CLAUDE.md file successfully generated |
-```
-
-### Target Format (Timeline)
-```markdown
-# Recent Activity
-
-### Jan 4, 2026
-
-**src/services/worker/agents/ResponseProcessor.ts**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #37110 | 6:35 PM | 🔴 | Folder CLAUDE.md updates moved from summary | ~85 |
-| #37109 | " | ✅ | ResponseProcessor.ts modified | ~92 |
-
-**General**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #37108 | 6:33 PM | 🟣 | Multiple CLAUDE.md files generated | ~78 |
-```
-
-## Key Changes
-
-1. **Group by date** - Use `### Jan 4, 2026` instead of `### Recent`
-2. **Group by file within each date** - Add `**filename**` headers
-3. **Expand columns** - Add ID and Read columns: `| ID | Time | T | Title | Read |`
-4. **Use type emojis** - Use `🔴` `🟣` `✅` etc. instead of text
-5. **Show ditto marks** - Use `"` for repeated times
-
----
-
-## Phase 1: Refactor formatTimelineForClaudeMd
-
-**File:** `src/utils/claude-md-utils.ts`
-
-**Tasks:**
-
-1. Add imports from shared utilities:
-   ```typescript
-   import { formatDate, formatTime, extractFirstFile, estimateTokens, groupByDate } from '../shared/timeline-formatting.js';
-   import { ModeManager } from '../services/domain/ModeManager.js';
-   ```
-
-2. Replace `formatTimelineForClaudeMd()` (lines 78-151) with new implementation that:
-   - Parses API response to extract full observation data (id, time, type emoji, title, files)
-   - Groups observations by date using `groupByDate()`
-   - Within each date, groups by file using a Map
-   - Renders file sections with `**filename**` headers
-   - Uses search table format: `| ID | Time | T | Title | Read |`
-   - Uses ditto marks for repeated times
-
-**Pattern to Copy From:** `src/services/worker/search/ResultFormatter.ts` lines 56-108
-
-**Key APIs:**
-- `groupByDate(items, getDate)` - from `src/shared/timeline-formatting.ts:104-127`
-- `formatTime(epoch)` - from `src/shared/timeline-formatting.ts:46-53`
-- `formatDate(epoch)` - from `src/shared/timeline-formatting.ts:59-66`
-- `extractFirstFile(filesModified, cwd)` - from `src/shared/timeline-formatting.ts:81-84`
-- `estimateTokens(text)` - from `src/shared/timeline-formatting.ts:89-92`
-- `ModeManager.getInstance().getTypeIcon(type)` - from `src/services/domain/ModeManager.ts`
-
-**Verification:**
-1. Run `npm run build` - no errors
-2. Restart worker: `npm run worker:restart`
-3. Make a test edit to trigger observation
-4. Check generated CLAUDE.md files for new format
-
----
-
-## Phase 2: Parse Full Observation Data from API
-
-**Context:** The current regex parsing extracts only time, type emoji, and title. Need to also extract:
-- Observation ID (for `#123` column)
-- File path (from files_modified in API response, for grouping)
-- Token estimate (for `Read` column)
-
-**Challenge:** The current API returns formatted text, not structured data. We need to:
-1. Parse the existing text format more thoroughly, OR
-2. Use a different API endpoint that returns JSON
-
-**Decision Point:** Check what data the `/api/search/by-file` endpoint returns. If it returns structured JSON with observations, use that. Otherwise, enhance parsing.
-
-**Investigation Required:**
-- Read `src/services/worker/http/routes/SearchRoutes.ts` to see by-file response format
-- Determine if we can access raw observation data or just formatted text
-
-**Verification:**
-- Confirm API response structure
-- Update parsing to extract all needed fields
-
----
-
-## Phase 3: Integrate File-Based Grouping
-
-**File:** `src/utils/claude-md-utils.ts`
-
-**Tasks:**
-
-1. Create helper to group by file:
-   ```typescript
-   function groupByFile(observations: ParsedObservation[]): Map<string, ParsedObservation[]> {
-     const byFile = new Map<string, ParsedObservation[]>();
-     for (const obs of observations) {
-       const file = obs.file || 'General';
-       if (!byFile.has(file)) byFile.set(file, []);
-       byFile.get(file)!.push(obs);
-     }
-     return byFile;
-   }
-   ```
-
-2. Render with file sections:
-   ```typescript
-   for (const [file, fileObs] of resultsByFile) {
-     lines.push(`**${file}**`);
-     lines.push(`| ID | Time | T | Title | Read |`);
-     lines.push(`|----|------|---|-------|------|`);
-     // render rows with ditto marks
-   }
-   ```
-
-**Pattern to Copy From:** `ResultFormatter.formatSearchResults()` lines 60-108
-
-**Verification:**
-- Generated CLAUDE.md shows file grouping
-- Files are displayed as relative paths when possible
-
----
-
-## Phase 4: Final Verification
-
-**Checklist:**
-
-1. **Build passes:** `npm run build`
-2. **Worker restarts cleanly:** `npm run worker:restart`
-3. **Format matches target:**
-   - Date headers: `### Jan 4, 2026`
-   - File sections: `**filename**`
-   - Table columns: `| ID | Time | T | Title | Read |`
-   - Type emojis: `🔴` `🟣` `✅` not text
-   - Ditto marks: `"` for repeated times
-4. **Anti-pattern checks:**
-   - No hardcoded type maps (use ModeManager)
-   - No invented APIs
-   - Reuses existing formatters from shared utils
-5. **Graceful degradation:** Empty results still show `*No recent activity*`
-
----
-
-## Files to Modify
-
-| File | Change |
-|------|--------|
-| `src/utils/claude-md-utils.ts` | Replace `formatTimelineForClaudeMd()` with timeline format |
-
-## Files to Read (Patterns to Copy)
-
-| File | Pattern |
-|------|---------|
-| `src/services/worker/search/ResultFormatter.ts:56-108` | Date/file grouping logic |
-| `src/shared/timeline-formatting.ts` | All formatting utilities |
-| `src/services/domain/ModeManager.ts` | Type icon lookup |
-
-## Anti-Patterns to Avoid
-
-- ❌ Creating new hardcoded type→emoji maps (use ModeManager)
-- ❌ Parsing dates manually (use shared formatters)
-- ❌ Skipping the existing groupByDate utility
-- ❌ Not handling ditto marks for repeated times

.claude/plans/intentional-patterns-execution.md

@@ -1,356 +0,0 @@
-# Execution Plan: Intentional Patterns Validation Actions
-
-**Created:** 2026-01-13
-**Source:** `docs/reports/intentional-patterns-validation.md`
-**Target:** `src/services/worker-service.ts` and related files
-
----
-
-## Phase 0: Documentation Discovery (COMPLETED)
-
-### Evidence Gathered
-
-**Files Analyzed:**
-- `docs/reports/intentional-patterns-validation.md` - Pattern verdicts and recommendations
-- `docs/reports/nonsense-logic.md` - Original 23 issues identified
-- `.claude/plans/cleanup-worker-service-nonsense-logic.md` - Existing cleanup plan
-- `src/services/worker-service.ts` (813 lines) - Current state
-
-**Current State:**
-- File has been reduced from 1445 lines to 813 lines in prior refactoring
-- `runInteractiveSetup` still exists at line 439 (~200 lines of dead code)
-- Re-export at line 78: `export { updateCursorContextForProject };`
-- MCP version hardcoded "1.0.0" at line 159
-- Fallback agents set at lines 144-146 without verification
-- Unused imports: `fs`, `spawn`, `homedir`, `readline` at lines 13-17
-
-**Allowed APIs (from validation report):**
-- Exit code 0 pattern: **KEEP** (documented Windows Terminal workaround)
-- `as Error` casts: **KEEP** (documented project policy)
-- Dual init tracking: **KEEP** (serves async + sync callers)
-- Signal handler ref pattern: **KEEP** (standard JS mutable state sharing)
-- Empty MCP capabilities: **KEEP** (correct per MCP spec)
-
-**Actions Required:**
-| Pattern | Action | Priority |
-|---------|--------|----------|
-| Re-export for circular import | Remove (no actual circular dep) | LOW |
-| Fallback agent without check | Add availability verification | HIGH |
-| MCP version hardcoded | Update to use package.json | LOW |
-| Dead code `runInteractiveSetup` | Delete (~200 lines) | HIGH |
-| Unused imports | Delete | LOW |
-
----
-
-## Phase 1: Delete Dead Code (HIGH PRIORITY)
-
-### 1.1 Delete `runInteractiveSetup` Function
-
-**What:** Delete lines 435-639 (approximately 200 lines)
-**File:** `src/services/worker-service.ts`
-
-**Location confirmed:** Line 439 starts `async function runInteractiveSetup(): Promise<number>`
-
-**Steps:**
-1. Read worker-service.ts lines 435-650 to find exact boundaries
-2. Delete the section comment and entire function
-3. Run build to verify no compile errors
-
-**Verification:**
-```bash
-grep -n "runInteractiveSetup" src/services/worker-service.ts
-# Expected: No output (function deleted)
-npm run build
-# Expected: No errors
-```
-
-### 1.2 Remove Unused Imports
-
-**What:** Delete imports only used by dead code
-**Lines to delete:** 13-17 (check each)
-
-**Current imports to remove:**
-```typescript
-import * as fs from 'fs';              // Line 13 - UNUSED (namespace never accessed)
-import { spawn } from 'child_process'; // Line 14 - UNUSED (MCP uses StdioClientTransport)
-import { homedir } from 'os';          // Line 15 - Only in dead code
-import * as readline from 'readline';  // Line 17 - Only in dead code
-```
-
-**Keep:**
-```typescript
-import { existsSync, writeFileSync, readFileSync, mkdirSync } from 'fs';  // Line 16 - CHECK
-```
-
-**Steps:**
-1. After deleting `runInteractiveSetup`, grep each import
-2. Delete any with zero usages
-3. Run build to verify
-
-**Verification:**
-```bash
-grep -n "^import \* as fs" src/services/worker-service.ts
-grep -n "import { spawn }" src/services/worker-service.ts
-# Expected: No output
-npm run build
-```
-
-### 1.3 Remove Unused CursorHooksInstaller Imports
-
-**After deleting dead code, check:**
-```typescript
-import {
-  updateCursorContextForProject,  // KEEP (re-exported)
-  handleCursorCommand,            // KEEP (used in main)
-  detectClaudeCode,               // DELETE (only in dead code)
-  findCursorHooksDir,             // DELETE (only in dead code)
-  installCursorHooks,             // DELETE (only in dead code)
-  configureCursorMcp              // DELETE (only in dead code)
-} from './integrations/CursorHooksInstaller.js';
-```
-
-**Verification:**
-```bash
-grep "detectClaudeCode\|findCursorHooksDir\|installCursorHooks\|configureCursorMcp" src/services/worker-service.ts
-# Expected: Only import line (which gets trimmed)
-```
-
----
-
-## Phase 2: Fix Fallback Agent Oversight (HIGH PRIORITY)
-
-### 2.1 Add SDKAgent Availability Check
-
-**Problem:** Lines 144-146 set Claude SDK as fallback without verifying it's configured
-```typescript
-this.geminiAgent.setFallbackAgent(this.sdkAgent);
-this.openRouterAgent.setFallbackAgent(this.sdkAgent);
-```
-
-**Risk:** User chooses Gemini because they lack Claude credentials → transient Gemini error → fallback to Claude SDK → cascading failure
-
-**Solution Options:**
-
-**Option A: Add isConfigured() method to SDKAgent**
-1. Add method to SDKAgent that checks for valid Claude SDK credentials
-2. Only set fallback if `sdkAgent.isConfigured()` returns true
-3. Log warning when fallback unavailable
-
-**Pattern to follow (from SDKAgent.ts constructor):**
-```typescript
-// Check if Claude SDK can be initialized
-public isConfigured(): boolean {
-  // Claude SDK uses subprocess, check if claude command exists
-  try {
-    // Check for ANTHROPIC_API_KEY or claude CLI availability
-    return !!process.env.ANTHROPIC_API_KEY || this.checkClaudeCliAvailable();
-  } catch {
-    return false;
-  }
-}
-```
-
-**Option B: Document limitation (minimal fix)**
-Add comment explaining the risk:
-```typescript
-// NOTE: Fallback to Claude SDK may fail if user lacks Claude credentials
-// Consider adding availability check in future (Issue #XXX)
-this.geminiAgent.setFallbackAgent(this.sdkAgent);
-```
-
-**Recommended: Option A**
-
-**Steps:**
-1. Read SDKAgent.ts to understand initialization pattern
-2. Add `isConfigured()` method that checks Claude CLI/credentials
-3. Update worker-service.ts to conditionally set fallback
-4. Add warning log when fallback unavailable
-5. Run tests
-
-**Verification:**
-```bash
-grep -n "isConfigured" src/services/worker/SDKAgent.ts
-# Expected: Method definition
-grep -n "setFallbackAgent" src/services/worker-service.ts
-# Expected: Conditional calls with isConfigured check
-npm test
-```
-
----
-
-## Phase 3: Remove Unnecessary Re-Export (LOW PRIORITY)
-
-### 3.1 Fix Misleading Re-Export
-
-**Current (worker-service.ts:77-78):**
-```typescript
-// Re-export updateCursorContextForProject for SDK agents
-export { updateCursorContextForProject };
-```
-
-**Issue:** Comment implies avoiding circular import, but investigation found NO circular dependency exists.
-
-**Import chain:**
-```
-CursorHooksInstaller.ts (defines) → worker-service.ts (imports, re-exports) → ResponseProcessor.ts (imports)
-```
-
-**ResponseProcessor.ts could import directly from CursorHooksInstaller.ts**
-
-**Options:**
-1. **Remove re-export entirely** - Update ResponseProcessor.ts to import from CursorHooksInstaller directly
-2. **Fix comment** - Update to reflect actual reason (API surface simplification)
-
-**Recommended: Option 1 (cleaner)**
-
-**Steps:**
-1. Update `src/services/worker/agents/ResponseProcessor.ts`:
-   - Change: `import { updateCursorContextForProject } from '../../worker-service.js';`
-   - To: `import { updateCursorContextForProject } from '../../integrations/CursorHooksInstaller.js';`
-2. Delete re-export from worker-service.ts (lines 77-78)
-3. Run build to verify
-
-**Verification:**
-```bash
-grep -n "export { updateCursorContextForProject" src/services/worker-service.ts
-# Expected: No output
-grep -n "updateCursorContextForProject" src/services/worker/agents/ResponseProcessor.ts
-# Expected: Import from CursorHooksInstaller
-npm run build
-```
-
----
-
-## Phase 4: Update MCP Version (LOW PRIORITY)
-
-### 4.1 Use Package Version for MCP Client
-
-**Current (worker-service.ts:157-160):**
-```typescript
-this.mcpClient = new Client({
-  name: 'worker-search-proxy',
-  version: '1.0.0'  // Hardcoded, should match package.json (9.0.4)
-}, { capabilities: {} });
-```
-
-**Also affects (from report):**
-- `src/services/sync/ChromaSync.ts:126-131`
-- MCP server (separate file)
-
-**Pattern to follow:**
-```typescript
-import { version } from '../../package.json' assert { type: 'json' };
-
-this.mcpClient = new Client({
-  name: 'worker-search-proxy',
-  version: version
-}, { capabilities: {} });
-```
-
-**Alternative (if JSON import not supported):**
-```typescript
-import { readFileSync } from 'fs';
-const pkg = JSON.parse(readFileSync(new URL('../../package.json', import.meta.url), 'utf-8'));
-
-this.mcpClient = new Client({
-  name: 'worker-search-proxy',
-  version: pkg.version
-}, { capabilities: {} });
-```
-
-**Steps:**
-1. Check if JSON import assertion works in project
-2. Update worker-service.ts MCP client initialization
-3. Update ChromaSync.ts similarly
-4. Run build to verify
-
-**Verification:**
-```bash
-grep -n "version: '1.0.0'" src/services/worker-service.ts src/services/sync/ChromaSync.ts
-# Expected: No output
-npm run build
-```
-
-### 4.2 Add MCP Capabilities Comment
-
-**Current:**
-```typescript
-}, { capabilities: {} });
-```
-
-**Add clarifying comment:**
-```typescript
-}, {
-  // MCP spec: Clients accept all server capabilities; no declaration needed
-  capabilities: {}
-});
-```
-
----
-
-## Phase 5: Verification
-
-### 5.1 Build Check
-```bash
-npm run build
-```
-**Expected:** No TypeScript errors
-
-### 5.2 Test Suite
-```bash
-npm test
-```
-**Expected:** All tests pass
-
-### 5.3 Grep for Anti-Patterns
-```bash
-# Verify dead code removed
-grep -r "runInteractiveSetup" src/
-# Expected: No matches
-
-# Verify unused imports removed
-grep "import \* as fs from 'fs'" src/services/worker-service.ts
-# Expected: No match
-
-# Verify re-export removed
-grep "export { updateCursorContextForProject" src/services/worker-service.ts
-# Expected: No match
-
-# Verify fallback has check
-grep -A2 "setFallbackAgent" src/services/worker-service.ts
-# Expected: Conditional with isConfigured check
-```
-
-### 5.4 Runtime Check
-```bash
-npm run build-and-sync
-# Manually verify worker starts and basic operations work
-```
-
----
-
-## Summary
-
-| Phase | Description | Lines Changed | Priority |
-|-------|-------------|---------------|----------|
-| Phase 1 | Delete dead code + imports | ~200 deleted | HIGH |
-| Phase 2 | Add fallback verification | ~10 added | HIGH |
-| Phase 3 | Remove re-export | ~5 changed | LOW |
-| Phase 4 | Update MCP version | ~3 changed | LOW |
-| Phase 5 | Verification | N/A | N/A |
-
-**Execution Order:** Phase 1 → Phase 2 → Phase 3 → Phase 4 → Phase 5
-
-**Note:** Each phase should be followed by verification (build + test) before proceeding.
-
----
-
-## Patterns Confirmed KEEP (No Action)
-
-These patterns were validated as intentional:
-
-1. **Exit code 0 always** - Windows Terminal tab accumulation workaround (commit 222a73da)
-2. **`as Error` casts** - Documented project policy with anti-pattern detection
-3. **Dual init tracking** - Promise for async, flag for sync callers
-4. **Signal handler ref pattern** - Standard JS mutable state sharing
-5. **Empty MCP capabilities** - Correct per MCP client spec

.claude/plans/pr-610-review-fixes.md

@@ -1,144 +0,0 @@
-# Plan: Address PR #610 Review Issues
-
-## Overview
-This plan addresses the issues identified in the PR review for PR #610 "fix: Update hooks for Claude Code 2.1.0/1 - SessionStart no longer shows user messages".
-
-## Phase 0: Verification and Discovery
-
-### 0.1 Verify Test Failure
-- **File**: `tests/hook-constants.test.ts`
-- **Issue**: Lines 61-63 test for `HOOK_EXIT_CODES.USER_MESSAGE_ONLY` which was removed
-- **Verification**: Run `bun test tests/hook-constants.test.ts` to confirm failure
-
-### 0.2 Verify No Code References USER_MESSAGE_ONLY
-- **Finding**: Grep found references only in:
-  - `tests/hook-constants.test.ts` (test file - needs fix)
-  - `src/services/CLAUDE.md` (memory context - auto-generated, not code)
-  - `plugin/scripts/CLAUDE.md` (memory context - auto-generated, not code)
-- **Conclusion**: Only the test file needs updating; CLAUDE.md files are memory records
-
-### 0.3 Verify CLAUDE.md Files Are Legitimate
-- **Clarification**: The PR reviewer mentioned "user-specific CLAUDE.md files starting with ~/"
-- **Finding**: All CLAUDE.md files in the commit are within the repository (`docs/`, `src/`, `plugin/`)
-- **Conclusion**: These are legitimate in-repo context files, not user-specific paths
-
----
-
-## Phase 1: Fix Test File (REQUIRED)
-
-### Task 1.1: Remove USER_MESSAGE_ONLY Test
-**File**: `tests/hook-constants.test.ts`
-**Action**: Delete lines 61-63 that test for the removed constant
-
-```typescript
-// DELETE THESE LINES:
-it('should define USER_MESSAGE_ONLY exit code', () => {
-  expect(HOOK_EXIT_CODES.USER_MESSAGE_ONLY).toBe(3);
-});
-```
-
-### Task 1.2: Add Test for BLOCKING_ERROR
-**File**: `tests/hook-constants.test.ts`
-**Action**: Add test for the new `BLOCKING_ERROR` constant (exit code 2) that replaced it
-
-```typescript
-// ADD THIS TEST:
-it('should define BLOCKING_ERROR exit code', () => {
-  expect(HOOK_EXIT_CODES.BLOCKING_ERROR).toBe(2);
-});
-```
-
-### Verification
-- Run `bun test tests/hook-constants.test.ts`
-- Expect: All tests pass
-
----
-
-## Phase 2: Documentation Consistency (NICE TO HAVE)
-
-### Issue
-Three similar notes about Claude Code 2.1.0 have slightly different wording:
-
-1. `docs/public/architecture/hooks.mdx:254`:
-   > "SessionStart hooks no longer display any user-visible messages. Context is still injected via `hookSpecificOutput.additionalContext` but users don't see startup output in the UI."
-
-2. `docs/public/hooks-architecture.mdx:31`:
-   > "SessionStart hooks no longer display any user-visible messages. Context is silently injected via `hookSpecificOutput.additionalContext`."
-
-3. `docs/public/hooks-architecture.mdx:441`:
-   > "SessionStart hooks output is never displayed to users. Context is injected silently via `hookSpecificOutput.additionalContext`."
-
-### Task 2.1: Standardize Note Wording
-**Action**: Use consistent wording across all three locations
-
-**Standard text**:
-```
-As of Claude Code 2.1.0 (ultrathink update), SessionStart hooks no longer display user-visible messages. Context is silently injected via `hookSpecificOutput.additionalContext`.
-```
-
-### Files to Update
-1. `docs/public/architecture/hooks.mdx:253-255` - Update Note block
-2. `docs/public/hooks-architecture.mdx:30-32` - Update Note block
-3. `docs/public/hooks-architecture.mdx:440-442` - Update Note block
-
-### Verification
-- Grep for the standard text in all three files
-- Visual review of documentation
-
----
-
-## Phase 3: Code Quality Improvements (OPTIONAL)
-
-### Issue 3.1: Hardcoded Promotional Message
-**File**: `src/hooks/context-hook.ts:66-68`
-**Current code**:
-```typescript
-const enhancedContext = `${text}
-
-Access 300k tokens of past research & decisions for just 19,008t. Use MCP search tools to access memories by ID.`;
-```
-
-### Options
-1. **Leave as-is**: The token count is a rough estimate and doesn't need to be exact
-2. **Make configurable**: Add to settings (over-engineering for this use case)
-3. **Remove hardcoded numbers**: Use relative language instead
-
-### Recommendation
-Leave as-is for now. The token counts are marketing copy, not critical functionality. Creating a PR just for this adds unnecessary complexity.
-
----
-
-## Phase 4: Final Verification
-
-### 4.1 Run Full Test Suite
-```bash
-bun test
-```
-
-### 4.2 Build Verification
-```bash
-npm run build
-```
-
-### 4.3 Grep Verification
-```bash
-grep -r "USER_MESSAGE_ONLY" src/ --include="*.ts" --include="*.js"
-```
-Expected: No results (CLAUDE.md files excluded as they're memory records)
-
----
-
-## Summary
-
-| Phase | Priority | Effort | Description |
-|-------|----------|--------|-------------|
-| 1 | REQUIRED | 5 min | Fix test file - remove USER_MESSAGE_ONLY test, add BLOCKING_ERROR test |
-| 2 | Nice to have | 10 min | Standardize documentation note wording |
-| 3 | Skip | - | Hardcoded token counts are fine as-is |
-| 4 | REQUIRED | 5 min | Run tests and build to verify |
-
-## Expected Outcome
-- All tests pass
-- Build succeeds
-- No code references to removed USER_MESSAGE_ONLY constant
-- Documentation uses consistent wording (if Phase 2 is done)

.claude/plans/pr-628-polish.md

@@ -1,223 +0,0 @@
-# Plan: PR #628 Polish Items
-
-**PR**: #628 - Windows Terminal Tab Accumulation & Windows 11 Compatibility
-**Status**: APPROVED by 3 reviewers with minor suggestions
-**Branch**: `feature/no-more-hook-files`
-
----
-
-## Phase 0: Documentation Discovery (Completed by Orchestrator)
-
-### Allowed APIs and Patterns
-
-**Exit Code Constants** - `src/shared/hook-constants.ts:18-23`:
-```typescript
-export const HOOK_EXIT_CODES = {
-  SUCCESS: 0,
-  FAILURE: 1,
-  BLOCKING_ERROR: 2,
-} as const;
-```
-
-**Timeout Constants** - `src/shared/hook-constants.ts:1-8`:
-```typescript
-export const HOOK_TIMEOUTS = {
-  DEFAULT: 300000,
-  HEALTH_CHECK: 30000,
-  WORKER_STARTUP_WAIT: 1000,
-  WORKER_STARTUP_RETRIES: 300,
-  PRE_RESTART_SETTLE_DELAY: 2000,
-  WINDOWS_MULTIPLIER: 1.5
-} as const;
-```
-
-**Platform Timeout Function** - `src/services/infrastructure/ProcessManager.ts:70-73`:
-```typescript
-export function getPlatformTimeout(baseMs: number): number {
-  const WINDOWS_MULTIPLIER = 2.0;
-  return process.platform === 'win32' ? Math.round(baseMs * WINDOWS_MULTIPLIER) : baseMs;
-}
-```
-
-**Migration Guide Pattern** - `docs/public/architecture/pm2-to-bun-migration.mdx`:
-- Uses MDX format with frontmatter
-- Starts with `<Note>` for historical context
-- Uses `<AccordionGroup>` for before/after comparisons
-- Includes executive summary, key benefits, migration impact sections
-
-**Exit Code Documentation** - `private/context/claude-code/exit-codes.md`:
-- Defines exit code 0, 2, and other behaviors
-- Per-hook event behavior table
-
-### Files to Modify
-
-| File | Change | Lines |
-|------|--------|-------|
-| `src/services/infrastructure/ProcessManager.ts` | Add POWERSHELL_TIMEOUT constant, reduce from 60000 to 10000 | 93, 123, 175, 241 |
-| `src/shared/hook-constants.ts` | Add POWERSHELL_TIMEOUT constant | After line 8 |
-| `CLAUDE.md` | Document exit code strategy | Architecture section |
-
-### Anti-Patterns to Avoid
-
-- DO NOT invent new exit code values (only 0, 1, 2 exist)
-- DO NOT change Windows multiplier (1.5x in hooks, 2.0x in ProcessManager - they serve different purposes)
-- DO NOT add upper bound PID validation (not in existing pattern, reviewers marked as "nice to have")
-- DO NOT create migration guide for Cursor (shell scripts still exist in cursor-hooks/, not removed)
-
----
-
-## Phase 1: Extract PowerShell Timeout Constant
-
-### What to Implement
-
-Add a `POWERSHELL_TIMEOUT` constant to centralize the magic number `60000` and reduce to `10000` (10 seconds) as recommended by reviewers.
-
-### Documentation References
-
-1. Copy constant pattern from `src/shared/hook-constants.ts:1-8`
-2. Copy usage pattern from `src/services/infrastructure/ProcessManager.ts:93`
-
-### Implementation Steps
-
-1. **Add constant to hook-constants.ts** after line 8:
-   ```typescript
-   POWERSHELL_COMMAND: 10000,     // PowerShell process enumeration (10s - typically completes in <1s)
-   ```
-
-2. **Import and use in ProcessManager.ts**:
-   - Import `HOOK_TIMEOUTS` from `../../shared/hook-constants.js`
-   - Replace `{ timeout: 60000 }` with `{ timeout: HOOK_TIMEOUTS.POWERSHELL_COMMAND }` at lines 93, 123, 175, 241
-
-### Verification Checklist
-
-- [ ] `grep -n "60000" src/services/infrastructure/ProcessManager.ts` returns 0 matches
-- [ ] `grep -n "POWERSHELL_COMMAND" src/services/infrastructure/ProcessManager.ts` returns 4 matches
-- [ ] `npm run build` succeeds
-- [ ] `npm test` passes (22/22 PowerShell tests still pass)
-
-### Anti-Pattern Guards
-
-- DO NOT use `getPlatformTimeout()` for PowerShell commands (they already run only on Windows)
-- DO NOT change timeout values in other files (only ProcessManager.ts uses PowerShell)
-
----
-
-## Phase 2: Document Exit Code Strategy in CLAUDE.md
-
-### What to Implement
-
-Add an "Exit Code Strategy" section to the main CLAUDE.md to explain the graceful exit philosophy adopted in this PR.
-
-### Documentation References
-
-1. Copy exit code definitions from `private/context/claude-code/exit-codes.md`
-2. Follow format of existing CLAUDE.md sections
-
-### Implementation Steps
-
-1. **Add section after "File Locations"** in `/Users/alexnewman/Scripts/claude-mem/CLAUDE.md`:
-
-```markdown
-## Exit Code Strategy
-
-Claude-mem hooks use specific exit codes per Claude Code's hook contract:
-
-- **Exit 0**: Success or graceful shutdown (Windows Terminal closes tabs)
-- **Exit 1**: Non-blocking error (stderr shown to user, continues)
-- **Exit 2**: Blocking error (stderr fed to Claude for processing)
-
-**Philosophy**: Worker/hook errors exit with code 0 to prevent Windows Terminal tab accumulation. The wrapper/plugin layer handles restart logic. ERROR-level logging is maintained for diagnostics.
-
-See `private/context/claude-code/exit-codes.md` for full hook behavior matrix.
-```
-
-### Verification Checklist
-
-- [ ] `grep -n "Exit Code Strategy" CLAUDE.md` returns 1 match
-- [ ] Section appears after "File Locations" section
-- [ ] No duplicate sections added
-
-### Anti-Pattern Guards
-
-- DO NOT copy the full exit-codes.md table (keep it brief, reference the source)
-- DO NOT change actual exit code behavior in code files
-
----
-
-## Phase 3: Update Tests for New Timeout Constant
-
-### What to Implement
-
-Add test coverage for the new `POWERSHELL_COMMAND` timeout constant.
-
-### Documentation References
-
-1. Copy test pattern from `tests/hook-constants.test.ts:26-48`
-
-### Implementation Steps
-
-1. **Add test to hook-constants.test.ts** after line 42:
-   ```typescript
-   test('POWERSHELL_COMMAND timeout is 10000ms', () => {
-     expect(HOOK_TIMEOUTS.POWERSHELL_COMMAND).toBe(10000);
-   });
-   ```
-
-### Verification Checklist
-
-- [ ] `npm test -- tests/hook-constants.test.ts` passes
-- [ ] New test appears in test output
-- [ ] All 22 PowerShell parsing tests still pass
-
-### Anti-Pattern Guards
-
-- DO NOT modify PowerShell parsing tests (they test parsing, not timeouts)
-- DO NOT add integration tests for actual PowerShell execution (out of scope)
-
----
-
-## Phase 4: Final Verification
-
-### Verification Checklist
-
-1. **Build passes**: `npm run build`
-2. **All tests pass**: `npm test`
-3. **No magic numbers remain**: `grep -rn "60000" src/services/infrastructure/ProcessManager.ts` returns 0
-4. **Exit code documentation exists**: `grep -n "Exit Code Strategy" CLAUDE.md` returns 1
-5. **Constant is used**: `grep -rn "POWERSHELL_COMMAND" src/` returns multiple matches
-
-### Anti-Pattern Grep Checks
-
-- [ ] `grep -rn "timeout: 60000" src/` returns 0 matches (no hardcoded 60s timeouts in ProcessManager)
-- [ ] `grep -rn "process.exit(3)" src/` returns 0 matches (exit code 3 not used)
-
-### Commit Message Template
-
-```
-polish: extract PowerShell timeout constant and document exit code strategy
-
-- Extract magic number 60000ms to HOOK_TIMEOUTS.POWERSHELL_COMMAND (10000ms)
-- Reduce PowerShell timeout from 60s to 10s per review feedback
-- Document exit code strategy in CLAUDE.md
-- Add test coverage for new constant
-
-Addresses review feedback from PR #628
-
-Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
-```
-
----
-
-## Summary
-
-| Phase | Description | Files Changed | Verification |
-|-------|-------------|---------------|--------------|
-| 0 | Documentation Discovery | N/A | Patterns identified |
-| 1 | Extract PowerShell timeout | hook-constants.ts, ProcessManager.ts | grep + build + test |
-| 2 | Document exit strategy | CLAUDE.md | grep |
-| 3 | Add test coverage | hook-constants.test.ts | npm test |
-| 4 | Final verification | N/A | All checks pass |
-
-**Estimated Changes**: ~20 lines added/modified across 4 files
-**Risk Level**: Low (constants extraction, documentation only)
-**Breaking Changes**: None

.claude/plans/remove-worker-start-calls.md

@@ -1,394 +0,0 @@
-# Plan: Remove Worker Start Calls - In-Process Architecture
-
-## Problem Statement
-
-Current architecture has problematic spawn patterns:
-1. `hooks.json` calls `worker-service.cjs start` which spawns a daemon
-2. Spawning is buggy on Windows - **HARD RULE: NO SPAWN**
-3. `user-message` hook is deprecated
-4. `smart-install` was supposed to chain: `smart-install && stop && context`
-
-## Target Architecture
-
-**NO SPAWN - Worker runs in-process within hook command**
-
-```
-SessionStart:
-  smart-install && stop && context
-```
-
-Flow:
-1. `smart-install` - Install dependencies if needed
-2. `stop` - Kill any existing worker (clean slate)
-3. `context` - Hook starts worker IN-PROCESS, becomes the worker
-
-**Key insight:** The first hook that needs the worker **becomes** the worker. No spawn, no daemon. The hook process IS the worker process.
-
----
-
-## Current vs Target hooks.json
-
-### Current (BROKEN)
-```json
-"SessionStart": [
-  { "hooks": [
-    { "command": "node smart-install.js" },
-    { "command": "bun worker-service.cjs start" },      // REMOVE - spawn
-    { "command": "bun worker-service.cjs hook ... context" },
-    { "command": "bun worker-service.cjs hook ... user-message" }  // REMOVE - deprecated
-  ]}
-]
-```
-
-### Target
-```json
-"SessionStart": [
-  { "hooks": [
-    { "command": "node smart-install.js && bun worker-service.cjs stop && bun worker-service.cjs hook claude-code context" }
-  ]}
-]
-```
-
----
-
-## Files Involved
-
-| File | Changes |
-|------|---------|
-| `plugin/hooks/hooks.json` | Restructure to chained commands, remove start/user-message |
-| `src/services/worker-service.ts` | `hook` case: start worker in-process if not running |
-| `src/cli/handlers/*.ts` | May need adjustment for in-process execution |
-| `src/shared/worker-utils.ts` | `ensureWorkerRunning()` → adapt for in-process |
-
----
-
-## Phase 0: Documentation Discovery
-
-### Available APIs
-
-**From `src/services/infrastructure/HealthMonitor.ts`:**
-- `isPortInUse(port): Promise<boolean>`
-- `waitForHealth(port, timeoutMs): Promise<boolean>`
-- `httpShutdown(port): Promise<void>`
-
-**From `src/services/worker-service.ts`:**
-- `WorkerService` class - the actual worker
-- `stop` command - shuts down worker via HTTP
-- `--daemon` case - starts WorkerService (currently only used after spawn)
-
-**BANNED (spawn patterns):**
-- ~~`spawnDaemon()`~~ - NO SPAWN
-- ~~`fork()`~~ - NO SPAWN
-- ~~`spawn()` with detached~~ - NO SPAWN
-
-### Anti-Patterns
-- **NO SPAWN** - Hard rule, Windows buggy
-- No `restart` command - removed for same reason
-- No detached processes
-
----
-
-## Phase 1: Modify `hook` Case for In-Process Worker
-
-### Location
-`src/services/worker-service.ts:564-576`
-
-### Current Code
-```typescript
-case 'hook': {
-  const platform = process.argv[3];
-  const event = process.argv[4];
-  if (!platform || !event) {
-    console.error('Usage: claude-mem hook <platform> <event>');
-    process.exit(1);
-  }
-  const { hookCommand } = await import('../cli/hook-command.js');
-  await hookCommand(platform, event);
-  break;
-}
-```
-
-### Target Code
-```typescript
-case 'hook': {
-  const platform = process.argv[3];
-  const event = process.argv[4];
-  if (!platform || !event) {
-    console.error('Usage: claude-mem hook <platform> <event>');
-    process.exit(1);
-  }
-
-  // Check if worker already running (port in use = valid, another process has it)
-  const portInUse = await isPortInUse(port);
-  if (portInUse) {
-    // Port in use - either healthy worker or something else
-    // Proceed with hook via HTTP to existing worker
-    const { hookCommand } = await import('../cli/hook-command.js');
-    await hookCommand(platform, event);
-    break;
-  }
-
-  // Port free - start worker IN THIS PROCESS (no spawn!)
-  logger.info('SYSTEM', 'Starting worker in-process for hook');
-  const worker = new WorkerService();
-
-  // Start worker (non-blocking, returns when server listening)
-  await worker.start();
-
-  // Now execute hook logic - worker is running in this process
-  // Can call handler directly (in-process) or via HTTP to self
-  const { hookCommand } = await import('../cli/hook-command.js');
-  await hookCommand(platform, event);
-
-  // DON'T exit - this process IS the worker now
-  // Worker stays alive serving requests
-  break;
-}
-```
-
-### Key Behavior
-- If port in use → hook runs via HTTP to existing worker, then exits
-- If port free → start worker in-process, run hook, process stays alive as worker
-
-### Verification
-- [ ] Stop worker, run hook command → should start worker and stay alive
-- [ ] Worker already running, run hook command → should complete and exit
-- [ ] `lsof -i :37777` shows hook process IS the worker
-
----
-
-## Phase 2: Update hooks.json - Chained Commands
-
-### Location
-`plugin/hooks/hooks.json`
-
-### Target Structure
-```json
-{
-  "description": "Claude-mem memory system hooks",
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "startup|clear|compact",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/smart-install.js\" && bun \"${CLAUDE_PLUGIN_ROOT}/scripts/worker-service.cjs\" stop && bun \"${CLAUDE_PLUGIN_ROOT}/scripts/worker-service.cjs\" hook claude-code context",
-            "timeout": 300
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bun \"${CLAUDE_PLUGIN_ROOT}/scripts/worker-service.cjs\" hook claude-code session-init",
-            "timeout": 60
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bun \"${CLAUDE_PLUGIN_ROOT}/scripts/worker-service.cjs\" hook claude-code observation",
-            "timeout": 120
-          }
-        ]
-      }
-    ],
-    "Stop": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bun \"${CLAUDE_PLUGIN_ROOT}/scripts/worker-service.cjs\" hook claude-code summarize",
-            "timeout": 120
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-### Changes Summary
-1. SessionStart: Chain `smart-install && stop && context` in single command
-2. Remove `user-message` hook (deprecated)
-3. Remove all separate `start` commands
-4. Other hooks unchanged (just hook command, auto-starts if needed)
-
-### Verification
-- [ ] JSON valid: `cat plugin/hooks/hooks.json | jq .`
-- [ ] No `start` command: `grep -c '"start"' plugin/hooks/hooks.json` = 0
-- [ ] No `user-message`: `grep -c 'user-message' plugin/hooks/hooks.json` = 0
-
----
-
-## Phase 3: Handle "Port In Use" Gracefully
-
-### Scenario
-Another process has port 37777 (not our worker). Hook should handle gracefully.
-
-### Current Behavior
-`ensureWorkerRunning()` polls for 15 seconds, then throws error.
-
-### Target Behavior
-If port in use but not healthy (not our worker):
-- Hook is "valid" - don't block Claude Code
-- Return graceful response (empty context, etc.)
-- Log warning for debugging
-
-### Location
-`src/shared/worker-utils.ts:117-141`
-
-### Changes
-```typescript
-export async function ensureWorkerRunning(): Promise<boolean> {
-  const port = getWorkerPort();
-
-  // Quick health check (2 seconds max)
-  try {
-    if (await isWorkerHealthy()) {
-      await checkWorkerVersion();
-      return true;  // Worker healthy
-    }
-  } catch (e) {
-    // Not healthy
-  }
-
-  // Port might be in use by something else
-  // Return false but don't throw - let caller decide
-  logger.warn('SYSTEM', 'Worker not healthy, hook will proceed gracefully');
-  return false;
-}
-```
-
-### Handler Updates
-Update handlers to handle `ensureWorkerRunning()` returning false:
-```typescript
-const workerReady = await ensureWorkerRunning();
-if (!workerReady) {
-  // Return graceful empty response
-  return { output: '', exitCode: HOOK_EXIT_CODES.SUCCESS };
-}
-```
-
-### Verification
-- [ ] Start non-worker process on 37777, run hook → completes gracefully
-- [ ] No 15-second hang when port blocked
-
----
-
-## Phase 4: Remove Deprecated Code
-
-### Remove `user-message` Handler (if unused elsewhere)
-- [ ] Check if `user-message.ts` is used anywhere else
-- [ ] Remove from `src/cli/handlers/index.ts` if safe
-- [ ] Consider keeping file but removing from hooks.json only
-
-### Remove `start` Command (optional)
-The `start` command in worker-service.ts can stay for manual use:
-```bash
-bun worker-service.cjs start  # Manual start if needed
-```
-But it should NOT be called from hooks.json.
-
-### Verification
-- [ ] `npm run build` succeeds
-- [ ] No references to removed handlers in hooks.json
-
----
-
-## Phase 5: Update Handler `ensureWorkerRunning()` Calls
-
-### Context
-Each handler currently calls `ensureWorkerRunning()` which polls for 15 seconds.
-
-With in-process architecture:
-- If hook started worker in-process → worker is THIS process, no HTTP needed
-- If worker already running → HTTP to existing worker
-
-### Decision
-**Keep handler calls** but modify `ensureWorkerRunning()` to:
-1. Return quickly if port is in use (assume valid)
-2. Return true if in-process worker (detect via global flag?)
-3. Graceful false return instead of throwing
-
-### Files
-- `src/cli/handlers/context.ts:15`
-- `src/cli/handlers/session-init.ts:15`
-- `src/cli/handlers/observation.ts:14`
-- `src/cli/handlers/summarize.ts:17`
-- `src/cli/handlers/file-edit.ts:15`
-
-### Verification
-- [ ] Handlers don't hang on port-in-use scenarios
-- [ ] In-process worker scenario works
-
----
-
-## Phase 6: Final Verification
-
-### Tests
-- [ ] `bun test` - All tests pass
-- [ ] `npm run build-and-sync` - Build succeeds
-
-### Manual Tests
-
-**Test 1: Clean Start**
-```bash
-bun plugin/scripts/worker-service.cjs stop
-# Start new Claude Code session
-# Verify: context hook starts worker in-process
-# Verify: lsof -i :37777 shows the hook process
-```
-
-**Test 2: Worker Already Running**
-```bash
-bun plugin/scripts/worker-service.cjs stop
-bun plugin/scripts/worker-service.cjs hook claude-code context &
-# Wait for worker to start
-bun plugin/scripts/worker-service.cjs hook claude-code observation
-# Verify: observation hook exits after completing (doesn't stay alive)
-```
-
-**Test 3: Port Blocked**
-```bash
-bun plugin/scripts/worker-service.cjs stop
-nc -l 37777 &  # Block port with netcat
-bun plugin/scripts/worker-service.cjs hook claude-code context
-# Verify: completes gracefully, doesn't hang
-kill %1  # Clean up netcat
-```
-
-**Test 4: Full Session**
-```bash
-# Start fresh Claude Code session
-# Do some work (creates observations)
-# End session (Ctrl+C or /exit)
-# Verify: summarize hook ran, observations saved
-```
-
----
-
-## Risk Assessment
-
-| Risk | Mitigation |
-|------|------------|
-| Hook stays alive forever | Expected - it's the worker now |
-| Multiple hooks compete for port | First one wins, others use HTTP |
-| Graceful shutdown on session end | Stop command in chain handles this |
-| Windows compatibility | No spawn = no Windows issues |
-
-## Rollback Plan
-
-If issues arise:
-1. Restore hooks.json with separate start commands
-2. Revert worker-service.ts hook case changes
-3. No database changes to rollback

.claude/plans/workflow-agents-integration.md

@@ -1,196 +0,0 @@
-# Plan: Integrate Workflow Agents and Commands into Claude-Mem
-
-## Executive Summary
-
-This plan integrates the `/make-plan` and `/do` orchestration workflow from `~/.claude/commands/` into the claude-mem plugin as project-level development tools.
-
-## Dependency Analysis
-
-### Commands to Copy (from `~/.claude/commands/`)
-
-| File | Purpose | Dependencies |
-|------|---------|--------------|
-| `make-plan.md` | Orchestrator for LLM-friendly phased planning | Uses Task tool with subagents |
-| `do.md` | Orchestrator for executing plans via subagents | Uses Task tool with subagents |
-| `anti-pattern-czar.md` | Error handling anti-pattern detection/fixing | Uses Read, Edit, Bash tools |
-
-### Specialized Agents Referenced
-
-The `/make-plan` and `/do` commands reference these **conceptual agent roles** (not actual agent files):
-
-| Agent Role | Referenced In | Description |
-|------------|---------------|-------------|
-| "Documentation Discovery" | make-plan.md | Fact-gathering from docs/examples |
-| "Verification" | make-plan.md, do.md | Verify implementation matches plan |
-| "Implementation" | do.md | Execute implementation tasks |
-| "Anti-pattern" | do.md | Grep for known bad patterns |
-| "Code Quality" | do.md | Review code changes |
-| "Commit" | do.md | Commit after verification passes |
-| "Branch/Sync" | do.md | Push and prepare phase handoffs |
-
-**Key Finding**: These are **role descriptions**, not separate agent files. The Task tool's `general-purpose` subagent_type executes all roles. The commands define *what* each role should do, not separate agent implementations.
-
-### Existing Project Assets
-
-Located in `.claude/`:
-- `agents/github-morning-reporter.md` - Already in project
-- `skills/version-bump/SKILL.md` - Already in project
-- No existing commands directory
-
----
-
-## Phase 0: Documentation Discovery (Complete)
-
-### Sources Consulted
-1. `/Users/alexnewman/.claude/commands/make-plan.md` (62 lines)
-2. `/Users/alexnewman/.claude/commands/do.md` (39 lines)
-3. `/Users/alexnewman/.claude/commands/anti-pattern-czar.md` (122 lines)
-4. `/Users/alexnewman/.claude/settings.json` (36 lines)
-5. `.claude/skills/CLAUDE.md` (30 lines)
-6. `.claude/agents/github-morning-reporter.md` (102 lines)
-
-### Allowed APIs/Patterns
-- **Commands**: `.claude/commands/*.md` files with `#$ARGUMENTS` placeholder for user input
-- **Skills**: `.claude/skills/<name>/SKILL.md` with YAML frontmatter (name, description)
-- **Agents**: `.claude/agents/*.md` with YAML frontmatter (name, description, model)
-
-### Anti-Patterns to Avoid
-- Skills require YAML frontmatter; commands do not
-- Commands use `#$ARGUMENTS` for input; skills/agents receive prompts differently
-- Don't create separate agent files for role descriptions - the Task tool handles routing
-
----
-
-## Phase 1: Create Commands Directory
-
-### What to Implement
-1. Create `.claude/commands/` directory
-2. Copy `make-plan.md` from `~/.claude/commands/make-plan.md`
-3. Copy `do.md` from `~/.claude/commands/do.md`
-4. Copy `anti-pattern-czar.md` from `~/.claude/commands/anti-pattern-czar.md`
-
-### Documentation References
-- Pattern: `~/.claude/commands/*.md` (source files)
-- Existing example: `.claude/skills/version-bump/SKILL.md` for claude-mem project tools
-
-### Verification Checklist
-```bash
-# Verify files exist
-ls -la .claude/commands/
-
-# Verify content matches source
-diff ~/.claude/commands/make-plan.md .claude/commands/make-plan.md
-diff ~/.claude/commands/do.md .claude/commands/do.md
-diff ~/.claude/commands/anti-pattern-czar.md .claude/commands/anti-pattern-czar.md
-
-# Verify #$ARGUMENTS placeholder exists
-grep '\$ARGUMENTS' .claude/commands/*.md
-```
-
-### Anti-Pattern Guards
-- Do NOT add YAML frontmatter to commands (they don't need it)
-- Do NOT modify the source content (copy verbatim)
-
----
-
-## Phase 2: Create CLAUDE.md Documentation
-
-### What to Implement
-Create `.claude/commands/CLAUDE.md` documenting the commands directory (following pattern from `.claude/skills/CLAUDE.md`)
-
-### Content Template
-```markdown
-# Project-Level Commands
-
-This directory contains slash commands **for developing and maintaining the claude-mem project itself**.
-
-## Commands in This Directory
-
-### /make-plan
-Orchestrator for creating LLM-friendly implementation plans in phases. Deploys subagents for documentation discovery and fact gathering.
-
-**Usage**: `/make-plan <task description>`
-
-### /do
-Orchestrator for executing plans via subagents. Deploys specialized subagents for implementation, verification, and code quality review.
-
-**Usage**: `/do <plan-file-path or inline plan>`
-
-### /anti-pattern-czar
-Interactive workflow for detecting and fixing error handling anti-patterns using the automated scanner.
-
-**Usage**: `/anti-pattern-czar`
-
-## Adding New Commands
-
-Commands are markdown files with `#$ARGUMENTS` placeholder for user input.
-```
-
-### Verification Checklist
-```bash
-# Verify file exists
-cat .claude/commands/CLAUDE.md
-```
-
----
-
-## Phase 3: Update Settings (if needed)
-
-### What to Implement
-Check if `.claude/settings.json` needs any permission updates for the new commands.
-
-### Verification Checklist
-```bash
-# Check current settings
-cat .claude/settings.json
-
-# Verify commands work by listing them
-# (After Claude Code restart, commands should appear in slash-command list)
-```
-
-### Anti-Pattern Guards
-- Do NOT add skill permissions for commands (they're different)
-- Commands don't require explicit permissions
-
----
-
-## Phase 4: Final Verification
-
-### Verification Checklist
-1. All three command files exist in `.claude/commands/`
-2. Content matches source files exactly (byte-for-byte if possible)
-3. CLAUDE.md documentation exists
-4. Git status shows new files ready for commit
-
-```bash
-# Full verification
-ls -la .claude/commands/
-wc -l .claude/commands/*.md
-git status
-```
-
-### Commit Message Template
-```
-feat: add /make-plan, /do, and /anti-pattern-czar workflow commands
-
-Add project-level orchestration commands for claude-mem development:
-- /make-plan: Create LLM-friendly implementation plans in phases
-- /do: Execute plans via coordinated subagents
-- /anti-pattern-czar: Detect and fix error handling anti-patterns
-
-These commands enable structured, agent-driven development workflows.
-```
-
----
-
-## Summary
-
-**Files to Create**:
-1. `.claude/commands/make-plan.md` (copy from ~/.claude/commands/)
-2. `.claude/commands/do.md` (copy from ~/.claude/commands/)
-3. `.claude/commands/anti-pattern-czar.md` (copy from ~/.claude/commands/)
-4. `.claude/commands/CLAUDE.md` (new documentation)
-
-**No Agent Files Needed**: The "agents" referenced in make-plan.md and do.md are role descriptions, not separate files. The Task tool's built-in subagent types handle execution.
-
-**Confidence**: High - analysis complete with full source file reads.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,6 +7,12 @@ assignees: ''
 
 ---
 
+## Before submitting
+
+- [ ] I searched [existing issues](https://github.com/thedotmack/claude-mem/issues) and confirmed this is not a duplicate
+
+---
+
 ## ⚡ Quick Bug Report (Recommended)
 
 **Use the automated bug report generator** for comprehensive diagnostics:

.github/ISSUE_TEMPLATE/feature_request.md

@@ -7,6 +7,12 @@ assignees: ''
 
 ---
 
+## Before submitting
+
+- [ ] I searched [existing issues](https://github.com/thedotmack/claude-mem/issues) and confirmed this is not a duplicate
+
+---
+
 **Is your feature request related to a problem? Please describe.**
 A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
 

.github/workflows/claude-code-review.yml

@@ -27,7 +27,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
         with:
           fetch-depth: 1
 

.github/workflows/claude.yml

@@ -26,7 +26,7 @@ jobs:
       actions: read # Required for Claude to read CI results on PRs
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
         with:
           fetch-depth: 1
 

.github/workflows/convert-feature-requests.yml

@@ -26,7 +26,7 @@ jobs:
     steps:
       - name: Get issue details and create discussion
         id: discussion
-        uses: actions/github-script@v7
+        uses: actions/github-script@v8
         with:
           script: |
             // Get issue details
@@ -87,7 +87,7 @@ jobs:
             }
 
       - name: Comment on issue
-        uses: actions/github-script@v7
+        uses: actions/github-script@v8
         with:
           script: |
             const issueNumber = ${{ steps.discussion.outputs.issue_number }};
@@ -105,7 +105,7 @@ jobs:
             console.log(`Added comment to issue #${issueNumber}`);
 
       - name: Close and lock issue
-        uses: actions/github-script@v7
+        uses: actions/github-script@v8
         with:
           script: |
             const issueNumber = ${{ steps.discussion.outputs.issue_number }};

.github/workflows/deploy-install-scripts.yml

@@ -0,0 +1,29 @@
+name: Deploy Install Scripts
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'openclaw/install.sh'
+      - 'install/**'
+  workflow_dispatch:
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Copy install scripts to deploy directory
+        run: |
+          mkdir -p install/public
+          cp openclaw/install.sh install/public/openclaw.sh
+
+      - name: Deploy to Vercel
+        uses: amondnet/vercel-action@v25
+        with:
+          vercel-token: ${{ secrets.VERCEL_TOKEN }}
+          vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
+          vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
+          vercel-args: '--prod'
+          working-directory: ./install

.github/workflows/npm-publish.yml

@@ -0,0 +1,21 @@
+name: Publish to npm
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install --ignore-scripts
+      - run: npm run build
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/summary.yml

@@ -14,11 +14,11 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
 
       - name: Run AI inference
         id: inference
-        uses: actions/ai-inference@v1
+        uses: actions/ai-inference@v2
         with:
           prompt: |
             Summarize the following GitHub issue in one paragraph:

.gitignore

@@ -11,12 +11,15 @@ dist/
 .claude/settings.local.json
 .claude/agents/
 .claude/skills/
+.claude/plans/
+.claude/worktrees/
 plugin/data/
 plugin/data.backup/
 package-lock.json
 bun.lock
 private/
 datasets/
+Auto Run Docs/
 
 # Generated UI files (built from viewer-template.html)
 src/ui/viewer.html
@@ -30,4 +33,7 @@ src/ui/viewer.html
 
 # Prevent other malformed path directories
 http*/
-https*/
+https*/
+
+# Ignore WebStorm project files (for dinosaur IDE users)
+.idea/

Auto Run Docs/Bigph00t-PRs/Phase-01-Merge-PR-745-Isolated-Credentials.md

@@ -1,82 +0,0 @@
-# Phase 01: Merge PR #745 - Isolated Credentials
-
-**PR:** https://github.com/thedotmack/claude-mem/pull/745
-**Branch:** `fix/isolated-credentials-733`
-**Status:** Has conflicts, needs rebase
-**Review:** Approved by bayanoj330-dev
-**Priority:** HIGH - Foundation for credential isolation, required by PR #847
-
-## Summary
-
-Fixes API key hijacking issue (#733) where SDK would use `ANTHROPIC_API_KEY` from random project `.env` files instead of Claude Code CLI subscription billing.
-
-**Root Cause:** The SDK's `query()` function inherits from `process.env` when no `env` option is passed.
-
-**Solution:** Centralized credential management via `~/.claude-mem/.env` with `EnvManager.ts`.
-
-## Files Changed
-
-| File | Change |
-|------|--------|
-| `src/shared/EnvManager.ts` | NEW: Centralized credential storage and isolated env builder |
-| `src/services/worker/SDKAgent.ts` | Pass isolated env to SDK `query()` |
-| `src/services/worker/GeminiAgent.ts` | Use `getCredential()` instead of `process.env` |
-| `src/services/worker/OpenRouterAgent.ts` | Use `getCredential()` instead of `process.env` |
-| `src/shared/SettingsDefaultsManager.ts` | Add `CLAUDE_MEM_CLAUDE_AUTH_METHOD` setting |
-
-## Dependencies
-
-- **None** - This is a foundation PR
-
-## Tasks
-
-- [x] Checkout PR branch `fix/isolated-credentials-733` and rebase onto main to resolve conflicts
-  - ✓ Resolved 4 conflicts (3 build artifacts, 1 source file)
-  - ✓ Merged both main's zombie process cleanup and PR's isolated credentials into SDKAgent.ts
-  - ✓ Commit 006ff401 now sits on top of main (aedee33c)
-- [x] Review `EnvManager.ts` implementation for security and correctness
-  - ✓ **Security Assessment - PASS**:
-    - Credentials stored in user-private location (`~/.claude-mem/.env`) with standard file permissions
-    - `buildIsolatedEnv()` explicitly excludes `process.env` credentials, preventing Issue #733
-    - Only whitelisted essential system vars (PATH, HOME, NODE_ENV, etc.) are passed to subprocesses
-    - Quote stripping in `.env` parser handles both single and double quotes correctly
-    - No credential logging - keys are never written to logs
-  - ✓ **Correctness Assessment - PASS**:
-    - `loadClaudeMemEnv()` gracefully returns empty object if `.env` doesn't exist (enables CLI billing fallback)
-    - `saveClaudeMemEnv()` preserves existing keys and creates directory if needed
-    - `getCredential()` used correctly by GeminiAgent and OpenRouterAgent
-    - SDKAgent passes `isolatedEnv` to SDK query() options, blocking random API key pollution
-    - Auth method description properly reflects whether CLI billing or explicit API key is used
-  - ✓ **Code Quality - GOOD**:
-    - Well-documented with JSDoc comments explaining Issue #733 fix
-    - Type-safe with `ClaudeMemEnv` interface
-    - Essential vars list covers cross-platform needs (Windows, Linux, macOS)
-- [x] Verify build succeeds after rebase
-  - ✓ Build completed successfully: worker-service (1788KB), mcp-server (332KB), context-generator (61KB), viewer UI
-- [x] Run test suite to ensure no regressions
-  - ✓ Fixed console.log/console.error usage in EnvManager.ts (replaced with logger calls per project standards)
-  - ✓ All 797 tests pass (0 fail, 3 skip)
-- [x] Merge PR #745 to main with admin override if needed
-  - ✓ Merged with `--no-ff` to preserve commit history
-  - ✓ Commit 486570d2 on main includes all 4 PR commits
-  - ✓ GitHub branch protection bypassed with admin privileges
-  - ✓ PR #745 auto-closed by GitHub upon detecting commits in main
-  - ✓ Build verified successful after merge
-- [x] Verify auth method shows "Claude Code CLI (subscription billing)" in logs after merge
-  - ✓ Rebuilt and synced local code (v9.0.14 release predated PR merge, so needed fresh build)
-  - ✓ Restarted worker with PR #745 code
-  - ✓ Confirmed log output: `authMethod=Claude Code CLI (subscription billing)`
-  - ✓ Verified `getAuthMethodDescription()` correctly detects no API key in `~/.claude-mem/.env`
-
-## Verification
-
-```bash
-# After merge, check logs for correct auth method
-grep -i "authMethod" ~/.claude-mem/logs/*.log | tail -5
-```
-
-## Notes
-
-- This PR creates the `EnvManager.ts` module that PR #847 depends on
-- The isolated env approach ensures SDK subprocess never sees random API keys from parent process
-- If no `ANTHROPIC_API_KEY` is in `~/.claude-mem/.env`, Claude Code CLI billing is used (default)

Auto Run Docs/Bigph00t-PRs/Phase-02-Merge-PR-820-Health-Check-Endpoint.md

@@ -1,57 +0,0 @@
-# Phase 02: Merge PR #820 - Health Check Endpoint Fix
-
-**PR:** https://github.com/thedotmack/claude-mem/pull/820
-**Branch:** `fix/health-check-endpoint-811`
-**Status:** Has conflicts, needs rebase
-**Review:** Approved by bayanoj330-dev
-**Priority:** HIGH - Fixes 15-second timeout issue affecting all users
-
-## Summary
-
-Fixes the "Worker did not become ready within 15 seconds" timeout issue by changing health check functions from `/api/readiness` to `/api/health`.
-
-**Root Cause:** `isWorkerHealthy()` and `waitForHealth()` were using `/api/readiness` which returns 503 until full initialization completes (including MCP connection which can take 5+ minutes). Hooks only have 15 seconds timeout.
-
-**Solution:** Use `/api/health` (liveness check) which returns 200 as soon as HTTP server is listening.
-
-## Files Changed
-
-| File | Change |
-|------|--------|
-| `src/shared/worker-utils.ts` | Change `/api/readiness` → `/api/health` in `isWorkerHealthy()` |
-| `src/services/infrastructure/HealthMonitor.ts` | Change `/api/readiness` → `/api/health` in `waitForHealth()` |
-| `tests/infrastructure/health-monitor.test.ts` | Update test to expect `/api/health` |
-
-## Dependencies
-
-- **None** - Independent fix
-
-## Fixes Issues
-
-- #811
-- #772
-- #729
-
-## Tasks
-
-- [x] Checkout PR branch `fix/health-check-endpoint-811` and rebase onto main to resolve conflicts *(Completed: Rebased successfully - build artifact conflicts resolved by accepting main and will rebuild)*
-- [x] Review the endpoint change logic in `worker-utils.ts` and `HealthMonitor.ts` *(Completed: Logic is sound - both files use `/api/health` with proper JSDoc explaining the liveness vs readiness distinction)*
-- [x] Verify build succeeds after rebase *(Completed: Build succeeded - all hooks, worker service, MCP server, context generator, and React viewer built successfully)*
-- [x] Run health monitor tests: `npm test -- tests/infrastructure/health-monitor.test.ts` *(Completed: All 14 tests pass with 24 expect() calls)*
-- [x] Merge PR #820 to main *(Completed: Fast-forward merge from fix/health-check-endpoint-811 to main, pushed to origin)*
-- [x] Manual verification: Kill worker and start fresh session - should not see 15-second timeout *(Completed: Worker health endpoint responds in ~12ms, no timeout errors in logs, both worker-utils.ts and HealthMonitor.ts correctly use /api/health)*
-
-## Verification
-
-```bash
-# After merge, verify hooks work during MCP initialization
-# Start a fresh session and observe logs
-tail -f ~/.claude-mem/logs/worker.log | grep -i "health"
-```
-
-## Notes
-
-- This is a quick fix with minimal code changes
-- The `/api/health` endpoint returns 200 as soon as Express is listening
-- Background initialization continues after health check passes
-- Related to PR #774 which had the same fix but has merge conflicts

Auto Run Docs/Bigph00t-PRs/Phase-03-Merge-PR-827-Bun-Runner.md

@@ -1,76 +0,0 @@
-# Phase 03: Merge PR #827 - Bun Runner for Fresh Install
-
-**PR:** https://github.com/thedotmack/claude-mem/pull/827
-**Branch:** `fix/fresh-install-bun-path-818`
-**Status:** Merged to main (commit 99138203)
-**Review:** Approved by bayanoj330-dev
-**Priority:** MEDIUM - Fixes fresh installation issues
-
-## Summary
-
-Fixes the fresh install issue where worker fails to start because Bun isn't in PATH yet after `smart-install.js` installs it.
-
-**Root Cause:** On fresh installations:
-1. `smart-install.js` installs Bun to `~/.bun/bin/bun`
-2. Bun isn't in current shell's PATH until terminal restart
-3. Hooks try to run `bun ...` directly and fail
-4. Worker never starts, database never created
-
-**Solution:** Introduce `bun-runner.js` - a Node.js script that finds Bun in common install locations (not just PATH) and runs commands with it.
-
-## Files Changed
-
-| File | Change |
-|------|--------|
-| `plugin/scripts/bun-runner.js` | NEW: Script to find and run Bun |
-| `plugin/hooks/hooks.json` | Use `node bun-runner.js` instead of direct `bun` calls |
-
-## Dependencies
-
-- **None** - Independent fix
-
-## Fixes Issues
-
-- #818
-
-## Bun Search Locations
-
-The bun-runner checks these locations in order:
-- PATH (via `which`/`where`)
-- `~/.bun/bin/bun` (default install location)
-- `/usr/local/bin/bun`
-- `/opt/homebrew/bin/bun` (macOS Homebrew)
-- `/home/linuxbrew/.linuxbrew/bin/bun` (Linuxbrew)
-- Windows: `%LOCALAPPDATA%\bun\bin\bun.exe` with fallback
-
-## Tasks
-
-- [x] Checkout PR branch `fix/fresh-install-bun-path-818` and rebase onto main to resolve conflicts
-  - Resolved hooks.json conflict: preserved Setup hook from main, applied bun-runner.js pattern to all hook commands
-- [x] Review `bun-runner.js` for correctness across platforms
-  - ESM imports work (plugin has `"type": "module"`), PATH check uses platform-correct `which`/`where`, covers standard install paths for macOS/Linux/Windows
-- [x] Verify hooks.json uses correct `node bun-runner.js` pattern
-  - All 9 hook commands use `node bun-runner.js`, zero direct `bun` calls remain
-- [x] Verify build succeeds after rebase
-  - `npm run build-and-sync` completed successfully, bun-runner.js synced to marketplace
-- [x] Merge PR #827 to main
-  - Merged with `--no-ff`, pushed to origin, PR #827 closed
-- [x] Test on fresh install (uninstall claude-mem, reinstall) to verify Bun is found
-  - `node plugin/scripts/bun-runner.js --version` returns Bun 1.2.20 successfully
-
-## Verification
-
-```bash
-# After merge, verify bun-runner finds Bun
-node plugin/scripts/bun-runner.js --version
-
-# Check hooks.json uses bun-runner
-grep -i "bun-runner" plugin/hooks/hooks.json
-```
-
-## Notes
-
-- This is a surgical fix that doesn't change core functionality
-- All hooks now go through the Node.js bun-runner script
-- Cross-platform: Linux, macOS, Windows
-- The bun-runner approach is more robust than relying on PATH

Auto Run Docs/Initiation/Phase-01-Merge-PR-856-Zombie-Observer-Fix.md

@@ -1,65 +0,0 @@
-# Phase 01: Test and Merge PR #856 - Zombie Observer Fix
-
-PR #856 adds idle timeout to `SessionQueueProcessor` to prevent zombie observer processes. This is the most mature PR with existing test coverage, passing CI, and no merge conflicts. By the end of this phase, the fix will be merged to main and the improvement will be live.
-
-## Tasks
-
-- [x] Checkout and verify PR #856:
-  - `git fetch origin fix/observer-idle-timeout`
-  - `git checkout fix/observer-idle-timeout`
-  - Verify the branch is up to date with origin
-  - ✅ Branch verified up to date with origin (pulled 4 new files: PR-SHIPPING-REPORT.md, package.json updates, hooks.json updates, setup.sh)
-
-- [x] Run the full test suite to confirm all tests pass:
-  - `npm test`
-  - Specifically verify the 11 SessionQueueProcessor tests pass
-  - Report any failures
-  - ✅ Full test suite passes: 797 pass, 3 skip (pre-existing), 0 fail
-  - ✅ All 11 SessionQueueProcessor tests pass: 11 pass, 0 fail, 20 expect() calls
-
-- [x] Run the build to confirm compilation succeeds:
-  - `npm run build`
-  - Verify no TypeScript errors
-  - Verify all artifacts are generated
-  - ✅ Build completed successfully with no TypeScript errors
-  - ✅ All artifacts generated:
-    - worker-service.cjs (1786.80 KB)
-    - mcp-server.cjs (332.41 KB)
-    - context-generator.cjs (61.57 KB)
-    - viewer-bundle.js and viewer.html
-
-- [x] Code review the changes for correctness:
-  - Read `src/services/queue/SessionQueueProcessor.ts` and verify:
-    - `IDLE_TIMEOUT_MS` is set to 3 minutes (180000ms)
-    - `waitForMessage()` accepts timeout parameter
-    - `lastActivityTime` is reset on spurious wakeup (race condition fix)
-    - Graceful exit logs with `thresholdMs` parameter
-  - Read `tests/services/queue/SessionQueueProcessor.test.ts` and verify test coverage
-  - ✅ Code review complete - all requirements verified:
-    - Line 6: `IDLE_TIMEOUT_MS = 3 * 60 * 1000` (180000ms)
-    - Line 90: `waitForMessage(signal: AbortSignal, timeoutMs: number = IDLE_TIMEOUT_MS)`
-    - Line 63: `lastActivityTime = Date.now()` on spurious wakeup with comment
-    - Lines 54-58: Logger includes `thresholdMs: IDLE_TIMEOUT_MS` parameter
-    - 11 test cases covering idle timeout, abort signal, message events, cleanup, errors, and conversion
-
-- [x] Merge PR #856 to main:
-  - `git checkout main`
-  - `git pull origin main`
-  - `gh pr merge 856 --squash --delete-branch`
-  - Verify merge succeeded
-  - ✅ PR #856 successfully merged to main on 2026-02-05T00:31:24Z
-  - ✅ Merge commit: 7566b8c650d670d7f06f0b4b321aeb56e4d3f109
-  - ✅ Branch fix/observer-idle-timeout deleted
-  - Note: Used --admin flag to bypass failing claude-review CI check (GitHub App not installed - configuration issue, not code issue)
-
-- [x] Run post-merge verification:
-  - `git pull origin main`
-  - `npm test` to confirm tests still pass on main
-  - `npm run build` to confirm build still works
-  - ✅ Main branch is up to date with origin
-  - ✅ Full test suite passes: 797 pass, 3 skip, 0 fail, 1491 expect() calls
-  - ✅ Build completed successfully with all artifacts generated:
-    - worker-service.cjs (1786.80 KB)
-    - mcp-server.cjs (332.41 KB)
-    - context-generator.cjs (61.57 KB)
-    - viewer-bundle.js and viewer.html

Auto Run Docs/Initiation/Phase-02-Merge-PR-722-In-Process-Worker.md

@@ -1,91 +0,0 @@
-# Phase 02: Resolve Conflicts and Merge PR #722 - In-Process Worker Architecture
-
-PR #722 replaces spawn-based worker startup with in-process architecture. Hook processes become the worker when port 37777 is free, eliminating Windows spawn issues. This PR has merge conflicts that must be resolved before merging.
-
-## Tasks
-
-- [x] Checkout PR #722 and assess conflict scope:
-  - `git fetch origin bugfix/claude-md-index`
-  - `git checkout bugfix/claude-md-index`
-  - `git merge main` to see conflicts
-  - List all conflicting files
-
-  **Completed 2026-02-04:** Identified 8 conflicting files:
-  - `docs/CLAUDE.md` (delete/modify - accepted main)
-  - `plugin/CLAUDE.md` (delete/modify - accepted main)
-  - `plugin/hooks/hooks.json` (content conflict - merged both features)
-  - `plugin/scripts/mcp-server.cjs` (build artifact - accepted main)
-  - `plugin/scripts/worker-service.cjs` (build artifact - accepted main)
-  - `src/services/domain/CLAUDE.md` (delete/modify - accepted main)
-  - `src/services/sqlite/CLAUDE.md` (delete/modify - accepted main)
-  - `src/utils/claude-md-utils.ts` (content conflict - preserved #794 fix from main)
-
-- [x] Resolve merge conflicts in each affected file:
-  - For each conflict, understand both sides:
-    - Main branch changes (likely from PR #856 merge)
-    - PR #722 changes (in-process worker architecture)
-  - Preserve both sets of functionality where possible
-  - Key files likely affected:
-    - `src/services/worker-service.ts`
-    - `src/services/queue/SessionQueueProcessor.ts`
-    - `plugin/hooks/hooks.json`
-
-  **Completed 2026-02-04:** All conflicts resolved:
-  - CLAUDE.md files: Accepted main's versions (project uses these for context)
-  - Build artifacts: Accepted main's versions (will be regenerated by build)
-  - hooks.json: Combined PR #722's chained command (smart-install + stop + hook) with main's dual-hook structure
-  - claude-md-utils.ts: Preserved main's #794 fix for empty CLAUDE.md handling
-
-- [x] Run tests after conflict resolution:
-  - `npm test`
-  - All tests must pass (761+ expected)
-  - Report any failures with details
-
-  **Completed 2026-02-04:** All 797 tests passed (3 skipped, 0 failed). 1490 expect() calls across 46 files in 9.99s.
-
-- [x] Run build after conflict resolution:
-  - `npm run build`
-  - Verify no TypeScript errors
-  - Verify all artifacts are generated
-
-  **Completed 2026-02-04:** Build succeeded with no errors. All artifacts generated:
-  - worker-service.cjs (1786.77 KB)
-  - mcp-server.cjs (332.41 KB)
-  - context-generator.cjs (61.57 KB)
-  - viewer.html and viewer-bundle.js
-
-- [x] Code review the in-process worker changes:
-  - Verify `worker-service.ts` hook case starts WorkerService in-process when port free
-  - Verify `hook-command.ts` has `skipExit` option
-  - Verify `hooks.json` uses single chained command
-  - Verify `worker-utils.ts` `ensureWorkerRunning()` returns boolean
-
-  **Completed 2026-02-04:** All review criteria verified:
-  - `worker-service.ts` (lines 638-665): Hook case checks `!portInUse`, creates `new WorkerService()`, calls `start()`, sets `startedWorkerInProcess = true`, uses `break` (not exit) to keep process alive
-  - `hook-command.ts` (lines 6-9, 24-27): `HookCommandOptions` interface has `skipExit?: boolean`, checked before `process.exit()`, returns exit code when skipped
-  - `hooks.json` (line 22): SessionStart uses chained command `smart-install.js && worker stop && worker hook claude-code context`
-  - `worker-utils.ts` (lines 117-135): `ensureWorkerRunning(): Promise<boolean>` returns true if healthy, false otherwise
-
-- [x] Commit conflict resolution and push:
-  - `git add .`
-  - `git commit -m "chore: resolve merge conflicts with main"`
-  - `git push origin bugfix/claude-md-index`
-
-  **Completed 2026-02-04:** Conflict resolution was committed (34b7e13a) and pushed to origin. Verified commit exists in remote branch history.
-
-- [x] Merge PR #722 to main:
-  - Wait for CI to pass after push
-  - `gh pr merge 722 --squash --delete-branch`
-  - Verify merge succeeded
-
-  **Completed 2026-02-04:** PR #722 merged using admin override (claude-review check stuck - same Claude Code GitHub App issue as Phase 01). Merge commit: 4df9f61347407f272fb72eb78b8e500ad1212703. Branch `bugfix/claude-md-index` auto-deleted.
-
-- [x] Run post-merge verification:
-  - `git checkout main && git pull origin main`
-  - `npm test` to confirm tests pass on main
-  - `npm run build` to confirm build works
-
-  **Completed 2026-02-04:** Post-merge verification successful:
-  - Checked out main and pulled latest (already up to date with origin/main)
-  - Tests: 797 passed, 3 skipped, 0 failed (1490 expect() calls across 46 files in 9.94s)
-  - Build: Succeeded with all artifacts generated (worker-service.cjs 1786.77 KB, mcp-server.cjs 332.41 KB, context-generator.cjs 61.57 KB, viewer.html and viewer-bundle.js)

Auto Run Docs/Initiation/Phase-03-Merge-PR-700-Windows-Popup-Fix.md

@@ -1,54 +0,0 @@
-# Phase 03: Resolve Conflicts and Merge PR #700 - Windows Terminal Popup Fix
-
-PR #700 eliminates Windows Terminal popups by removing spawn-based daemon startup. The worker `start` command now becomes daemon directly instead of spawning a child process. This PR has merge conflicts and may have significant overlap with PR #722 (in-process worker).
-
-## Tasks
-
-- [ ] Checkout PR #700 and assess conflict scope:
-  - `git fetch origin bugfix/spawners`
-  - `git checkout bugfix/spawners`
-  - `git merge main` to see conflicts
-  - List all conflicting files
-  - Assess if changes overlap significantly with already-merged PR #722
-
-- [ ] Evaluate if PR #700 is still needed:
-  - PR #722 (in-process worker) may have already addressed the same Windows spawn issues
-  - Compare the changes in both PRs
-  - If #722 fully supersedes #700, close #700 with explanation
-  - Otherwise proceed with conflict resolution
-
-- [ ] If proceeding, resolve merge conflicts:
-  - Key files likely affected:
-    - `src/services/worker-service.ts` (daemon startup changes)
-    - `src/services/sync/ChromaSync.ts` (windowsHide removal)
-    - `plugin/hooks/hooks.json` (command changes)
-  - Preserve functionality from main while adding non-spawn daemon behavior
-
-- [ ] Run tests after conflict resolution:
-  - `npm test`
-  - All tests must pass
-  - Report any failures with details
-
-- [ ] Run build after conflict resolution:
-  - `npm run build`
-  - Verify no TypeScript errors
-
-- [ ] Code review the Windows-specific changes:
-  - Verify worker `start` command becomes daemon directly (no child spawn)
-  - Verify `restart` command removal (users do stop then start)
-  - Verify windowsHide removal from ChromaSync
-
-- [ ] Commit conflict resolution and push:
-  - `git add .`
-  - `git commit -m "chore: resolve merge conflicts with main"`
-  - `git push origin bugfix/spawners`
-
-- [ ] Merge PR #700 to main:
-  - Wait for CI to pass after push
-  - `gh pr merge 700 --squash --delete-branch`
-  - Verify merge succeeded
-
-- [ ] Run post-merge verification:
-  - `git checkout main && git pull origin main`
-  - `npm test` to confirm tests pass
-  - `npm run build` to confirm build works

Auto Run Docs/Initiation/Phase-04-Merge-PR-657-CLI-Commands.md

@@ -1,54 +0,0 @@
-# Phase 04: Resolve Conflicts and Merge PR #657 - CLI Generate/Clean Commands
-
-PR #657 adds `claude-mem generate` and `claude-mem clean` CLI commands with cross-platform support. It also fixes validation gaps that caused deleted folders to be recreated from stale DB records, and adds automatic shell alias installation. This PR has merge conflicts.
-
-## Tasks
-
-- [ ] Checkout PR #657 and assess conflict scope:
-  - `git fetch origin bugfix/jan10-bug-2`
-  - `git checkout bugfix/jan10-bug-2`
-  - `git merge main` to see conflicts
-  - List all conflicting files
-
-- [ ] Resolve merge conflicts:
-  - Key files likely affected:
-    - `src/services/worker-service.ts` (generate/clean command cases)
-    - `plugin/scripts/smart-install.js` (CLI installation)
-  - Preserve all existing functionality while adding CLI commands
-
-- [ ] Run tests after conflict resolution:
-  - `npm test`
-  - All tests must pass
-  - Report any failures with details
-
-- [ ] Run build after conflict resolution:
-  - `npm run build`
-  - Verify no TypeScript errors
-
-- [ ] Test the CLI commands manually:
-  - `bun plugin/scripts/worker-service.cjs generate --dry-run`
-  - `bun plugin/scripts/worker-service.cjs clean --dry-run`
-  - Both should exit with code 0
-  - Review output for sensible behavior
-
-- [ ] Code review the CLI implementation:
-  - Verify `src/cli/claude-md-commands.ts` exports generate/clean functions
-  - Verify validation fixes in `regenerateFolder()` (folder existence check)
-  - Verify path traversal prevention
-  - Verify cross-platform path handling (`toDbPath()`, `toFsPath()`)
-
-- [ ] Commit conflict resolution and push:
-  - `git add .`
-  - `git commit -m "chore: resolve merge conflicts with main"`
-  - `git push origin bugfix/jan10-bug-2`
-
-- [ ] Merge PR #657 to main:
-  - Wait for CI to pass after push
-  - `gh pr merge 657 --squash --delete-branch`
-  - Verify merge succeeded
-
-- [ ] Run post-merge verification:
-  - `git checkout main && git pull origin main`
-  - `npm test` to confirm tests pass
-  - `npm run build` to confirm build works
-  - Verify CLI commands still work: `bun plugin/scripts/worker-service.cjs generate --dry-run`

Auto Run Docs/Initiation/Phase-05-Merge-PR-863-Ragtime-Email.md

@@ -1,46 +0,0 @@
-# Phase 05: Test and Merge PR #863 - Ragtime Email Investigation
-
-PR #863 adds email investigation mode via `CLAUDE_MEM_MODE` environment variable. Each file is processed in a new session with context managed by Claude-mem hooks. It includes configurable transcript cleanup to prevent buildup. This PR has no merge conflicts and CI is passing.
-
-## Tasks
-
-- [ ] Checkout and verify PR #863:
-  - `git fetch origin claude/setup-ragtime-epstein-analysis-JApkL`
-  - `git checkout claude/setup-ragtime-epstein-analysis-JApkL`
-  - Verify the branch is up to date with origin
-
-- [ ] Rebase onto main to incorporate previous PR merges:
-  - `git rebase main`
-  - If conflicts arise, resolve them
-  - Push with `git push --force-with-lease origin claude/setup-ragtime-epstein-analysis-JApkL`
-
-- [ ] Run the full test suite:
-  - `npm test`
-  - All tests must pass
-  - Report any failures
-
-- [ ] Run the build:
-  - `npm run build`
-  - Verify no TypeScript errors
-
-- [ ] Code review the ragtime implementation:
-  - Understand the `CLAUDE_MEM_MODE` environment variable usage
-  - Review session-per-file processing approach
-  - Review transcript cleanup configuration (default 24h)
-  - Verify environment variable configuration for paths and settings
-
-- [ ] Evaluate if this feature belongs in main:
-  - This appears to be an experimental/specialized feature
-  - Consider if it should be merged or kept as experimental branch
-  - If appropriate for main, proceed with merge
-  - If experimental, document status and skip merge
-
-- [ ] If proceeding, merge PR #863 to main:
-  - `gh pr merge 863 --squash --delete-branch`
-  - Verify merge succeeded
-
-- [ ] Run final verification:
-  - `git checkout main && git pull origin main`
-  - `npm test` to confirm all tests pass
-  - `npm run build` to confirm build works
-  - Verify all 5 PRs are now merged

CHANGELOG.md

@@ -2,6 +2,502 @@
 
 All notable changes to claude-mem.
 
+## [v10.2.4] - 2026-02-18
+
+## Chroma Vector DB Backfill Fix
+
+Fixes the Chroma backfill system to correctly sync all SQLite observations into the vector database on worker startup.
+
+### Bug Fixes
+
+- **Backfill all projects on startup** — `backfillAllProjects()` now runs on worker startup, iterating all projects in SQLite and syncing missing observations to Chroma. Previously `ensureBackfilled()` existed but was never called, leaving Chroma with incomplete data after cache clears.
+
+- **Fixed critical collection routing bug** — Backfill now uses the shared `cm__claude-mem` collection (matching how DatabaseManager and SearchManager operate) instead of creating per-project orphan collections that no search path reads from.
+
+- **Hardened collection name sanitization** — Project names with special characters (e.g., "YC Stuff") are sanitized for Chroma's naming constraints, including stripping trailing non-alphanumeric characters.
+
+- **Eliminated shared mutable state** — `ensureBackfilled()` and `getExistingChromaIds()` now accept project as a parameter instead of mutating instance state, keeping a single Chroma connection while avoiding fragile property mutation across iterations.
+
+- **Chroma readiness guard** — Backfill waits for Chroma server readiness before running, preventing spurious error logs when Chroma fails to start.
+
+### Changed Files
+
+- `src/services/sync/ChromaSync.ts` — Core backfill logic, sanitization, parameter passing
+- `src/services/worker-service.ts` — Startup backfill trigger + readiness guard
+- `src/utils/logger.ts` — Added `CHROMA_SYNC` log component
+
+## [v10.2.3] - 2026-02-17
+
+## Fix Chroma ONNX Model Cache Corruption
+
+Addresses the persistent embedding pipeline failures reported across #1104, #1105, #1110, and subsequent sessions. Three root causes identified and fixed:
+
+### Changes
+
+- **Removed nuclear `bun pm cache rm`** from both `smart-install.js` and `sync-marketplace.cjs`. This was added in v10.2.2 for the now-removed sharp dependency but destroyed all cached packages, breaking the ONNX resolution chain.
+- **Added `bun install` in plugin cache directory** after marketplace sync. The cache directory had a `package.json` with `@chroma-core/default-embed` as a dependency but never ran install, so the worker couldn't resolve it at runtime.
+- **Moved HuggingFace model cache to `~/.claude-mem/models/`** outside `node_modules`. The ~23MB ONNX model was stored inside `node_modules/@huggingface/transformers/.cache/`, so any reinstall or cache clear corrupted it.
+- **Added self-healing retry** for Protobuf parsing failures. If the downloaded model is corrupted, the cache is cleared and re-downloaded automatically on next use.
+
+### Files Changed
+
+- `scripts/smart-install.js` — removed `bun pm cache rm`
+- `scripts/sync-marketplace.cjs` — removed `bun pm cache rm`, added `bun install` in cache dir
+- `src/services/sync/ChromaSync.ts` — moved model cache, added corruption recovery
+
+## [v10.2.2] - 2026-02-17
+
+## Bug Fixes
+
+- **Removed `node-addon-api` dev dependency** — was only needed for `sharp`, which was already removed in v10.2.1
+- **Simplified native module cache clearing** in `smart-install.js` and `sync-marketplace.cjs` — replaced targeted `@img/sharp` directory deletion and lockfile removal with `bun pm cache rm`
+- Reduced ~30 lines of brittle file system manipulation to a clean Bun CLI command
+
+## [v10.2.1] - 2026-02-16
+
+## Bug Fixes
+
+- **Bun install & sharp native modules**: Fixed stale native module cache issues on Bun updates, added `node-addon-api` as a dev dependency required by sharp (#1140)
+- **PendingMessageStore consolidation**: Deduplicated PendingMessageStore initialization in worker-service; added session-scoped filtering to `resetStaleProcessingMessages` to prevent cross-session message resets (#1140)
+- **Gemini empty response handling**: Fixed silent message deletion when Gemini returns empty summary responses — now logs a warning and preserves the original message (#1138)
+- **Idle timeout session scoping**: Fixed idle timeout handler to only reset messages for the timed-out session instead of globally resetting all sessions (#1138)
+- **Shell injection in sync-marketplace**: Replaced `execSync` with `spawnSync` for rsync calls to eliminate command injection via gitignore patterns (#1138)
+- **Sharp cache invalidation**: Added cache clearing for sharp's native bindings when Bun version changes (#1138)
+- **Marketplace install**: Switched marketplace sync from npm to bun for package installation consistency (#1140)
+
+## [v10.1.0] - 2026-02-16
+
+## SessionStart System Message & Cleaner Defaults
+
+### New Features
+
+- **SessionStart `systemMessage` support** — Hooks can now display user-visible ANSI-colored messages directly in the CLI via a new `systemMessage` field on `HookResult`. The SessionStart hook uses this to render a colored timeline summary (separate from the markdown context injected for Claude), giving users an at-a-glance view of recent activity every time they start a session.
+
+- **"View Observations Live" link** — Each session start now appends a clickable `http://localhost:{port}` URL so users can jump straight to the live observation viewer.
+
+### Performance
+
+- **Truly parallel context fetching** — The SessionStart handler now uses `Promise.all` to fetch both the markdown context (for Claude) and the ANSI-colored timeline (for user display) simultaneously, eliminating the serial fetch overhead.
+
+### Defaults Changes
+
+- **Cleaner out-of-box experience** — New installs now default to a streamlined context display:
+  - Read tokens column: hidden (`CLAUDE_MEM_CONTEXT_SHOW_READ_TOKENS: false`)
+  - Work tokens column: hidden (`CLAUDE_MEM_CONTEXT_SHOW_WORK_TOKENS: false`)
+  - Savings amount: hidden (`CLAUDE_MEM_CONTEXT_SHOW_SAVINGS_AMOUNT: false`)
+  - Full observation expansion: disabled (`CLAUDE_MEM_CONTEXT_FULL_COUNT: 0`)
+  - Savings percentage remains visible by default
+
+  Existing users are unaffected — your `~/.claude-mem/settings.json` overrides these defaults.
+
+### Technical Details
+
+- Added `systemMessage?: string` to `HookResult` interface (`src/cli/types.ts`)
+- Claude Code adapter now forwards `systemMessage` in hook output (`src/cli/adapters/claude-code.ts`)
+- Context handler refactored for parallel fetch with graceful fallback (`src/cli/handlers/context.ts`)
+- Default settings tuned in `SettingsDefaultsManager` (`src/shared/SettingsDefaultsManager.ts`)
+
+## [v10.0.8] - 2026-02-16
+
+## Bug Fixes
+
+### Orphaned Subprocess Cleanup
+- Add explicit subprocess cleanup after SDK query loop using existing `ProcessRegistry` infrastructure (`getProcessBySession` + `ensureProcessExit`), preventing orphaned Claude subprocesses from accumulating
+- Closes #1010, #1089, #1090, #1068
+
+### Chroma Binary Resolution
+- Replace `npx chroma run` with absolute binary path resolution via `require.resolve`, falling back to `npx` with explicit `cwd` when the binary isn't found directly
+- Closes #1120
+
+### Cross-Platform Embedding Fix
+- Remove `@chroma-core/default-embed` which pulled in `onnxruntime` + `sharp` native binaries that fail on many platforms
+- Use WASM backend for Chroma embeddings, eliminating native binary compilation issues
+- Closes #1104, #1105, #1110
+
+## [v10.0.7] - 2026-02-14
+
+## Chroma HTTP Server Architecture
+
+- **Persistent HTTP server**: Switched from in-process Chroma to a persistent HTTP server managed by the new `ChromaServerManager` for better reliability and performance
+- **Local embeddings**: Added `DefaultEmbeddingFunction` for local vector embeddings — no external API required
+- **Pinned chromadb v3.2.2**: Fixed compatibility with v2 API heartbeat endpoint
+- **Server lifecycle improvements**: Addressed PR review feedback for proper start/stop/health check handling
+
+## Bug Fixes
+
+- Fixed SDK spawn failures and sharp native binary crashes
+- Added `plugin.json` to root `.claude-plugin` directory for proper plugin structure
+- Removed duplicate else block from merge artifact
+
+## Infrastructure
+
+- Added multi-tenancy support for claude-mem Pro
+- Updated OpenClaw install URLs to `install.cmem.ai`
+- Added Vercel deploy workflow for install scripts
+- Added `.claude/plans` and `.claude/worktrees` to `.gitignore`
+
+## [v10.0.6] - 2026-02-13
+
+## Bug Fixes
+
+- **OpenClaw: Fix MEMORY.md project query mismatch** — `syncMemoryToWorkspace` now includes both the base project name and the agent-scoped project name (e.g., both "openclaw" and "openclaw-main") when querying for context injection, ensuring the correct observations are pulled into MEMORY.md.
+
+- **OpenClaw: Add feed botToken support for Telegram** — Feeds can now configure a dedicated `botToken` for direct Telegram message delivery, bypassing the OpenClaw gateway channel. This fixes scenarios where the gateway bot token couldn't be used for feed messages.
+
+## Other
+
+- Changed OpenClaw plugin kind from "integration" to "memory" for accuracy.
+
+## [v10.0.5] - 2026-02-13
+
+## OpenClaw Installer & Distribution
+
+This release introduces the OpenClaw one-liner installer and fixes several OpenClaw plugin issues.
+
+### New Features
+
+- **OpenClaw Installer** (`openclaw/install.sh`): Full cross-platform installer script with `curl | bash` support
+  - Platform detection (macOS, Linux, WSL)
+  - Automatic dependency management (Bun, uv, Node.js)
+  - Interactive AI provider setup with settings writer
+  - OpenClaw gateway detection, plugin install, and memory slot configuration
+  - Worker startup and health verification with rich diagnostics
+  - TTY detection, `--provider`/`--api-key` CLI flags
+  - Error recovery and upgrade handling for existing installations
+  - jq/python3/node fallback chain for JSON config writing
+- **Distribution readiness tests** (`openclaw/test-install.sh`): Comprehensive test suite for the installer
+- **Enhanced `/api/health` endpoint**: Now returns version, uptime, workerPath, and AI status
+
+### Bug Fixes
+
+- Fix: use `event.prompt` instead of `ctx.sessionKey` for prompt storage in OpenClaw plugin
+- Fix: detect both `openclaw` and `openclaw.mjs` binary names in gateway discovery
+- Fix: pass file paths via env vars instead of bash interpolation in `node -e` calls
+- Fix: handle stale plugin config that blocks OpenClaw CLI during reinstall
+- Fix: remove stale memory slot reference during reinstall cleanup
+- Fix: remove opinionated filters from OpenClaw plugin
+
+## [v10.0.4] - 2026-02-12
+
+## Revert: v10.0.3 chroma-mcp spawn storm fix
+
+v10.0.3 introduced regressions. This release reverts the codebase to the stable v10.0.2 state.
+
+### What was reverted
+
+- Connection mutex via promise memoization
+- Pre-spawn process count guard
+- Hardened `close()` with try-finally + Unix `pkill -P` fallback
+- Count-based orphan reaper in `ProcessManager`
+- Circuit breaker (3 failures → 60s cooldown)
+- `etime`-based sorting for process guards
+
+### Files restored to v10.0.2
+
+- `src/services/sync/ChromaSync.ts`
+- `src/services/infrastructure/GracefulShutdown.ts`
+- `src/services/infrastructure/ProcessManager.ts`
+- `src/services/worker-service.ts`
+- `src/services/worker/ProcessRegistry.ts`
+- `tests/infrastructure/process-manager.test.ts`
+- `tests/integration/chroma-vector-sync.test.ts`
+
+## [v10.0.3] - 2026-02-11
+
+## Fix: Prevent chroma-mcp spawn storm (PR #1065)
+
+Fixes a critical bug where killing the worker daemon during active sessions caused **641 chroma-mcp Python processes** to spawn in ~5 minutes, consuming 75%+ CPU and ~64GB virtual memory.
+
+### Root Cause
+
+`ChromaSync.ensureConnection()` had no connection mutex. Concurrent fire-and-forget `syncObservation()` calls from multiple sessions raced through the check-then-act guard, each spawning a chroma-mcp subprocess via `StdioClientTransport`. Error-driven reconnection created a positive feedback loop.
+
+### 5-Layer Defense
+
+| Layer | Mechanism | Purpose |
+|-------|-----------|---------|
+| **0** | Connection mutex via promise memoization | Coalesces concurrent callers onto a single spawn attempt |
+| **1** | Pre-spawn process count guard (`execFileSync('ps')`) | Kills excess chroma-mcp processes before spawning new ones |
+| **2** | Hardened `close()` with try-finally + Unix `pkill -P` fallback | Guarantees state reset even on error, kills orphaned children |
+| **3** | Count-based orphan reaper in `ProcessManager` | Kills by count (not age), catches spawn storms where all processes are young |
+| **4** | Circuit breaker (3 failures → 60s cooldown) | Stops error-driven reconnection positive feedback loop |
+
+### Additional Fix
+
+- Process guards now use `etime`-based sorting instead of PID ordering for reliable age determination (PIDs wrap and don't guarantee ordering)
+
+### Testing
+
+- 16 new tests for mutex, circuit breaker, close() hardening, and count guard
+- All tests pass (947 pass, 3 skip)
+
+Closes #1063, closes #695. Relates to #1010, #707.
+
+**Contributors:** @rodboev
+
+## [v10.0.2] - 2026-02-11
+
+## Bug Fixes
+
+- **Prevent daemon silent death from SIGHUP + unhandled errors** — Worker process could silently die when receiving SIGHUP signals or encountering unhandled errors, leaving hooks without a backend. Now properly handles these signals and prevents silent crashes.
+- **Hook resilience and worker lifecycle improvements** — Comprehensive fixes for hook command error classification, addressing issues #957, #923, #984, #987, and #1042. Hooks now correctly distinguish between worker unavailability errors and other failures.
+- **Clarify TypeError order dependency in error classifier** — Fixed error classification logic to properly handle TypeError ordering edge cases.
+
+## New Features
+
+- **Project-scoped statusline counter utility** — Added `statusline-counts.js` for tracking observation counts per project in the Claude Code status line.
+
+## Internal
+
+- Added test coverage for hook command error classification and process manager
+- Worker service and MCP server lifecycle improvements
+- Process manager enhancements for better cross-platform stability
+
+### Contributors
+- @rodboev — Hook resilience and worker lifecycle fixes (PR #1056)
+
+## [v10.0.1] - 2026-02-11
+
+## What's Changed
+
+### OpenClaw Observation Feed
+- Enabled SSE observation feed for OpenClaw agent sessions, allowing real-time streaming of observations to connected OpenClaw clients
+- Fixed `ObservationSSEPayload.project` type to be nullable, preventing type errors when project context is unavailable
+- Added `EnvManager` support for OpenClaw environment configuration
+
+### Build Artifacts
+- Rebuilt worker service and MCP server with latest changes
+
+## [v10.0.0] - 2026-02-11
+
+## OpenClaw Plugin — Persistent Memory for OpenClaw Agents
+
+Claude-mem now has an official [OpenClaw](https://openclaw.ai) plugin, bringing persistent memory to agents running on the OpenClaw gateway. This is a major milestone — claude-mem's memory system is no longer limited to Claude Code sessions.
+
+### What It Does
+
+The plugin bridges claude-mem's observation pipeline with OpenClaw's embedded runner (`pi-embedded`), which calls the Anthropic API directly without spawning a `claude` process. Three core capabilities:
+
+1. **Observation Recording** — Captures every tool call from OpenClaw agents and sends it to the claude-mem worker for AI-powered compression and storage
+2. **MEMORY.md Live Sync** — Writes a continuously-updated memory timeline to each agent's workspace, so agents start every session with full context from previous work
+3. **Observation Feed** — Streams new observations to messaging channels (Telegram, Discord, Slack, Signal, WhatsApp, LINE) in real-time via SSE
+
+### Quick Start
+
+Add claude-mem to your OpenClaw gateway config:
+
+```json
+{
+  "plugins": {
+    "claude-mem": {
+      "enabled": true,
+      "config": {
+        "project": "my-project",
+        "syncMemoryFile": true,
+        "observationFeed": {
+          "enabled": true,
+          "channel": "telegram",
+          "to": "your-chat-id"
+        }
+      }
+    }
+  }
+}
+```
+
+The claude-mem worker service must be running on the same machine (`localhost:37777`).
+
+### Commands
+
+- `/claude-mem-status` — Worker health check, active sessions, feed connection state
+- `/claude-mem-feed` — Show/toggle observation feed status
+- `/claude-mem-feed on|off` — Enable/disable feed
+
+### How the Event Lifecycle Works
+
+```
+OpenClaw Gateway
+  ├── session_start ──────────→ Init claude-mem session
+  ├── before_agent_start ─────→ Sync MEMORY.md + track workspace
+  ├── tool_result_persist ────→ Record observation + re-sync MEMORY.md
+  ├── agent_end ──────────────→ Summarize + complete session
+  ├── session_end ────────────→ Clean up session tracking
+  └── gateway_start ──────────→ Reset all tracking
+```
+
+All observation recording and MEMORY.md syncs are fire-and-forget — they never block the agent.
+
+📖 Full documentation: [OpenClaw Integration Guide](https://docs.claude-mem.ai/docs/openclaw-integration)
+
+---
+
+## Windows Platform Improvements
+
+- **ProcessManager**: Migrated daemon spawning from deprecated WMIC to PowerShell `Start-Process` with `-WindowStyle Hidden`
+- **ChromaSync**: Re-enabled vector search on Windows (was previously disabled entirely)
+- **Worker Service**: Added unified DB-ready gate middleware — all DB-dependent endpoints now wait for initialization instead of returning "Database not initialized" errors
+- **EnvManager**: Switched from fragile allowlist to simple blocklist for subprocess env vars (only strips `ANTHROPIC_API_KEY` per Issue #733)
+
+## Session Management Fixes
+
+- Fixed unbounded session tracking map growth — maps are now cleaned up on `session_end`
+- Session init moved to `session_start` and `after_compaction` hooks for correct lifecycle handling
+
+## SSE Fixes
+
+- Fixed stream URL consistency across the codebase
+- Fixed multi-line SSE data frame parsing (concatenates `data:` lines per SSE spec)
+
+## Issue Triage
+
+Closed 37+ duplicate/stale/invalid issues across multiple triage phases, significantly cleaning up the issue tracker.
+
+## [v9.1.1] - 2026-02-07
+
+## Critical Bug Fix: Worker Initialization Failure
+
+**v9.1.0 was unable to initialize its database on existing installations.** This patch fixes the root cause and several related issues.
+
+### Bug Fixes
+
+- **Fix FOREIGN KEY constraint failure during migration** — The `addOnUpdateCascadeToForeignKeys` migration (schema v21) crashed when orphaned observations existed (observations whose `memory_session_id` has no matching row in `sdk_sessions`). Fixed by disabling FK checks (`PRAGMA foreign_keys = OFF`) during table recreation, following SQLite's recommended migration pattern.
+
+- **Remove hardcoded CHECK constraints on observation type column** — Multiple locations enforced `CHECK(type IN ('decision', 'bugfix', ...))` but the mode system (v8.0.0+) allows custom observation types, causing constraint violations. Removed all 5 occurrences across `SessionStore.ts`, `migrations.ts`, and `migrations/runner.ts`.
+
+- **Fix Express middleware ordering for initialization guard** — The `/api/*` guard middleware that waits for DB initialization was registered AFTER routes, so Express matched routes before the guard. Moved guard middleware registration BEFORE route registrations. Added dedicated early handler for `/api/context/inject` to fail-open during init.
+
+### New
+
+- **Restored mem-search skill** — Recreated `plugin/skills/mem-search/SKILL.md` with the 3-layer workflow (search → timeline → batch fetch) updated for the current MCP tool set.
+
+## [v9.1.0] - 2026-02-07
+
+## v9.1.0 — The Great PR Triage
+
+100 open PRs reviewed, triaged, and resolved. 157 commits, 123 files changed, +6,104/-721 lines. This release focuses on stability, security, and community contributions.
+
+### Highlights
+
+- **100 PR triage**: Reviewed every open PR — merged 48, cherry-picked 13, closed 39 (stale/duplicate/YAGNI)
+- **Fail-open hook architecture**: Hooks no longer block Claude Code prompts when the worker is starting up
+- **DB initialization guard**: All API endpoints now wait for database initialization instead of crashing with "Database not initialized"
+- **Security hardening**: CORS restricted to localhost, XSS defense-in-depth via DOMPurify
+- **3 new features**: Manual memory save, project exclusion, folder exclude setting
+
+---
+
+### Security
+
+- **CORS restricted to localhost** — Worker API no longer accepts cross-origin requests from arbitrary websites. Only localhost/127.0.0.1 origins allowed. (PR #917 by @Spunky84)
+- **XSS defense-in-depth** — Added DOMPurify sanitization to TerminalPreview.tsx viewer component (concept from PR #896)
+
+### New Features
+
+- **Manual memory storage** — New \`save_memory\` MCP tool and \`POST /api/memory/save\` endpoint for explicit memory capture (PR #662 by @darconada, closes #645)
+- **Project exclusion setting** — \`CLAUDE_MEM_EXCLUDED_PROJECTS\` glob patterns to exclude entire projects from tracking (PR #920 by @Spunky84)
+- **Folder exclude setting** — \`CLAUDE_MEM_FOLDER_MD_EXCLUDE\` JSON array to exclude paths from CLAUDE.md generation, fixing Xcode/drizzle build conflicts (PR #699 by @leepokai, closes #620)
+- **Folder CLAUDE.md opt-in** — \`CLAUDE_MEM_FOLDER_CLAUDEMD_ENABLED\` now defaults to \`false\` (opt-in) instead of always-on (PR #913 by @superbiche)
+- **Generate/clean CLI commands** — \`generate\` and \`clean\` commands for CLAUDE.md management with \`--dry-run\` support (PR #657 by @thedotmack)
+- **Ragtime email investigation** — Batch processor for email investigation workflows (PR #863 by @thedotmack)
+
+### Hook Resilience (Fail-Open Architecture)
+
+Hooks no longer block Claude Code when the worker is unavailable or slow:
+
+- **Graceful hook failures** — Hooks exit 0 with empty responses instead of crashing with exit 2 (PR #973 by @farikh)
+- **Fail-open context injection** — Returns empty context during initialization instead of 503 (PR #959 by @rodboev)
+- **Fetch timeouts** — All hook fetch calls have timeouts via \`fetchWithTimeout()\` helper (PR #964 by @rodboev)
+- **Removed stale user-message hook** — Eliminated startup error from incorrectly bundled hook (PR #960 by @rodboev)
+- **DB initialization middleware** — All \`/api/*\` routes now wait for DB init with 30s timeout instead of crashing
+
+### Windows Stability
+
+- **Path spaces fix** — bun-runner.js no longer fails for Windows usernames with spaces (PR #972 by @farikh)
+- **Spawn guard** — 2-minute cooldown prevents repeated worker popup windows on startup failure
+
+### Process & Zombie Management
+
+- **Daemon children cleanup** — Orphan reaper now catches idle daemon child processes (PR #879 by @boaz-robopet)
+- **Expanded orphan cleanup** — Startup cleanup now targets mcp-server.cjs and worker-service.cjs processes
+- **Session-complete hook** — New Stop phase 2 hook removes sessions from active map, enabling effective orphan reaper cleanup (PR #844 by @thusdigital, fixes #842)
+
+### Session Management
+
+- **Prompt-too-long termination** — Sessions terminate cleanly instead of infinite retry loops (PR #934 by @jayvenn21)
+- **Infinite restart prevention** — Max 3 restart attempts with exponential backoff, prevents runaway API costs (PR #693 by @ajbmachon)
+- **Orphaned message fallback** — Messages from terminated sessions drain via Gemini/OpenRouter fallback (PR #937 by @jayvenn21, fixes #936)
+- **Project field backfill** — Sessions correctly scoped when PostToolUse creates session before UserPromptSubmit (PR #940 by @miclip)
+- **Provider-aware recovery** — Startup recovery uses correct provider instead of hardcoding SDKAgent (PR #741 by @licutis)
+- **AbortController reset** — Prevents infinite "Generator aborted" loops after session abort (PR #627 by @TranslateMe)
+- **Stateless provider IDs** — Synthetic memorySessionId generation for Gemini/OpenRouter (concept from PR #615 by @JiehoonKwak)
+- **Duplicate generator prevention** — Legacy init endpoint uses idempotent \`ensureGeneratorRunning()\` (PR #932 by @jayvenn21)
+- **DB readiness wait** — Session-init endpoint waits for database initialization (PR #828 by @rajivsinclair)
+- **Image-only prompt support** — Empty/media prompts use \`[media prompt]\` placeholder (concept from PR #928 by @iammike)
+
+### CLAUDE.md Path & Generation
+
+- **Race condition fix** — Two-pass detection prevents corruption when Claude Code edits CLAUDE.md (concept from PR #974 by @cheapsteak)
+- **Duplicate path prevention** — Detects \`frontend/frontend/\` style nested duplicates (concept from PR #836 by @Glucksberg)
+- **Unsafe directory exclusion** — Blocks generation in \`res/\`, \`.git/\`, \`build/\`, \`node_modules/\`, \`__pycache__/\` (concept from PR #929 by @jayvenn21)
+
+### Chroma/Vector Search
+
+- **ID/metadata alignment fix** — Search results no longer misaligned after deduplication (PR #887 by @abkrim)
+- **Transport zombie prevention** — Connection error handlers now close transport (PR #769 by @jenyapoyarkov)
+- **Zscaler SSL support** — Enterprise environments with SSL inspection now work via combined cert path (PR #884 by @RClark4958)
+
+### Parser & Config
+
+- **Nested XML tag handling** — Parser correctly extracts fields with nested XML content (PR #835 by @Glucksberg)
+- **Graceful empty transcripts** — Transcript parser returns empty string instead of crashing (PR #862 by @DennisHartrampf)
+- **Gemini model name fix** — Corrected \`gemini-3-flash\` → \`gemini-3-flash-preview\` (PR #831 by @Glucksberg)
+- **CLAUDE_CONFIG_DIR support** — Plugin paths respect custom config directory (PR #634 by @Kuroakira, fixes #626)
+- **Env var priority** — \`env > file > defaults\` ordering via \`applyEnvOverrides()\` (PR #712 by @cjpeterein)
+- **Minimum Bun version check** — smart-install.js enforces Bun 1.1.14+ (PR #524 by @quicktime, fixes #519)
+- **Stdin timeout** — JSON self-delimiting detection with 30s safety timeout prevents hook hangs (PR #771 by @rajivsinclair, fixes #727)
+- **FK constraint prevention** — \`ensureMemorySessionIdRegistered()\` guard + \`ON UPDATE CASCADE\` schema migration (PR #889 by @Et9797, fixes #846)
+- **Cursor bun runtime** — Cursor hooks use bun instead of node, fixing bun:sqlite crashes (PR #721 by @polux0)
+
+### Documentation
+
+- **9 README PRs merged**: formatting fixes, Korean/Japanese/Chinese render fixes, documentation link updates, Traditional Chinese + Urdu translations (PRs #953, #898, #864, #637, #636, #894, #907, #691 by @Leonard013, @youngsu5582, @eltociear, @WuMingDao, @fengluodb, @PeterDaveHello, @yasirali646)
+- **Windows setup note** — npm PATH instructions (PR #919 by @kamran-khalid-v9)
+- **Issue templates** — Duplicate check checkbox added (PR #970 by @bmccann36)
+
+### Community Contributors
+
+Thank you to the 35+ contributors whose PRs were reviewed in this release:
+
+@Spunky84, @farikh, @rodboev, @boaz-robopet, @jayvenn21, @ajbmachon, @miclip, @licutis, @TranslateMe, @JiehoonKwak, @rajivsinclair, @iammike, @cheapsteak, @Glucksberg, @abkrim, @jenyapoyarkov, @RClark4958, @DennisHartrampf, @Kuroakira, @cjpeterein, @quicktime, @polux0, @Et9797, @thusdigital, @superbiche, @darconada, @leepokai, @Leonard013, @youngsu5582, @eltociear, @WuMingDao, @fengluodb, @PeterDaveHello, @yasirali646, @kamran-khalid-v9, @bmccann36
+
+---
+
+**Full Changelog**: https://github.com/thedotmack/claude-mem/compare/v9.0.17...v9.1.0
+
+## [v9.0.17] - 2026-02-05
+
+## Bug Fixes
+
+### Fix Fresh Install Bun PATH Resolution (#818)
+
+On fresh installations, hooks would fail because Bun wasn't in PATH until terminal restart. The `smart-install.js` script installs Bun to `~/.bun/bin/bun`, but the current shell session doesn't have it in PATH.
+
+**Fix:** Introduced `bun-runner.js` — a Node.js wrapper that searches common Bun installation locations across all platforms:
+- PATH (via `which`/`where`)
+- `~/.bun/bin/bun` (default install location)
+- `/usr/local/bin/bun`
+- `/opt/homebrew/bin/bun` (macOS Homebrew)
+- `/home/linuxbrew/.linuxbrew/bin/bun` (Linuxbrew)
+- Windows: `%LOCALAPPDATA%\bun` or fallback paths
+
+All 9 hook definitions updated to use `node bun-runner.js` instead of direct `bun` calls.
+
+**Files changed:**
+- `plugin/scripts/bun-runner.js` — New 88-line Bun discovery script
+- `plugin/hooks/hooks.json` — All hook commands now route through bun-runner
+
+Fixes #818 | PR #827 by @bigphoot
+
 ## [v9.0.16] - 2026-02-05
 
 ## Bug Fixes
@@ -943,411 +1439,3 @@ This patch release addresses several issues discovered after the session continu
 
 Full changelog: https://github.com/thedotmack/claude-mem/compare/v8.2.4...v8.2.5
 
-## [v8.2.4] - 2025-12-28
-
-Patch release v8.2.4
-
-## [v8.2.3] - 2025-12-27
-
-## Bug Fixes
-
-- Fix worker port environment variable in smart-install script
-- Implement file-based locking mechanism for worker operations to prevent race conditions
-- Fix restart command references in documentation (changed from `claude-mem restart` to `npm run worker:restart`)
-
-## [v8.2.2] - 2025-12-27
-
-## What's Changed
-
-### Features
-- Add OpenRouter provider settings and documentation
-- Add modal footer with save button and status indicators
-- Implement self-spawn pattern for background worker execution
-
-### Bug Fixes
-- Resolve critical error handling issues in worker lifecycle
-- Handle Windows/Unix kill errors in orphaned process cleanup
-- Validate spawn pid before writing PID file
-- Handle process exit in waitForProcessesExit filter
-- Use readiness endpoint for health checks instead of port check
-- Add missing OpenRouter and Gemini settings to settingKeys array
-
-### Other Changes
-- Enhance error handling and validation in agents and routes
-- Delete obsolete process management files (ProcessManager, worker-wrapper, worker-cli)
-- Update hooks.json to use worker-service.cjs CLI
-- Add comprehensive tests for hook constants and worker spawn functionality
-
-## [v8.2.1] - 2025-12-27
-
-## 🔧 Worker Lifecycle Hardening
-
-This patch release addresses critical bugs discovered during PR review of the self-spawn pattern introduced in 8.2.0. The worker daemon now handles edge cases robustly across both Unix and Windows platforms.
-
-### 🐛 Critical Bug Fixes
-
-#### Process Exit Detection Fixed
-The `waitForProcessesExit` function was crashing when processes exited during monitoring. The `process.kill(pid, 0)` call throws when a process no longer exists, which was not being caught. Now wrapped in try/catch to correctly identify exited processes.
-
-#### Spawn PID Validation
-The worker daemon now validates that `spawn()` actually returned a valid PID before writing to the PID file. Previously, spawn failures could leave invalid PID files that broke subsequent lifecycle operations.
-
-#### Cross-Platform Orphan Cleanup
-- **Unix**: Replaced single `kill` command with individual `process.kill()` calls wrapped in try/catch, so one already-exited process doesn't abort cleanup of remaining orphans
-- **Windows**: Wrapped `taskkill` calls in try/catch for the same reason
-
-#### Health Check Reliability
-Changed `waitForHealth` to use the `/api/readiness` endpoint (returns 503 until fully initialized) instead of just checking if the port is in use. Callers now wait for *actual* worker readiness, not just network availability.
-
-### 🔄 Refactoring
-
-#### Code Consolidation (-580 lines)
-Deleted obsolete process management infrastructure that was replaced by the self-spawn pattern:
-- `src/services/process/ProcessManager.ts` (433 lines) - PID management now in worker-service
-- `src/cli/worker-cli.ts` (81 lines) - CLI handling now in worker-service
-- `src/services/worker-wrapper.ts` (157 lines) - Replaced by `--daemon` flag
-
-#### Updated Hook Commands
-All hooks now use `worker-service.cjs` CLI directly instead of the deleted `worker-cli.js`.
-
-### ⏱️ Timeout Adjustments
-
-Increased timeouts throughout for compatibility with slow systems:
-
-| Component | Before | After |
-|-----------|--------|-------|
-| Default hook timeout | 120s | 300s |
-| Health check timeout | 1s | 30s |
-| Health check retries | 15 | 300 |
-| Context initialization | 30s | 300s |
-| MCP connection | 15s | 300s |
-| PowerShell commands | 5s | 60s |
-| Git commands | 30s | 300s |
-| NPM install | 120s | 600s |
-| Hook worker commands | 30s | 180s |
-
-### 🧪 Testing
-
-Added comprehensive test suites:
-- `tests/hook-constants.test.ts` - Validates timeout configurations
-- `tests/worker-spawn.test.ts` - Tests worker CLI and health endpoints
-
-### 🛡️ Additional Robustness
-
-- PID validation in restart command (matches start command behavior)
-- Try/catch around `forceKillProcess()` for graceful shutdown
-- Try/catch around `getChildProcesses()` for Windows failures
-- Improved logging for PID file operations and HTTP shutdown
-
----
-
-**Full Changelog**: https://github.com/thedotmack/claude-mem/compare/v8.2.0...v8.2.1
-
-## [v8.2.0] - 2025-12-26
-
-## 🚀 Gemini API as Alternative AI Provider
-
-This release introduces **Google Gemini API** as an alternative to the Claude Agent SDK for observation extraction. This gives users flexibility in choosing their AI backend while maintaining full feature parity.
-
-### ✨ New Features
-
-#### Gemini Provider Integration
-- **New `GeminiAgent`**: Complete implementation using Gemini's REST API for observation and summary extraction
-- **Provider selection**: Choose between Claude or Gemini directly in the Settings UI
-- **API key management**: Configure via UI or `GEMINI_API_KEY` environment variable
-- **Multi-turn conversations**: Full conversation history tracking for context-aware extraction
-
-#### Supported Gemini Models
-- `gemini-2.5-flash-preview-05-20` (default)
-- `gemini-2.5-pro-preview-05-06`
-- `gemini-2.0-flash`
-- `gemini-2.0-flash-lite`
-
-#### Rate Limiting
-- Built-in rate limiting for Gemini free tier (15 RPM) and paid tier (1000 RPM)
-- Configurable via `gemini_has_billing` setting in the UI
-
-#### Resilience Features
-- **Graceful fallback**: Automatically falls back to Claude SDK if Gemini is selected but no API key is configured
-- **Hot-swap providers**: Switch between Claude and Gemini without restarting the worker
-- **Empty response handling**: Messages properly marked as processed even when Gemini returns empty responses (prevents stuck queue states)
-- **Timestamp preservation**: Recovered backlog messages retain their original timestamps
-
-### 🎨 UI Improvements
-
-- **Spinning favicon**: Visual indicator during observation processing
-- **Provider status**: Clear indication of which AI provider is active
-
-### 📚 Documentation
-
-- New [Gemini Provider documentation](https://docs.claude-mem.ai/usage/gemini-provider) with setup guide and troubleshooting
-
-### ⚙️ New Settings
-
-| Setting | Values | Description |
-|---------|--------|-------------|
-| `CLAUDE_MEM_PROVIDER` | `claude` \| `gemini` | AI provider for observation extraction |
-| `CLAUDE_MEM_GEMINI_API_KEY` | string | Gemini API key |
-| `CLAUDE_MEM_GEMINI_MODEL` | see above | Gemini model to use |
-| `gemini_has_billing` | boolean | Enable higher rate limits for paid accounts |
-
----
-
-## 🙏 Contributor Shout-out
-
-Huge thanks to **Alexander Knigge** ([@AlexanderKnigge](https://x.com/AlexanderKnigge)) for contributing the Gemini provider implementation! This feature significantly expands claude-mem's flexibility and gives users more choice in their AI backend.
-
----
-
-**Full Changelog**: https://github.com/thedotmack/claude-mem/compare/v8.1.0...v8.2.0
-
-## [v8.1.0] - 2025-12-25
-
-## The 3-Month Battle Against Complexity
-
-**TL;DR:** For three months, Claude's instinct to add code instead of delete it caused the same bugs to recur. What should have been 5 lines of code became ~1000 lines, 11 useless methods, and 7+ failed "fixes." The timestamp corruption that finally broke things was just a symptom. The real achievement: **984 lines of code deleted.**
-
----
-
-## What Actually Happened
-
-Every Claude Code hook receives a session ID. That's all you need.
-
-But Claude built an entire redundant session management system on top:
-- An `sdk_sessions` table with status tracking, port assignment, and prompt counting
-- 11 methods in `SessionStore` to manage this artificial complexity
-- Auto-creation logic scattered across 3 locations
-- A cleanup hook that "completed" sessions at the end
-
-**Why?** Because it seemed "robust." Because "what if the session doesn't exist?" 
-
-But the edge cases didn't exist. Hooks ALWAYS provide session IDs. The "defensive" code was solving imaginary problems while creating real ones.
-
----
-
-## The Pattern of Failure
-
-Every time a bug appeared, Claude's instinct was to **ADD** more code:
-
-| Bug | What Claude Added | What Should Have Happened |
-|-----|------------------|--------------------------|
-| Race conditions | Auto-create fallbacks | Delete the auto-create logic |
-| Duplicate observations | Validation layers | Delete the code path allowing duplicates |
-| UNIQUE constraint violations | Try-catch with fallbacks | Use `INSERT OR IGNORE` (5 characters) |
-| Session not found | Silent auto-creation | **FAIL LOUDLY** (it's a hook bug) |
-
----
-
-## The 7+ Failed Attempts
-
-- **Nov 4**: "Always store session data regardless of pre-existence." Complexity planted.
-- **Nov 11**: `INSERT OR IGNORE` recognized. But complexity documented, not removed.
-- **Nov 21**: Duplicate observations bug. Fixed. Then broken again by endless mode.
-- **Dec 5**: "6 hours of work delivered zero value." User requests self-audit.
-- **Dec 20**: "Phase 2: Eliminated Race Conditions" — felt like progress. Complexity remained.
-- **Dec 24**: Finally, forced deletion.
-
-The user stated "hooks provide session IDs, no extra management needed" **seven times** across months. Claude didn't listen.
-
----
-
-## The Fix
-
-### Deleted (984 lines):
-- 11 `SessionStore` methods: `incrementPromptCounter`, `getPromptCounter`, `setWorkerPort`, `getWorkerPort`, `markSessionCompleted`, `markSessionFailed`, `reactivateSession`, `findActiveSDKSession`, `findAnySDKSession`, `updateSDKSessionId`
-- Auto-create logic from `storeObservation` and `storeSummary`
-- The entire cleanup hook (was aborting SDK agent and causing data loss)
-- 117 lines from `worker-utils.ts`
-
-### What remains (~10 lines):
-```javascript
-createSDKSession(sessionId) {
-  db.run('INSERT OR IGNORE INTO sdk_sessions (...) VALUES (...)');
-  return db.query('SELECT id FROM sdk_sessions WHERE ...').get(sessionId);
-}
-```
-
-**That's it.**
-
----
-
-## Behavior Change
-
-- **Before:** Missing session? Auto-create silently. Bug hidden.
-- **After:** Missing session? Storage fails. Bug visible immediately.
-
----
-
-## New Tools
-
-Since we're now explicit about recovery instead of silently papering over problems:
-
-- `GET /api/pending-queue` - See what's stuck
-- `POST /api/pending-queue/process` - Manually trigger recovery  
-- `npm run queue:check` / `npm run queue:process` - CLI equivalents
-
----
-
-## Dependencies
-- Upgraded `@anthropic-ai/claude-agent-sdk` from `^0.1.67` to `^0.1.76`
-
----
-
-**PR #437:** https://github.com/thedotmack/claude-mem/pull/437
-
-*The evidence: Observations #3646, #6738, #7598, #12860, #12866, #13046, #15259, #20995, #21055, #30524, #31080, #32114, #32116, #32125, #32126, #32127, #32146, #32324—the complete record of a 3-month battle.*
-
-## [v8.0.6] - 2025-12-24
-
-## Bug Fixes
-
-- Add error handlers to Chroma sync operations to prevent worker crashes on timeout (#428)
-
-This patch release improves stability by adding proper error handling to Chroma vector database sync operations, preventing worker crashes when sync operations timeout.
-
-## [v8.0.5] - 2025-12-24
-
-## Bug Fixes
-
-- **Context Loading**: Fixed observation filtering for non-code modes, ensuring observations are properly retrieved across all mode types
-
-## Technical Details
-
-Refactored context loading logic to differentiate between code and non-code modes, resolving issues where mode-specific observations were filtered by stale settings.
-
-## [v8.0.4] - 2025-12-23
-
-## Changes
-
-- Changed worker start script
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-
-## [v8.0.3] - 2025-12-23
-
-Fix critical worker crashes on startup (v8.0.2 regression)
-
-## [v8.0.2] - 2025-12-23
-
-New "chill" remix of code mode for users who want fewer, more selective observations.
-
-## Features
-
-- **code--chill mode**: A behavioral variant that produces fewer observations
-  - Only records things "painful to rediscover" - shipped features, architectural decisions, non-obvious gotchas
-  - Skips routine work, straightforward implementations, and obvious changes
-  - Philosophy: "When in doubt, skip it"
-
-## Documentation
-
-- Updated modes.mdx with all 28 language modes (was 10)
-- Added Code Mode Variants section documenting chill mode
-
-## Usage
-
-Set in ~/.claude-mem/settings.json:
-```json
-{
-  "CLAUDE_MEM_MODE": "code--chill"
-}
-```
-
-## [v8.0.1] - 2025-12-23
-
-## 🎨 UI Improvements
-
-- **Header Redesign**: Moved documentation and X (Twitter) links from settings modal to main header for better accessibility
-- **Removed Product Hunt Badge**: Cleaned up header layout by removing the Product Hunt badge
-- **Icon Reorganization**: Reordered header icons for improved UX flow (Docs → X → Discord → GitHub)
-
----
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-
-## [v8.0.0] - 2025-12-23
-
-## 🌍 Major Features
-
-### **Mode System**: Context-aware observation capture tailored to different workflows
-- **Code Development mode** (default): Tracks bugfixes, features, refactors, and more
-- **Email Investigation mode**: Optimized for email analysis workflows
-- Extensible architecture for custom domains
-
-### **28 Language Support**: Full multilingual memory
-- Arabic, Bengali, Chinese, Czech, Danish, Dutch, Finnish, French, German, Greek
-- Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Norwegian, Polish
-- Portuguese (Brazilian), Romanian, Russian, Spanish, Swedish, Thai, Turkish
-- Ukrainian, Vietnamese
-- All observations, summaries, and narratives generated in your chosen language
-
-### **Inheritance Architecture**: Language modes inherit from base modes
-- Consistent observation types across languages
-- Locale-specific output while maintaining structural integrity
-- JSON-based configuration for easy customization
-
-## 🔧 Technical Improvements
-
-- **ModeManager**: Centralized mode loading and configuration validation
-- **Dynamic Prompts**: SDK prompts now adapt based on active mode
-- **Mode-Specific Icons**: Observation types display contextual icons/emojis per mode
-- **Fail-Fast Error Handling**: Complete removal of silent failures across all layers
-
-## 📚 Documentation
-
-- New docs/public/modes.mdx documenting the mode system
-- 28 translated README files for multilingual community support
-- Updated configuration guide for mode selection
-
-## 🔨 Breaking Changes
-
-- **None** - Mode system is fully backward compatible
-- Default mode is 'code' (existing behavior)
-- Settings: New `CLAUDE_MEM_MODE` option (defaults to 'code')
-
----
-
-**Full Changelog**: https://github.com/thedotmack/claude-mem/compare/v7.4.5...v8.0.0
-**View PR**: https://github.com/thedotmack/claude-mem/pull/412
-
-## [v7.4.5] - 2025-12-21
-
-## Bug Fixes
-
-- Fix missing `formatDateTime` import in SearchManager that broke `get_context_timeline` mem-search function
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-
-## [v7.4.4] - 2025-12-21
-
-## What's Changed
-
-* Code quality: comprehensive nonsense audit cleanup (20 issues) by @thedotmack in #400
-
-**Full Changelog**: https://github.com/thedotmack/claude-mem/compare/v7.4.3...v7.4.4
-
-## [v7.4.3] - 2025-12-20
-
-Added Discord notification script for release announcements.
-
-### Added
-- `scripts/discord-release-notify.js` - Posts formatted release notifications to Discord using webhook URL from `.env`
-- `npm run discord:notify <version>` - New npm script to trigger Discord notifications
-- Updated version-bump skill workflow to include Discord notification step
-
-### Configuration
-Set `DISCORD_UPDATES_WEBHOOK` in your `.env` file to enable release notifications.
-
----
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-
-## [v7.4.2] - 2025-12-20
-
-Patch release v7.4.2
-
-## Changes
-- Refactored worker commands from npm scripts to claude-mem CLI
-- Added path alias script
-- Fixed Windows worker stop/restart reliability (#395)
-- Simplified build commands section in CLAUDE.md
-

PLAN.md

@@ -1,154 +0,0 @@
-# Plan: Address PR #856 Review Feedback
-
-## Summary of Review Feedback
-
-Multiple reviewers identified the same core issues:
-
-1. **Race Condition in Idle Detection** (Medium-High Priority)
-   - When timeout fires at 3:00 but last message was at 2:59, `idleDuration` is 1 second, check fails
-   - Need to either remove redundant check or reset `lastActivityTime` on timeout
-
-2. **Missing Test Coverage** (High Priority)
-   - No tests for SessionQueueProcessor timeout logic
-   - Critical fix for high-impact bug (79 processes, 13.4GB swap)
-
-3. **Minor: Optional Chaining** (Low Priority)
-   - Use `onIdleTimeout?.()` instead of `if (onIdleTimeout) { onIdleTimeout() }`
-
-4. **Minor: Logging Enhancement** (Low Priority)
-   - Add timeout threshold to log message for debugging
-
----
-
-## Phase 0: Documentation Discovery (COMPLETE)
-
-### Sources Consulted
-- PR #856 comments from claude, greptile-apps reviewers
-- `src/services/queue/SessionQueueProcessor.ts` (current implementation)
-
-### Allowed APIs
-- `waitForMessage(signal, timeoutMs)` → Promise<boolean>
-- `logger.info('SESSION', ...)` for logging
-
-### The Fix Strategy
-
-The reviewers suggest two options:
-
-**Option A**: Remove redundant check since `waitForMessage` enforces timeout
-```typescript
-if (!receivedMessage && !signal.aborted) {
-  // Timeout occurred - exit gracefully
-  const idleDuration = Date.now() - lastActivityTime;
-  logger.info('SESSION', 'Exiting queue iterator due to idle timeout', { ... });
-  onIdleTimeout?.();
-  return;
-}
-```
-
-**Option B**: Reset `lastActivityTime` on timeout to handle edge cases
-```typescript
-if (!receivedMessage && !signal.aborted) {
-  const idleDuration = Date.now() - lastActivityTime;
-  if (idleDuration >= IDLE_TIMEOUT_MS) {
-    logger.info('SESSION', 'Exiting...', { ... });
-    onIdleTimeout?.();
-    return;
-  }
-  // CRITICAL: Reset timer since we know queue is empty now
-  lastActivityTime = Date.now();
-}
-```
-
-**Decision**: Use Option B - it's defensive and handles spurious wakeups correctly.
-
----
-
-## Phase 1: Fix Race Condition in SessionQueueProcessor
-
-### What to Implement
-Fix the idle timeout logic to reset `lastActivityTime` when timeout occurs but duration check fails.
-
-### Tasks
-1. In `createIterator()` at lines 50-62, add `lastActivityTime = Date.now()` after the duration check fails
-2. Use optional chaining for `onIdleTimeout?.()`
-3. Add timeout threshold to log message
-
-### Pattern to Follow
-```typescript
-if (!receivedMessage && !signal.aborted) {
-  const idleDuration = Date.now() - lastActivityTime;
-  if (idleDuration >= IDLE_TIMEOUT_MS) {
-    logger.info('SESSION', 'Idle timeout reached, triggering abort to kill subprocess', {
-      sessionDbId,
-      idleDurationMs: idleDuration,
-      thresholdMs: IDLE_TIMEOUT_MS
-    });
-    onIdleTimeout?.();
-    return;
-  }
-  // Reset timer on spurious wakeup - queue is empty but duration check failed
-  lastActivityTime = Date.now();
-}
-```
-
-### Verification
-```bash
-npm run build
-grep -A10 "idleDuration >= IDLE_TIMEOUT_MS" src/services/queue/SessionQueueProcessor.ts
-```
-
----
-
-## Phase 2: Add Unit Tests for SessionQueueProcessor
-
-### What to Implement
-Create test file covering the idle timeout behavior.
-
-### Test Cases Required
-1. Iterator exits after idle timeout when no messages arrive
-2. `onIdleTimeout` callback is invoked on timeout
-3. Message arrival resets the idle timer
-4. Abort signal takes precedence over timeout
-5. Event listener cleanup happens correctly
-
-### Location
-`tests/services/queue/SessionQueueProcessor.test.ts`
-
-### Verification
-```bash
-npm run test -- SessionQueueProcessor
-```
-
----
-
-## Phase 3: Build and Verify
-
-### Tasks
-1. Run `npm run build` - verify no TypeScript errors
-2. Run tests to ensure timeout behavior works
-3. Commit changes to fix/observer-idle-timeout branch
-4. Push to update PR #856
-
-### Verification
-```bash
-npm run build
-npm run test
-git diff --stat
-```
-
----
-
-## Phase 4: Update PR Description
-
-### Tasks
-1. Update test plan checkboxes in PR description
-2. Add note about race condition fix
-
----
-
-## Summary of Changes
-
-| File | Change |
-|------|--------|
-| `src/services/queue/SessionQueueProcessor.ts` | Fix race condition, optional chaining, enhanced logging |
-| `tests/services/queue/SessionQueueProcessor.test.ts` | New test file for timeout behavior |

README.md

@@ -22,12 +22,14 @@
 
 <p align="center">
   <a href="docs/i18n/README.zh.md">🇨🇳 中文</a> •
+  <a href="docs/i18n/README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="docs/i18n/README.ja.md">🇯🇵 日本語</a> •
+  <a href="docs/i18n/README.pt.md">🇵🇹 Português</a> •
   <a href="docs/i18n/README.pt-br.md">🇧🇷 Português</a> •
   <a href="docs/i18n/README.ko.md">🇰🇷 한국어</a> •
   <a href="docs/i18n/README.es.md">🇪🇸 Español</a> •
   <a href="docs/i18n/README.de.md">🇩🇪 Deutsch</a> •
-  <a href="docs/i18n/README.fr.md">🇫🇷 Français</a>
+  <a href="docs/i18n/README.fr.md">🇫🇷 Français</a> •
   <a href="docs/i18n/README.he.md">🇮🇱 עברית</a> •
   <a href="docs/i18n/README.ar.md">🇸🇦 العربية</a> •
   <a href="docs/i18n/README.ru.md">🇷🇺 Русский</a> •
@@ -37,10 +39,12 @@
   <a href="docs/i18n/README.tr.md">🇹🇷 Türkçe</a> •
   <a href="docs/i18n/README.uk.md">🇺🇦 Українська</a> •
   <a href="docs/i18n/README.vi.md">🇻🇳 Tiếng Việt</a> •
+  <a href="docs/i18n/README.tl.md">🇵🇭 Tagalog</a> •
   <a href="docs/i18n/README.id.md">🇮🇩 Indonesia</a> •
   <a href="docs/i18n/README.th.md">🇹🇭 ไทย</a> •
   <a href="docs/i18n/README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="docs/i18n/README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="docs/i18n/README.ur.md">🇵🇰 اردو</a> •
   <a href="docs/i18n/README.ro.md">🇷🇴 Română</a> •
   <a href="docs/i18n/README.sv.md">🇸🇪 Svenska</a> •
   <a href="docs/i18n/README.it.md">🇮🇹 Italiano</a> •
@@ -109,13 +113,25 @@
 Start a new Claude Code session in the terminal and enter the following commands:
 
 ```
-> /plugin marketplace add thedotmack/claude-mem
+/plugin marketplace add thedotmack/claude-mem
 
-> /plugin install claude-mem
+/plugin install claude-mem
 ```
 
 Restart Claude Code. Context from previous sessions will automatically appear in new sessions.
 
+> **Note:** Claude-Mem is also published on npm, but `npm install -g claude-mem` installs the **SDK/library only** — it does not register the plugin hooks or set up the worker service. To use Claude-Mem as a plugin, always install via the `/plugin` commands above.
+
+### 🦞 OpenClaw Gateway
+
+Install claude-mem as a persistent memory plugin on [OpenClaw](https://openclaw.ai) gateways with a single command:
+
+```bash
+curl -fsSL https://install.cmem.ai/openclaw.sh | bash
+```
+
+The installer handles dependencies, plugin setup, AI provider configuration, worker startup, and optional real-time observation feeds to Telegram, Discord, Slack, and more. See the [OpenClaw Integration Guide](https://docs.claude-mem.ai/openclaw-integration) for details.
+
 **Key Features:**
 
 - 🧠 **Persistent Memory** - Context survives across sessions
@@ -133,7 +149,7 @@ Restart Claude Code. Context from previous sessions will automatically appear in
 
 ## Documentation
 
-📚 **[View Full Documentation](docs/)** - Browse markdown docs on GitHub
+📚 **[View Full Documentation](https://docs.claude-mem.ai/)** - Browse on official website
 
 ### Getting Started
 
@@ -182,7 +198,7 @@ See [Architecture Overview](https://docs.claude-mem.ai/architecture/overview) fo
 
 ## MCP Search Tools
 
-Claude-Mem provides intelligent memory search through **4 MCP tools** following a token-efficient **3-layer workflow pattern**:
+Claude-Mem provides intelligent memory search through **5 MCP tools** following a token-efficient **3-layer workflow pattern**:
 
 **The 3-Layer Workflow:**
 
@@ -195,6 +211,7 @@ Claude-Mem provides intelligent memory search through **4 MCP tools** following
 - Start with `search` to get an index of results
 - Use `timeline` to see what was happening around specific observations
 - Use `get_observations` to fetch full details for relevant IDs
+- Use `save_memory` to manually store important information
 - **~10x token savings** by filtering before fetching details
 
 **Available MCP Tools:**
@@ -202,7 +219,8 @@ Claude-Mem provides intelligent memory search through **4 MCP tools** following
 1. **`search`** - Search memory index with full-text queries, filters by type/date/project
 2. **`timeline`** - Get chronological context around a specific observation or query
 3. **`get_observations`** - Fetch full observation details by IDs (always batch multiple IDs)
-4. **`__IMPORTANT`** - Workflow documentation (always visible to Claude)
+4. **`save_memory`** - Manually save a memory/observation for semantic search
+5. **`__IMPORTANT`** - Workflow documentation (always visible to Claude)
 
 **Example Usage:**
 
@@ -214,6 +232,9 @@ search(query="authentication bug", type="bugfix", limit=10)
 
 // Step 3: Fetch full details
 get_observations(ids=[123, 456])
+
+// Save important information manually
+save_memory(text="API requires auth header X-API-Key", title="API Auth")
 ```
 
 See [Search Tools Guide](https://docs.claude-mem.ai/usage/search-tools) for detailed examples.
@@ -236,6 +257,17 @@ See **[Beta Features Documentation](https://docs.claude-mem.ai/beta-features)**
 - **uv**: Python package manager for vector search (auto-installed if missing)
 - **SQLite 3**: For persistent storage (bundled)
 
+---
+### Windows Setup Notes
+
+If you see an error like:
+
+```powershell
+npm : The term 'npm' is not recognized as the name of a cmdlet
+```
+
+Make sure Node.js and npm are installed and added to your PATH. Download the latest Node.js installer from https://nodejs.org and restart your terminal after installation.
+
 ---
 
 ## Configuration

docs/bug-fixes/windows-spaces-issue.md

@@ -0,0 +1,98 @@
+---
+Title: Bug: SDK Agent fails on Windows when username contains spaces
+---
+
+## Bug Report
+
+**Summary:** Claude SDK Agent fails to start on Windows when the user's path contains spaces (e.g., `C:\Users\Anderson Wang\`), causing PostToolUse hooks to hang indefinitely.
+
+**Severity:** High - Core functionality broken
+
+**Affected Platform:** Windows only
+
+---
+
+## Symptoms
+
+PostToolUse hook displays `(1/2 done)` indefinitely. Worker logs show:
+
+```
+ERROR [SESSION] Generator failed {provider=claude, error=Claude Code process exited with code 1}
+ERROR [SESSION] Generator exited unexpectedly
+```
+
+---
+
+## Root Cause
+
+Two issues in the Windows code path:
+
+1. **`SDKAgent.ts`** - Returns full auto-detected path with spaces:
+   ```
+   C:\Users\Anderson Wang\AppData\Roaming\npm\claude.cmd
+   ```
+
+2. **`ProcessRegistry.ts`** - Node.js `spawn()` cannot directly execute `.cmd` files when the path contains spaces
+
+---
+
+## Proposed Fix
+
+### File 1: `src/services/worker/SDKAgent.ts`
+
+On Windows, prefer `claude.cmd` via PATH instead of full auto-detected path:
+
+```typescript
+// On Windows, prefer "claude.cmd" (via PATH) to avoid spawn issues with spaces in paths
+if (process.platform === 'win32') {
+  try {
+    execSync('where claude.cmd', { encoding: 'utf8', windowsHide: true, stdio: ['ignore', 'pipe', 'ignore'] });
+    return 'claude.cmd'; // Let Windows resolve via PATHEXT
+  } catch {
+    // Fall through to generic error
+  }
+}
+```
+
+### File 2: `src/services/worker/ProcessRegistry.ts`
+
+Use `cmd.exe /d /c` wrapper for .cmd files on Windows:
+
+```typescript
+const useCmdWrapper = process.platform === 'win32' && spawnOptions.command.endsWith('.cmd');
+
+if (useCmdWrapper) {
+  child = spawn('cmd.exe', ['/d', '/c', spawnOptions.command, ...spawnOptions.args], {
+    cwd: spawnOptions.cwd,
+    env: spawnOptions.env,
+    stdio: ['pipe', 'pipe', 'pipe'],
+    signal: spawnOptions.signal,
+    windowsHide: true
+  });
+}
+```
+
+---
+
+## Why This Works
+
+- **PATHEXT Resolution:** Windows searches PATH and tries each extension in PATHEXT automatically
+- **cmd.exe wrapper:** Properly handles paths with spaces and argument passing
+- **Avoids shell parsing:** Using direct arguments instead of `shell: true` prevents empty string misparsing
+
+---
+
+## Testing
+
+Verified on Windows 11 with username containing spaces:
+- PostToolUse hook completes successfully
+- Observations are stored to database
+- No more "process exited with code 1" errors
+
+---
+
+## Additional Notes
+
+- Maintains backward compatibility with `CLAUDE_CODE_PATH` setting
+- No impact on non-Windows platforms
+- Related to Issue #733 (credential isolation) - separate fix

docs/i18n/README.ar.md

@@ -13,6 +13,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -32,6 +33,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -129,7 +131,7 @@ Claude-Mem هو نظام متطور مصمم لضغط وحفظ الذاكرة ل
 
 ## المستندات 
 
-📚 **[عرض التوثيق الكامل](docs/)** - تصفح مستندات markdown على GitHub
+📚 **[عرض التوثيق الكامل](https://docs.claude-mem.ai/)** - تصفح على الموقع الرسمي
 
 ### البدء
 

docs/i18n/README.bn.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Claude Code পুনরায় চালু করুন। পূর্ব
 
 ## ডকুমেন্টেশন
 
-📚 **[সম্পূর্ণ ডকুমেন্টেশন দেখুন](docs/)** - GitHub-এ markdown ডক্স ব্রাউজ করুন
+📚 **[সম্পূর্ণ ডকুমেন্টেশন দেখুন](https://docs.claude-mem.ai/)** - অফিসিয়াল ওয়েবসাইটে ব্রাউজ করুন
 
 ### শুরু করা
 

docs/i18n/README.cs.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Restartujte Claude Code. Kontext z předchozích sezení se automaticky objeví
 
 ## Dokumentace
 
-📚 **[Zobrazit kompletní dokumentaci](docs/)** - Procházejte dokumentaci v markdown na GitHubu
+📚 **[Zobrazit kompletní dokumentaci](https://docs.claude-mem.ai/)** - Procházet na oficiálních stránkách
 
 ### Začínáme
 

docs/i18n/README.da.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Genstart Claude Code. Kontekst fra tidligere sessioner vil automatisk vises i ny
 
 ## Dokumentation
 
-📚 **[Se Fuld Dokumentation](docs/)** - Gennemse markdown-dokumenter på GitHub
+📚 **[Se Fuld Dokumentation](https://docs.claude-mem.ai/)** - Gennemse på den officielle hjemmeside
 
 ### Kom Godt I Gang
 

docs/i18n/README.de.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Starten Sie Claude Code neu. Kontext aus vorherigen Sitzungen wird automatisch i
 
 ## Dokumentation
 
-📚 **[Vollständige Dokumentation anzeigen](docs/)** - Markdown-Dokumentation auf GitHub durchsuchen
+📚 **[Vollständige Dokumentation anzeigen](https://docs.claude-mem.ai/)** - Auf der offiziellen Website durchsuchen
 
 ### Erste Schritte
 

docs/i18n/README.el.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@
 
 ## Τεκμηρίωση
 
-📚 **[Προβολή Πλήρους Τεκμηρίωσης](docs/)** - Περιήγηση στα markdown έγγραφα στο GitHub
+📚 **[Προβολή Πλήρους Τεκμηρίωσης](https://docs.claude-mem.ai/)** - Περιήγηση στον επίσημο ιστότοπο
 
 ### Ξεκινώντας
 

docs/i18n/README.es.md

@@ -16,6 +16,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -35,6 +36,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -127,7 +129,7 @@ Reinicia Claude Code. El contexto de sesiones anteriores aparecerá automáticam
 
 ## Documentación
 
-📚 **[Ver Documentación Completa](docs/)** - Explora documentos markdown en GitHub
+📚 **[Ver Documentación Completa](https://docs.claude-mem.ai/)** - Navegar en el sitio web oficial
 
 ### Primeros Pasos
 

docs/i18n/README.fi.md

@@ -14,6 +14,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -33,6 +34,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -125,7 +127,7 @@ Käynnistä Claude Code uudelleen. Aiempien istuntojen konteksti ilmestyy automa
 
 ## Dokumentaatio
 
-📚 **[Näytä täydellinen dokumentaatio](docs/)** - Selaa markdown-dokumentteja GitHubissa
+📚 **[Näytä täydellinen dokumentaatio](https://docs.claude-mem.ai/)** - Selaa virallisella verkkosivustolla
 
 ### Aloitus
 

docs/i18n/README.fr.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Redémarrez Claude Code. Le contexte des sessions précédentes apparaîtra auto
 
 ## Documentation
 
-📚 **[Voir la documentation complète](docs/)** - Parcourez la documentation markdown sur GitHub
+📚 **[Voir la documentation complète](https://docs.claude-mem.ai/)** - Parcourir sur le site officiel
 
 ### Pour commencer
 

docs/i18n/README.he.md

@@ -14,6 +14,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -33,6 +34,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -125,7 +127,7 @@
 
 ## תיעוד
 
-📚 **[צפה בתיעוד המלא](docs/)** - עיין במסמכי markdown ב-GitHub
+📚 **[צפה בתיעוד המלא](https://docs.claude-mem.ai/)** - דפדף באתר הרשמי
 
 ### תחילת העבודה
 

docs/i18n/README.hi.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Claude Code को पुनः आरंभ करें। पिछले स
 
 ## दस्तावेज़ीकरण
 
-📚 **[पूर्ण दस्तावेज़ीकरण देखें](docs/)** - GitHub पर markdown दस्तावेज़ ब्राउज़ करें
+📚 **[पूर्ण दस्तावेज़ीकरण देखें](https://docs.claude-mem.ai/)** - आधिकारिक वेबसाइट पर ब्राउज़ करें
 
 ### शुरुआत करना
 

docs/i18n/README.hu.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Indítsa újra a Claude Code-ot. A korábbi munkamenetek kontextusa automatikusa
 
 ## Dokumentáció
 
-📚 **[Teljes dokumentáció megtekintése](docs/)** - Markdown dokumentumok böngészése GitHub-on
+📚 **[Teljes dokumentáció megtekintése](https://docs.claude-mem.ai/)** - Böngészés a hivatalos weboldalon
 
 ### Első lépések
 

docs/i18n/README.id.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Restart Claude Code. Konteks dari sesi sebelumnya akan secara otomatis muncul di
 
 ## Dokumentasi
 
-📚 **[Lihat Dokumentasi Lengkap](docs/)** - Telusuri dokumen markdown di GitHub
+📚 **[Lihat Dokumentasi Lengkap](https://docs.claude-mem.ai/)** - Jelajahi di situs web resmi
 
 ### Memulai
 

docs/i18n/README.it.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Riavvia Claude Code. Il contesto delle sessioni precedenti apparirà automaticam
 
 ## Documentazione
 
-📚 **[Visualizza Documentazione Completa](docs/)** - Sfoglia i documenti markdown su GitHub
+📚 **[Visualizza Documentazione Completa](https://docs.claude-mem.ai/)** - Sfoglia sul sito ufficiale
 
 ### Per Iniziare
 

docs/i18n/README.ja.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Claude Codeを再起動します。以前のセッションからのコンテキ
 
 ## ドキュメント
 
-📚 **[完全なドキュメントを見る](docs/)** - GitHubでマークダウンドキュメントを閲覧
+📚 **[完全なドキュメントを見る](https://docs.claude-mem.ai/)** - 公式ウェブサイトで閲覧
 
 ### はじめに
 
@@ -212,7 +214,7 @@ Claude-Memは、過去の作業について尋ねると自動的に呼び出さ
 
 Claude-Memは、**Endless Mode**(拡張セッション用の生体模倣メモリアーキテクチャ)などの実験的機能を備えた**ベータチャネル**を提供します。http://localhost:37777 → SettingsのWebビューアUIから安定版とベータ版を切り替えます。
 
-Endless Modeと試用方法の詳細については、**[ベータ機能ドキュメント](https://docs.claude-mem.ai/beta-features)**を参照してください。
+Endless Modeと試用方法の詳細については、**[ベータ機能ドキュメント](https://docs.claude-mem.ai/beta-features)** を参照してください。
 
 ---
 
@@ -230,13 +232,13 @@ Endless Modeと試用方法の詳細については、**[ベータ機能ドキ
 
 設定は`~/.claude-mem/settings.json`で管理されます(初回実行時にデフォルト値で自動作成)。AIモデル、ワーカーポート、データディレクトリ、ログレベル、コンテキスト注入設定を構成します。
 
-利用可能なすべての設定と例については、**[設定ガイド](https://docs.claude-mem.ai/configuration)**を参照してください。
+利用可能なすべての設定と例については、**[設定ガイド](https://docs.claude-mem.ai/configuration)** を参照してください。
 
 ---
 
 ## 開発
 
-ビルド手順、テスト、コントリビューションワークフローについては、**[開発ガイド](https://docs.claude-mem.ai/development)**を参照してください。
+ビルド手順、テスト、コントリビューションワークフローについては、**[開発ガイド](https://docs.claude-mem.ai/development)** を参照してください。
 
 ---
 
@@ -244,7 +246,7 @@ Endless Modeと試用方法の詳細については、**[ベータ機能ドキ
 
 問題が発生した場合は、Claudeに問題を説明すると、troubleshootスキルが自動的に診断して修正を提供します。
 
-よくある問題と解決策については、**[トラブルシューティングガイド](https://docs.claude-mem.ai/troubleshooting)**を参照してください。
+よくある問題と解決策については、**[トラブルシューティングガイド](https://docs.claude-mem.ai/troubleshooting)** を参照してください。
 
 ---
 
@@ -286,7 +288,7 @@ Copyright (C) 2025 Alex Newman (@thedotmack). All rights reserved.
 - 派生作品もAGPL-3.0の下でライセンスする必要があります
 - このソフトウェアには保証がありません
 
-**Ragtimeに関する注意**: `ragtime/`ディレクトリは**PolyForm Noncommercial License 1.0.0**の下で個別にライセンスされています。詳細は[ragtime/LICENSE](ragtime/LICENSE)を参照してください。
+**Ragtimeに関する注意**: `ragtime/`ディレクトリは **PolyForm Noncommercial License 1.0.0** の下で個別にライセンスされています。詳細は[ragtime/LICENSE](ragtime/LICENSE)を参照してください。
 
 ---
 
@@ -299,4 +301,4 @@ Copyright (C) 2025 Alex Newman (@thedotmack). All rights reserved.
 
 ---
 
-**Claude Agent SDKで構築** | **Claude Codeで動作** | **TypeScriptで作成**
+**Claude Agent SDKで構築** | **Claude Codeで動作** | **TypeScriptで作成**

docs/i18n/README.ko.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -114,19 +116,19 @@ Claude Code를 재시작하세요. 이전 세션의 컨텍스트가 자동으로
 - 🧠 **지속적인 메모리** - 세션 간 컨텍스트 유지
 - 📊 **점진적 공개** - 토큰 비용 가시성을 갖춘 계층화된 메모리 검색
 - 🔍 **스킬 기반 검색** - mem-search 스킬로 프로젝트 기록 쿼리
-- 🖥️ **웹 뷰어 UI** - http://localhost:37777에서 실시간 메모리 스트림 확인
+- 🖥️ **웹 뷰어 UI** - http://localhost:37777 에서 실시간 메모리 스트림 확인
 - 💻 **Claude Desktop 스킬** - Claude Desktop 대화에서 메모리 검색
 - 🔒 **개인정보 제어** - `<private>` 태그를 사용하여 민감한 콘텐츠를 저장소에서 제외
 - ⚙️ **컨텍스트 설정** - 주입되는 컨텍스트에 대한 세밀한 제어
 - 🤖 **자동 작동** - 수동 개입 불필요
-- 🔗 **인용** - ID로 과거 관찰 참조 (http://localhost:37777/api/observation/{id}를 통해 액세스하거나 http://localhost:37777의 웹 뷰어에서 모두 보기)
+- 🔗 **인용** - ID로 과거 관찰 참조 (http://localhost:37777/api/observation/{id} 를 통해 액세스하거나 http://localhost:37777 의 웹 뷰어에서 모두 보기)
 - 🧪 **베타 채널** - 버전 전환을 통해 Endless Mode와 같은 실험적 기능 사용
 
 ---
 
 ## 문서
 
-📚 **[전체 문서 보기](docs/)** - GitHub에서 마크다운 문서 탐색
+📚 **[전체 문서 보기](https://docs.claude-mem.ai/)** - 공식 웹사이트에서 찾아보기
 
 ### 시작하기
 

docs/i18n/README.nl.md

@@ -14,6 +14,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -33,6 +34,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -125,7 +127,7 @@ Herstart Claude Code. Context van eerdere sessies verschijnt automatisch in nieu
 
 ## Documentatie
 
-📚 **[Bekijk Volledige Documentatie](docs/)** - Blader door markdown documenten op GitHub
+📚 **[Bekijk Volledige Documentatie](https://docs.claude-mem.ai/)** - Bladeren op de officiële website
 
 ### Aan de Slag
 

docs/i18n/README.no.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Start Claude Code på nytt. Kontekst fra tidligere økter vil automatisk vises i
 
 ## Dokumentasjon
 
-📚 **[Se Full Dokumentasjon](docs/)** - Bla gjennom markdown-dokumenter på GitHub
+📚 **[Se Full Dokumentasjon](https://docs.claude-mem.ai/)** - Bla gjennom på det offisielle nettstedet
 
 ### Komme I Gang
 

docs/i18n/README.pl.md

@@ -14,6 +14,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -33,6 +34,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -125,7 +127,7 @@ Uruchom ponownie Claude Code. Kontekst z poprzednich sesji automatycznie pojawi
 
 ## Dokumentacja
 
-📚 **[Wyświetl Pełną Dokumentację](docs/)** - Przeglądaj dokumentację markdown na GitHub
+📚 **[Wyświetl Pełną Dokumentację](https://docs.claude-mem.ai/)** - Przeglądaj na oficjalnej stronie
 
 ### Pierwsze Kroki
 

docs/i18n/README.pt-br.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Reinicie o Claude Code. O contexto de sessões anteriores aparecerá automaticam
 
 ## Documentação
 
-📚 **[Ver Documentação Completa](docs/)** - Navegue pelos documentos markdown no GitHub
+📚 **[Ver Documentação Completa](https://docs.claude-mem.ai/)** - Navegar no site oficial
 
 ### Começando
 

docs/i18n/README.ro.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Reporniți Claude Code. Contextul din sesiunile anterioare va apărea automat î
 
 ## Documentație
 
-📚 **[Vizualizați Documentația Completă](docs/)** - Răsfoiți documentele markdown pe GitHub
+📚 **[Vizualizați Documentația Completă](https://docs.claude-mem.ai/)** - Răsfoiți pe site-ul oficial
 
 ### Introducere
 

docs/i18n/README.ru.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@
 
 ## Документация
 
-📚 **[Просмотреть полную документацию](docs/)** - Просмотр markdown-документов на GitHub
+📚 **[Просмотреть полную документацию](https://docs.claude-mem.ai/)** - Просмотр на официальном сайте
 
 ### Начало работы
 

docs/i18n/README.sv.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Starta om Claude Code. Kontext från tidigare sessioner kommer automatiskt att v
 
 ## Dokumentation
 
-📚 **[Visa fullständig dokumentation](docs/)** - Bläddra bland markdown-dokument på GitHub
+📚 **[Visa fullständig dokumentation](https://docs.claude-mem.ai/)** - Bläddra på den officiella webbplatsen
 
 ### Komma igång
 

docs/i18n/README.th.md

@@ -14,6 +14,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -33,6 +34,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -125,7 +127,7 @@
 
 ## เอกสาร
 
-📚 **[ดูเอกสารฉบับเต็ม](docs/)** - เรียกดูเอกสาร markdown บน GitHub
+📚 **[ดูเอกสารฉบับเต็ม](https://docs.claude-mem.ai/)** - เรียกดูบนเว็บไซต์อย่างเป็นทางการ
 
 ### เริ่มต้นใช้งาน
 

docs/i18n/README.tl.md

@@ -0,0 +1,328 @@
+🌐 Ito ay isang awtomatikong pagsasalin. Malugod na tinatanggap ang mga pagwawasto mula sa komunidad!
+
+---
+<h1 align="center">
+  <br>
+  <a href="https://github.com/thedotmack/claude-mem">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-dark-mode.webp">
+      <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-light-mode.webp">
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-light-mode.webp" alt="Claude-Mem" width="400">
+    </picture>
+  </a>
+  <br>
+</h1>
+
+<p align="center">
+  <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
+  <a href="README.ja.md">🇯🇵 日本語</a> •
+  <a href="README.pt-br.md">🇧🇷 Português</a> •
+  <a href="README.ko.md">🇰🇷 한국어</a> •
+  <a href="README.es.md">🇪🇸 Español</a> •
+  <a href="README.de.md">🇩🇪 Deutsch</a> •
+  <a href="README.fr.md">🇫🇷 Français</a> •
+  <a href="README.he.md">🇮🇱 עברית</a> •
+  <a href="README.ar.md">🇸🇦 العربية</a> •
+  <a href="README.ru.md">🇷🇺 Русский</a> •
+  <a href="README.pl.md">🇵🇱 Polski</a> •
+  <a href="README.cs.md">🇨🇿 Čeština</a> •
+  <a href="README.nl.md">🇳🇱 Nederlands</a> •
+  <a href="README.tr.md">🇹🇷 Türkçe</a> •
+  <a href="README.uk.md">🇺🇦 Українська</a> •
+  <a href="README.vi.md">🇻🇳 Tiếng Việt</a> •
+  <a href="README.tl.md">🇵🇭 Tagalog</a> •
+  <a href="README.id.md">🇮🇩 Indonesia</a> •
+  <a href="README.th.md">🇹🇭 ไทย</a> •
+  <a href="README.hi.md">🇮🇳 हिन्दी</a> •
+  <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
+  <a href="README.ro.md">🇷🇴 Română</a> •
+  <a href="README.sv.md">🇸🇪 Svenska</a> •
+  <a href="README.it.md">🇮🇹 Italiano</a> •
+  <a href="README.el.md">🇬🇷 Ελληνικά</a> •
+  <a href="README.hu.md">🇭🇺 Magyar</a> •
+  <a href="README.fi.md">🇫🇮 Suomi</a> •
+  <a href="README.da.md">🇩🇰 Dansk</a> •
+  <a href="README.no.md">🇳🇴 Norsk</a>
+</p>
+
+<h4 align="center">Sistema ng kompresyon ng persistent memory na ginawa para sa <a href="https://claude.com/claude-code" target="_blank">Claude Code</a>.</h4>
+
+<p align="center">
+  <a href="LICENSE">
+    <img src="https://img.shields.io/badge/License-AGPL%203.0-blue.svg" alt="License">
+  </a>
+  <a href="package.json">
+    <img src="https://img.shields.io/badge/version-6.5.0-green.svg" alt="Version">
+  </a>
+  <a href="package.json">
+    <img src="https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen.svg" alt="Node">
+  </a>
+  <a href="https://github.com/thedotmack/awesome-claude-code">
+    <img src="https://awesome.re/mentioned-badge.svg" alt="Mentioned in Awesome Claude Code">
+  </a>
+</p>
+
+<p align="center">
+  <a href="https://trendshift.io/repositories/15496" target="_blank">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge-dark.svg">
+      <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge.svg">
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge.svg" alt="thedotmack/claude-mem | Trendshift" width="250" height="55"/>
+    </picture>
+  </a>
+</p>
+
+<br>
+
+<p align="center">
+  <a href="https://github.com/thedotmack/claude-mem">
+    <picture>
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/cm-preview.gif" alt="Claude-Mem Preview" width="800">
+    </picture>
+  </a>
+</p>
+
+<p align="center">
+  <a href="#mabilis-na-pagsisimula">Mabilis na Pagsisimula</a> •
+  <a href="#paano-ito-gumagana">Paano Ito Gumagana</a> •
+  <a href="#mga-search-tool-ng-mcp">Mga Search Tool</a> •
+  <a href="#dokumentasyon">Dokumentasyon</a> •
+  <a href="#konpigurasyon">Konpigurasyon</a> •
+  <a href="#pag-troubleshoot">Pag-troubleshoot</a> •
+  <a href="#lisensya">Lisensya</a>
+</p>
+
+<p align="center">
+  Pinapanatili ng Claude-Mem ang konteksto sa pagitan ng mga session sa pamamagitan ng awtomatikong pagkuha ng mga obserbasyon sa paggamit ng mga tool, pagbuo ng mga semantikong buod, at paggawa nitong available sa mga susunod na session. Dahil dito, napapanatili ni Claude ang tuloy-tuloy na kaalaman tungkol sa mga proyekto kahit matapos o muling kumonekta ang mga session.
+</p>
+
+---
+
+## Mabilis na Pagsisimula
+
+Magsimula ng bagong Claude Code session sa terminal at ilagay ang mga sumusunod na command:
+
+```
+/plugin marketplace add thedotmack/claude-mem
+
+/plugin install claude-mem
+```
+
+I-restart ang Claude Code. Awtomatikong lalabas sa mga bagong session ang konteksto mula sa mga nakaraang session.
+
+**Mga Pangunahing Tampok:**
+
+- 🧠 **Persistent Memory** - Nananatili ang konteksto sa pagitan ng mga session
+- 📊 **Progressive Disclosure** - Layered na pagkuha ng memory na may visibility ng token cost
+- 🔍 **Skill-Based Search** - I-query ang history ng proyekto gamit ang mem-search skill
+- 🖥️ **Web Viewer UI** - Real-time memory stream sa http://localhost:37777
+- 💻 **Claude Desktop Skill** - Maghanap sa memory mula sa Claude Desktop conversations
+- 🔒 **Privacy Control** - Gamitin ang `<private>` tags para hindi ma-store ang sensitibong nilalaman
+- ⚙️ **Context Configuration** - Mas pinong kontrol kung anong konteksto ang ini-inject
+- 🤖 **Automatic Operation** - Walang kailangang manual na intervention
+- 🔗 **Citations** - I-refer ang mga lumang obserbasyon gamit ang IDs (i-access sa http://localhost:37777/api/observation/{id} o tingnan lahat sa web viewer sa http://localhost:37777)
+- 🧪 **Beta Channel** - Subukan ang mga experimental feature tulad ng Endless Mode sa pamamagitan ng version switching
+
+---
+
+## Dokumentasyon
+
+📚 **[Tingnan ang Buong Dokumentasyon](https://docs.claude-mem.ai/)** - I-browse sa opisyal na website
+
+### Pagsisimula
+
+- **[Gabay sa Pag-install](https://docs.claude-mem.ai/installation)** - Mabilis na pagsisimula at advanced installation
+- **[Gabay sa Paggamit](https://docs.claude-mem.ai/usage/getting-started)** - Paano awtomatikong gumagana ang Claude-Mem
+- **[Mga Search Tool](https://docs.claude-mem.ai/usage/search-tools)** - I-query ang history ng proyekto gamit ang natural language
+- **[Mga Beta Feature](https://docs.claude-mem.ai/beta-features)** - Subukan ang mga experimental feature tulad ng Endless Mode
+
+### Best Practices
+
+- **[Context Engineering](https://docs.claude-mem.ai/context-engineering)** - Mga prinsipyo ng context optimization para sa AI agents
+- **[Progressive Disclosure](https://docs.claude-mem.ai/progressive-disclosure)** - Pilosopiya sa likod ng context priming strategy ng Claude-Mem
+
+### Arkitektura
+
+- **[Overview](https://docs.claude-mem.ai/architecture/overview)** - Mga bahagi ng sistema at daloy ng data
+- **[Architecture Evolution](https://docs.claude-mem.ai/architecture-evolution)** - Ang paglalakbay mula v3 hanggang v5
+- **[Hooks Architecture](https://docs.claude-mem.ai/hooks-architecture)** - Paano gumagamit ang Claude-Mem ng lifecycle hooks
+- **[Hooks Reference](https://docs.claude-mem.ai/architecture/hooks)** - 7 hook scripts, ipinaliwanag
+- **[Worker Service](https://docs.claude-mem.ai/architecture/worker-service)** - HTTP API at Bun management
+- **[Database](https://docs.claude-mem.ai/architecture/database)** - SQLite schema at FTS5 search
+- **[Search Architecture](https://docs.claude-mem.ai/architecture/search-architecture)** - Hybrid search gamit ang Chroma vector database
+
+### Konpigurasyon at Pagbuo
+
+- **[Konpigurasyon](https://docs.claude-mem.ai/configuration)** - Environment variables at settings
+- **[Pagbuo](https://docs.claude-mem.ai/development)** - Build, test, at contribution workflow
+- **[Pag-troubleshoot](https://docs.claude-mem.ai/troubleshooting)** - Karaniwang isyu at solusyon
+
+---
+
+## Paano Ito Gumagana
+
+**Mga Pangunahing Bahagi:**
+
+1. **5 Lifecycle Hooks** - SessionStart, UserPromptSubmit, PostToolUse, Stop, SessionEnd (6 hook scripts)
+2. **Smart Install** - Cached dependency checker (pre-hook script, hindi lifecycle hook)
+3. **Worker Service** - HTTP API sa port 37777 na may web viewer UI at 10 search endpoints, pinamamahalaan ng Bun
+4. **SQLite Database** - Nag-iimbak ng sessions, observations, summaries
+5. **mem-search Skill** - Natural language queries na may progressive disclosure
+6. **Chroma Vector Database** - Hybrid semantic + keyword search para sa matalinong pagkuha ng konteksto
+
+Tingnan ang [Architecture Overview](https://docs.claude-mem.ai/architecture/overview) para sa detalye.
+
+---
+
+## Mga Search Tool ng MCP
+
+Nagbibigay ang Claude-Mem ng intelligent memory search sa pamamagitan ng **5 MCP tools** na sumusunod sa token-efficient na **3-layer workflow pattern**:
+
+**Ang 3-Layer Workflow:**
+
+1. **`search`** - Kumuha ng compact index na may IDs (~50-100 tokens/result)
+2. **`timeline`** - Kumuha ng chronological context sa paligid ng mga interesting na result
+3. **`get_observations`** - Kunin ang full details PARA LANG sa na-filter na IDs (~500-1,000 tokens/result)
+
+**Paano Ito Gumagana:**
+
+- Gumagamit si Claude ng MCP tools para maghanap sa iyong memory
+- Magsimula sa `search` para makakuha ng index ng results
+- Gamitin ang `timeline` para makita ang nangyari sa paligid ng mga partikular na observation
+- Gamitin ang `get_observations` para kunin ang full details ng mga relevant na IDs
+- Gamitin ang `save_memory` para manual na mag-store ng importanteng impormasyon
+- **~10x tipid sa tokens** dahil nagfi-filter muna bago kunin ang full details
+
+**Available na MCP Tools:**
+
+1. **`search`** - Hanapin ang memory index gamit ang full-text queries, may filters (type/date/project)
+2. **`timeline`** - Kumuha ng chronological context sa paligid ng isang observation o query
+3. **`get_observations`** - Kumuha ng full observation details gamit ang IDs (laging i-batch ang maraming IDs)
+4. **`save_memory`** - Manual na mag-save ng memory/observation para sa semantic search
+5. **`__IMPORTANT`** - Workflow documentation (laging visible kay Claude)
+
+**Halimbawa ng Paggamit:**
+
+```typescript
+// Step 1: Search for index
+search(query="authentication bug", type="bugfix", limit=10)
+
+// Step 2: Review index, identify relevant IDs (e.g., #123, #456)
+
+// Step 3: Fetch full details
+get_observations(ids=[123, 456])
+
+// Save important information manually
+save_memory(text="API requires auth header X-API-Key", title="API Auth")
+```
+
+Tingnan ang [Search Tools Guide](https://docs.claude-mem.ai/usage/search-tools) para sa mas detalyadong mga halimbawa.
+
+---
+
+## Mga Beta Feature
+
+May **beta channel** ang Claude-Mem na may mga experimental feature gaya ng **Endless Mode** (biomimetic memory architecture para sa mas mahahabang session). Magpalit sa pagitan ng stable at beta versions sa web viewer UI sa http://localhost:37777 → Settings.
+
+Tingnan ang **[Dokumentasyon ng Mga Beta Feature](https://docs.claude-mem.ai/beta-features)** para sa detalye ng Endless Mode at kung paano ito subukan.
+
+---
+
+## Mga Pangangailangan ng Sistema
+
+- **Node.js**: 18.0.0 o mas mataas
+- **Claude Code**: Pinakabagong bersyon na may plugin support
+- **Bun**: JavaScript runtime at process manager (auto-installed kung wala)
+- **uv**: Python package manager para sa vector search (auto-installed kung wala)
+- **SQLite 3**: Para sa persistent storage (kasama)
+
+---
+
+### Mga Tala sa Windows Setup
+
+Kung makakita ka ng error gaya ng:
+
+```powershell
+npm : The term 'npm' is not recognized as the name of a cmdlet
+```
+
+Siguraduhing naka-install ang Node.js at npm at nakadagdag sa PATH. I-download ang pinakabagong Node.js installer mula sa https://nodejs.org at i-restart ang terminal matapos mag-install.
+
+---
+
+## Konpigurasyon
+
+Pinamamahalaan ang settings sa `~/.claude-mem/settings.json` (auto-created na may defaults sa unang run). I-configure ang AI model, worker port, data directory, log level, at context injection settings.
+
+Tingnan ang **[Gabay sa Konpigurasyon](https://docs.claude-mem.ai/configuration)** para sa lahat ng available na settings at mga halimbawa.
+
+---
+
+## Pagbuo
+
+Tingnan ang **[Gabay nang pagbuo](https://docs.claude-mem.ai/development)** para sa pag build instructions, testing, at contribution workflow.
+
+---
+
+## Pag-troubleshoot
+
+Kung may issue, ilarawan ang problema kay Claude at awtomatikong magdi-diagnose at magbibigay ng mga ayos ang troubleshoot skill.
+
+Tingnan ang **[Troubleshooting Guide](https://docs.claude-mem.ai/troubleshooting)** para sa mga karaniwang isyu at solusyon.
+
+---
+
+## Bug Reports
+
+Gumawa ng kumpletong bug reports gamit ang automated generator:
+
+```bash
+cd ~/.claude/plugins/marketplaces/thedotmack
+npm run bug-report
+```
+
+## Pag-aambag
+
+Malugod na tinatanggap ang mga kontribusyon! Pakisunod:
+
+1. I-fork ang repository
+2. Gumawa ng feature branch
+3. Gawin ang mga pagbabago kasama ang tests
+4. I-update ang dokumentasyon
+5. Mag-submit ng Pull Request
+
+Tingnan ang [Gabay nang pagbuo](https://docs.claude-mem.ai/development) para sa contribution workflow.
+
+---
+
+## Lisensya
+
+Ang proyektong ito ay licensed sa ilalim ng **GNU Affero General Public License v3.0** (AGPL-3.0).
+
+Copyright (C) 2025 Alex Newman (@thedotmack). All rights reserved.
+
+Tingnan ang [LICENSE](LICENSE) file para sa buong detalye.
+
+**Ano ang ibig sabihin nito:**
+
+- Maaari mong gamitin, baguhin, at ipamahagi ang software na ito nang libre
+- Kung babaguhin mo at i-deploy sa isang network server, kailangan mong gawing available ang iyong source code
+- Dapat ding naka-license sa AGPL-3.0 ang mga derivative works
+- WALANG WARRANTY para sa software na ito
+
+**Tala tungkol sa Ragtime**: Ang `ragtime/` directory ay may hiwalay na lisensya sa ilalim ng **PolyForm Noncommercial License 1.0.0**. Tingnan ang [ragtime/LICENSE](ragtime/LICENSE) para sa detalye.
+
+---
+
+## Suporta
+
+- **Dokumentasyon**: [docs/](docs/)
+- **Issues**: [GitHub Issues](https://github.com/thedotmack/claude-mem/issues)
+- **Repository**: [github.com/thedotmack/claude-mem](https://github.com/thedotmack/claude-mem)
+- **Author**: Alex Newman ([@thedotmack](https://github.com/thedotmack))
+
+---
+
+**Built with Claude Agent SDK** | **Powered by Claude Code** | **Made with TypeScript**

docs/i18n/README.tr.md

@@ -14,6 +14,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -33,6 +34,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -125,7 +127,7 @@ Claude Code'u yeniden başlatın. Önceki oturumlardaki bağlam otomatik olarak
 
 ## Dokümantasyon
 
-📚 **[Tam Dokümantasyonu Görüntüle](docs/)** - GitHub'da markdown dökümanlarına göz atın
+📚 **[Tam Dokümantasyonu Görüntüle](https://docs.claude-mem.ai/)** - Resmi web sitesinde göz atın
 
 ### Başlarken
 

docs/i18n/README.uk.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@
 
 ## Документація
 
-📚 **[Переглянути повну документацію](docs/)** - Переглядайте markdown документи на GitHub
+📚 **[Переглянути повну документацію](https://docs.claude-mem.ai/)** - Переглянути на офіційному сайті
 
 ### Початок роботи
 

docs/i18n/README.ur.md

@@ -0,0 +1,311 @@
+<section dir="rtl">
+🌐 یہ ایک خودکار ترجمہ ہے۔ کمیونٹی کی اصلاحات کا خیر مقدم ہے!
+
+---
+<h1 align="center">
+  <br>
+  <a href="https://github.com/thedotmack/claude-mem">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-dark-mode.webp">
+      <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-light-mode.webp">
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-light-mode.webp" alt="Claude-Mem" width="400">
+    </picture>
+  </a>
+  <br>
+</h1>
+
+<p align="center" dir="ltr">
+  <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.ja.md">🇯🇵 日本語</a> •
+  <a href="README.pt-br.md">🇧🇷 Português</a> •
+  <a href="README.ko.md">🇰🇷 한국어</a> •
+  <a href="README.es.md">🇪🇸 Español</a> •
+  <a href="README.de.md">🇩🇪 Deutsch</a> •
+  <a href="README.fr.md">🇫🇷 Français</a>
+  <a href="README.he.md">🇮🇱 עברית</a> •
+  <a href="README.ar.md">🇸🇦 العربية</a> •
+  <a href="README.ru.md">🇷🇺 Русский</a> •
+  <a href="README.pl.md">🇵🇱 Polski</a> •
+  <a href="README.cs.md">🇨🇿 Čeština</a> •
+  <a href="README.nl.md">🇳🇱 Nederlands</a> •
+  <a href="README.tr.md">🇹🇷 Türkçe</a> •
+  <a href="README.uk.md">🇺🇦 Українська</a> •
+  <a href="README.vi.md">🇻🇳 Tiếng Việt</a> •
+  <a href="README.id.md">🇮🇩 Indonesia</a> •
+  <a href="README.th.md">🇹🇭 ไทย</a> •
+  <a href="README.hi.md">🇮🇳 हिन्दी</a> •
+  <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
+  <a href="README.ro.md">🇷🇴 Română</a> •
+  <a href="README.sv.md">🇸🇪 Svenska</a> •
+  <a href="README.it.md">🇮🇹 Italiano</a> •
+  <a href="README.el.md">🇬🇷 Ελληνικά</a> •
+  <a href="README.hu.md">🇭🇺 Magyar</a> •
+  <a href="README.fi.md">🇫🇮 Suomi</a> •
+  <a href="README.da.md">🇩🇰 Dansk</a> •
+  <a href="README.no.md">🇳🇴 Norsk</a>
+</p>
+
+<h4 align="center"><a href="https://claude.com/claude-code" target="_blank">Claude Code</a> کے لیے بنایا گیا مستقل میموری کمپریشن سسٹم۔</h4>
+
+<p align="center">
+  <a href="LICENSE">
+    <img src="https://img.shields.io/badge/License-AGPL%203.0-blue.svg" alt="License">
+  </a>
+  <a href="package.json">
+    <img src="https://img.shields.io/badge/version-6.5.0-green.svg" alt="Version">
+  </a>
+  <a href="package.json">
+    <img src="https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen.svg" alt="Node">
+  </a>
+  <a href="https://github.com/thedotmack/awesome-claude-code">
+    <img src="https://awesome.re/mentioned-badge.svg" alt="Mentioned in Awesome Claude Code">
+  </a>
+</p>
+
+<p align="center">
+  <a href="https://trendshift.io/repositories/15496" target="_blank">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge-dark.svg">
+      <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge.svg">
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge.svg" alt="thedotmack/claude-mem | Trendshift" width="250" height="55"/>
+    </picture>
+  </a>
+</p>
+
+<br>
+
+<p align="center">
+  <a href="https://github.com/thedotmack/claude-mem">
+    <picture>
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/cm-preview.gif" alt="Claude-Mem Preview" width="800">
+    </picture>
+  </a>
+</p>
+
+<p align="center">
+  <a href="#تیز-رفتار-شروعات">تیز رفتار شروعات</a> •
+  <a href="#یہ-کیسے-کام-کرتا-ہے">یہ کیسے کام کرتا ہے</a> •
+  <a href="#تلاش-کے-اوزار">تلاش کے اوزار</a> •
+  <a href="#دستاویزات">دستاویزات</a> •
+  <a href="#ترتیبات">ترتیبات</a> •
+  <a href="#مسائل-کی-تشخیص">مسائل کی تشخیص</a> •
+  <a href="#لائسنس">لائسنس</a>
+</p>
+
+<p align="center">
+  Claude-Mem خودکار طور پر ٹول کے استعمال کے بعد کے مشاہدات کو ریکارڈ کرتا ہے، سیمانٹک خلاصے تیار کرتا ہے اور انہیں مستقبل کے سیشنز میں دستیاب کرتا ہے تاکہ آپ سیشن میں براہ راست تناسب محفوظ رہے۔ یہ Claude کو سیشن ختم ہونے یا دوبارہ جڑنے کے بعد بھی منصوبے کے بارے میں معلومات کی مسلسلیت برقرار رکھنے کے قابل بناتا ہے۔
+</p>
+
+---
+
+## تیز رفتار شروعات
+
+ٹرمنل میں نیا Claude Code سیشن شروع کریں اور ہیں کمانڈز درج کریں:
+
+```
+> /plugin marketplace add thedotmack/claude-mem
+
+> /plugin install claude-mem
+```
+
+Claude Code کو دوبارہ شروع کریں۔ سابقہ سیشن کا تناسب خودکار طور پر نئے سیشن میں موجود ہوگا۔
+
+**اہم خصوصیات:**
+
+- 🧠 **مستقل میموری** - تناسب سیشن کے دوران برقرار رہتا ہے
+- 📊 **بتدریج ظہور** - لیئرڈ میموری کی بازیافت ٹوکن کی لاگت کی نمائندگی کے ساتھ
+- 🔍 **کمکردہ تلاش** - mem-search مہارت کے ساتھ اپنے منصوبے کی تاریخ میں تلاش کریں
+- 🖥️ **ویب ویور یو آئی** - http://localhost:37777 پر حقیقی وقت میموری اسٹریم
+- 💻 **Claude Desktop مہارت** - Claude Desktop بات چیت سے میموری تلاش کریں
+- 🔒 **رازداری کے کنٹرولز** - حساس مواد کو ذخیرہ سے خارج کرنے کے لیے `<private>` ٹیگ استعمال کریں
+- ⚙️ **تناسب کی ترتیبات** - کون سا تناسب انجیکٹ کیا جائے اس پر باریک کنٹرول
+- 🤖 **خودکار آپریشن** - کسی دستی مداخلت کی ضرورت نہیں
+- 🔗 **حوالہ** - ID کے ذریعے سابقہ مشاہدات کا حوالہ دیں (http://localhost:37777/api/observation/{id} کے ذریعے رسائی حاصل کریں یا تمام کو http://localhost:37777 پر ویب ویور میں دیکھیں)
+- 🧪 **بیٹا چینل** - ورژن تبدیل کرنے کے ذریعے Endless Mode جیسی تجرباتی خصوصیات آزمائیں
+
+---
+
+## دستاویزات
+
+📚 **[مکمل دستاویزات دیکھیں](docs/)** - GitHub پر markdown ڈاکس کو براؤز کریں
+
+### شروعات کرنا
+
+- **[انسٹالیشن گائیڈ](https://docs.claude-mem.ai/installation)** - تیز رفتار شروعات اور اعلیٰ درجے کی انسٹالیشن
+- **[استعمال گائیڈ](https://docs.claude-mem.ai/usage/getting-started)** - Claude-Mem خودکار طور پر کیسے کام کرتا ہے
+- **[تلاش کے اوزار](https://docs.claude-mem.ai/usage/search-tools)** - قدرتی زبان کے ساتھ اپنے منصوبے کی تاریخ میں تلاش کریں
+- **[بیٹا خصوصیات](https://docs.claude-mem.ai/beta-features)** - Endless Mode جیسی تجرباتی خصوصیات آزمائیں
+
+### بہترین طریقہ کار
+
+- **[تناسب انجینیئرنگ](https://docs.claude-mem.ai/context-engineering)** - AI ایجنٹ کے تناسب کی اہمیت کے اصول
+- **[بتدریج ظہور](https://docs.claude-mem.ai/progressive-disclosure)** - Claude-Mem کے تناسب کی تیاری کی حکمت عملی کے پیچھے فلسفہ
+
+### تعمیر
+
+- **[جائزہ](https://docs.claude-mem.ai/architecture/overview)** - نظام کے اجزاء اور ڈیٹا کے بہاؤ
+- **[تعمیر کا ارتقاء](https://docs.claude-mem.ai/architecture-evolution)** - v3 سے v5 تک کا سفر
+- **[ہکس تعمیر](https://docs.claude-mem.ai/hooks-architecture)** - Claude-Mem لائف سائیکل ہکس کا استعمال کیسے کرتا ہے
+- **[ہکس حوالہ](https://docs.claude-mem.ai/architecture/hooks)** - 7 ہک اسکرپٹس کی تشریح
+- **[ورکر سروس](https://docs.claude-mem.ai/architecture/worker-service)** - HTTP API اور Bun انتظام
+- **[ڈیٹا بیس](https://docs.claude-mem.ai/architecture/database)** - SQLite اسکیما اور FTS5 تلاش
+- **[تلاش تعمیر](https://docs.claude-mem.ai/architecture/search-architecture)** - Chroma ویکٹر ڈیٹا بیس کے ساتھ ہائبرڈ تلاش
+
+### ترتیبات اور ترقی
+
+- **[ترتیبات](https://docs.claude-mem.ai/configuration)** - ماحول کے متغیرات اور سیٹنگز
+- **[ترقی](https://docs.claude-mem.ai/development)** - تعمیر، جانچ، حصہ داری
+- **[مسائل کی تشخیص](https://docs.claude-mem.ai/troubleshooting)** - عام مسائل اور حل
+
+---
+
+## یہ کیسے کام کرتا ہے
+
+**اہم اجزاء:**
+
+1. **5 لائف سائیکل ہکس** - SessionStart، UserPromptSubmit، PostToolUse، Stop، SessionEnd (6 ہک اسکرپٹس)
+2. **سمارٹ انسٹالیشن** - کیش شدہ منحصرات چیکر (پری ہک اسکرپٹ، لائف سائیکل ہک نہیں)
+3. **ورکر سروس** - ویب ویور UI اور 10 تلاش کے endpoints کے ساتھ پورٹ 37777 پر HTTP API، Bun کے ذریعے برتاؤ
+4. **SQLite ڈیٹا بیس** - سیشنز، مشاہدات، خلاصہ ذخیرہ کرتا ہے
+5. **mem-search مہارت** - بتدریج ظہور کے ساتھ قدرتی زبان کے سوالات
+6. **Chroma ویکٹر ڈیٹا بیس** - ہائبرڈ سیمانٹک + کلیدی لفظ تلاش ذہین تناسب کی بازیافت کے لیے
+
+تفصیلات کے لیے [تعمیر کا جائزہ](https://docs.claude-mem.ai/architecture/overview) دیکھیں۔
+
+---
+
+## MCP تلاش کے اوزار
+
+Claude-Mem ٹوکن-موثر **3-لیئر ورک فلو پیٹرن** کی پیروی کرتے ہوئے **4 MCP اوزار** کے ذریعے ذہین میموری تلاش فراہم کرتا ہے:
+
+**3-لیئر ورک فلو:**
+
+1. **`search`** - IDs کے ساتھ کمپیکٹ انڈیکس حاصل کریں (~50-100 ٹوکن/نتیجہ)
+2. **`timeline`** - دلچسپ نتائج کے ارد گرد زمانی تناسب حاصل کریں
+3. **`get_observations`** - فلٹر شدہ IDs کے لیے صرف مکمل تفصیلات حاصل کریں (~500-1,000 ٹوکن/نتیجہ)
+
+**یہ کیسے کام کرتا ہے:**
+- Claude آپ کی میموری میں تلاش کے لیے MCP اوزار استعمال کرتا ہے
+- نتائج کا انڈیکس حاصل کرنے کے لیے `search` سے شروع کریں
+- مخصوص مشاہدات کے ارد گرد کیا ہو رہا تھا دیکھنے کے لیے `timeline` استعمال کریں
+- متعلقہ IDs کے لیے مکمل تفصیلات حاصل کرنے کے لیے `get_observations` استعمال کریں
+- تفصیلات حاصل کرنے سے پہلے فلٹرنگ کے ذریعے **~10x ٹوکن کی بچت**
+
+**دستیاب MCP اوزار:**
+
+1. **`search`** - مکمل متن کی تلاش کے سوالات کے ساتھ میموری انڈیکس تلاش کریں، قسم/تاریخ/منصوبے کے لحاظ سے فلٹر کریں
+2. **`timeline`** - مخصوص مشاہدہ یا سوال کے ارد گرد زمانی تناسب حاصل کریں
+3. **`get_observations`** - IDs کے ذریعے مکمل مشاہدہ تفصیلات حاصل کریں (ہمیشہ متعدد IDs کو بیچ کریں)
+4. **`__IMPORTANT`** - ورک فلو دستاویزات (ہمیشہ Claude کو نظر آتی ہے)
+
+**استعمال کی مثال:**
+
+```typescript
+// مرحلہ 1: انڈیکس کے لیے تلاش کریں
+search(query="authentication bug", type="bugfix", limit=10)
+
+// مرحلہ 2: انڈیکس کا جائزہ لیں، متعلقہ IDs کی شناخت کریں (مثلاً، #123, #456)
+
+// مرحلہ 3: مکمل تفصیلات حاصل کریں
+get_observations(ids=[123, 456])
+```
+
+تفصیلی مثالوں کے لیے [تلاش کے اوزار گائیڈ](https://docs.claude-mem.ai/usage/search-tools) دیکھیں۔
+
+---
+
+## بیٹا خصوصیات
+
+Claude-Mem ایک **بیٹا چینل** فراہم کرتا ہے جس میں **Endless Mode** جیسی تجرباتی خصوصیات ہیں (بڑھی ہوئی سیشنز کے لیے حیاتی نقل میموری کی تعمیر)۔ http://localhost:37777 → Settings میں ویب ویور UI سے مستحکم اور بیٹا ورژن کے درمیان سوئچ کریں۔
+
+Endless Mode اور اسے کیسے آزمائیں اس کے بارے میں تفصیلات کے لیے **[بیٹا خصوصیات دستاویزات](https://docs.claude-mem.ai/beta-features)** دیکھیں۔
+
+---
+
+## نظام کی ضروریات
+
+- **Node.js**: 18.0.0 یا اس سے اوپر
+- **Claude Code**: پلگ ان سپورٹ کے ساتھ جدید ترین ورژن
+- **Bun**: JavaScript رن ٹائم اور پروسیس مینیجر (غیر موجود ہو تو خودکار طور پر انسٹال ہوگا)
+- **uv**: ویکٹر تلاش کے لیے Python پیکج مینیجر (غیر موجود ہو تو خودکار طور پر انسٹال ہوگا)
+- **SQLite 3**: مستقل اسٹوریج کے لیے (بنڈل شدہ)
+
+---
+
+## ترتیبات
+
+سیٹنگز `~/.claude-mem/settings.json` میں منظم ہیں (پہلی رن میں ڈیفالٹ کے ساتھ خودکار طور پر بنائی جاتی ہے)۔ AI ماڈل، ورکر پورٹ، ڈیٹا ڈائریکٹری، لاگ لیول اور تناسب انجیکشن سیٹنگز کو ترتیب دیں۔
+
+تمام دستیاب سیٹنگز اور مثالوں کے لیے **[ترتیبات گائیڈ](https://docs.claude-mem.ai/configuration)** دیکھیں۔
+
+---
+
+## ترقی
+
+تعمیر کی ہدایات، جانچ اور حصہ داری کے کام کے بہاؤ کے لیے **[ترقی گائیڈ](https://docs.claude-mem.ai/development)** دیکھیں۔
+
+---
+
+## مسائل کی تشخیص
+
+اگر مسائل کا سامنا ہو تو Claude کو مسئلہ بتائیں اور troubleshoot مہارت خودکار طور پر تشخیص دے گی اور حل فراہم کرے گی۔
+
+عام مسائل اور حل کے لیے **[مسائل کی تشخیص گائیڈ](https://docs.claude-mem.ai/troubleshooting)** دیکھیں۔
+
+---
+
+## خرابی کی رپورٹ
+
+خودکار جنریٹر کے ساتھ تفصیلی خرابی کی رپورٹ تیار کریں:
+
+```bash
+cd ~/.claude/plugins/marketplaces/thedotmack
+npm run bug-report
+```
+
+## حصہ داری
+
+حصہ داری کا خیر مقدم ہے! براہ کرم:
+
+1. رپوزیٹری کو فورک کریں
+2. ایک خصوصیت کی برانچ بنائیں
+3. ٹیسٹ کے ساتھ اپنی تبدیلیاں کریں
+4. دستاویزات کو اپڈیٹ کریں
+5. ایک Pull Request جمع کریں
+
+حصہ داری کے کام کے بہاؤ کے لیے [ترقی گائیڈ](https://docs.claude-mem.ai/development) دیکھیں۔
+
+---
+
+## لائسنس
+
+یہ منصوبہ **GNU Affero General Public License v3.0** (AGPL-3.0) کے تحت لائسنس ہے۔
+
+Copyright (C) 2025 Alex Newman (@thedotmack)۔ تمام حقوق محفوظ ہیں۔
+
+مکمل تفصیلات کے لیے [LICENSE](LICENSE) فائل دیکھیں۔
+
+**اس کا مطلب کیا ہے:**
+
+- آپ اس سافٹ ویئر کو آزادی سے استعمال، تبدیل اور تقسیم کر سکتے ہیں
+- اگر آپ اسے تبدیل کریں اور نیٹ ورک سرور میں نشر کریں تو آپ کو اپنا سورس کوڈ دستیاب کرنا ہوگا
+- ماخوذ کام بھی AGPL-3.0 کے تحت لائسنس ہونے چاہیں
+- اس سافٹ ویئر کے لیے کوئی وارنٹی نہیں
+
+**Ragtime کے بارے میں نوٹ**: `ragtime/` ڈائریکٹری الگ سے **PolyForm Noncommercial License 1.0.0** کے تحت لائسنس ہے۔ تفصیلات کے لیے [ragtime/LICENSE](ragtime/LICENSE) دیکھیں۔
+
+---
+
+## معاونت
+
+- **دستاویزات**: [docs/](docs/)
+- **مسائل**: [GitHub Issues](https://github.com/thedotmack/claude-mem/issues)
+- **رپوزیٹری**: [github.com/thedotmack/claude-mem](https://github.com/thedotmack/claude-mem)
+- **مصنف**: Alex Newman ([@thedotmack](https://github.com/thedotmack))
+
+---
+
+**Claude Agent SDK کے ساتھ بنایا گیا** | **Claude Code کے ذریعے طاقت ور** | **TypeScript کے ساتھ بنایا گیا**
+
+</section>

docs/i18n/README.vi.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@ Khởi động lại Claude Code. Ngữ cảnh từ các phiên trước sẽ t
 
 ## Tài Liệu
 
-📚 **[Xem Tài Liệu Đầy Đủ](docs/)** - Duyệt tài liệu markdown trên GitHub
+📚 **[Xem Tài Liệu Đầy Đủ](https://docs.claude-mem.ai/)** - Duyệt trên trang web chính thức
 
 ### Bắt Đầu
 

docs/i18n/README.zh-tw.md

@@ -0,0 +1,311 @@
+🌐 這是自動翻譯。歡迎社群貢獻修正！
+
+---
+<h1 align="center">
+  <br>
+  <a href="https://github.com/thedotmack/claude-mem">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-dark-mode.webp">
+      <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-light-mode.webp">
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-light-mode.webp" alt="Claude-Mem" width="400">
+    </picture>
+  </a>
+  <br>
+</h1>
+
+<p align="center">
+  <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
+  <a href="README.ja.md">🇯🇵 日本語</a> •
+  <a href="README.pt-br.md">🇧🇷 Português</a> •
+  <a href="README.ko.md">🇰🇷 한국어</a> •
+  <a href="README.es.md">🇪🇸 Español</a> •
+  <a href="README.de.md">🇩🇪 Deutsch</a> •
+  <a href="README.fr.md">🇫🇷 Français</a>
+  <a href="README.he.md">🇮🇱 עברית</a> •
+  <a href="README.ar.md">🇸🇦 العربية</a> •
+  <a href="README.ru.md">🇷🇺 Русский</a> •
+  <a href="README.pl.md">🇵🇱 Polski</a> •
+  <a href="README.cs.md">🇨🇿 Čeština</a> •
+  <a href="README.nl.md">🇳🇱 Nederlands</a> •
+  <a href="README.tr.md">🇹🇷 Türkçe</a> •
+  <a href="README.uk.md">🇺🇦 Українська</a> •
+  <a href="README.vi.md">🇻🇳 Tiếng Việt</a> •
+  <a href="README.id.md">🇮🇩 Indonesia</a> •
+  <a href="README.th.md">🇹🇭 ไทย</a> •
+  <a href="README.hi.md">🇮🇳 हिन्दी</a> •
+  <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ro.md">🇷🇴 Română</a> •
+  <a href="README.sv.md">🇸🇪 Svenska</a> •
+  <a href="README.it.md">🇮🇹 Italiano</a> •
+  <a href="README.el.md">🇬🇷 Ελληνικά</a> •
+  <a href="README.hu.md">🇭🇺 Magyar</a> •
+  <a href="README.fi.md">🇫🇮 Suomi</a> •
+  <a href="README.da.md">🇩🇰 Dansk</a> •
+  <a href="README.no.md">🇳🇴 Norsk</a>
+</p>
+
+<h4 align="center">為 <a href="https://claude.com/claude-code" target="_blank">Claude Code</a> 打造的持久記憶壓縮系統</h4>
+
+<p align="center">
+  <a href="LICENSE">
+    <img src="https://img.shields.io/badge/License-AGPL%203.0-blue.svg" alt="License">
+  </a>
+  <a href="package.json">
+    <img src="https://img.shields.io/badge/version-6.5.0-green.svg" alt="Version">
+  </a>
+  <a href="package.json">
+    <img src="https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen.svg" alt="Node">
+  </a>
+  <a href="https://github.com/thedotmack/awesome-claude-code">
+    <img src="https://awesome.re/mentioned-badge.svg" alt="Mentioned in Awesome Claude Code">
+  </a>
+</p>
+
+<p align="center">
+  <a href="https://trendshift.io/repositories/15496" target="_blank">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge-dark.svg">
+      <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge.svg">
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge.svg" alt="thedotmack/claude-mem | Trendshift" width="250" height="55"/>
+    </picture>
+  </a>
+</p>
+
+<br>
+
+<p align="center">
+  <a href="https://github.com/thedotmack/claude-mem">
+    <picture>
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/cm-preview.gif" alt="Claude-Mem Preview" width="800">
+    </picture>
+  </a>
+</p>
+
+<p align="center">
+  <a href="#快速開始">快速開始</a> •
+  <a href="#運作原理">運作原理</a> •
+  <a href="#mcp-搜尋工具">搜尋工具</a> •
+  <a href="#文件">文件</a> •
+  <a href="#設定">設定</a> •
+  <a href="#疑難排解">疑難排解</a> •
+  <a href="#授權條款">授權條款</a>
+</p>
+
+<p align="center">
+  Claude-Mem 透過自動擷取工具使用觀察、產生語意摘要並在未來的工作階段中提供使用，無縫保留跨工作階段的脈絡。這使 Claude 即使在工作階段結束或重新連線後，仍能維持對專案的知識連續性。
+</p>
+
+---
+
+## 快速開始
+
+在終端機中開啟新的 Claude Code 工作階段，並輸入以下指令：
+
+```
+> /plugin marketplace add thedotmack/claude-mem
+
+> /plugin install claude-mem
+```
+
+重新啟動 Claude Code。先前工作階段的脈絡將自動出現在新的工作階段中。
+
+**主要功能：**
+
+- 🧠 **持久記憶** - 脈絡跨工作階段保留
+- 📊 **漸進式揭露** - 具有 Token 成本可見性的分層記憶擷取
+- 🔍 **技能式搜尋** - 使用 mem-search 技能查詢專案歷史
+- 🖥️ **網頁檢視介面** - 在 http://localhost:37777 即時檢視記憶串流
+- 💻 **Claude Desktop 技能** - 從 Claude Desktop 對話中搜尋記憶
+- 🔒 **隱私控制** - 使用 `<private>` 標籤排除敏感內容的儲存
+- ⚙️ **脈絡設定** - 精細控制注入哪些脈絡
+- 🤖 **自動運作** - 無需手動介入
+- 🔗 **引用** - 使用 ID 參考過去的觀察（透過 http://localhost:37777/api/observation/{id} 存取，或在 http://localhost:37777 的網頁檢視器中檢視全部）
+- 🧪 **Beta 通道** - 透過版本切換試用 Endless Mode 等實驗性功能
+
+---
+
+## 文件
+
+📚 **[檢視完整文件](docs/)** - 在 GitHub 上瀏覽 Markdown 文件
+
+### 入門指南
+
+- **[安裝指南](https://docs.claude-mem.ai/installation)** - 快速開始與進階安裝
+- **[使用指南](https://docs.claude-mem.ai/usage/getting-started)** - Claude-Mem 如何自動運作
+- **[搜尋工具](https://docs.claude-mem.ai/usage/search-tools)** - 使用自然語言查詢專案歷史
+- **[Beta 功能](https://docs.claude-mem.ai/beta-features)** - 試用 Endless Mode 等實驗性功能
+
+### 最佳實務
+
+- **[脈絡工程](https://docs.claude-mem.ai/context-engineering)** - AI 代理脈絡最佳化原則
+- **[漸進式揭露](https://docs.claude-mem.ai/progressive-disclosure)** - Claude-Mem 脈絡啟動策略背後的理念
+
+### 架構
+
+- **[概覽](https://docs.claude-mem.ai/architecture/overview)** - 系統元件與資料流程
+- **[架構演進](https://docs.claude-mem.ai/architecture-evolution)** - 從 v3 到 v5 的旅程
+- **[Hooks 架構](https://docs.claude-mem.ai/hooks-architecture)** - Claude-Mem 如何使用生命週期掛鉤
+- **[Hooks 參考](https://docs.claude-mem.ai/architecture/hooks)** - 7 個掛鉤腳本說明
+- **[Worker 服務](https://docs.claude-mem.ai/architecture/worker-service)** - HTTP API 與 Bun 管理
+- **[資料庫](https://docs.claude-mem.ai/architecture/database)** - SQLite 結構描述與 FTS5 搜尋
+- **[搜尋架構](https://docs.claude-mem.ai/architecture/search-architecture)** - 使用 Chroma 向量資料庫的混合搜尋
+
+### 設定與開發
+
+- **[設定](https://docs.claude-mem.ai/configuration)** - 環境變數與設定
+- **[開發](https://docs.claude-mem.ai/development)** - 建置、測試、貢獻
+- **[疑難排解](https://docs.claude-mem.ai/troubleshooting)** - 常見問題與解決方案
+
+---
+
+## 運作原理
+
+**核心元件：**
+
+1. **5 個生命週期掛鉤** - SessionStart、UserPromptSubmit、PostToolUse、Stop、SessionEnd（6 個掛鉤腳本）
+2. **智慧安裝** - 快取的相依性檢查器（pre-hook 腳本，非生命週期掛鉤）
+3. **Worker 服務** - 連接埠 37777 上的 HTTP API，含網頁檢視介面與 10 個搜尋端點，由 Bun 管理
+4. **SQLite 資料庫** - 儲存工作階段、觀察、摘要
+5. **mem-search 技能** - 具有漸進式揭露的自然語言查詢
+6. **Chroma 向量資料庫** - 用於智慧脈絡擷取的混合語意 + 關鍵字搜尋
+
+詳情請參閱[架構概覽](https://docs.claude-mem.ai/architecture/overview)。
+
+---
+
+## MCP 搜尋工具
+
+Claude-Mem 透過遵循 Token 高效的 **3 層工作流程模式**，以 **4 個 MCP 工具**提供智慧記憶搜尋：
+
+**3 層工作流程：**
+
+1. **`search`** - 取得精簡索引與 ID（每筆結果約 50-100 tokens）
+2. **`timeline`** - 取得有趣結果周圍的時間脈絡
+3. **`get_observations`** - 僅為過濾後的 ID 擷取完整詳情（每筆結果約 500-1,000 tokens）
+
+**運作方式：**
+
+- Claude 使用 MCP 工具搜尋您的記憶
+- 從 `search` 開始取得結果索引
+- 使用 `timeline` 檢視特定觀察周圍發生的事情
+- 使用 `get_observations` 擷取相關 ID 的完整詳情
+- 透過在擷取詳情前過濾，**節省約 10 倍 token**
+
+**可用的 MCP 工具：**
+
+1. **`search`** - 使用全文查詢搜尋記憶索引，依類型/日期/專案過濾
+2. **`timeline`** - 取得特定觀察或查詢周圍的時間脈絡
+3. **`get_observations`** - 依 ID 擷取完整觀察詳情（批次處理多個 ID）
+4. **`__IMPORTANT`** - 工作流程文件（Claude 永遠可見）
+
+**使用範例：**
+
+```typescript
+// 步驟 1：搜尋索引
+search(query="authentication bug", type="bugfix", limit=10)
+
+// 步驟 2：檢閱索引，識別相關 ID（例如 #123、#456）
+
+// 步驟 3：擷取完整詳情
+get_observations(ids=[123, 456])
+```
+
+詳細範例請參閱[搜尋工具指南](https://docs.claude-mem.ai/usage/search-tools)。
+
+---
+
+## Beta 功能
+
+Claude-Mem 提供具有實驗性功能的 **Beta 通道**，例如 **Endless Mode**（用於延長工作階段的仿生記憶架構）。在 http://localhost:37777 → Settings 的網頁檢視介面中切換穩定版與 Beta 版。
+
+有關 Endless Mode 與如何試用的詳情，請參閱 **[Beta 功能文件](https://docs.claude-mem.ai/beta-features)**。
+
+---
+
+## 系統需求
+
+- **Node.js**：18.0.0 或更高版本
+- **Claude Code**：具有外掛支援的最新版本
+- **Bun**：JavaScript 執行環境與程序管理員（如缺少將自動安裝）
+- **uv**：用於向量搜尋的 Python 套件管理員（如缺少將自動安裝）
+- **SQLite 3**：用於持久儲存（已內建）
+
+---
+
+## 設定
+
+設定在 `~/.claude-mem/settings.json` 中管理（首次執行時自動以預設值建立）。設定 AI 模型、Worker 連接埠、資料目錄、日誌層級與脈絡注入設定。
+
+所有可用設定與範例請參閱 **[設定指南](https://docs.claude-mem.ai/configuration)**。
+
+---
+
+## 開發
+
+建置說明、測試與貢獻工作流程請參閱 **[開發指南](https://docs.claude-mem.ai/development)**。
+
+---
+
+## 疑難排解
+
+如遇問題，向 Claude 描述問題，troubleshoot 技能將自動診斷並提供修正。
+
+常見問題與解決方案請參閱 **[疑難排解指南](https://docs.claude-mem.ai/troubleshooting)**。
+
+---
+
+## 錯誤回報
+
+使用自動產生器建立完整的錯誤回報：
+
+```bash
+cd ~/.claude/plugins/marketplaces/thedotmack
+npm run bug-report
+```
+
+## 貢獻
+
+歡迎貢獻！請依照以下步驟：
+
+1. Fork 儲存庫
+2. 建立功能分支
+3. 加入測試並進行變更
+4. 更新文件
+5. 提交 Pull Request
+
+貢獻工作流程請參閱[開發指南](https://docs.claude-mem.ai/development)。
+
+---
+
+## 授權條款
+
+本專案採用 **GNU Affero 通用公共授權條款 v3.0**（AGPL-3.0）授權。
+
+Copyright (C) 2025 Alex Newman (@thedotmack). All rights reserved.
+
+完整詳情請參閱 [LICENSE](LICENSE) 檔案。
+
+**這代表什麼：**
+
+- 您可以自由使用、修改與散佈此軟體
+- 如果您修改並部署於網路伺服器上，您必須公開您的原始碼
+- 衍生作品也必須採用 AGPL-3.0 授權
+- 本軟體不提供任何擔保
+
+**關於 Ragtime 的說明**：`ragtime/` 目錄採用 **PolyForm Noncommercial License 1.0.0** 另行授權。詳情請參閱 [ragtime/LICENSE](ragtime/LICENSE)。
+
+---
+
+## 支援
+
+- **文件**：[docs/](docs/)
+- **Issues**：[GitHub Issues](https://github.com/thedotmack/claude-mem/issues)
+- **儲存庫**：[github.com/thedotmack/claude-mem](https://github.com/thedotmack/claude-mem)
+- **官方 X 帳號**：[@Claude_Memory](https://x.com/Claude_Memory)
+- **官方 Discord**：[加入 Discord](https://discord.com/invite/J4wttp9vDu)
+- **作者**：Alex Newman ([@thedotmack](https://github.com/thedotmack))
+
+---
+
+**使用 Claude Agent SDK 建置** | **由 Claude Code 驅動** | **以 TypeScript 開發**

docs/i18n/README.zh.md

@@ -15,6 +15,7 @@
 
 <p align="center">
   <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
   <a href="README.ja.md">🇯🇵 日本語</a> •
   <a href="README.pt-br.md">🇧🇷 Português</a> •
   <a href="README.ko.md">🇰🇷 한국어</a> •
@@ -34,6 +35,7 @@
   <a href="README.th.md">🇹🇭 ไทย</a> •
   <a href="README.hi.md">🇮🇳 हिन्दी</a> •
   <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
   <a href="README.ro.md">🇷🇴 Română</a> •
   <a href="README.sv.md">🇸🇪 Svenska</a> •
   <a href="README.it.md">🇮🇹 Italiano</a> •
@@ -126,7 +128,7 @@
 
 ## 文档
 
-📚 **[查看完整文档](docs/)** - 在 GitHub 上浏览 Markdown 文档
+📚 **[查看完整文档](https://docs.claude-mem.ai/)** - 在官方网站浏览
 
 ### 入门指南
 
@@ -212,7 +214,7 @@ Claude-Mem 通过 mem-search 技能提供智能搜索,当您询问过去的工
 
 Claude-Mem 提供**测试版渠道**,包含实验性功能,如**无尽模式**(用于扩展会话的仿生记忆架构)。从 Web 查看器界面 http://localhost:37777 → 设置 切换稳定版和测试版。
 
-详见**[测试版功能文档](https://docs.claude-mem.ai/beta-features)**了解无尽模式的详细信息和试用方法。
+详见 **[测试版功能文档](https://docs.claude-mem.ai/beta-features)** 了解无尽模式的详细信息和试用方法。
 
 ---
 
@@ -230,13 +232,13 @@ Claude-Mem 提供**测试版渠道**,包含实验性功能,如**无尽模式**(
 
 设置在 `~/.claude-mem/settings.json` 中管理(首次运行时自动创建默认设置)。可配置 AI 模型、worker 端口、数据目录、日志级别和上下文注入设置。
 
-详见**[配置指南](https://docs.claude-mem.ai/configuration)**了解所有可用设置和示例。
+详见 **[配置指南](https://docs.claude-mem.ai/configuration)** 了解所有可用设置和示例。
 
 ---
 
 ## 开发
 
-详见**[开发指南](https://docs.claude-mem.ai/development)**了解构建说明、测试和贡献工作流程。
+详见 **[开发指南](https://docs.claude-mem.ai/development)** 了解构建说明、测试和贡献工作流程。
 
 ---
 
@@ -244,7 +246,7 @@ Claude-Mem 提供**测试版渠道**,包含实验性功能,如**无尽模式**(
 
 如果遇到问题,向 Claude 描述问题,troubleshoot 技能将自动诊断并提供修复方案。
 
-详见**[故障排除指南](https://docs.claude-mem.ai/troubleshooting)**了解常见问题和解决方案。
+详见 **[故障排除指南](https://docs.claude-mem.ai/troubleshooting)** 了解常见问题和解决方案。
 
 ---
 
@@ -301,4 +303,4 @@ Copyright (C) 2025 Alex Newman (@thedotmack)。保留所有权利。
 
 **使用 Claude Agent SDK 构建** | **由 Claude Code 驱动** | **使用 TypeScript 制作**
 
----
+---

docs/i18n/pt.md

@@ -0,0 +1,305 @@
+🌐 Esta é uma tradução manual por mig4ng. Correções da comunidade são bem-vindas!
+
+---
+<h1 align="center">
+  <br>
+  <a href="https://github.com/thedotmack/claude-mem">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-dark-mode.webp">
+      <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-light-mode.webp">
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/claude-mem-logo-for-light-mode.webp" alt="Claude-Mem" width="400">
+    </picture>
+  </a>
+  <br>
+</h1>
+
+<p align="center">
+  <a href="README.zh.md">🇨🇳 中文</a> •
+  <a href="README.zh-tw.md">🇹🇼 繁體中文</a> •
+  <a href="README.ja.md">🇯🇵 日本語</a> •
+  <a href="README.pt.md">🇵🇹 Português</a> •
+  <a href="README.pt-br.md">🇧🇷 Português (Brasil)</a> •
+  <a href="README.ko.md">🇰🇷 한국어</a> •
+  <a href="README.es.md">🇪🇸 Español</a> •
+  <a href="README.de.md">🇩🇪 Deutsch</a> •
+  <a href="README.fr.md">🇫🇷 Français</a>
+  <a href="README.he.md">🇮🇱 עברית</a> •
+  <a href="README.ar.md">🇸🇦 العربية</a> •
+  <a href="README.ru.md">🇷🇺 Русский</a> •
+  <a href="README.pl.md">🇵🇱 Polski</a> •
+  <a href="README.cs.md">🇨🇿 Čeština</a> •
+  <a href="README.nl.md">🇳🇱 Nederlands</a> •
+  <a href="README.tr.md">🇹🇷 Türkçe</a> •
+  <a href="README.uk.md">🇺🇦 Українська</a> •
+  <a href="README.vi.md">🇻🇳 Tiếng Việt</a> •
+  <a href="README.id.md">🇮🇩 Indonesia</a> •
+  <a href="README.th.md">🇹🇭 ไทย</a> •
+  <a href="README.hi.md">🇮🇳 हिन्दी</a> •
+  <a href="README.bn.md">🇧🇩 বাংলা</a> •
+  <a href="README.ur.md">🇵🇰 اردو</a> •
+  <a href="README.ro.md">🇷🇴 Română</a> •
+  <a href="README.sv.md">🇸🇪 Svenska</a> •
+  <a href="README.it.md">🇮🇹 Italiano</a> •
+  <a href="README.el.md">🇬🇷 Ελληνικά</a> •
+  <a href="README.hu.md">🇭🇺 Magyar</a> •
+  <a href="README.fi.md">🇫🇮 Suomi</a> •
+  <a href="README.da.md">🇩🇰 Dansk</a> •
+  <a href="README.no.md">🇳🇴 Norsk</a>
+</p>
+
+<h4 align="center">Sistema de compressão de memória persistente construído para <a href="https://claude.com/claude-code" target="_blank">Claude Code</a>.</h4>
+
+<p align="center">
+  <a href="LICENSE">
+    <img src="https://img.shields.io/badge/License-AGPL%203.0-blue.svg" alt="License">
+  </a>
+  <a href="package.json">
+    <img src="https://img.shields.io/badge/version-6.5.0-green.svg" alt="Version">
+  </a>
+  <a href="package.json">
+    <img src="https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen.svg" alt="Node">
+  </a>
+  <a href="https://github.com/thedotmack/awesome-claude-code">
+    <img src="https://awesome.re/mentioned-badge.svg" alt="Mentioned in Awesome Claude Code">
+  </a>
+</p>
+
+<p align="center">
+  <a href="https://trendshift.io/repositories/15496" target="_blank">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge-dark.svg">
+      <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge.svg">
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/trendshift-badge.svg" alt="thedotmack/claude-mem | Trendshift" width="250" height="55"/>
+    </picture>
+  </a>
+</p>
+
+<br>
+
+<p align="center">
+  <a href="https://github.com/thedotmack/claude-mem">
+    <picture>
+      <img src="https://raw.githubusercontent.com/thedotmack/claude-mem/main/docs/public/cm-preview.gif" alt="Claude-Mem Preview" width="800">
+    </picture>
+  </a>
+</p>
+
+<p align="center">
+  <a href="#início-rápido">Início Rápido</a> •
+  <a href="#como-funciona">Como Funciona</a> •
+  <a href="#ferramentas-de-procura-mcp">Ferramentas de Procura</a> •
+  <a href="#documentação">Documentação</a> •
+  <a href="#configuração">Configuração</a> •
+  <a href="#solução-de-problemas">Solução de Problemas</a> •
+  <a href="#licença">Licença</a>
+</p>
+
+<p align="center">
+  Claude-Mem preserva o contexto perfeitamente entre sessões, capturando automaticamente observações de uso de ferramentas, gerando resumos semânticos e disponibilizando-os para sessões futuras. Isso permite que Claude mantenha a continuidade do conhecimento sobre projetos mesmo após o término ou reconexão de sessões.
+</p>
+
+---
+
+## Início Rápido
+
+Inicie uma nova sessão do Claude Code no terminal e digite os seguintes comandos:
+
+```
+> /plugin marketplace add thedotmack/claude-mem
+
+> /plugin install claude-mem
+```
+
+Reinicie o Claude Code. O contexto de sessões anteriores aparecerá automaticamente em novas sessões.
+
+**Principais Recursos:**
+
+- 🧠 **Memória Persistente** - O contexto sobrevive entre sessões
+- 📊 **Divulgação Progressiva** - Recuperação de memória em camadas com visibilidade de custo de tokens
+- 🔍 **Procura Baseada em Skill** - Consulte seu histórico de projeto com a skill mem-search
+- 🖥️ **Interface Web de Visualização** - Fluxo de memória em tempo real em http://localhost:37777
+- 💻 **Skill para Claude Desktop** - Busque memória em conversas do Claude Desktop
+- 🔒 **Controle de Privacidade** - Use tags `<private>` para excluir conteúdo sensível do armazenamento
+- ⚙️ **Configuração de Contexto** - Controle refinado sobre qual contexto é injetado
+- 🤖 **Operação Automática** - Nenhuma intervenção manual necessária
+- 🔗 **Citações** - Referencie observações passadas com IDs (acesse via http://localhost:37777/api/observation/{id} ou visualize todas no visualizador web em http://localhost:37777)
+- 🧪 **Canal Beta** - Experimente recursos experimentais como o Endless Mode através da troca de versões
+
+---
+
+## Documentação
+
+📚 **[Ver Documentação Completa](https://docs.claude-mem.ai/)** - Navegar no site oficial
+
+### Começando
+
+- **[Guia de Instalação](https://docs.claude-mem.ai/installation)** - Início rápido e instalação avançada
+- **[Guia de Uso](https://docs.claude-mem.ai/usage/getting-started)** - Como Claude-Mem funciona automaticamente
+- **[Ferramentas de Procura](https://docs.claude-mem.ai/usage/search-tools)** - Consulte seu histórico de projeto com linguagem natural
+- **[Recursos Beta](https://docs.claude-mem.ai/beta-features)** - Experimente recursos experimentais como o Endless Mode
+
+### Melhores Práticas
+
+- **[Engenharia de Contexto](https://docs.claude-mem.ai/context-engineering)** - Princípios de otimização de contexto para agentes de IA
+- **[Divulgação Progressiva](https://docs.claude-mem.ai/progressive-disclosure)** - Filosofia por trás da estratégia de preparação de contexto do Claude-Mem
+
+### Arquitetura
+
+- **[Visão Geral](https://docs.claude-mem.ai/architecture/overview)** - Componentes do sistema e fluxo de dados
+- **[Evolução da Arquitetura](https://docs.claude-mem.ai/architecture-evolution)** - A jornada da v3 à v5
+- **[Arquitetura de Hooks](https://docs.claude-mem.ai/hooks-architecture)** - Como Claude-Mem usa hooks de ciclo de vida
+- **[Referência de Hooks](https://docs.claude-mem.ai/architecture/hooks)** - 7 scripts de hook explicados
+- **[Serviço Worker](https://docs.claude-mem.ai/architecture/worker-service)** - API HTTP e gerenciamento do Bun
+- **[Banco de Dados](https://docs.claude-mem.ai/architecture/database)** - Schema SQLite e Procura FTS5
+- **[Arquitetura de Procura](https://docs.claude-mem.ai/architecture/search-architecture)** - Procura híbrida com banco de dados vetorial Chroma
+
+### Configuração e Desenvolvimento
+
+- **[Configuração](https://docs.claude-mem.ai/configuration)** - Variáveis de ambiente e configurações
+- **[Desenvolvimento](https://docs.claude-mem.ai/development)** - Build, testes e contribuição
+- **[Solução de Problemas](https://docs.claude-mem.ai/troubleshooting)** - Problemas comuns e soluções
+
+---
+
+## Como Funciona
+
+**Componentes Principais:**
+
+1. **5 Hooks de Ciclo de Vida** - SessionStart, UserPromptSubmit, PostToolUse, Stop, SessionEnd (6 scripts de hook)
+2. **Instalação Inteligente** - Verificador de dependências em cache (script pré-hook, não um hook de ciclo de vida)
+3. **Serviço Worker** - API HTTP na porta 37777 com interface de visualização web e 10 endpoints de Procura, gerenciado pelo Bun
+4. **Banco de Dados SQLite** - Armazena sessões, observações, resumos
+5. **Skill mem-search** - Consultas em linguagem natural com divulgação progressiva
+6. **Banco de Dados Vetorial Chroma** - Procura híbrida semântica + palavra-chave para recuperação inteligente de contexto
+
+Veja [Visão Geral da Arquitetura](https://docs.claude-mem.ai/architecture/overview) para detalhes.
+
+---
+
+## Skill mem-search
+
+Claude-Mem fornece Procura inteligente através da skill mem-search que se auto-invoca quando você pergunta sobre trabalhos anteriores:
+
+**Como Funciona:**
+- Pergunte naturalmente: *"O que fizemos na última sessão?"* ou *"Já corrigimos esse bug antes?"*
+- Claude invoca automaticamente a skill mem-search para encontrar contexto relevante
+
+**Operações de Procura Disponíveis:**
+
+1. **Search Observations** - Procura de texto completo em observações
+2. **Search Sessions** - Procura de texto completo em resumos de sessão
+3. **Search Prompts** - Procura em solicitações brutas do usuário
+4. **By Concept** - Encontre por tags de conceito (discovery, problem-solution, pattern, etc.)
+5. **By File** - Encontre observações que referenciam arquivos específicos
+6. **By Type** - Encontre por tipo (decision, bugfix, feature, refactor, discovery, change)
+7. **Recent Context** - Obtenha contexto de sessão recente para um projeto
+8. **Timeline** - Obtenha linha do tempo unificada de contexto em torno de um ponto específico no tempo
+9. **Timeline by Query** - Busque observações e obtenha contexto de linha do tempo em torno da melhor correspondência
+10. **API Help** - Obtenha documentação da API de Procura
+
+**Exemplos de Consultas em Linguagem Natural:**
+
+```
+"Quais bugs corrigimos na última sessão?"
+"Como implementamos a autenticação?"
+"Quais mudanças foram feitas em worker-service.ts?"
+"Mostre-me trabalhos recentes neste projeto"
+"O que estava acontecendo quando adicionamos a interface de visualização?"
+```
+
+Veja [Guia de Ferramentas de Procura](https://docs.claude-mem.ai/usage/search-tools) para exemplos detalhados.
+
+---
+
+## Recursos Beta
+
+Claude-Mem oferece um **canal beta** com recursos experimentais como **Endless Mode** (arquitetura de memória biomimética para sessões estendidas). Alterne entre versões estável e beta pela interface de visualização web em http://localhost:37777 → Settings.
+
+Veja **[Documentação de Recursos Beta](https://docs.claude-mem.ai/beta-features)** para detalhes sobre o Endless Mode e como experimentá-lo.
+
+---
+
+## Requisitos do Sistema
+
+- **Node.js**: 18.0.0 ou superior
+- **Claude Code**: Versão mais recente com suporte a plugins
+- **Bun**: Runtime JavaScript e gerenciador de processos (instalado automaticamente se ausente)
+- **uv**: Gerenciador de pacotes Python para Procura vetorial (instalado automaticamente se ausente)
+- **SQLite 3**: Para armazenamento persistente (incluído)
+
+---
+
+## Configuração
+
+As configurações são gerenciadas em `~/.claude-mem/settings.json` (criado automaticamente com valores padrão na primeira execução). Configure modelo de IA, porta do worker, diretório de dados, nível de log e configurações de injeção de contexto.
+
+Veja o **[Guia de Configuração](https://docs.claude-mem.ai/configuration)** para todas as configurações disponíveis e exemplos.
+
+---
+
+## Desenvolvimento
+
+Veja o **[Guia de Desenvolvimento](https://docs.claude-mem.ai/development)** para instruções de build, testes e fluxo de contribuição.
+
+---
+
+## Solução de Problemas
+
+Se você estiver enfrentando problemas, descreva o problema para Claude e a skill troubleshoot diagnosticará automaticamente e fornecerá correções.
+
+Veja o **[Guia de Solução de Problemas](https://docs.claude-mem.ai/troubleshooting)** para problemas comuns e soluções.
+
+---
+
+## Relatos de Bug
+
+Crie relatos de bug abrangentes com o gerador automatizado:
+
+```bash
+cd ~/.claude/plugins/marketplaces/thedotmack
+npm run bug-report
+```
+
+## Contribuindo
+
+Contribuições são bem-vindas! Por favor:
+
+1. Faça um fork do repositório
+2. Crie uma branch de feature
+3. Faça suas alterações com testes
+4. Atualize a documentação
+5. Envie um Pull Request
+
+Veja [Guia de Desenvolvimento](https://docs.claude-mem.ai/development) para o fluxo de contribuição.
+
+---
+
+## Licença
+
+Este projeto está licenciado sob a **GNU Affero General Public License v3.0** (AGPL-3.0).
+
+Copyright (C) 2025 Alex Newman (@thedotmack). Todos os direitos reservados.
+
+Veja o arquivo [LICENSE](LICENSE) para detalhes completos.
+
+**O Que Isso Significa:**
+
+- Você pode usar, modificar e distribuir este software livremente
+- Se você modificar e implantar em um servidor de rede, você deve disponibilizar seu código-fonte
+- Trabalhos derivados também devem ser licenciados sob AGPL-3.0
+- NÃO HÁ GARANTIA para este software
+
+**Nota sobre Ragtime**: O diretório `ragtime/` é licenciado separadamente sob a **PolyForm Noncommercial License 1.0.0**. Veja [ragtime/LICENSE](ragtime/LICENSE) para detalhes.
+
+---
+
+## Suporte
+
+- **Documentação**: [docs/](docs/)
+- **Issues**: [GitHub Issues](https://github.com/thedotmack/claude-mem/issues)
+- **Repositório**: [github.com/thedotmack/claude-mem](https://github.com/thedotmack/claude-mem)
+- **Autor**: Alex Newman ([@thedotmack](https://github.com/thedotmack))
+
+---
+
+**Construído com Claude Agent SDK** | **Desenvolvido por Claude Code** | **Feito com TypeScript** | **Editado por mig4ng**

docs/public/configuration.mdx

@@ -26,7 +26,7 @@ Settings are managed in `~/.claude-mem/settings.json`. The file is auto-created
 | Setting                       | Default                         | Description                           |
 |-------------------------------|---------------------------------|---------------------------------------|
 | `CLAUDE_MEM_GEMINI_API_KEY`   | —                               | Gemini API key ([get free key](https://aistudio.google.com/app/apikey)) |
-| `CLAUDE_MEM_GEMINI_MODEL`     | `gemini-2.5-flash-lite`          | Gemini model: `gemini-2.5-flash-lite`, `gemini-2.5-flash`, `gemini-3-flash` |
+| `CLAUDE_MEM_GEMINI_MODEL`     | `gemini-2.5-flash-lite`          | Gemini model: `gemini-2.5-flash-lite`, `gemini-2.5-flash`, `gemini-3-flash-preview` |
 
 See [Gemini Provider](usage/gemini-provider) for detailed configuration and free tier information.
 

docs/public/cursor/gemini-setup.mdx

@@ -103,7 +103,7 @@ Open http://localhost:37777 to see the memory viewer.
 |-------|---------------|-------|
 | `gemini-2.5-flash-lite` | 10 (4,000 with billing) | **Default.** Fastest, highest free tier RPM |
 | `gemini-2.5-flash` | 5 (1,000 with billing) | Higher capability |
-| `gemini-3-flash` | 5 (1,000 with billing) | Latest model |
+| `gemini-3-flash-preview` | 5 (1,000 with billing) | Latest model |
 
 To change the model, update your settings:
 

docs/public/docs.json

@@ -73,7 +73,8 @@
           "modes",
           "development",
           "troubleshooting",
-          "platform-integration"
+          "platform-integration",
+          "openclaw-integration"
         ]
       },
       {

docs/public/installation.mdx

@@ -22,6 +22,10 @@ That's it! The plugin will automatically:
 
 Start a new Claude Code session and you'll see context from previous sessions automatically loaded.
 
+> **Important:** Claude-Mem is published on npm, but running `npm install -g claude-mem` installs the
+> **SDK/library only**. It does **not** register plugin hooks or start the worker service.
+> To use Claude-Mem as a persistent memory plugin, always install via the `/plugin` commands above.
+
 ## System Requirements
 
 - **Node.js**: 18.0.0 or higher

docs/public/modes.mdx

@@ -65,6 +65,7 @@ Inherits all behavior from Code Mode but instructs Claude to generate **all** me
 | **Hindi** | `code--hi` | हिन्दी |
 | **Hungarian** | `code--hu` | Magyar |
 | **Indonesian** | `code--id` | Bahasa Indonesia |
+| **Urdu** | `code--ur` | اردو |
 | **Italian** | `code--it` | Italiano |
 | **Japanese** | `code--ja` | 日本語 |
 | **Korean** | `code--ko` | 한국어 |

docs/public/openclaw-integration.mdx

@@ -0,0 +1,385 @@
+---
+title: OpenClaw Integration
+description: Persistent memory for OpenClaw agents — observation recording, MEMORY.md live sync, and real-time observation feeds
+icon: dragon
+---
+
+## Overview
+
+The OpenClaw plugin gives claude-mem persistent memory to agents running on the [OpenClaw](https://openclaw.ai) gateway. It handles three things:
+
+1. **Observation recording** — Captures tool usage from OpenClaw's embedded runner and sends it to the claude-mem worker for AI processing
+2. **MEMORY.md live sync** — Writes a continuously-updated timeline to each agent's workspace so agents always have context from previous sessions
+3. **Observation feed** — Streams new observations to messaging channels (Telegram, Discord, Slack, etc.) in real-time via SSE
+
+<Info>
+OpenClaw's embedded runner (`pi-embedded`) calls the Anthropic API directly without spawning a `claude` process, so claude-mem's standard hooks never fire. This plugin bridges that gap by using OpenClaw's event system to capture the same data.
+</Info>
+
+## How It Works
+
+```plaintext
+OpenClaw Gateway
+  │
+  ├── before_agent_start ──→ Sync MEMORY.md + Init session
+  ├── tool_result_persist ──→ Record observation + Re-sync MEMORY.md
+  ├── agent_end ────────────→ Summarize + Complete session
+  └── gateway_start ────────→ Reset session tracking
+                    │
+                    ▼
+         Claude-Mem Worker (localhost:37777)
+           ├── POST /api/sessions/init
+           ├── POST /api/sessions/observations
+           ├── POST /api/sessions/summarize
+           ├── POST /api/sessions/complete
+           ├── GET  /api/context/inject ──→ MEMORY.md content
+           └── GET  /stream ─────────────→ SSE → Messaging channels
+```
+
+### Event Lifecycle
+
+<Steps>
+  <Step title="Agent starts (before_agent_start)">
+    When an OpenClaw agent starts, the plugin does two things:
+
+    1. **Syncs MEMORY.md** — Fetches the latest timeline from the worker's `/api/context/inject` endpoint and writes it to `MEMORY.md` in the agent's workspace directory. This gives the agent context from all previous sessions before it starts working.
+
+    2. **Initializes a session** — Sends the user prompt to `POST /api/sessions/init` so the worker can create a new session and start processing.
+
+    Short prompts (under 10 characters) skip session init but still sync MEMORY.md.
+  </Step>
+  <Step title="Tool use recorded (tool_result_persist)">
+    Every time the agent uses a tool (Read, Write, Bash, etc.), the plugin:
+
+    1. **Sends the observation** to `POST /api/sessions/observations` with the tool name, input, and truncated response (max 1000 chars)
+    2. **Re-syncs MEMORY.md** with the latest timeline from the worker
+
+    Both operations are fire-and-forget — they don't block the agent from continuing work. The MEMORY.md file gets progressively richer as the session continues.
+
+    Tools prefixed with `memory_` are skipped to avoid recursive recording.
+  </Step>
+  <Step title="Agent finishes (agent_end)">
+    When the agent completes, the plugin extracts the last assistant message and sends it to `POST /api/sessions/summarize`, then calls `POST /api/sessions/complete` to close the session. Both are fire-and-forget.
+  </Step>
+  <Step title="Gateway restarts (gateway_start)">
+    Clears all session tracking (session IDs, workspace directory mappings) so agents get fresh state after a gateway restart.
+  </Step>
+</Steps>
+
+### MEMORY.md Live Sync
+
+The plugin writes a `MEMORY.md` file to each agent's workspace directory containing the full timeline of observations and summaries from previous sessions. This file is updated:
+
+- On every `before_agent_start` event (agent gets fresh context before starting)
+- On every `tool_result_persist` event (context stays current during the session)
+
+The content comes from the worker's `GET /api/context/inject?projects=<project>` endpoint, which generates a formatted markdown timeline from the SQLite database.
+
+<Info>
+MEMORY.md updates are fire-and-forget. They run in the background without blocking the agent. The file reflects whatever the worker has processed so far — it doesn't wait for the current observation to be fully processed before writing.
+</Info>
+
+### Observation Feed (SSE → Messaging)
+
+The plugin runs a background service that connects to the worker's SSE stream (`GET /stream`) and forwards `new_observation` events to a configured messaging channel. This lets you monitor what your agents are learning in real-time from Telegram, Discord, Slack, or any supported OpenClaw channel.
+
+The SSE connection uses exponential backoff (1s → 30s) for automatic reconnection.
+
+## Setting Up the Observation Feed
+
+The observation feed sends a formatted message to your OpenClaw channel every time claude-mem creates a new observation. Each message includes the observation title and subtitle so you can follow along as your agents work.
+
+Messages look like this in your channel:
+
+```
+🧠 Claude-Mem Observation
+**Implemented retry logic for API client**
+Added exponential backoff with configurable max retries to handle transient failures
+```
+
+### Step 1: Choose your channel
+
+The observation feed works with any channel that your OpenClaw gateway has configured. You need two pieces of information:
+
+- **Channel type** — The name of the channel plugin registered with OpenClaw (e.g., `telegram`, `discord`, `slack`, `signal`, `whatsapp`, `line`)
+- **Target ID** — The chat ID, channel ID, or user ID where messages should be sent
+
+<AccordionGroup>
+  <Accordion title="Telegram" icon="telegram">
+    **Channel type:** `telegram`
+
+    **Target ID:** Your Telegram chat ID (numeric). To find it:
+    1. Message [@userinfobot](https://t.me/userinfobot) on Telegram
+    2. It will reply with your chat ID (e.g., `123456789`)
+    3. For group chats, the ID is negative (e.g., `-1001234567890`)
+
+    ```json
+    "observationFeed": {
+      "enabled": true,
+      "channel": "telegram",
+      "to": "123456789"
+    }
+    ```
+  </Accordion>
+
+  <Accordion title="Discord" icon="discord">
+    **Channel type:** `discord`
+
+    **Target ID:** The Discord channel ID. To find it:
+    1. Enable Developer Mode in Discord (Settings → Advanced → Developer Mode)
+    2. Right-click the channel → Copy Channel ID
+
+    ```json
+    "observationFeed": {
+      "enabled": true,
+      "channel": "discord",
+      "to": "1234567890123456789"
+    }
+    ```
+  </Accordion>
+
+  <Accordion title="Slack" icon="slack">
+    **Channel type:** `slack`
+
+    **Target ID:** The Slack channel ID (not the channel name). To find it:
+    1. Open the channel in Slack
+    2. Click the channel name at the top
+    3. Scroll to the bottom of the channel details — the ID looks like `C01ABC2DEFG`
+
+    ```json
+    "observationFeed": {
+      "enabled": true,
+      "channel": "slack",
+      "to": "C01ABC2DEFG"
+    }
+    ```
+  </Accordion>
+
+  <Accordion title="Signal" icon="signal-messenger">
+    **Channel type:** `signal`
+
+    **Target ID:** The Signal phone number or group ID configured in your OpenClaw gateway.
+
+    ```json
+    "observationFeed": {
+      "enabled": true,
+      "channel": "signal",
+      "to": "+1234567890"
+    }
+    ```
+  </Accordion>
+
+  <Accordion title="WhatsApp" icon="whatsapp">
+    **Channel type:** `whatsapp`
+
+    **Target ID:** The WhatsApp phone number or group JID configured in your OpenClaw gateway.
+
+    ```json
+    "observationFeed": {
+      "enabled": true,
+      "channel": "whatsapp",
+      "to": "+1234567890"
+    }
+    ```
+  </Accordion>
+
+  <Accordion title="LINE" icon="line">
+    **Channel type:** `line`
+
+    **Target ID:** The LINE user ID or group ID from the LINE Developer Console.
+
+    ```json
+    "observationFeed": {
+      "enabled": true,
+      "channel": "line",
+      "to": "U1234567890abcdef"
+    }
+    ```
+  </Accordion>
+</AccordionGroup>
+
+### Step 2: Add the config to your gateway
+
+Add the `observationFeed` block to your claude-mem plugin config in your OpenClaw gateway configuration:
+
+```json
+{
+  "plugins": {
+    "claude-mem": {
+      "enabled": true,
+      "config": {
+        "project": "my-project",
+        "observationFeed": {
+          "enabled": true,
+          "channel": "telegram",
+          "to": "123456789"
+        }
+      }
+    }
+  }
+}
+```
+
+<Warning>
+The `channel` value must match a channel plugin that is already configured and running on your OpenClaw gateway. If the channel isn't registered, you'll see `Unknown channel type: <channel>` in the logs.
+</Warning>
+
+### Step 3: Verify the connection
+
+After starting the gateway, check that the feed is connected:
+
+1. **Check the logs** — You should see:
+   ```
+   [claude-mem] Observation feed starting — channel: telegram, target: 123456789
+   [claude-mem] Connecting to SSE stream at http://localhost:37777/stream
+   [claude-mem] Connected to SSE stream
+   ```
+
+2. **Use the status command** — Run `/claude_mem_feed` in any OpenClaw chat to see:
+   ```
+   Claude-Mem Observation Feed
+   Enabled: yes
+   Channel: telegram
+   Target: 123456789
+   Connection: connected
+   ```
+
+3. **Trigger a test** — Have an agent do some work. When the worker processes the tool usage into an observation, you'll receive a message in your configured channel.
+
+<Info>
+The feed only sends `new_observation` events — not raw tool usage. Observations are generated asynchronously by the worker's AI agent, so there's a 1-2 second delay between tool use and the observation message appearing in your channel.
+</Info>
+
+### Troubleshooting the Feed
+
+| Symptom | Cause | Fix |
+|---------|-------|-----|
+| `Connection: disconnected` | Worker not running or wrong port | Check `workerPort` config, run `npm run worker:status` |
+| `Connection: reconnecting` | Worker was running but connection dropped | The plugin auto-reconnects with backoff — wait up to 30s |
+| `Unknown channel type` in logs | Channel plugin not loaded on gateway | Verify your OpenClaw gateway has the channel plugin configured |
+| No messages appearing | Feed connected but no observations being created | Check that agents are running and the worker is processing observations |
+| `Observation feed disabled` in logs | `enabled` is `false` or missing | Set `observationFeed.enabled` to `true` |
+| `Observation feed misconfigured` in logs | Missing `channel` or `to` | Both `channel` and `to` are required |
+
+## Installation
+
+Run this one-liner to install everything automatically:
+
+```bash
+curl -fsSL https://install.cmem.ai/openclaw.sh | bash
+```
+
+The installer handles dependency checks (Bun, uv), plugin installation, memory slot configuration, AI provider setup, worker startup, and optional observation feed configuration.
+
+You can also pre-select options:
+
+```bash
+# With a specific AI provider
+curl -fsSL https://install.cmem.ai/openclaw.sh | bash -s -- --provider=gemini --api-key=YOUR_KEY
+
+# Fully unattended (defaults to Claude Max Plan)
+curl -fsSL https://install.cmem.ai/openclaw.sh | bash -s -- --non-interactive
+
+# Upgrade existing installation
+curl -fsSL https://install.cmem.ai/openclaw.sh | bash -s -- --upgrade
+```
+
+### Manual Configuration
+
+Add `claude-mem` to your OpenClaw gateway's plugin configuration:
+
+```json
+{
+  "plugins": {
+    "claude-mem": {
+      "enabled": true,
+      "config": {
+        "project": "my-project",
+        "syncMemoryFile": true,
+        "workerPort": 37777,
+        "observationFeed": {
+          "enabled": true,
+          "channel": "telegram",
+          "to": "your-chat-id"
+        }
+      }
+    }
+  }
+}
+```
+
+<Note>
+The claude-mem worker service must be running on the same machine as the OpenClaw gateway. The plugin communicates with it via HTTP on `localhost:37777`.
+</Note>
+
+## Configuration
+
+<ParamField body="project" type="string" default="openclaw">
+  Project name for scoping observations in the memory database. All observations from this gateway will be stored under this project name.
+</ParamField>
+
+<ParamField body="syncMemoryFile" type="boolean" default={true}>
+  Enable automatic MEMORY.md sync to agent workspaces. Set to `false` if you don't want the plugin writing files to workspace directories.
+</ParamField>
+
+<ParamField body="workerPort" type="number" default={37777}>
+  Port for the claude-mem worker service. Override if your worker runs on a non-default port.
+</ParamField>
+
+<ParamField body="observationFeed.enabled" type="boolean" default={false}>
+  Enable live observation streaming to messaging channels.
+</ParamField>
+
+<ParamField body="observationFeed.channel" type="string">
+  Channel type: `telegram`, `discord`, `signal`, `slack`, `whatsapp`, `line`
+</ParamField>
+
+<ParamField body="observationFeed.to" type="string">
+  Target chat/user/channel ID to send observations to.
+</ParamField>
+
+## Commands
+
+### /claude_mem_feed
+
+Show or toggle the observation feed status.
+
+```
+/claude_mem_feed        # Show current status
+/claude_mem_feed on     # Request enable
+/claude_mem_feed off    # Request disable
+```
+
+### /claude_mem_status
+
+Check worker health and session status.
+
+```
+/claude_mem_status
+```
+
+Returns worker status, port, active session count, and observation feed connection state.
+
+## Architecture
+
+The plugin uses HTTP calls to the already-running claude-mem worker service rather than spawning subprocesses. This means:
+
+- No `bun` dependency required on the gateway
+- No process spawn overhead per event
+- Uses the same worker API that Claude Code hooks use
+- All operations are non-blocking (fire-and-forget where possible)
+
+### Session Tracking
+
+Each OpenClaw agent session gets a unique `contentSessionId` (format: `openclaw-<sessionKey>-<timestamp>`) that maps to a claude-mem session in the worker. The plugin tracks:
+
+- `sessionIds` — Maps OpenClaw session keys to content session IDs
+- `workspaceDirsBySessionKey` — Maps session keys to workspace directories so `tool_result_persist` events can sync MEMORY.md even when the event context doesn't include `workspaceDir`
+
+Both maps are cleared on `gateway_start`.
+
+## Requirements
+
+- Claude-mem worker service running on `localhost:37777` (or configured port)
+- OpenClaw gateway with plugin support
+- Network access between gateway and worker (localhost only)

docs/public/usage/gemini-provider.mdx

@@ -39,7 +39,7 @@ Claude-mem supports Google's Gemini API as an alternative to the Claude Agent SD
 |---------|--------|---------|-------------|
 | `CLAUDE_MEM_PROVIDER` | `claude`, `gemini` | `claude` | AI provider for observation extraction |
 | `CLAUDE_MEM_GEMINI_API_KEY` | string | — | Your Gemini API key |
-| `CLAUDE_MEM_GEMINI_MODEL` | `gemini-2.5-flash-lite`, `gemini-2.5-flash`, `gemini-3-flash` | `gemini-2.5-flash-lite` | Gemini model to use |
+| `CLAUDE_MEM_GEMINI_MODEL` | `gemini-2.5-flash-lite`, `gemini-2.5-flash`, `gemini-3-flash-preview` | `gemini-2.5-flash-lite` | Gemini model to use |
 | `CLAUDE_MEM_GEMINI_BILLING_ENABLED` | `true`, `false` | `false` | Skip rate limiting if billing is enabled on Google Cloud |
 
 ### Using the Settings UI
@@ -79,7 +79,7 @@ The settings file takes precedence over the environment variable.
 |-------|--------------|-------|
 | `gemini-2.5-flash-lite` | 10 | Default, recommended for free tier (highest RPM) |
 | `gemini-2.5-flash` | 5 | Higher capability, lower rate limit |
-| `gemini-3-flash` | 5 | Latest model, lower rate limit |
+| `gemini-3-flash-preview` | 5 | Latest model, lower rate limit |
 
 ## Provider Switching
 
@@ -139,7 +139,7 @@ Google has two rate limit tiers for free usage:
 |-------|-----|-----|
 | gemini-2.5-flash-lite | 10 | 250K |
 | gemini-2.5-flash | 5 | 250K |
-| gemini-3-flash | 5 | 250K |
+| gemini-3-flash-preview | 5 | 250K |
 
 Claude-mem enforces these limits automatically with built-in delays between requests. Processing may be slower but stays within limits.
 
@@ -149,7 +149,7 @@ Claude-mem enforces these limits automatically with built-in delays between requ
 |-------|-----|-----|
 | gemini-2.5-flash-lite | 4,000 | 4M |
 | gemini-2.5-flash | 1,000 | 1M |
-| gemini-3-flash | 1,000 | 1M |
+| gemini-3-flash-preview | 1,000 | 1M |
 
 <Tip>
 **Recommended**: Enable billing on your Google Cloud project to unlock much higher rate limits. You won't be charged unless you exceed the generous free quota. This allows claude-mem to process observations instantly instead of waiting between requests.

install/.gitignore

@@ -0,0 +1,2 @@
+.vercel
+public/openclaw.sh

install/public/install.sh

@@ -0,0 +1,59 @@
+#!/bin/bash
+set -euo pipefail
+
+# claude-mem installer bootstrap
+# Usage: curl -fsSL https://install.cmem.ai | bash
+#   or:  curl -fsSL https://install.cmem.ai | bash -s -- --provider=gemini --api-key=YOUR_KEY
+
+INSTALLER_URL="https://raw.githubusercontent.com/thedotmack/claude-mem/main/installer/dist/index.js"
+
+# Colors
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+CYAN='\033[0;36m'
+NC='\033[0m' # No Color
+
+error() { echo -e "${RED}Error: $1${NC}" >&2; exit 1; }
+info() { echo -e "${CYAN}$1${NC}"; }
+
+# Check Node.js
+if ! command -v node &> /dev/null; then
+  error "Node.js is required but not found. Install from https://nodejs.org"
+fi
+
+NODE_VERSION=$(node -v | sed 's/v//')
+NODE_MAJOR=$(echo "$NODE_VERSION" | cut -d. -f1)
+if [ "$NODE_MAJOR" -lt 18 ]; then
+  error "Node.js >= 18 required. Current: v${NODE_VERSION}"
+fi
+
+info "claude-mem installer (Node.js v${NODE_VERSION})"
+
+# Create temp file for installer
+TMPFILE=$(mktemp "${TMPDIR:-/tmp}/claude-mem-installer.XXXXXX.mjs")
+
+# Cleanup on exit
+cleanup() {
+  rm -f "$TMPFILE"
+}
+trap cleanup EXIT INT TERM
+
+# Download installer
+info "Downloading installer..."
+if command -v curl &> /dev/null; then
+  curl -fsSL "$INSTALLER_URL" -o "$TMPFILE"
+elif command -v wget &> /dev/null; then
+  wget -q "$INSTALLER_URL" -O "$TMPFILE"
+else
+  error "curl or wget required to download installer"
+fi
+
+# Run installer with TTY access
+# When piped (curl | bash), stdin is the script. We need to reconnect to the terminal.
+if [ -t 0 ]; then
+  # Already have TTY (script was downloaded and run directly)
+  node "$TMPFILE" "$@"
+else
+  # Piped execution -- reconnect stdin to terminal
+  node "$TMPFILE" "$@" </dev/tty
+fi

install/vercel.json

@@ -0,0 +1,19 @@
+{
+  "$schema": "https://openapi.vercel.sh/vercel.json",
+  "headers": [
+    {
+      "source": "/(.*)\\.sh",
+      "headers": [
+        { "key": "Content-Type", "value": "text/plain; charset=utf-8" },
+        { "key": "Cache-Control", "value": "public, max-age=300, s-maxage=60" }
+      ]
+    },
+    {
+      "source": "/(.*)\\.js",
+      "headers": [
+        { "key": "Content-Type", "value": "application/javascript; charset=utf-8" },
+        { "key": "Cache-Control", "value": "public, max-age=300, s-maxage=60" }
+      ]
+    }
+  ]
+}

installer/build.mjs

@@ -0,0 +1,16 @@
+import { build } from 'esbuild';
+
+await build({
+  entryPoints: ['src/index.ts'],
+  bundle: true,
+  format: 'esm',
+  platform: 'node',
+  target: 'node18',
+  outfile: 'dist/index.js',
+  banner: {
+    js: '#!/usr/bin/env node',
+  },
+  external: [],
+});
+
+console.log('Build complete: dist/index.js');

installer/package.json

@@ -0,0 +1,21 @@
+{
+  "name": "claude-mem-installer",
+  "version": "1.0.0",
+  "type": "module",
+  "bin": { "claude-mem-installer": "./dist/index.js" },
+  "files": ["dist"],
+  "scripts": {
+    "build": "node build.mjs",
+    "dev": "node build.mjs && node dist/index.js"
+  },
+  "dependencies": {
+    "@clack/prompts": "^1.0.1",
+    "picocolors": "^1.1.1"
+  },
+  "devDependencies": {
+    "esbuild": "^0.24.0",
+    "typescript": "^5.7.0",
+    "@types/node": "^22.0.0"
+  },
+  "engines": { "node": ">=18.0.0" }
+}

installer/src/index.ts

@@ -0,0 +1,49 @@
+import * as p from '@clack/prompts';
+import { runWelcome } from './steps/welcome.js';
+import { runDependencyChecks } from './steps/dependencies.js';
+import { runIdeSelection } from './steps/ide-selection.js';
+import { runProviderConfiguration } from './steps/provider.js';
+import { runSettingsConfiguration } from './steps/settings.js';
+import { writeSettings } from './utils/settings-writer.js';
+import { runInstallation } from './steps/install.js';
+import { runWorkerStartup } from './steps/worker.js';
+import { runCompletion } from './steps/complete.js';
+
+async function runInstaller(): Promise<void> {
+  if (!process.stdin.isTTY) {
+    console.error('Error: This installer requires an interactive terminal.');
+    console.error('Run directly: npx claude-mem-installer');
+    process.exit(1);
+  }
+
+  const installMode = await runWelcome();
+
+  // Dependency checks (all modes)
+  await runDependencyChecks();
+
+  // IDE and provider selection
+  const selectedIDEs = await runIdeSelection();
+  const providerConfig = await runProviderConfiguration();
+
+  // Settings configuration
+  const settingsConfig = await runSettingsConfiguration();
+
+  // Write settings file
+  writeSettings(providerConfig, settingsConfig);
+  p.log.success('Settings saved.');
+
+  // Installation (fresh or upgrade)
+  if (installMode !== 'configure') {
+    await runInstallation(selectedIDEs);
+    await runWorkerStartup(settingsConfig.workerPort, settingsConfig.dataDir);
+  }
+
+  // Completion summary
+  runCompletion(providerConfig, settingsConfig, selectedIDEs);
+}
+
+runInstaller().catch((error) => {
+  p.cancel('Installation failed.');
+  console.error(error);
+  process.exit(1);
+});

installer/src/steps/complete.ts

@@ -0,0 +1,56 @@
+import * as p from '@clack/prompts';
+import pc from 'picocolors';
+import type { ProviderConfig } from './provider.js';
+import type { SettingsConfig } from './settings.js';
+import type { IDE } from './ide-selection.js';
+
+function getProviderLabel(config: ProviderConfig): string {
+  switch (config.provider) {
+    case 'claude':
+      return config.claudeAuthMethod === 'api' ? 'Claude (API Key)' : 'Claude (CLI subscription)';
+    case 'gemini':
+      return `Gemini (${config.model ?? 'gemini-2.5-flash-lite'})`;
+    case 'openrouter':
+      return `OpenRouter (${config.model ?? 'xiaomi/mimo-v2-flash:free'})`;
+  }
+}
+
+function getIDELabels(ides: IDE[]): string {
+  return ides.map((ide) => {
+    switch (ide) {
+      case 'claude-code': return 'Claude Code';
+      case 'cursor': return 'Cursor';
+    }
+  }).join(', ');
+}
+
+export function runCompletion(
+  providerConfig: ProviderConfig,
+  settingsConfig: SettingsConfig,
+  selectedIDEs: IDE[],
+): void {
+  const summaryLines = [
+    `Provider:   ${pc.cyan(getProviderLabel(providerConfig))}`,
+    `IDEs:       ${pc.cyan(getIDELabels(selectedIDEs))}`,
+    `Data dir:   ${pc.cyan(settingsConfig.dataDir)}`,
+    `Port:       ${pc.cyan(settingsConfig.workerPort)}`,
+    `Chroma:     ${settingsConfig.chromaEnabled ? pc.green('enabled') : pc.dim('disabled')}`,
+  ];
+
+  p.note(summaryLines.join('\n'), 'Configuration Summary');
+
+  const nextStepsLines: string[] = [];
+
+  if (selectedIDEs.includes('claude-code')) {
+    nextStepsLines.push('Open Claude Code and start a conversation — memory is automatic!');
+  }
+  if (selectedIDEs.includes('cursor')) {
+    nextStepsLines.push('Open Cursor — hooks are active in your projects.');
+  }
+  nextStepsLines.push(`View your memories: ${pc.underline(`http://localhost:${settingsConfig.workerPort}`)}`);
+  nextStepsLines.push(`Search past work: use ${pc.bold('/mem-search')} in Claude Code`);
+
+  p.note(nextStepsLines.join('\n'), 'Next Steps');
+
+  p.outro(pc.green('claude-mem installed successfully!'));
+}

installer/src/steps/dependencies.ts

@@ -0,0 +1,168 @@
+import * as p from '@clack/prompts';
+import pc from 'picocolors';
+import { findBinary, compareVersions, installBun, installUv } from '../utils/dependencies.js';
+import { detectOS } from '../utils/system.js';
+
+const BUN_EXTRA_PATHS = ['~/.bun/bin/bun', '/usr/local/bin/bun', '/opt/homebrew/bin/bun'];
+const UV_EXTRA_PATHS = ['~/.local/bin/uv', '~/.cargo/bin/uv'];
+
+interface DependencyStatus {
+  nodeOk: boolean;
+  gitOk: boolean;
+  bunOk: boolean;
+  uvOk: boolean;
+  bunPath: string | null;
+  uvPath: string | null;
+}
+
+export async function runDependencyChecks(): Promise<DependencyStatus> {
+  const status: DependencyStatus = {
+    nodeOk: false,
+    gitOk: false,
+    bunOk: false,
+    uvOk: false,
+    bunPath: null,
+    uvPath: null,
+  };
+
+  await p.tasks([
+    {
+      title: 'Checking Node.js',
+      task: async () => {
+        const version = process.version.slice(1); // remove 'v'
+        if (compareVersions(version, '18.0.0')) {
+          status.nodeOk = true;
+          return `Node.js ${process.version} ${pc.green('✓')}`;
+        }
+        return `Node.js ${process.version} — requires >= 18.0.0 ${pc.red('✗')}`;
+      },
+    },
+    {
+      title: 'Checking git',
+      task: async () => {
+        const info = findBinary('git');
+        if (info.found) {
+          status.gitOk = true;
+          return `git ${info.version ?? ''} ${pc.green('✓')}`;
+        }
+        return `git not found ${pc.red('✗')}`;
+      },
+    },
+    {
+      title: 'Checking Bun',
+      task: async () => {
+        const info = findBinary('bun', BUN_EXTRA_PATHS);
+        if (info.found && info.version && compareVersions(info.version, '1.1.14')) {
+          status.bunOk = true;
+          status.bunPath = info.path;
+          return `Bun ${info.version} ${pc.green('✓')}`;
+        }
+        if (info.found && info.version) {
+          return `Bun ${info.version} — requires >= 1.1.14 ${pc.yellow('⚠')}`;
+        }
+        return `Bun not found ${pc.yellow('⚠')}`;
+      },
+    },
+    {
+      title: 'Checking uv',
+      task: async () => {
+        const info = findBinary('uv', UV_EXTRA_PATHS);
+        if (info.found) {
+          status.uvOk = true;
+          status.uvPath = info.path;
+          return `uv ${info.version ?? ''} ${pc.green('✓')}`;
+        }
+        return `uv not found ${pc.yellow('⚠')}`;
+      },
+    },
+  ]);
+
+  // Handle missing dependencies
+  if (!status.gitOk) {
+    const os = detectOS();
+    p.log.error('git is required but not found.');
+    if (os === 'macos') {
+      p.log.info('Install with: xcode-select --install');
+    } else if (os === 'linux') {
+      p.log.info('Install with: sudo apt install git (or your distro equivalent)');
+    } else {
+      p.log.info('Download from: https://git-scm.com/downloads');
+    }
+    p.cancel('Please install git and try again.');
+    process.exit(1);
+  }
+
+  if (!status.nodeOk) {
+    p.log.error(`Node.js >= 18.0.0 is required. Current: ${process.version}`);
+    p.cancel('Please upgrade Node.js and try again.');
+    process.exit(1);
+  }
+
+  if (!status.bunOk) {
+    const shouldInstall = await p.confirm({
+      message: 'Bun is required but not found. Install it now?',
+      initialValue: true,
+    });
+
+    if (p.isCancel(shouldInstall)) {
+      p.cancel('Installation cancelled.');
+      process.exit(0);
+    }
+
+    if (shouldInstall) {
+      const s = p.spinner();
+      s.start('Installing Bun...');
+      try {
+        installBun();
+        const recheck = findBinary('bun', BUN_EXTRA_PATHS);
+        if (recheck.found) {
+          status.bunOk = true;
+          status.bunPath = recheck.path;
+          s.stop(`Bun installed ${pc.green('✓')}`);
+        } else {
+          s.stop(`Bun installed but not found in PATH. You may need to restart your shell.`);
+        }
+      } catch {
+        s.stop(`Bun installation failed. Install manually: curl -fsSL https://bun.sh/install | bash`);
+      }
+    } else {
+      p.log.warn('Bun is required for claude-mem. Install manually: curl -fsSL https://bun.sh/install | bash');
+      p.cancel('Cannot continue without Bun.');
+      process.exit(1);
+    }
+  }
+
+  if (!status.uvOk) {
+    const shouldInstall = await p.confirm({
+      message: 'uv (Python package manager) is recommended for Chroma. Install it now?',
+      initialValue: true,
+    });
+
+    if (p.isCancel(shouldInstall)) {
+      p.cancel('Installation cancelled.');
+      process.exit(0);
+    }
+
+    if (shouldInstall) {
+      const s = p.spinner();
+      s.start('Installing uv...');
+      try {
+        installUv();
+        const recheck = findBinary('uv', UV_EXTRA_PATHS);
+        if (recheck.found) {
+          status.uvOk = true;
+          status.uvPath = recheck.path;
+          s.stop(`uv installed ${pc.green('✓')}`);
+        } else {
+          s.stop('uv installed but not found in PATH. You may need to restart your shell.');
+        }
+      } catch {
+        s.stop('uv installation failed. Install manually: curl -fsSL https://astral.sh/uv/install.sh | sh');
+      }
+    } else {
+      p.log.warn('Skipping uv — Chroma vector search will not be available.');
+    }
+  }
+
+  return status;
+}

installer/src/steps/ide-selection.ts

@@ -0,0 +1,32 @@
+import * as p from '@clack/prompts';
+
+export type IDE = 'claude-code' | 'cursor';
+
+export async function runIdeSelection(): Promise<IDE[]> {
+  const result = await p.multiselect({
+    message: 'Which IDEs do you use?',
+    options: [
+      { value: 'claude-code' as const, label: 'Claude Code', hint: 'recommended' },
+      { value: 'cursor' as const, label: 'Cursor' },
+      // Windsurf coming soon - not yet selectable
+    ],
+    initialValues: ['claude-code'],
+    required: true,
+  });
+
+  if (p.isCancel(result)) {
+    p.cancel('Installation cancelled.');
+    process.exit(0);
+  }
+
+  const selectedIDEs = result as IDE[];
+
+  if (selectedIDEs.includes('claude-code')) {
+    p.log.info('Claude Code: Plugin will be registered via marketplace.');
+  }
+  if (selectedIDEs.includes('cursor')) {
+    p.log.info('Cursor: Hooks will be configured for your projects.');
+  }
+
+  return selectedIDEs;
+}

installer/src/steps/install.ts

@@ -0,0 +1,167 @@
+import * as p from '@clack/prompts';
+import pc from 'picocolors';
+import { execSync } from 'child_process';
+import { existsSync, mkdirSync, readFileSync, writeFileSync, cpSync } from 'fs';
+import { join } from 'path';
+import { homedir, tmpdir } from 'os';
+import type { IDE } from './ide-selection.js';
+
+const MARKETPLACE_DIR = join(homedir(), '.claude', 'plugins', 'marketplaces', 'thedotmack');
+const PLUGINS_DIR = join(homedir(), '.claude', 'plugins');
+const CLAUDE_SETTINGS_PATH = join(homedir(), '.claude', 'settings.json');
+
+function ensureDir(directoryPath: string): void {
+  if (!existsSync(directoryPath)) {
+    mkdirSync(directoryPath, { recursive: true });
+  }
+}
+
+function readJsonFile(filepath: string): any {
+  if (!existsSync(filepath)) return {};
+  return JSON.parse(readFileSync(filepath, 'utf-8'));
+}
+
+function writeJsonFile(filepath: string, data: any): void {
+  ensureDir(join(filepath, '..'));
+  writeFileSync(filepath, JSON.stringify(data, null, 2) + '\n', 'utf-8');
+}
+
+function registerMarketplace(): void {
+  const knownMarketplacesPath = join(PLUGINS_DIR, 'known_marketplaces.json');
+  const knownMarketplaces = readJsonFile(knownMarketplacesPath);
+
+  knownMarketplaces['thedotmack'] = {
+    source: {
+      source: 'github',
+      repo: 'thedotmack/claude-mem',
+    },
+    installLocation: MARKETPLACE_DIR,
+    lastUpdated: new Date().toISOString(),
+    autoUpdate: true,
+  };
+
+  ensureDir(PLUGINS_DIR);
+  writeJsonFile(knownMarketplacesPath, knownMarketplaces);
+}
+
+function registerPlugin(version: string): void {
+  const installedPluginsPath = join(PLUGINS_DIR, 'installed_plugins.json');
+  const installedPlugins = readJsonFile(installedPluginsPath);
+
+  if (!installedPlugins.version) installedPlugins.version = 2;
+  if (!installedPlugins.plugins) installedPlugins.plugins = {};
+
+  const pluginCachePath = join(PLUGINS_DIR, 'cache', 'thedotmack', 'claude-mem', version);
+  const now = new Date().toISOString();
+
+  installedPlugins.plugins['claude-mem@thedotmack'] = [
+    {
+      scope: 'user',
+      installPath: pluginCachePath,
+      version,
+      installedAt: now,
+      lastUpdated: now,
+    },
+  ];
+
+  writeJsonFile(installedPluginsPath, installedPlugins);
+
+  // Copy built plugin to cache directory
+  ensureDir(pluginCachePath);
+  const pluginSourceDir = join(MARKETPLACE_DIR, 'plugin');
+  if (existsSync(pluginSourceDir)) {
+    cpSync(pluginSourceDir, pluginCachePath, { recursive: true });
+  }
+}
+
+function enablePluginInClaudeSettings(): void {
+  const settings = readJsonFile(CLAUDE_SETTINGS_PATH);
+
+  if (!settings.enabledPlugins) settings.enabledPlugins = {};
+  settings.enabledPlugins['claude-mem@thedotmack'] = true;
+
+  writeJsonFile(CLAUDE_SETTINGS_PATH, settings);
+}
+
+function getPluginVersion(): string {
+  const pluginJsonPath = join(MARKETPLACE_DIR, 'plugin', '.claude-plugin', 'plugin.json');
+  if (existsSync(pluginJsonPath)) {
+    const pluginJson = JSON.parse(readFileSync(pluginJsonPath, 'utf-8'));
+    return pluginJson.version ?? '1.0.0';
+  }
+  return '1.0.0';
+}
+
+export async function runInstallation(selectedIDEs: IDE[]): Promise<void> {
+  const tempDir = join(tmpdir(), `claude-mem-install-${Date.now()}`);
+
+  await p.tasks([
+    {
+      title: 'Cloning claude-mem repository',
+      task: async (message) => {
+        message('Downloading latest release...');
+        execSync(
+          `git clone --depth 1 https://github.com/thedotmack/claude-mem.git "${tempDir}"`,
+          { stdio: 'pipe' },
+        );
+        return `Repository cloned ${pc.green('OK')}`;
+      },
+    },
+    {
+      title: 'Installing dependencies',
+      task: async (message) => {
+        message('Running npm install...');
+        execSync('npm install', { cwd: tempDir, stdio: 'pipe' });
+        return `Dependencies installed ${pc.green('OK')}`;
+      },
+    },
+    {
+      title: 'Building plugin',
+      task: async (message) => {
+        message('Compiling TypeScript and bundling...');
+        execSync('npm run build', { cwd: tempDir, stdio: 'pipe' });
+        return `Plugin built ${pc.green('OK')}`;
+      },
+    },
+    {
+      title: 'Registering plugin',
+      task: async (message) => {
+        message('Copying files to marketplace directory...');
+        ensureDir(MARKETPLACE_DIR);
+
+        // Sync from cloned repo to marketplace dir, excluding .git and lock files
+        execSync(
+          `rsync -a --delete --exclude=.git --exclude=package-lock.json --exclude=bun.lock "${tempDir}/" "${MARKETPLACE_DIR}/"`,
+          { stdio: 'pipe' },
+        );
+
+        message('Registering marketplace...');
+        registerMarketplace();
+
+        message('Installing marketplace dependencies...');
+        execSync('npm install', { cwd: MARKETPLACE_DIR, stdio: 'pipe' });
+
+        message('Registering plugin in Claude Code...');
+        const version = getPluginVersion();
+        registerPlugin(version);
+
+        message('Enabling plugin...');
+        enablePluginInClaudeSettings();
+
+        return `Plugin registered (v${getPluginVersion()}) ${pc.green('OK')}`;
+      },
+    },
+  ]);
+
+  // Cleanup temp directory (non-critical if it fails)
+  try {
+    execSync(`rm -rf "${tempDir}"`, { stdio: 'pipe' });
+  } catch {
+    // Temp dir will be cleaned by OS eventually
+  }
+
+  if (selectedIDEs.includes('cursor')) {
+    p.log.info('Cursor hook configuration will be available after first launch.');
+    p.log.info('Run: claude-mem cursor-setup (coming soon)');
+  }
+}

installer/src/steps/provider.ts

@@ -0,0 +1,140 @@
+import * as p from '@clack/prompts';
+import pc from 'picocolors';
+
+export type ProviderType = 'claude' | 'gemini' | 'openrouter';
+export type ClaudeAuthMethod = 'cli' | 'api';
+
+export interface ProviderConfig {
+  provider: ProviderType;
+  claudeAuthMethod?: ClaudeAuthMethod;
+  apiKey?: string;
+  model?: string;
+  rateLimitingEnabled?: boolean;
+}
+
+export async function runProviderConfiguration(): Promise<ProviderConfig> {
+  const provider = await p.select({
+    message: 'Which AI provider should claude-mem use for memory compression?',
+    options: [
+      { value: 'claude' as const, label: 'Claude', hint: 'uses your Claude subscription' },
+      { value: 'gemini' as const, label: 'Gemini', hint: 'free tier available' },
+      { value: 'openrouter' as const, label: 'OpenRouter', hint: 'free models available' },
+    ],
+  });
+
+  if (p.isCancel(provider)) {
+    p.cancel('Installation cancelled.');
+    process.exit(0);
+  }
+
+  const config: ProviderConfig = { provider };
+
+  if (provider === 'claude') {
+    const authMethod = await p.select({
+      message: 'How should Claude authenticate?',
+      options: [
+        { value: 'cli' as const, label: 'CLI (Max Plan subscription)', hint: 'no API key needed' },
+        { value: 'api' as const, label: 'API Key', hint: 'uses Anthropic API credits' },
+      ],
+    });
+
+    if (p.isCancel(authMethod)) {
+      p.cancel('Installation cancelled.');
+      process.exit(0);
+    }
+
+    config.claudeAuthMethod = authMethod;
+
+    if (authMethod === 'api') {
+      const apiKey = await p.password({
+        message: 'Enter your Anthropic API key:',
+        validate: (value) => {
+          if (!value || value.trim().length === 0) return 'API key is required';
+          if (!value.startsWith('sk-ant-')) return 'Anthropic API keys start with sk-ant-';
+        },
+      });
+
+      if (p.isCancel(apiKey)) {
+        p.cancel('Installation cancelled.');
+        process.exit(0);
+      }
+
+      config.apiKey = apiKey;
+    }
+  }
+
+  if (provider === 'gemini') {
+    const apiKey = await p.password({
+      message: 'Enter your Gemini API key:',
+      validate: (value) => {
+        if (!value || value.trim().length === 0) return 'API key is required';
+      },
+    });
+
+    if (p.isCancel(apiKey)) {
+      p.cancel('Installation cancelled.');
+      process.exit(0);
+    }
+
+    config.apiKey = apiKey;
+
+    const model = await p.select({
+      message: 'Which Gemini model?',
+      options: [
+        { value: 'gemini-2.5-flash-lite' as const, label: 'Gemini 2.5 Flash Lite', hint: 'fastest, highest free RPM' },
+        { value: 'gemini-2.5-flash' as const, label: 'Gemini 2.5 Flash', hint: 'balanced' },
+        { value: 'gemini-3-flash-preview' as const, label: 'Gemini 3 Flash Preview', hint: 'latest' },
+      ],
+    });
+
+    if (p.isCancel(model)) {
+      p.cancel('Installation cancelled.');
+      process.exit(0);
+    }
+
+    config.model = model;
+
+    const rateLimiting = await p.confirm({
+      message: 'Enable rate limiting? (recommended for free tier)',
+      initialValue: true,
+    });
+
+    if (p.isCancel(rateLimiting)) {
+      p.cancel('Installation cancelled.');
+      process.exit(0);
+    }
+
+    config.rateLimitingEnabled = rateLimiting;
+  }
+
+  if (provider === 'openrouter') {
+    const apiKey = await p.password({
+      message: 'Enter your OpenRouter API key:',
+      validate: (value) => {
+        if (!value || value.trim().length === 0) return 'API key is required';
+      },
+    });
+
+    if (p.isCancel(apiKey)) {
+      p.cancel('Installation cancelled.');
+      process.exit(0);
+    }
+
+    config.apiKey = apiKey;
+
+    const model = await p.text({
+      message: 'Which OpenRouter model?',
+      defaultValue: 'xiaomi/mimo-v2-flash:free',
+      placeholder: 'xiaomi/mimo-v2-flash:free',
+    });
+
+    if (p.isCancel(model)) {
+      p.cancel('Installation cancelled.');
+      process.exit(0);
+    }
+
+    config.model = model;
+  }
+
+  return config;
+}

installer/src/steps/settings.ts

@@ -0,0 +1,174 @@
+import * as p from '@clack/prompts';
+import pc from 'picocolors';
+
+export interface SettingsConfig {
+  workerPort: string;
+  dataDir: string;
+  contextObservations: string;
+  logLevel: string;
+  pythonVersion: string;
+  chromaEnabled: boolean;
+  chromaMode?: 'local' | 'remote';
+  chromaHost?: string;
+  chromaPort?: string;
+  chromaSsl?: boolean;
+}
+
+export async function runSettingsConfiguration(): Promise<SettingsConfig> {
+  const useDefaults = await p.confirm({
+    message: 'Use default settings? (recommended for most users)',
+    initialValue: true,
+  });
+
+  if (p.isCancel(useDefaults)) {
+    p.cancel('Installation cancelled.');
+    process.exit(0);
+  }
+
+  if (useDefaults) {
+    return {
+      workerPort: '37777',
+      dataDir: '~/.claude-mem',
+      contextObservations: '50',
+      logLevel: 'INFO',
+      pythonVersion: '3.13',
+      chromaEnabled: true,
+      chromaMode: 'local',
+    };
+  }
+
+  // Custom settings
+  const workerPort = await p.text({
+    message: 'Worker service port:',
+    defaultValue: '37777',
+    placeholder: '37777',
+    validate: (value = '') => {
+      const port = parseInt(value, 10);
+      if (isNaN(port) || port < 1024 || port > 65535) {
+        return 'Port must be between 1024 and 65535';
+      }
+    },
+  });
+  if (p.isCancel(workerPort)) { p.cancel('Installation cancelled.'); process.exit(0); }
+
+  const dataDir = await p.text({
+    message: 'Data directory:',
+    defaultValue: '~/.claude-mem',
+    placeholder: '~/.claude-mem',
+  });
+  if (p.isCancel(dataDir)) { p.cancel('Installation cancelled.'); process.exit(0); }
+
+  const contextObservations = await p.text({
+    message: 'Number of context observations per session:',
+    defaultValue: '50',
+    placeholder: '50',
+    validate: (value = '') => {
+      const num = parseInt(value, 10);
+      if (isNaN(num) || num < 1 || num > 200) {
+        return 'Must be between 1 and 200';
+      }
+    },
+  });
+  if (p.isCancel(contextObservations)) { p.cancel('Installation cancelled.'); process.exit(0); }
+
+  const logLevel = await p.select({
+    message: 'Log level:',
+    options: [
+      { value: 'DEBUG', label: 'DEBUG', hint: 'verbose' },
+      { value: 'INFO', label: 'INFO', hint: 'default' },
+      { value: 'WARN', label: 'WARN' },
+      { value: 'ERROR', label: 'ERROR', hint: 'errors only' },
+    ],
+    initialValue: 'INFO',
+  });
+  if (p.isCancel(logLevel)) { p.cancel('Installation cancelled.'); process.exit(0); }
+
+  const pythonVersion = await p.text({
+    message: 'Python version (for Chroma):',
+    defaultValue: '3.13',
+    placeholder: '3.13',
+  });
+  if (p.isCancel(pythonVersion)) { p.cancel('Installation cancelled.'); process.exit(0); }
+
+  const chromaEnabled = await p.confirm({
+    message: 'Enable Chroma vector search?',
+    initialValue: true,
+  });
+  if (p.isCancel(chromaEnabled)) { p.cancel('Installation cancelled.'); process.exit(0); }
+
+  let chromaMode: 'local' | 'remote' | undefined;
+  let chromaHost: string | undefined;
+  let chromaPort: string | undefined;
+  let chromaSsl: boolean | undefined;
+
+  if (chromaEnabled) {
+    const mode = await p.select({
+      message: 'Chroma mode:',
+      options: [
+        { value: 'local' as const, label: 'Local', hint: 'starts local Chroma server' },
+        { value: 'remote' as const, label: 'Remote', hint: 'connect to existing server' },
+      ],
+    });
+    if (p.isCancel(mode)) { p.cancel('Installation cancelled.'); process.exit(0); }
+    chromaMode = mode;
+
+    if (mode === 'remote') {
+      const host = await p.text({
+        message: 'Chroma host:',
+        defaultValue: '127.0.0.1',
+        placeholder: '127.0.0.1',
+      });
+      if (p.isCancel(host)) { p.cancel('Installation cancelled.'); process.exit(0); }
+      chromaHost = host;
+
+      const port = await p.text({
+        message: 'Chroma port:',
+        defaultValue: '8000',
+        placeholder: '8000',
+        validate: (value = '') => {
+          const portNum = parseInt(value, 10);
+          if (isNaN(portNum) || portNum < 1 || portNum > 65535) return 'Port must be between 1 and 65535';
+        },
+      });
+      if (p.isCancel(port)) { p.cancel('Installation cancelled.'); process.exit(0); }
+      chromaPort = port;
+
+      const ssl = await p.confirm({
+        message: 'Use SSL for Chroma connection?',
+        initialValue: false,
+      });
+      if (p.isCancel(ssl)) { p.cancel('Installation cancelled.'); process.exit(0); }
+      chromaSsl = ssl;
+    }
+  }
+
+  const config: SettingsConfig = {
+    workerPort,
+    dataDir,
+    contextObservations,
+    logLevel,
+    pythonVersion,
+    chromaEnabled,
+    chromaMode,
+    chromaHost,
+    chromaPort,
+    chromaSsl,
+  };
+
+  // Show summary
+  const summaryLines = [
+    `Worker port: ${pc.cyan(workerPort)}`,
+    `Data directory: ${pc.cyan(dataDir)}`,
+    `Context observations: ${pc.cyan(contextObservations)}`,
+    `Log level: ${pc.cyan(logLevel)}`,
+    `Python version: ${pc.cyan(pythonVersion)}`,
+    `Chroma: ${chromaEnabled ? pc.green('enabled') : pc.dim('disabled')}`,
+  ];
+  if (chromaEnabled && chromaMode) {
+    summaryLines.push(`Chroma mode: ${pc.cyan(chromaMode)}`);
+  }
+
+  p.note(summaryLines.join('\n'), 'Settings Summary');
+
+  return config;
+}

installer/src/steps/welcome.ts

@@ -0,0 +1,43 @@
+import * as p from '@clack/prompts';
+import pc from 'picocolors';
+import { existsSync } from 'fs';
+import { expandHome } from '../utils/system.js';
+
+export type InstallMode = 'fresh' | 'upgrade' | 'configure';
+
+export async function runWelcome(): Promise<InstallMode> {
+  p.intro(pc.bgCyan(pc.black(' claude-mem installer ')));
+
+  p.log.info(`Version: 1.0.0`);
+  p.log.info(`Platform: ${process.platform} (${process.arch})`);
+
+  const settingsExist = existsSync(expandHome('~/.claude-mem/settings.json'));
+  const pluginExist = existsSync(expandHome('~/.claude/plugins/marketplaces/thedotmack/'));
+
+  const alreadyInstalled = settingsExist && pluginExist;
+
+  if (alreadyInstalled) {
+    p.log.warn('Existing claude-mem installation detected.');
+  }
+
+  const installMode = await p.select({
+    message: 'What would you like to do?',
+    options: alreadyInstalled
+      ? [
+          { value: 'upgrade' as const, label: 'Upgrade', hint: 'update to latest version' },
+          { value: 'configure' as const, label: 'Configure', hint: 'change settings only' },
+          { value: 'fresh' as const, label: 'Fresh Install', hint: 'reinstall from scratch' },
+        ]
+      : [
+          { value: 'fresh' as const, label: 'Fresh Install', hint: 'recommended' },
+          { value: 'configure' as const, label: 'Configure Only', hint: 'set up settings without installing' },
+        ],
+  });
+
+  if (p.isCancel(installMode)) {
+    p.cancel('Installation cancelled.');
+    process.exit(0);
+  }
+
+  return installMode;
+}

installer/src/steps/worker.ts

@@ -0,0 +1,67 @@
+import * as p from '@clack/prompts';
+import pc from 'picocolors';
+import { spawn } from 'child_process';
+import { join } from 'path';
+import { homedir } from 'os';
+import { expandHome } from '../utils/system.js';
+import { findBinary } from '../utils/dependencies.js';
+
+const MARKETPLACE_DIR = join(homedir(), '.claude', 'plugins', 'marketplaces', 'thedotmack');
+
+const HEALTH_CHECK_INTERVAL_MS = 1000;
+const HEALTH_CHECK_MAX_ATTEMPTS = 30;
+
+async function pollHealthEndpoint(port: string, maxAttempts: number = HEALTH_CHECK_MAX_ATTEMPTS): Promise<boolean> {
+  for (let attempt = 0; attempt < maxAttempts; attempt++) {
+    try {
+      const response = await fetch(`http://127.0.0.1:${port}/api/health`);
+      if (response.ok) return true;
+    } catch {
+      // Expected during startup — worker not listening yet
+    }
+    await new Promise((resolve) => setTimeout(resolve, HEALTH_CHECK_INTERVAL_MS));
+  }
+  return false;
+}
+
+export async function runWorkerStartup(workerPort: string, dataDir: string): Promise<void> {
+  const bunInfo = findBinary('bun', ['~/.bun/bin/bun', '/usr/local/bin/bun', '/opt/homebrew/bin/bun']);
+
+  if (!bunInfo.found || !bunInfo.path) {
+    p.log.error('Bun is required to start the worker but was not found.');
+    p.log.info('Install Bun: curl -fsSL https://bun.sh/install | bash');
+    return;
+  }
+
+  const workerScript = join(MARKETPLACE_DIR, 'plugin', 'scripts', 'worker-service.cjs');
+  const expandedDataDir = expandHome(dataDir);
+  const logPath = join(expandedDataDir, 'logs');
+
+  const s = p.spinner();
+  s.start('Starting worker service...');
+
+  // Start worker as a detached background process
+  const child = spawn(bunInfo.path, [workerScript], {
+    cwd: MARKETPLACE_DIR,
+    detached: true,
+    stdio: 'ignore',
+    env: {
+      ...process.env,
+      CLAUDE_MEM_WORKER_PORT: workerPort,
+      CLAUDE_MEM_DATA_DIR: expandedDataDir,
+    },
+  });
+
+  child.unref();
+
+  // Poll the health endpoint until the worker is responsive
+  const workerIsHealthy = await pollHealthEndpoint(workerPort);
+
+  if (workerIsHealthy) {
+    s.stop(`Worker running on port ${pc.cyan(workerPort)} ${pc.green('OK')}`);
+  } else {
+    s.stop(`Worker may still be starting. Check logs at: ${logPath}`);
+    p.log.warn('Health check timed out. The worker might need more time to initialize.');
+    p.log.info(`Check status: curl http://127.0.0.1:${workerPort}/api/health`);
+  }
+}

installer/src/utils/dependencies.ts

@@ -0,0 +1,74 @@
+import { existsSync } from 'fs';
+import { execSync } from 'child_process';
+import { commandExists, runCommand, expandHome, detectOS } from './system.js';
+
+export interface BinaryInfo {
+  found: boolean;
+  path: string | null;
+  version: string | null;
+}
+
+export function findBinary(name: string, extraPaths: string[] = []): BinaryInfo {
+  // Check PATH first
+  if (commandExists(name)) {
+    const result = runCommand('which', [name]);
+    const versionResult = runCommand(name, ['--version']);
+    return {
+      found: true,
+      path: result.stdout,
+      version: parseVersion(versionResult.stdout) || parseVersion(versionResult.stderr),
+    };
+  }
+
+  // Check extra known locations
+  for (const extraPath of extraPaths) {
+    const fullPath = expandHome(extraPath);
+    if (existsSync(fullPath)) {
+      const versionResult = runCommand(fullPath, ['--version']);
+      return {
+        found: true,
+        path: fullPath,
+        version: parseVersion(versionResult.stdout) || parseVersion(versionResult.stderr),
+      };
+    }
+  }
+
+  return { found: false, path: null, version: null };
+}
+
+function parseVersion(output: string): string | null {
+  if (!output) return null;
+  const match = output.match(/(\d+\.\d+(\.\d+)?)/);
+  return match ? match[1] : null;
+}
+
+export function compareVersions(current: string, minimum: string): boolean {
+  const currentParts = current.split('.').map(Number);
+  const minimumParts = minimum.split('.').map(Number);
+
+  for (let i = 0; i < Math.max(currentParts.length, minimumParts.length); i++) {
+    const a = currentParts[i] || 0;
+    const b = minimumParts[i] || 0;
+    if (a > b) return true;
+    if (a < b) return false;
+  }
+  return true; // equal
+}
+
+export function installBun(): void {
+  const os = detectOS();
+  if (os === 'windows') {
+    execSync('powershell -c "irm bun.sh/install.ps1 | iex"', { stdio: 'inherit' });
+  } else {
+    execSync('curl -fsSL https://bun.sh/install | bash', { stdio: 'inherit' });
+  }
+}
+
+export function installUv(): void {
+  const os = detectOS();
+  if (os === 'windows') {
+    execSync('powershell -c "irm https://astral.sh/uv/install.ps1 | iex"', { stdio: 'inherit' });
+  } else {
+    execSync('curl -fsSL https://astral.sh/uv/install.sh | sh', { stdio: 'inherit' });
+  }
+}

installer/src/utils/settings-writer.ts

@@ -0,0 +1,82 @@
+import { existsSync, mkdirSync, readFileSync, writeFileSync } from 'fs';
+import { join } from 'path';
+import { homedir } from 'os';
+import type { ProviderConfig } from '../steps/provider.js';
+import type { SettingsConfig } from '../steps/settings.js';
+
+export function expandDataDir(dataDir: string): string {
+  if (dataDir.startsWith('~')) {
+    return join(homedir(), dataDir.slice(1));
+  }
+  return dataDir;
+}
+
+export function buildSettingsObject(
+  providerConfig: ProviderConfig,
+  settingsConfig: SettingsConfig,
+): Record<string, string> {
+  const settings: Record<string, string> = {
+    CLAUDE_MEM_WORKER_PORT: settingsConfig.workerPort,
+    CLAUDE_MEM_WORKER_HOST: '127.0.0.1',
+    CLAUDE_MEM_DATA_DIR: expandDataDir(settingsConfig.dataDir),
+    CLAUDE_MEM_CONTEXT_OBSERVATIONS: settingsConfig.contextObservations,
+    CLAUDE_MEM_LOG_LEVEL: settingsConfig.logLevel,
+    CLAUDE_MEM_PYTHON_VERSION: settingsConfig.pythonVersion,
+    CLAUDE_MEM_PROVIDER: providerConfig.provider,
+  };
+
+  // Provider-specific settings
+  if (providerConfig.provider === 'claude') {
+    settings.CLAUDE_MEM_CLAUDE_AUTH_METHOD = providerConfig.claudeAuthMethod ?? 'cli';
+  }
+
+  if (providerConfig.provider === 'gemini') {
+    if (providerConfig.apiKey) settings.CLAUDE_MEM_GEMINI_API_KEY = providerConfig.apiKey;
+    if (providerConfig.model) settings.CLAUDE_MEM_GEMINI_MODEL = providerConfig.model;
+    settings.CLAUDE_MEM_GEMINI_RATE_LIMITING_ENABLED = providerConfig.rateLimitingEnabled !== false ? 'true' : 'false';
+  }
+
+  if (providerConfig.provider === 'openrouter') {
+    if (providerConfig.apiKey) settings.CLAUDE_MEM_OPENROUTER_API_KEY = providerConfig.apiKey;
+    if (providerConfig.model) settings.CLAUDE_MEM_OPENROUTER_MODEL = providerConfig.model;
+  }
+
+  // Chroma settings
+  if (settingsConfig.chromaEnabled) {
+    settings.CLAUDE_MEM_CHROMA_MODE = settingsConfig.chromaMode ?? 'local';
+    if (settingsConfig.chromaMode === 'remote') {
+      if (settingsConfig.chromaHost) settings.CLAUDE_MEM_CHROMA_HOST = settingsConfig.chromaHost;
+      if (settingsConfig.chromaPort) settings.CLAUDE_MEM_CHROMA_PORT = settingsConfig.chromaPort;
+      if (settingsConfig.chromaSsl !== undefined) settings.CLAUDE_MEM_CHROMA_SSL = String(settingsConfig.chromaSsl);
+    }
+  }
+
+  return settings;
+}
+
+export function writeSettings(
+  providerConfig: ProviderConfig,
+  settingsConfig: SettingsConfig,
+): void {
+  const dataDir = expandDataDir(settingsConfig.dataDir);
+  const settingsPath = join(dataDir, 'settings.json');
+
+  // Ensure data directory exists
+  if (!existsSync(dataDir)) {
+    mkdirSync(dataDir, { recursive: true });
+  }
+
+  // Merge with existing settings if upgrading
+  let existingSettings: Record<string, string> = {};
+  if (existsSync(settingsPath)) {
+    const raw = readFileSync(settingsPath, 'utf-8');
+    existingSettings = JSON.parse(raw);
+  }
+
+  const newSettings = buildSettingsObject(providerConfig, settingsConfig);
+
+  // Merge: new settings override existing ones
+  const merged = { ...existingSettings, ...newSettings };
+
+  writeFileSync(settingsPath, JSON.stringify(merged, null, 2) + '\n', 'utf-8');
+}

installer/src/utils/system.ts

@@ -0,0 +1,49 @@
+import { execSync } from 'child_process';
+import { homedir } from 'os';
+import { join } from 'path';
+
+export type OSType = 'macos' | 'linux' | 'windows';
+
+export function detectOS(): OSType {
+  switch (process.platform) {
+    case 'darwin': return 'macos';
+    case 'win32': return 'windows';
+    default: return 'linux';
+  }
+}
+
+export function commandExists(command: string): boolean {
+  try {
+    execSync(`which ${command}`, { stdio: 'pipe' });
+    return true;
+  } catch {
+    return false;
+  }
+}
+
+export interface CommandResult {
+  stdout: string;
+  stderr: string;
+  exitCode: number;
+}
+
+export function runCommand(command: string, args: string[] = []): CommandResult {
+  try {
+    const fullCommand = [command, ...args].join(' ');
+    const stdout = execSync(fullCommand, { encoding: 'utf-8', stdio: ['pipe', 'pipe', 'pipe'] });
+    return { stdout: stdout.trim(), stderr: '', exitCode: 0 };
+  } catch (error: any) {
+    return {
+      stdout: error.stdout?.toString().trim() ?? '',
+      stderr: error.stderr?.toString().trim() ?? '',
+      exitCode: error.status ?? 1,
+    };
+  }
+}
+
+export function expandHome(filepath: string): string {
+  if (filepath.startsWith('~')) {
+    return join(homedir(), filepath.slice(1));
+  }
+  return filepath;
+}

installer/tsconfig.json

@@ -0,0 +1,17 @@
+{
+  "compilerOptions": {
+    "module": "ESNext",
+    "target": "ES2022",
+    "moduleResolution": "bundler",
+    "esModuleInterop": true,
+    "strict": true,
+    "outDir": "dist",
+    "rootDir": "src",
+    "declaration": false,
+    "skipLibCheck": true,
+    "resolveJsonModule": true,
+    "forceConsistentCasingInFileNames": true
+  },
+  "include": ["src/**/*.ts"],
+  "exclude": ["node_modules", "dist"]
+}

openclaw/.gitignore

@@ -0,0 +1,2 @@
+node_modules/
+dist/

openclaw/Dockerfile.e2e

@@ -0,0 +1,69 @@
+# Dockerfile.e2e — End-to-end test: install claude-mem plugin on a real OpenClaw instance
+# Simulates the complete plugin installation flow a user would follow.
+#
+# Usage:
+#   docker build -f Dockerfile.e2e -t openclaw-e2e-test . && docker run --rm openclaw-e2e-test
+#
+# Interactive (for human testing):
+#   docker run --rm -it openclaw-e2e-test /bin/bash
+
+FROM ghcr.io/openclaw/openclaw:main
+
+USER root
+
+# Install curl for health checks in e2e-verify.sh, and TypeScript for building
+RUN apt-get update && apt-get install -y --no-install-recommends curl && rm -rf /var/lib/apt/lists/*
+RUN npm install -g typescript@5
+
+# Create staging directory for the plugin source
+WORKDIR /tmp/claude-mem-plugin
+
+# Copy plugin source files
+COPY package.json tsconfig.json openclaw.plugin.json ./
+COPY src/ ./src/
+
+# Build the plugin (TypeScript → JavaScript)
+# NODE_ENV=production is set in the base image; override to install devDependencies
+RUN NODE_ENV=development npm install && npx tsc
+
+# Create the installable plugin package:
+# OpenClaw `plugins install` expects package.json with openclaw.extensions field.
+# The package name must match the plugin ID in openclaw.plugin.json (claude-mem).
+# Only include the main plugin entry point, not test/mock files.
+RUN mkdir -p /tmp/claude-mem-installable/dist && \
+    cp dist/index.js /tmp/claude-mem-installable/dist/ && \
+    cp dist/index.d.ts /tmp/claude-mem-installable/dist/ 2>/dev/null || true && \
+    cp openclaw.plugin.json /tmp/claude-mem-installable/ && \
+    node -e " \
+      const pkg = { \
+        name: 'claude-mem', \
+        version: '1.0.0', \
+        type: 'module', \
+        main: 'dist/index.js', \
+        openclaw: { extensions: ['./dist/index.js'] } \
+      }; \
+      require('fs').writeFileSync('/tmp/claude-mem-installable/package.json', JSON.stringify(pkg, null, 2)); \
+    "
+
+# Switch back to app directory and node user for installation
+WORKDIR /app
+USER node
+
+# Create the OpenClaw config directory
+RUN mkdir -p /home/node/.openclaw
+
+# Install the plugin using OpenClaw's official CLI
+RUN node openclaw.mjs plugins install /tmp/claude-mem-installable
+
+# Enable the plugin
+RUN node openclaw.mjs plugins enable claude-mem
+
+# Copy the e2e verification script and mock worker
+COPY --chown=node:node e2e-verify.sh /app/e2e-verify.sh
+USER root
+RUN chmod +x /app/e2e-verify.sh && \
+    cp /tmp/claude-mem-plugin/dist/mock-worker.js /app/mock-worker.js
+USER node
+
+# Default: run the automated verification
+CMD ["/bin/bash", "/app/e2e-verify.sh"]

openclaw/SKILL.md

@@ -0,0 +1,458 @@
+# Claude-Mem OpenClaw Plugin — Setup Guide
+
+This guide walks through setting up the claude-mem plugin on an OpenClaw gateway. By the end, your agents will have persistent memory across sessions, a live-updating MEMORY.md in their workspace, and optionally a real-time observation feed streaming to a messaging channel.
+
+## Quick Install (Recommended)
+
+Run this one-liner to install everything automatically:
+
+```bash
+curl -fsSL https://install.cmem.ai/openclaw.sh | bash
+```
+
+The installer handles dependency checks (Bun, uv), plugin installation, memory slot configuration, AI provider setup, worker startup, and optional observation feed configuration — all interactively.
+
+### Install with options
+
+Pre-select your AI provider and API key to skip interactive prompts:
+
+```bash
+curl -fsSL https://install.cmem.ai/openclaw.sh | bash -s -- --provider=gemini --api-key=YOUR_KEY
+```
+
+For fully unattended installation (defaults to Claude Max Plan, skips observation feed):
+
+```bash
+curl -fsSL https://install.cmem.ai/openclaw.sh | bash -s -- --non-interactive
+```
+
+To upgrade an existing installation (preserves settings, updates plugin):
+
+```bash
+curl -fsSL https://install.cmem.ai/openclaw.sh | bash -s -- --upgrade
+```
+
+After installation, skip to [Step 4: Restart the Gateway and Verify](#step-4-restart-the-gateway-and-verify) to confirm everything is working.
+
+---
+
+## Manual Setup
+
+The steps below are for manual installation if you prefer not to use the automated installer, or need to troubleshoot individual steps.
+
+### Step 1: Clone the Claude-Mem Repo
+
+First, clone the claude-mem repository to a location accessible by your OpenClaw gateway. This gives you the worker service source and the plugin code.
+
+```bash
+cd /opt  # or wherever you want to keep it
+git clone https://github.com/thedotmack/claude-mem.git
+cd claude-mem
+npm install
+npm run build
+```
+
+You'll need **bun** installed for the worker service. If you don't have it:
+
+```bash
+curl -fsSL https://bun.sh/install | bash
+```
+
+### Step 2: Get the Worker Running
+
+The claude-mem worker is an HTTP service on port 37777. It stores observations, generates summaries, and serves the context timeline. The plugin talks to it over HTTP — it doesn't matter where the worker is running, just that it's reachable on localhost:37777.
+
+#### Check if it's already running
+
+If this machine also runs Claude Code with claude-mem installed, the worker may already be running:
+
+```bash
+curl http://localhost:37777/api/health
+```
+
+**Got `{"status":"ok"}`?** The worker is already running. Skip to Step 3.
+
+**Got connection refused or no response?** The worker isn't running. Continue below.
+
+#### If Claude Code has claude-mem installed
+
+If claude-mem is installed as a Claude Code plugin (at `~/.claude/plugins/marketplaces/thedotmack/`), start the worker from that installation:
+
+```bash
+cd ~/.claude/plugins/marketplaces/thedotmack
+npm run worker:restart
+```
+
+Verify:
+```bash
+curl http://localhost:37777/api/health
+```
+
+**Got `{"status":"ok"}`?** You're set. Skip to Step 3.
+
+**Still not working?** Check `npm run worker:status` for error details, or check that bun is installed and on your PATH.
+
+#### If there's no Claude Code installation
+
+Run the worker from the cloned repo:
+
+```bash
+cd /opt/claude-mem  # wherever you cloned it
+npm run worker:start
+```
+
+Verify:
+```bash
+curl http://localhost:37777/api/health
+```
+
+**Got `{"status":"ok"}`?** You're set. Move to Step 3.
+
+**Still not working?** Debug steps:
+- Check that bun is installed: `bun --version`
+- Check the worker status: `npm run worker:status`
+- Check if something else is using port 37777: `lsof -i :37777`
+- Check logs: `npm run worker:logs` (if available)
+- Try running it directly to see errors: `bun plugin/scripts/worker-service.cjs start`
+
+### Step 3: Add the Plugin to Your Gateway
+
+Add the `claude-mem` plugin to your OpenClaw gateway configuration:
+
+```json
+{
+  "plugins": {
+    "claude-mem": {
+      "enabled": true,
+      "config": {
+        "project": "my-project",
+        "syncMemoryFile": true,
+        "workerPort": 37777
+      }
+    }
+  }
+}
+```
+
+#### Config fields explained
+
+- **`project`** (string, default: `"openclaw"`) — The project name that scopes all observations in the memory database. Use a unique name per gateway/use-case so observations don't mix. For example, if this gateway runs a coding bot, use `"coding-bot"`.
+
+- **`syncMemoryFile`** (boolean, default: `true`) — When enabled, the plugin writes a `MEMORY.md` file to each agent's workspace directory. This file contains the full timeline of observations and summaries from previous sessions, and it updates on every tool use so agents always have fresh context. Set to `false` only if you don't want the plugin writing files to agent workspaces.
+
+- **`workerPort`** (number, default: `37777`) — The port where the claude-mem worker service is listening. Only change this if you configured the worker to use a different port.
+
+---
+
+## Step 4: Restart the Gateway and Verify
+
+Restart your OpenClaw gateway so it picks up the new plugin configuration. After restart, check the gateway logs for:
+
+```
+[claude-mem] OpenClaw plugin loaded — v1.0.0 (worker: 127.0.0.1:37777)
+```
+
+If you see this, the plugin is loaded. You can also verify by running `/claude_mem_status` in any OpenClaw chat:
+
+```
+Claude-Mem Worker Status
+Status: ok
+Port: 37777
+Active sessions: 0
+Observation feed: disconnected
+```
+
+The observation feed shows `disconnected` because we haven't configured it yet. That's next.
+
+## Step 5: Verify Observations Are Being Recorded
+
+Have an agent do some work. The plugin automatically records observations through these OpenClaw events:
+
+1. **`before_agent_start`** — Initializes a claude-mem session when the agent starts, syncs MEMORY.md to the workspace
+2. **`tool_result_persist`** — Records each tool use (Read, Write, Bash, etc.) as an observation, re-syncs MEMORY.md
+3. **`agent_end`** — Summarizes the session and marks it complete
+
+All of this happens automatically. No additional configuration needed.
+
+To verify it's working, check the agent's workspace directory for a `MEMORY.md` file after the agent runs. It should contain a formatted timeline of observations.
+
+You can also check the worker's viewer UI at http://localhost:37777 to see observations appearing in real time.
+
+## Step 6: Set Up the Observation Feed (Streaming to a Channel)
+
+The observation feed connects to the claude-mem worker's SSE (Server-Sent Events) stream and forwards every new observation to a messaging channel in real time. Your agents learn things, and you see them learning in your Telegram/Discord/Slack/etc.
+
+### What you'll see
+
+Every time claude-mem creates a new observation from your agent's tool usage, a message like this appears in your channel:
+
+```
+🧠 Claude-Mem Observation
+**Implemented retry logic for API client**
+Added exponential backoff with configurable max retries to handle transient failures
+```
+
+### Pick your channel
+
+You need two things:
+- **Channel type** — Must match a channel plugin already running on your OpenClaw gateway
+- **Target ID** — The chat/channel/user ID where messages go
+
+#### Telegram
+
+Channel type: `telegram`
+
+To find your chat ID:
+1. Message @userinfobot on Telegram — https://t.me/userinfobot
+2. It replies with your numeric chat ID (e.g., `123456789`)
+3. For group chats, the ID is negative (e.g., `-1001234567890`)
+
+```json
+"observationFeed": {
+  "enabled": true,
+  "channel": "telegram",
+  "to": "123456789"
+}
+```
+
+#### Discord
+
+Channel type: `discord`
+
+To find your channel ID:
+1. Enable Developer Mode in Discord: Settings → Advanced → Developer Mode
+2. Right-click the target channel → Copy Channel ID
+
+```json
+"observationFeed": {
+  "enabled": true,
+  "channel": "discord",
+  "to": "1234567890123456789"
+}
+```
+
+#### Slack
+
+Channel type: `slack`
+
+To find your channel ID (not the channel name):
+1. Open the channel in Slack
+2. Click the channel name at the top
+3. Scroll to the bottom of the channel details — the ID looks like `C01ABC2DEFG`
+
+```json
+"observationFeed": {
+  "enabled": true,
+  "channel": "slack",
+  "to": "C01ABC2DEFG"
+}
+```
+
+#### Signal
+
+Channel type: `signal`
+
+Use the phone number or group ID configured in your OpenClaw gateway's Signal plugin.
+
+```json
+"observationFeed": {
+  "enabled": true,
+  "channel": "signal",
+  "to": "+1234567890"
+}
+```
+
+#### WhatsApp
+
+Channel type: `whatsapp`
+
+Use the phone number or group JID configured in your OpenClaw gateway's WhatsApp plugin.
+
+```json
+"observationFeed": {
+  "enabled": true,
+  "channel": "whatsapp",
+  "to": "+1234567890"
+}
+```
+
+#### LINE
+
+Channel type: `line`
+
+Use the user ID or group ID from the LINE Developer Console.
+
+```json
+"observationFeed": {
+  "enabled": true,
+  "channel": "line",
+  "to": "U1234567890abcdef"
+}
+```
+
+### Add it to your config
+
+Your complete plugin config should now look like this (using Telegram as an example):
+
+```json
+{
+  "plugins": {
+    "claude-mem": {
+      "enabled": true,
+      "config": {
+        "project": "my-project",
+        "syncMemoryFile": true,
+        "workerPort": 37777,
+        "observationFeed": {
+          "enabled": true,
+          "channel": "telegram",
+          "to": "123456789"
+        }
+      }
+    }
+  }
+}
+```
+
+### Restart and verify
+
+Restart the gateway. Check the logs for these three lines in order:
+
+```
+[claude-mem] Observation feed starting — channel: telegram, target: 123456789
+[claude-mem] Connecting to SSE stream at http://localhost:37777/stream
+[claude-mem] Connected to SSE stream
+```
+
+Then run `/claude_mem_feed` in any OpenClaw chat:
+
+```
+Claude-Mem Observation Feed
+Enabled: yes
+Channel: telegram
+Target: 123456789
+Connection: connected
+```
+
+If `Connection` shows `connected`, you're done. Have an agent do some work and watch observations stream to your channel.
+
+## Commands Reference
+
+The plugin registers two commands:
+
+### /claude_mem_status
+
+Reports worker health and current session state.
+
+```
+/claude_mem_status
+```
+
+Output:
+```
+Claude-Mem Worker Status
+Status: ok
+Port: 37777
+Active sessions: 2
+Observation feed: connected
+```
+
+### /claude_mem_feed
+
+Shows observation feed status. Accepts optional `on`/`off` argument.
+
+```
+/claude_mem_feed          — show status
+/claude_mem_feed on       — request enable (update config to persist)
+/claude_mem_feed off      — request disable (update config to persist)
+```
+
+## How It All Works
+
+```
+OpenClaw Gateway
+  │
+  ├── before_agent_start ──→ Sync MEMORY.md + Init session
+  ├── tool_result_persist ──→ Record observation + Re-sync MEMORY.md
+  ├── agent_end ────────────→ Summarize + Complete session
+  └── gateway_start ────────→ Reset session tracking
+                    │
+                    ▼
+         Claude-Mem Worker (localhost:37777)
+           ├── POST /api/sessions/init
+           ├── POST /api/sessions/observations
+           ├── POST /api/sessions/summarize
+           ├── POST /api/sessions/complete
+           ├── GET  /api/context/inject ──→ MEMORY.md content
+           └── GET  /stream ─────────────→ SSE → Messaging channels
+```
+
+### MEMORY.md live sync
+
+The plugin writes `MEMORY.md` to each agent's workspace with the full observation timeline. It updates:
+- On every `before_agent_start` — agent gets fresh context before starting
+- On every `tool_result_persist` — context stays current as the agent works
+
+Updates are fire-and-forget (non-blocking). The agent is never held up waiting for MEMORY.md to write.
+
+### Observation recording
+
+Every tool use (Read, Write, Bash, etc.) is sent to the claude-mem worker as an observation. The worker's AI agent processes it into a structured observation with title, subtitle, facts, concepts, and narrative. Tools prefixed with `memory_` are skipped to avoid recursive recording.
+
+### Session lifecycle
+
+- **`before_agent_start`** — Creates a session in the worker, syncs MEMORY.md. Short prompts (under 10 chars) skip session init but still sync.
+- **`tool_result_persist`** — Records observation (fire-and-forget), re-syncs MEMORY.md (fire-and-forget). Tool responses are truncated to 1000 characters.
+- **`agent_end`** — Sends the last assistant message for summarization, then completes the session. Both fire-and-forget.
+- **`gateway_start`** — Clears all session tracking (session IDs, workspace mappings) so agents start fresh.
+
+### Observation feed
+
+A background service connects to the worker's SSE stream and forwards `new_observation` events to a configured messaging channel. The connection auto-reconnects with exponential backoff (1s → 30s max).
+
+## Troubleshooting
+
+| Problem | What to check |
+|---------|---------------|
+| Worker health check fails | Is bun installed? (`bun --version`). Is something else on port 37777? (`lsof -i :37777`). Try running directly: `bun plugin/scripts/worker-service.cjs start` |
+| Worker started from Claude Code install but not responding | Check `cd ~/.claude/plugins/marketplaces/thedotmack && npm run worker:status`. May need `npm run worker:restart`. |
+| Worker started from cloned repo but not responding | Check `cd /path/to/claude-mem && npm run worker:status`. Make sure you ran `npm install && npm run build` first. |
+| No MEMORY.md appearing | Check that `syncMemoryFile` is not set to `false`. Verify the agent's event context includes `workspaceDir`. |
+| Observations not being recorded | Check gateway logs for `[claude-mem]` messages. The worker must be running and reachable on localhost:37777. |
+| Feed shows `disconnected` | Worker's `/stream` endpoint not reachable. Check `workerPort` matches the actual worker port. |
+| Feed shows `reconnecting` | Connection dropped. The plugin auto-reconnects — wait up to 30 seconds. |
+| `Unknown channel type` in logs | The channel plugin (e.g., telegram) isn't loaded on your gateway. Make sure the channel is configured and running. |
+| `Observation feed disabled` in logs | Set `observationFeed.enabled` to `true` in your config. |
+| `Observation feed misconfigured` in logs | Both `observationFeed.channel` and `observationFeed.to` are required. |
+| No messages in channel despite `connected` | The feed only sends processed observations, not raw tool usage. There's a 1-2 second delay. Make sure the worker is actually processing observations (check http://localhost:37777). |
+
+## Full Config Reference
+
+```json
+{
+  "plugins": {
+    "claude-mem": {
+      "enabled": true,
+      "config": {
+        "project": "openclaw",
+        "syncMemoryFile": true,
+        "workerPort": 37777,
+        "observationFeed": {
+          "enabled": false,
+          "channel": "telegram",
+          "to": "123456789"
+        }
+      }
+    }
+  }
+}
+```
+
+| Field | Type | Default | Description |
+|-------|------|---------|-------------|
+| `project` | string | `"openclaw"` | Project name scoping observations in the database |
+| `syncMemoryFile` | boolean | `true` | Write MEMORY.md to agent workspaces |
+| `workerPort` | number | `37777` | Claude-mem worker service port |
+| `observationFeed.enabled` | boolean | `false` | Stream observations to a messaging channel |
+| `observationFeed.channel` | string | — | Channel type: `telegram`, `discord`, `slack`, `signal`, `whatsapp`, `line` |
+| `observationFeed.to` | string | — | Target chat/channel/user ID |

openclaw/TESTING.md

@@ -0,0 +1,279 @@
+# OpenClaw Claude-Mem Plugin — Testing Guide
+
+## Quick Start (Docker)
+
+The fastest way to test the plugin is using the pre-built Docker E2E environment:
+
+```bash
+cd openclaw
+
+# Automated test (builds, installs plugin on real OpenClaw, verifies everything)
+./test-e2e.sh
+
+# Interactive shell (for manual exploration)
+./test-e2e.sh --interactive
+
+# Just build the image
+./test-e2e.sh --build-only
+```
+
+---
+
+## Test Layers
+
+### 1. Unit Tests (fastest)
+
+```bash
+cd openclaw
+npm test    # compiles TypeScript, runs 17 tests
+```
+
+Tests plugin registration, service lifecycle, command handling, SSE integration, and all 6 channel types.
+
+### 2. Smoke Test
+
+```bash
+node test-sse-consumer.js
+```
+
+Quick check that the plugin loads and registers its service + command correctly.
+
+### 3. Container Unit Tests (fresh install)
+
+```bash
+./test-container.sh          # Unit tests in clean Docker
+./test-container.sh --full   # Integration tests with mock worker
+```
+
+### 4. E2E on Real OpenClaw (Docker)
+
+```bash
+./test-e2e.sh
+```
+
+This is the most comprehensive test. It:
+1. Uses the official `ghcr.io/openclaw/openclaw:main` Docker image
+2. Installs the plugin via `openclaw plugins install` (same as a real user)
+3. Enables the plugin via `openclaw plugins enable`
+4. Starts a mock claude-mem worker on port 37777
+5. Starts the OpenClaw gateway with plugin config
+6. Verifies the plugin loads, connects to SSE, and processes events
+
+**All 16 checks must pass.**
+
+---
+
+## Human E2E Testing (Interactive Docker)
+
+For manual walkthrough testing, use the interactive Docker mode:
+
+```bash
+./test-e2e.sh --interactive
+```
+
+This drops you into a fully-configured OpenClaw container with the plugin pre-installed.
+
+### Step-by-step inside the container
+
+#### 1. Verify plugin is installed
+
+```bash
+node openclaw.mjs plugins list
+node openclaw.mjs plugins info claude-mem
+node openclaw.mjs plugins doctor
+```
+
+**Expected:**
+- `claude-mem` appears in the plugins list as "enabled" or "loaded"
+- Info shows version 1.0.0, source at `/home/node/.openclaw/extensions/claude-mem/`
+- Doctor reports no issues
+
+#### 2. Inspect plugin files
+
+```bash
+ls -la /home/node/.openclaw/extensions/claude-mem/
+cat /home/node/.openclaw/extensions/claude-mem/openclaw.plugin.json
+cat /home/node/.openclaw/extensions/claude-mem/package.json
+```
+
+**Expected:**
+- `dist/index.js` exists (compiled plugin)
+- `openclaw.plugin.json` has `"id": "claude-mem"` and `"kind": "memory"`
+- `package.json` has `openclaw.extensions` field pointing to `./dist/index.js`
+
+#### 3. Start mock worker
+
+```bash
+node /app/mock-worker.js &
+```
+
+Verify it's running:
+
+```bash
+curl -s http://localhost:37777/health
+# → {"status":"ok"}
+
+curl -s --max-time 3 http://localhost:37777/stream
+# → data: {"type":"connected","message":"Mock worker SSE stream"}
+# → data: {"type":"new_observation","observation":{...}}
+```
+
+#### 4. Configure and start gateway
+
+```bash
+cat > /home/node/.openclaw/openclaw.json << 'EOF'
+{
+  "gateway": {
+    "mode": "local",
+    "auth": {
+      "mode": "token",
+      "token": "e2e-test-token"
+    }
+  },
+  "plugins": {
+    "slots": {
+      "memory": "claude-mem"
+    },
+    "entries": {
+      "claude-mem": {
+        "enabled": true,
+        "config": {
+          "workerPort": 37777,
+          "observationFeed": {
+            "enabled": true,
+            "channel": "telegram",
+            "to": "test-chat-id-12345"
+          }
+        }
+      }
+    }
+  }
+}
+EOF
+
+node openclaw.mjs gateway --allow-unconfigured --verbose --token e2e-test-token
+```
+
+**Expected in gateway logs:**
+- `[claude-mem] OpenClaw plugin loaded — v1.0.0`
+- `[claude-mem] Observation feed starting — channel: telegram, target: test-chat-id-12345`
+- `[claude-mem] Connecting to SSE stream at http://localhost:37777/stream`
+- `[claude-mem] Connected to SSE stream`
+
+#### 5. Run automated verification (optional)
+
+From a second shell in the container (or after stopping the gateway):
+
+```bash
+/bin/bash /app/e2e-verify.sh
+```
+
+---
+
+## Manual E2E (Real OpenClaw + Real Worker)
+
+For testing with a real claude-mem worker and real messaging channel:
+
+### Prerequisites
+
+- OpenClaw gateway installed and configured
+- Claude-Mem worker running on port 37777
+- Plugin built: `cd openclaw && npm run build`
+
+### 1. Install the plugin
+
+```bash
+# Build the plugin
+cd openclaw && npm run build
+
+# Install on OpenClaw (from the openclaw/ directory)
+openclaw plugins install .
+
+# Enable it
+openclaw plugins enable claude-mem
+```
+
+### 2. Configure
+
+Edit `~/.openclaw/openclaw.json` to add plugin config:
+
+```json
+{
+  "plugins": {
+    "entries": {
+      "claude-mem": {
+        "enabled": true,
+        "config": {
+          "workerPort": 37777,
+          "observationFeed": {
+            "enabled": true,
+            "channel": "telegram",
+            "to": "YOUR_CHAT_ID"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+**Supported channels:** `telegram`, `discord`, `signal`, `slack`, `whatsapp`, `line`
+
+### 3. Restart gateway
+
+```bash
+openclaw restart
+```
+
+**Look for in logs:**
+- `[claude-mem] OpenClaw plugin loaded — v1.0.0`
+- `[claude-mem] Connected to SSE stream`
+
+### 4. Trigger an observation
+
+Start a Claude Code session with claude-mem enabled and perform any action. The worker will emit a `new_observation` SSE event.
+
+### 5. Verify delivery
+
+Check the target messaging channel for:
+
+```
+🧠 Claude-Mem Observation
+**Observation Title**
+Optional subtitle
+```
+
+---
+
+## Troubleshooting
+
+### `api.log is not a function`
+The plugin was built against the wrong API. Ensure `src/index.ts` uses `api.logger.info()` not `api.log()`. Rebuild with `npm run build`.
+
+### Worker not running
+- **Symptom:** `SSE stream error: fetch failed. Reconnecting in 1s`
+- **Fix:** Start the worker: `cd /path/to/claude-mem && npm run build-and-sync`
+
+### Port mismatch
+- **Fix:** Ensure `workerPort` in config matches the worker's actual port (default: 37777)
+
+### Channel not configured
+- **Symptom:** `Observation feed misconfigured — channel or target missing`
+- **Fix:** Add both `channel` and `to` to `observationFeed` in config
+
+### Unknown channel type
+- **Fix:** Use: `telegram`, `discord`, `signal`, `slack`, `whatsapp`, or `line`
+
+### Feed disabled
+- **Symptom:** `Observation feed disabled`
+- **Fix:** Set `observationFeed.enabled: true`
+
+### Messages not arriving
+1. Verify the bot/integration is configured in the target channel
+2. Check the target ID (`to`) is correct
+3. Look for `Failed to send to <channel>` in logs
+4. Test the channel via OpenClaw's built-in tools
+
+### Memory slot conflict
+- **Symptom:** `plugin disabled (memory slot set to "memory-core")`
+- **Fix:** Add `"slots": { "memory": "claude-mem" }` to plugins config