chore: bump version to 12.1.5

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.agent/rules/claude-mem-context.md

@@ -0,0 +1,7 @@
+<claude-mem-context>
+# claude-mem: Cross-Session Memory
+
+*No context yet. Complete your first session and context will appear here.*
+
+Use claude-mem's MCP search tools for manual memory queries.
+</claude-mem-context>

.claude-plugin/CLAUDE.md

@@ -1,8 +1,6 @@
 <claude-mem-context>
 # Recent Activity
 
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
 ### Oct 25, 2025
 
 | ID | Time | T | Title | Read |

.claude-plugin/marketplace.json

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

.claude-plugin/plugin.json

@@ -0,0 +1,24 @@
+{
+  "name": "claude-mem",
+  "version": "12.1.5",
+  "description": "Memory compression system for Claude Code - persist context across sessions",
+  "author": {
+    "name": "Alex Newman"
+  },
+  "repository": "https://github.com/thedotmack/claude-mem",
+  "license": "AGPL-3.0",
+  "keywords": [
+    "claude",
+    "claude-code",
+    "claude-agent-sdk",
+    "mcp",
+    "plugin",
+    "memory",
+    "compression",
+    "knowledge-graph",
+    "transcript",
+    "typescript",
+    "nodejs"
+  ],
+  "homepage": "https://github.com/thedotmack/claude-mem#readme"
+}

.claude/CLAUDE.md

@@ -1,29 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Dec 21, 2025
-
-**test-analysis-report.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #31743 | 10:36 PM | 🔵 | PR #412 proposes mode system with inheritance and multilingual support | ~523 |
-
-### Dec 22, 2025
-
-**test-analysis-report.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #31865 | 6:56 PM | ✅ | 開発ドキュメントのクリーンアップをコミット | ~150 |
-| #31864 | " | ✅ | 計画ドキュメントと分析ファイルの削除 | ~142 |
-| #31859 | 6:55 PM | ✅ | 計画ドキュメントファイルの削除 | ~109 |
-| #31855 | 6:53 PM | ✅ | テストスイートの大規模削除とテスト分析レポートの追加 | ~197 |
-
-### Dec 25, 2025
-
-**settings.json**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #32602 | 8:42 PM | 🔵 | Identified potential settings configuration files | ~224 |
-</claude-mem-context>

.claude/commands/CLAUDE.md

@@ -1,34 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Oct 25, 2025
-
-**changelog.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #2491 | 10:59 PM | 🟣 | Added changelog viewer slash command | ~290 |
-
-**terminal-shortcut.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #2480 | 6:32 PM | 🟣 | Cross-platform terminal shortcut command for claude-mem CLI | ~459 |
-
-**setup-alias.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #2479 | 6:29 PM | 🟣 | Shell Alias Setup Slash Command | ~423 |
-
-**version-bump.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #2358 | 1:07 PM | 🟣 | Created version-bump slash command for automated version updates | ~361 |
-
-### Jan 1, 2026
-
-**anti-pattern-czar.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #35638 | 11:17 PM | 🟣 | Anti-Pattern Czar Custom Command Created | ~583 |
-</claude-mem-context>

.claude/commands/do.md

@@ -1,38 +0,0 @@
-You are an ORCHESTRATOR.
-
-Primary instruction: deploy subagents to execute *all* work for #$ARGUMENTS.
-Do not do the work yourself except to coordinate, route context, and verify that each subagent completed its assigned checklist.
-
-Deploy subagents to execute each phase of #$ARGUMENTS independently and consecutively. For every checklist item below, explicitly deploy (or reuse) a subagent responsible for that item and record its outcome before proceeding.
-
-## Execution Protocol (Orchestrator-Driven)
-
-Orchestrator rules:
-- Each phase uses fresh subagents where noted (or when context is large/unclear).
-- The orchestrator assigns one clear objective per subagent and requires evidence (commands run, outputs, files changed).
-- Do not advance to the next step until the assigned subagent reports completion and the orchestrator confirms it matches the plan.
-
-### During Each Phase:
-Deploy an "Implementation" subagent to:
-1. Execute the implementation as specified
-2. COPY patterns from documentation, don't invent
-3. Cite documentation sources in code comments when using unfamiliar APIs
-4. If an API seems missing, STOP and verify - don't assume it exists
-
-### After Each Phase:
-Deploy subagents for each post-phase responsibility:
-1. **Run verification checklist** - Deploy a "Verification" subagent to prove the phase worked
-2. **Anti-pattern check** - Deploy an "Anti-pattern" subagent to grep for known bad patterns from the plan
-3. **Code quality review** - Deploy a "Code Quality" subagent to review changes
-4. **Commit only if verified** - Deploy a "Commit" subagent *only after* verification passes; otherwise, do not commit
-
-### Between Phases:
-Deploy a "Branch/Sync" subagent to:
-- Push to working branch after each verified phase
-- Prepare the next phase handoff so the next phase's subagents start fresh but have plan context
-
-## Failure Modes to Prevent
-- Don't invent APIs that "should" exist - verify against docs
-- Don't add undocumented parameters - copy exact signatures
-- Don't skip verification - deploy a verification subagent and run the checklist
-- Don't commit before verification passes (or without explicit orchestrator approval)

.claude/commands/make-plan.md

@@ -1,61 +0,0 @@
-You are an ORCHESTRATOR.
-
-Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.
-
-Delegation model (because subagents can under-report):
-- Use subagents for *fact gathering and extraction* (docs, examples, signatures, grep results).
-- Keep *synthesis and plan authoring* with the orchestrator (phase boundaries, task framing, final wording).
-- If a subagent report is incomplete or lacks evidence, the orchestrator must re-check with targeted reads/greps before finalizing the plan.
-
-Subagent reporting contract (MANDATORY):
-- Each subagent response must include:
-   1) Sources consulted (files/URLs) and what was read
-   2) Concrete findings (exact API names/signatures; exact file paths/locations)
-   3) Copy-ready snippet locations (example files/sections to copy)
-   4) "Confidence" note + known gaps (what might still be missing)
-- Reject and redeploy the subagent if it reports conclusions without sources.
-
-## Plan Structure Requirements
-
-### Phase 0: Documentation Discovery (ALWAYS FIRST)
-Before planning implementation, you MUST:
-Deploy one or more "Documentation Discovery" subagents to:
-1. Search for and read relevant documentation, examples, and existing patterns
-2. Identify the actual APIs, methods, and signatures available (not assumed)
-3. Create a brief "Allowed APIs" list citing specific documentation sources
-4. Note any anti-patterns to avoid (methods that DON'T exist, deprecated parameters)
-
-Then the orchestrator consolidates their findings into a single Phase 0 output.
-
-### Each Implementation Phase Must Include:
-1. **What to implement** - Frame tasks to COPY from docs, not transform existing code
-   - Good: "Copy the V2 session pattern from docs/examples.ts:45-60"
-   - Bad: "Migrate the existing code to V2"
-2. **Documentation references** - Cite specific files/lines for patterns to follow
-3. **Verification checklist** - How to prove this phase worked (tests, grep checks)
-4. **Anti-pattern guards** - What NOT to do (invented APIs, undocumented params)
-
-Subagent-friendly split:
-- Subagents can propose candidate doc references and verification commands.
-- The orchestrator must write the final phase text, ensuring tasks are copy-based, scoped, and independently executable.
-
-### Final Phase: Verification
-1. Verify all implementations match documentation
-2. Check for anti-patterns (grep for known bad patterns)
-3. Run tests to confirm functionality
-
-Delegation guidance:
-- Deploy a "Verification" subagent to draft the checklist and commands.
-- The orchestrator must review the checklist for completeness and ensure it maps to earlier phase outputs.
-
-## Key Principles
-- Documentation Availability ≠ Usage: Explicitly require reading docs
-- Task Framing Matters: Direct agents to docs, not just outcomes
-- Verify > Assume: Require proof, not assumptions about APIs
-- Session Boundaries: Each phase should be self-contained with its own doc references
-
-## Anti-Patterns to Prevent
-- Inventing API methods that "should" exist
-- Adding parameters not in documentation
-- Skipping verification steps
-- Assuming structure without checking examples

.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/CLAUDE.md

@@ -1,7 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-*No recent activity*
-</claude-mem-context>

.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/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/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-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/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/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.

.claude/reports/CLAUDE.md

@@ -1,22 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Jan 5, 2026
-
-**CLAUDE.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #38082 | 10:13 PM | ✅ | Merge Conflict Resolution - Kept Feature Branch Versions | ~431 |
-
-**test-audit-2026-01-05.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #37776 | 6:35 PM | 🔵 | Test Audit Reveals Quality Issues and Architecture Recommendations | ~372 |
-| #37775 | " | 🔵 | Test Audit Identifies Zero Coverage for Logger FormatTool Tests | ~280 |
-| #37747 | 6:20 PM | 🔵 | Comprehensive Test Suite Audit Completed: 41 Files Analyzed | ~664 |
-| #37736 | 6:16 PM | 🔵 | Test Suite Audit Reveals Critical Test Failure Root Cause | ~660 |
-| #37735 | " | ✅ | Test Suite Audit Report Generated: 41 Tests Scored and Analyzed | ~634 |
-| #37732 | 6:15 PM | 🔵 | Test Quality Audit Completed: Identified Critical Mock Pollution Issue | ~490 |
-</claude-mem-context>

.claude/scheduled_tasks.lock

@@ -0,0 +1 @@
+{"sessionId":"6a00de6e-282e-4cd8-98ec-b5afb73c468d","pid":50072,"acquiredAt":1775678989779}

.claude/skills/CLAUDE.md

@@ -26,49 +26,4 @@ Manages semantic versioning for the claude-mem project itself. Handles updating
 ## Adding New Skills
 
 **For claude-mem development** → Add to `.claude/skills/`
-**For end users** → Add to `plugin/skills/` (gets distributed with plugin)
-
-
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Nov 9, 2025
-
-**CLAUDE.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #5901 | 6:54 PM | ✅ | Project Skills Documentation Created | ~317 |
-
-### Dec 13, 2025
-
-**CLAUDE.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #24725 | 4:07 PM | 🔵 | Claude Skills Infrastructure for Automation | ~220 |
-
-### Dec 14, 2025
-
-**CLAUDE.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #26354 | 9:20 PM | 🔵 | PR #317 Second CLAUDE.md Compliance Review Confirms No Violations | ~442 |
-| #26353 | " | 🔵 | PR #317 CLAUDE.md Compliance Review Completed | ~402 |
-| #26193 | 8:15 PM | 🔵 | PR spans 21 files with net addition of 374 lines across codebase | ~375 |
-| #26173 | 8:08 PM | ✅ | Updated Skills CLAUDE.md Documentation for Version Bump | ~277 |
-
-### Dec 28, 2025
-
-**CLAUDE.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #33311 | 3:09 PM | ✅ | Version 8.2.3 Release Deployed with Worker Stability Improvements | ~434 |
-
-### Jan 5, 2026
-
-**CLAUDE.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #38082 | 10:13 PM | ✅ | Merge Conflict Resolution - Kept Feature Branch Versions | ~431 |
-</claude-mem-context>
+**For end users** → Add to `plugin/skills/` (gets distributed with plugin)

.codex-plugin/plugin.json

@@ -0,0 +1,43 @@
+{
+  "name": "claude-mem",
+  "version": "12.1.5",
+  "description": "Memory compression system for Claude Code - persist context across sessions",
+  "author": {
+    "name": "Alex Newman",
+    "url": "https://github.com/thedotmack"
+  },
+  "homepage": "https://github.com/thedotmack/claude-mem#readme",
+  "repository": "https://github.com/thedotmack/claude-mem",
+  "license": "AGPL-3.0",
+  "keywords": [
+    "claude",
+    "claude-code",
+    "claude-agent-sdk",
+    "mcp",
+    "plugin",
+    "memory",
+    "compression",
+    "knowledge-graph",
+    "transcript",
+    "typescript",
+    "nodejs"
+  ],
+  "interface": {
+    "displayName": "claude-mem",
+    "shortDescription": "Persistent memory and context compression across coding sessions.",
+    "longDescription": "claude-mem captures coding-session activity, compresses it into reusable observations, and injects relevant context back into future Claude Code and Codex-compatible sessions.",
+    "developerName": "Alex Newman",
+    "category": "Productivity",
+    "capabilities": [
+      "Interactive",
+      "Write"
+    ],
+    "websiteURL": "https://github.com/thedotmack/claude-mem",
+    "defaultPrompt": [
+      "Find what I already learned about this codebase before I start a new task.",
+      "Show recent observations related to the files I am editing right now.",
+      "Summarize the last session and inject the most relevant context into this one."
+    ],
+    "brandColor": "#1F6FEB"
+  }
+}

.gitattributes

@@ -0,0 +1,21 @@
+# Normalize all text files to LF on commit and checkout.
+# This prevents CRLF shebang lines in bundled scripts from breaking
+# the MCP server on macOS/Linux when built on Windows. Fixes #1342.
+* text=auto eol=lf
+
+# Compiled plugin scripts must always be LF — CRLF in the shebang
+# causes "env: node\r: No such file or directory" on non-Windows hosts.
+plugin/scripts/*.cjs eol=lf
+plugin/scripts/*.js  eol=lf
+
+# Explicitly mark binary assets so git never modifies them.
+*.png  binary
+*.jpg  binary
+*.jpeg binary
+*.ico  binary
+*.gif  binary
+*.woff  binary
+*.woff2 binary
+*.ttf   binary
+*.eot   binary
+*.otf   binary

.github/ISSUE_TEMPLATE/CLAUDE.md

@@ -1,21 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Dec 13, 2025
-
-**feature_request.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #25012 | 6:41 PM | 🟣 | Auto-Convert Feature Requests to GitHub Discussions | ~298 |
-| #25011 | " | ✅ | Staged GitHub Feature Request Automation Files | ~206 |
-| #25009 | 6:40 PM | ✅ | Feature Request Template Auto-Labeling Configured | ~241 |
-| #24995 | 6:26 PM | 🔵 | Standard Feature Request Template Configuration | ~260 |
-
-**bug_report.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #24994 | 6:26 PM | 🔵 | Standard Bug Report Template Configuration | ~258 |
-| #24992 | " | 🔵 | GitHub Issue Templates Located | ~188 |
-</claude-mem-context>

.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/copilot-instructions.md

@@ -0,0 +1,7 @@
+<claude-mem-context>
+# claude-mem: Cross-Session Memory
+
+*No context yet. Complete your first session and context will appear here.*
+
+Use claude-mem's MCP search tools for manual memory queries.
+</claude-mem-context>

.github/issues/CLAUDE.md

@@ -1,7 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-*No recent activity*
-</claude-mem-context>

.github/workflows/CLAUDE.md

@@ -1,82 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Dec 13, 2025
-
-**convert-feature-requests.yml**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #25022 | 6:48 PM | ✅ | Workflow Fix Committed to Repository | ~289 |
-| #25021 | " | 🔴 | Fixed Issue Number Reference in Workflow Steps | ~277 |
-| #25020 | " | 🔴 | Workflow String Interpolation Fixed by Consolidating Steps | ~339 |
-| #25019 | 6:47 PM | 🔵 | GitHub Workflow Automates Feature Request Triage | ~328 |
-| #25012 | 6:41 PM | 🟣 | Auto-Convert Feature Requests to GitHub Discussions | ~298 |
-| #25011 | " | ✅ | Staged GitHub Feature Request Automation Files | ~206 |
-| #25010 | 6:40 PM | 🟣 | GitHub Action Workflow for Feature Request Auto-Conversion | ~414 |
-
-**summary.yml**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #25002 | 6:38 PM | 🔵 | AI Summary Workflow for New Issues | ~239 |
-
-**claude.yml**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #24997 | 6:27 PM | 🔵 | Claude Code Action Workflow for Issue and PR Comments | ~242 |
-| #24727 | 4:08 PM | 🔵 | GitHub Automation Baseline Assessment | ~312 |
-| #24722 | 4:06 PM | 🔵 | Existing Claude Workflow Trigger Configuration | ~233 |
-
-**claude-code-review.yml**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #24996 | 6:27 PM | 🔵 | Existing GitHub Actions Workflows Identified | ~199 |
-| #24723 | 4:06 PM | 🔵 | Automated PR Review Workflow Pattern | ~268 |
-| #24720 | " | 🔵 | GitHub Workflows Inventory | ~142 |
-
-### Dec 17, 2025
-
-**issue-list-query**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #28918 | 7:27 PM | 🔵 | Four open issues identified - MCP connection, Bun PATH, web UI path, and endless mode | ~432 |
-
-**pr-list-query**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #28917 | 7:27 PM | 🔵 | Recent PRs audit reveals comprehensive Windows stabilization and MCP fixes | ~414 |
-
-**windows-ci.yml**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #28655 | 5:30 PM | ✅ | Windows CI Removal Committed to Repository | ~253 |
-| #28654 | " | ✅ | Windows CI Workflow File Removed | ~174 |
-| #28650 | 5:26 PM | ✅ | Committed Windows CI Workflow Simplification | ~213 |
-| #28649 | " | ✅ | Removed Build and Install Steps from Windows CI | ~278 |
-| #28648 | " | 🔵 | Windows CI Workflow Includes Build Step | ~288 |
-| #28644 | 5:24 PM | ✅ | Modified 27 files with 693 additions and 239 deletions for Windows support | ~447 |
-| #28625 | 5:19 PM | 🟣 | Windows CI Testing Workflow Deployed | ~303 |
-| #28624 | " | ✅ | Windows CI Workflow File Staged for Commit | ~163 |
-| #28623 | " | 🔵 | Windows CI Workflow File Present But Untracked | ~178 |
-| #28622 | 5:18 PM | 🟣 | Windows CI Pipeline with Worker Lifecycle Testing | ~326 |
-
-### Dec 31, 2025
-
-**claude-code-review.yml**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34627 | 3:01 PM | 🔵 | Claude Code Review GitHub Action Provides Automated PR Review Integration | ~478 |
-
-**claude.yml**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34626 | 3:01 PM | 🔵 | Test-Driven Validation Agent Performing Extensive Infrastructure Analysis | ~501 |
-
-### Jan 6, 2026
-
-**windows-ci.yml**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #38108 | 12:15 AM | 🔵 | Complete Windows Zombie Port Bug Technical Deep Dive | ~935 |
-</claude-mem-context>

.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:
@@ -27,7 +27,7 @@ jobs:
 
       - name: Comment with AI summary
         run: |
-          gh issue comment $ISSUE_NUMBER --body '${{ steps.inference.outputs.response }}'
+          gh issue comment "$ISSUE_NUMBER" --body "$RESPONSE"
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           ISSUE_NUMBER: ${{ github.event.issue.number }}

.gitignore

@@ -1,6 +1,7 @@
 datasets/
 node_modules/
 dist/
+**/_tree-sitter/
 *.log
 .DS_Store
 .env
@@ -11,12 +12,14 @@ 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
@@ -25,9 +28,13 @@ src/ui/viewer.html
 .mcp.json
 .cursor/
 
-# Prevent literal tilde directories (path validation bug artifacts)
-~*/
+# Ignore WebStorm project files (for dinosaur IDE users)
+.idea/
 
-# Prevent other malformed path directories
-http*/
-https*/
+.claude-octopus/
+.claude/session-intent.md
+.claude/session-plan.md
+.octo/
+
+# Local contribution analysis (not part of upstream)
+CONTRIB_NOTES.md

.markdownlint.json

@@ -0,0 +1,3 @@
+{
+  "MD013": false
+}

.npmignore

@@ -0,0 +1,48 @@
+# Source code (dist/ and plugin/ are the shipped artifacts)
+src/
+scripts/
+tests/
+docs/
+datasets/
+private/
+antipattern-czar/
+
+# Heavy binaries installed at runtime via smart-install.js
+plugin/node_modules/
+plugin/scripts/claude-mem
+plugin/bun.lock
+plugin/data/
+plugin/data.backup/
+
+# Development files
+*.ts
+!*.d.ts
+tsconfig*.json
+.eslintrc*
+.prettierrc*
+.editorconfig
+jest.config*
+vitest.config*
+
+# Git and CI
+.git/
+.github/
+.gitignore
+.claude/
+.cursor/
+.mcp.json
+.plan/
+
+# OS files
+.DS_Store
+*.log
+*.tmp
+*.temp
+Thumbs.db
+
+# Misc
+Auto Run Docs/
+~*/
+http*/
+https*/
+.idea/

.npmrc

@@ -0,0 +1 @@
+legacy-peer-deps=true

.plan/npx-distribution.md

@@ -0,0 +1,736 @@
+# Plan: NPX Distribution + Universal IDE/CLI Coverage for claude-mem
+
+## Problem
+
+1. **Installation is slow and fragile**: Current install clones the full git repo, runs `npm install`, and builds from source. The npm package already ships pre-built artifacts.
+
+2. **IDE coverage is limited**: claude-mem only supports Claude Code (plugin) and Cursor (hooks installer). The AI coding tools landscape has exploded — Gemini CLI (95k stars), OpenCode (110k stars), Windsurf (~1M users), Codex CLI, Antigravity, Goose, Crush, Copilot CLI, and more all support extensibility.
+
+## Key Insights
+
+- **npm package already has everything**: `plugin/` directory ships pre-built. No git clone or build needed.
+- **Transcript watcher already exists**: `src/services/transcripts/` has a fully built schema-based JSONL tailer. It just needs schemas for more tools.
+- **3 integration tiers exist**: (1) Hook/plugin-based (Claude Code, Gemini CLI, OpenCode, Windsurf, Codex CLI, OpenClaw), (2) MCP-based (Cursor, Copilot CLI, Antigravity, Goose, Crush, Roo Code), (3) Transcript-based (anything with structured log files).
+- **OpenClaw plugin already built**: Full plugin at `openclaw/src/index.ts` (1000+ lines). Needs to be wired into the npx installer.
+- **Gemini CLI is architecturally near-identical to Claude Code**: 11 lifecycle hooks, JSON via stdin/stdout, exit code 0/2 convention, `GEMINI.md` context files, `~/.gemini/settings.json`. This is the easiest high-value integration.
+- **OpenCode has the richest plugin system**: 20+ hook events across 12 categories, JS/TS plugin modules, custom tool creation, MCP support. 110k stars — largest open-source AI CLI.
+- **`npx skills` by Vercel supports 41 agents** — proving the multi-IDE installer UX works. Their agent detection pattern (check if config dir exists) is the right model.
+- **All IDEs share a single worker on port 37777**: One worker serves all integrations. Session source (which IDE) is tracked via the `source` field in hook payloads. No per-IDE worker instances.
+- **This npx CLI fully replaces the old `claude-mem-installer`**: Not a supplement — the complete replacement.
+
+## Solution
+
+`npx claude-mem` becomes a unified CLI: install, configure any IDE, manage the worker, search memory.
+
+```
+npx claude-mem                          # Interactive install + IDE selection
+npx claude-mem install                  # Same as above
+npx claude-mem install --ide windsurf   # Direct IDE setup
+npx claude-mem start / stop / status    # Worker management
+npx claude-mem search <query>           # Search memory from terminal
+npx claude-mem transcript watch         # Start transcript watcher
+```
+
+## Platform Support
+
+**Windows, macOS, and Linux are all first-class targets.** Platform-specific considerations:
+
+- **Config paths**: Use `os.homedir()` and `path.join()` everywhere — never hardcode `/` or `~`
+- **Shebangs**: `#!/usr/bin/env node` for the CLI entry point (cross-platform via Node)
+- **Bun detection**: Check `PATH`, common install locations per platform (`%USERPROFILE%\.bun\bin\bun.exe` on Windows, `~/.bun/bin/bun` on Unix)
+- **File permissions**: `fs.chmod` is a no-op on Windows; don't gate on it
+- **Process management**: Worker start/stop uses signals on Unix, taskkill on Windows — match existing `worker-service.ts` patterns
+- **VS Code paths**: `~/Library/Application Support/Code/` (macOS), `~/.config/Code/` (Linux), `%APPDATA%/Code/` (Windows)
+- **Shell config**: `.bashrc`/`.zshrc` on Unix, PowerShell profile on Windows (for PATH modifications if needed)
+
+---
+
+## Phase 0: Research Findings
+
+### IDE Integration Tiers
+
+**Tier 1 — Native Hook/Plugin Systems** (highest fidelity, real-time capture):
+
+| Tool | Hooks | Config Location | Context Injection | Stars/Users |
+|------|-------|----------------|-------------------|-------------|
+| Claude Code | 5 lifecycle hooks | `~/.claude/settings.json` | CLAUDE.md, plugins | ~25% market |
+| Gemini CLI | 11 lifecycle hooks | `~/.gemini/settings.json` | GEMINI.md | ~95k stars |
+| OpenCode | 20+ event hooks + plugin SDK | `~/.config/opencode/opencode.json` | AGENTS.md + rules dirs | ~110k stars |
+| Windsurf | 11 Cascade hooks | `.windsurf/hooks.json` | `.windsurf/rules/*.md` | ~1M users |
+| Codex CLI | `notify` hook | `~/.codex/config.toml` | `.codex/AGENTS.md`, MCP | Growing (OpenAI) |
+| OpenClaw | 8 event hooks + plugin SDK | `~/.openclaw/openclaw.json` | MEMORY.md sync | ~196k stars |
+
+**Tier 2 — MCP Integration** (tool-based, search + context injection):
+
+| Tool | MCP Support | Config Location | Context Injection |
+|------|------------|----------------|-------------------|
+| Cursor | First-class | `.cursor/mcp.json` | `.cursor/rules/*.mdc` |
+| Copilot CLI | First-class (default MCP) | `~/.copilot/config` | `.github/copilot-instructions.md` |
+| Antigravity | First-class + MCP Store | `~/.gemini/antigravity/mcp_config.json` | `.agent/rules/`, GEMINI.md |
+| Goose | Native MCP (co-developed protocol) | `~/.config/goose/config.yaml` | MCP context |
+| Crush | MCP + Skills | JSON config (charm.land schema) | Skills system |
+| Roo Code | First-class | `.roo/` | `.roo/rules/*.md`, `AGENTS.md` |
+| Warp | MCP + Warp Drive | `WARP.md` + Warp Drive UI | `WARP.md` |
+
+**Tier 3 — Transcript File Watching** (passive, file-based):
+
+| Tool | Transcript Location | Format |
+|------|-------------------|--------|
+| Claude Code | `~/.claude/projects/<proj>/<session>.jsonl` | JSONL |
+| Codex CLI | `~/.codex/sessions/**/*.jsonl` | JSONL |
+| Gemini CLI | `~/.gemini/tmp/<hash>/chats/` | JSON |
+| OpenCode | `.opencode/` (SQLite) | SQLite — needs export |
+
+### What claude-mem Already Has
+
+| Component | Status | Location |
+|-----------|--------|----------|
+| Claude Code plugin | Complete | `plugin/hooks/hooks.json` |
+| Cursor hooks installer | Complete | `src/services/integrations/CursorHooksInstaller.ts` |
+| Platform adapters | Claude Code + Cursor + raw | `src/cli/adapters/` |
+| Transcript watcher | Complete (schema-based JSONL) | `src/services/transcripts/` |
+| Codex transcript schema | Sample exists | `src/services/transcripts/config.ts` |
+| OpenClaw plugin | Complete (1000+ lines) | `openclaw/src/index.ts` |
+| MCP server | Complete | `plugin/scripts/mcp-server.cjs` |
+| Gemini CLI support | Not started | — |
+| OpenCode support | Not started | — |
+| Windsurf support | Not started | — |
+
+### Patterns to Copy
+
+- **Agent detection from `npx skills`** (`vercel-labs/skills/src/agents.ts`): Check if config directory exists
+- **Existing installer logic** (`installer/src/steps/install.ts:29-83`): registerMarketplace, registerPlugin, enablePluginInClaudeSettings — **extract shared logic** from existing installer into reusable modules (DRY with the new CLI)
+- **Bun resolution** (`plugin/scripts/bun-runner.js`): PATH lookup + common locations per platform
+- **CursorHooksInstaller** (`src/services/integrations/CursorHooksInstaller.ts`): Reference implementation for IDE hooks installation
+
+---
+
+## Phase 1: NPX CLI Entry Point
+
+### What to implement
+
+1. **Add `bin` field to `package.json`**:
+   ```json
+   "bin": {
+     "claude-mem": "./dist/cli/index.js"
+   }
+   ```
+
+2. **Create `src/npx-cli/index.ts`** — a Node.js CLI router (NOT Bun) with command categories:
+
+   **Install commands** (pure Node.js, no Bun required):
+   - `npx claude-mem` or `npx claude-mem install` → interactive install (IDE multi-select)
+   - `npx claude-mem install --ide <name>` → direct IDE setup (only for implemented IDEs; unimplemented ones error with "Support for <name> coming soon")
+   - `npx claude-mem update` → update to latest version
+   - `npx claude-mem uninstall` → remove plugin and IDE configs
+   - `npx claude-mem version` → print version
+
+   **Runtime commands** (delegate to Bun via installed plugin):
+   - `npx claude-mem start` → spawns `bun worker-service.cjs start`
+   - `npx claude-mem stop` → spawns `bun worker-service.cjs stop`
+   - `npx claude-mem restart` → spawns `bun worker-service.cjs restart`
+   - `npx claude-mem status` → spawns `bun worker-service.cjs status`
+   - `npx claude-mem search <query>` → hits `GET http://localhost:37777/api/search?q=<query>`
+   - `npx claude-mem transcript watch` → starts transcript watcher
+
+   **Runtime commands must check for installation first**: If plugin directory doesn't exist at `~/.claude/plugins/marketplaces/thedotmack/`, print "claude-mem is not installed. Run: npx claude-mem install" and exit.
+
+3. **The install flow** (fully replaces git clone + build):
+   - Detect the npm package's own location (`import.meta.url` or `__dirname`)
+   - Copy `plugin/` from the npm package to `~/.claude/plugins/marketplaces/thedotmack/`
+   - Copy `plugin/` to `~/.claude/plugins/cache/thedotmack/claude-mem/<version>/`
+   - Register marketplace in `~/.claude/plugins/known_marketplaces.json`
+   - Register plugin in `~/.claude/plugins/installed_plugins.json`
+   - Enable in `~/.claude/settings.json`
+   - Run `npm install` in the marketplace dir (for `@chroma-core/default-embed` — native ONNX binaries, can't be bundled)
+   - Trigger smart-install.js for Bun/uv setup
+   - Run IDE-specific setup for each selected IDE
+
+4. **Interactive IDE selection** (auto-detect + prompt):
+   - Auto-detect installed IDEs by checking config directories
+   - Present multi-select with detected IDEs pre-selected
+   - Detection map:
+     - Claude Code: `~/.claude/` exists
+     - Gemini CLI: `~/.gemini/` exists
+     - OpenCode: `~/.config/opencode/` exists OR `opencode` in PATH
+     - OpenClaw: `~/.openclaw/` exists
+     - Windsurf: `~/.codeium/windsurf/` exists
+     - Codex CLI: `~/.codex/` exists
+     - Cursor: `~/.cursor/` exists
+     - Copilot CLI: `copilot` in PATH (it's a CLI tool, not a config dir)
+     - Antigravity: `~/.gemini/antigravity/` exists
+     - Goose: `~/.config/goose/` exists OR `goose` in PATH
+     - Crush: `crush` in PATH
+     - Roo Code: check for VS Code extension directory containing `roo-code`
+     - Warp: `~/.warp/` exists OR `warp` in PATH
+
+5. **The runtime command routing**:
+   - Locate the installed plugin directory
+   - Find Bun binary (same logic as `bun-runner.js`, platform-aware)
+   - Spawn `bun worker-service.cjs <command>` and pipe stdio through
+   - For `search`: HTTP request to running worker
+
+### Patterns to follow
+
+- `installer/src/steps/install.ts:29-83` for marketplace registration — **extract to shared module**
+- `plugin/scripts/bun-runner.js` for Bun resolution
+- `vercel-labs/skills/src/agents.ts` for IDE auto-detection pattern
+
+### Verification
+
+- `npx claude-mem install` copies plugin to correct directories on macOS, Linux, and Windows
+- Auto-detection finds installed IDEs
+- `npx claude-mem start/stop/status` work after install
+- `npx claude-mem search "test"` returns results
+- `npx claude-mem start` before install prints helpful error message
+- `npx claude-mem update` and `npx claude-mem uninstall` work correctly
+- `npx claude-mem version` prints version
+
+### Anti-patterns
+
+- Do NOT require Bun for install commands — pure Node.js
+- Do NOT clone the git repo
+- Do NOT build from source at install time
+- Do NOT depend on `bun:sqlite` in the CLI entry point
+
+---
+
+## Phase 2: Build Pipeline Integration
+
+### What to implement
+
+1. **Add CLI build step to `scripts/build-hooks.js`**:
+   - Compile `src/npx-cli/index.ts` → `dist/cli/index.js`
+   - Bundle `@clack/prompts` and `picocolors` into the output (self-contained)
+   - Shebang: `#!/usr/bin/env node`
+   - Set executable permissions (no-op on Windows, that's fine)
+
+2. **Move `@clack/prompts` and `picocolors`** to main package.json as dev dependencies (bundled by esbuild into dist/cli/index.js)
+
+3. **Verify `package.json` `files` field**: Currently `["dist", "plugin"]`. `dist/cli/index.js` is already included since it's under `dist/`. No change needed.
+
+4. **Update `prepublishOnly`** to ensure CLI is built before npm publish (already covered — `npm run build` calls `build-hooks.js`)
+
+5. **Pre-build OpenClaw plugin**: Add an esbuild step that compiles `openclaw/src/index.ts` → `openclaw/dist/index.js` so it ships ready-to-use. No `tsc` at install time.
+
+6. **Add `openclaw/dist/` to `package.json` `files` field** (or add `openclaw` if the whole directory should ship)
+
+### Verification
+
+- `npm run build` produces `dist/cli/index.js` with correct shebang
+- `npm run build` produces `openclaw/dist/index.js` pre-built
+- `npm pack` includes both `dist/cli/index.js` and `openclaw/dist/`
+- `node dist/cli/index.js --help` works without Bun
+- Package size is reasonable (check with `npm pack --dry-run`)
+
+---
+
+## Phase 3: Gemini CLI Integration (Tier 1 — Hook-Based)
+
+**Why first among new IDEs**: Near-identical architecture to Claude Code. 11 lifecycle hooks with JSON stdin/stdout, same exit code conventions (0=success, 2=block), `GEMINI.md` context files. 95k GitHub stars. Lowest effort, highest confidence.
+
+### Gemini CLI Hook Events
+
+| Event | Map to claude-mem | Use |
+|-------|-------------------|-----|
+| `SessionStart` | `session-init` | Start tracking session |
+| `BeforeAgent` | `user-prompt` | Capture user prompt |
+| `AfterAgent` | `observation` | Capture full agent response |
+| `BeforeTool` | — | Skip (pre-execution, no result yet) |
+| `AfterTool` | `observation` | Capture tool name + input + response |
+| `BeforeModel` | — | Skip (too low-level, LLM request details) |
+| `AfterModel` | — | Skip (raw LLM response, redundant with AfterAgent) |
+| `BeforeToolSelection` | — | Skip (internal planning step) |
+| `PreCompress` | `summary` | Trigger summary before context compression |
+| `Notification` | — | Skip (system alerts, not session data) |
+| `SessionEnd` | `session-end` | Finalize session |
+
+**Mapped**: 5 of 11 events. **Skipped**: 6 events that are either too low-level (BeforeModel/AfterModel), pre-execution (BeforeTool, BeforeToolSelection), or system-level (Notification).
+
+### Verified Stdin Payload Schemas (from `packages/core/src/hooks/types.ts`)
+
+**Base input (all hooks receive):**
+```typescript
+{ session_id: string, transcript_path: string, cwd: string, hook_event_name: string, timestamp: string }
+```
+
+**Event-specific fields:**
+| Event | Additional Fields |
+|-------|-------------------|
+| `SessionStart` | `source: "startup" \| "resume" \| "clear"` |
+| `SessionEnd` | `reason: "exit" \| "clear" \| "logout" \| "prompt_input_exit" \| "other"` |
+| `BeforeAgent` | `prompt: string` |
+| `AfterAgent` | `prompt: string, prompt_response: string, stop_hook_active: boolean` |
+| `BeforeTool` | `tool_name: string, tool_input: Record<string, unknown>, mcp_context?: McpToolContext, original_request_name?: string` |
+| `AfterTool` | `tool_name: string, tool_input: Record<string, unknown>, tool_response: Record<string, unknown>, mcp_context?: McpToolContext` |
+| `PreCompress` | `trigger: "auto" \| "manual"` |
+| `Notification` | `notification_type: "ToolPermission", message: string, details: Record<string, unknown>` |
+
+**Output (all hooks can return):**
+```typescript
+{ continue?: boolean, stopReason?: string, suppressOutput?: boolean, systemMessage?: string, decision?: "allow" | "deny" | "block" | "approve" | "ask", reason?: string, hookSpecificOutput?: Record<string, unknown> }
+```
+
+**Advisory (non-blocking) hooks:** SessionStart, SessionEnd, PreCompress, Notification — `continue` and `decision` fields are ignored.
+
+**Environment variables provided:** `GEMINI_PROJECT_DIR`, `GEMINI_SESSION_ID`, `GEMINI_CWD`, `CLAUDE_PROJECT_DIR` (compat alias)
+
+### What to implement
+
+1. **Create Gemini CLI platform adapter** at `src/cli/adapters/gemini-cli.ts`:
+   - Normalize Gemini CLI's hook JSON to `NormalizedHookInput`
+   - Base fields always present: `session_id`, `transcript_path`, `cwd`, `hook_event_name`, `timestamp`
+   - Map per event:
+     - `SessionStart`: `source` → session init metadata
+     - `BeforeAgent`: `prompt` → user prompt text
+     - `AfterAgent`: `prompt` + `prompt_response` → full conversation turn
+     - `AfterTool`: `tool_name` + `tool_input` + `tool_response` → observation
+     - `PreCompress`: `trigger` → summary trigger
+     - `SessionEnd`: `reason` → session finalization
+
+2. **Create Gemini CLI hooks installer** at `src/services/integrations/GeminiCliHooksInstaller.ts`:
+   - Write hooks to `~/.gemini/settings.json` under the `hooks` key
+   - Must **merge** with existing settings (read → parse → deep merge → write)
+   - Hook config format (verified against official docs):
+     ```json
+     {
+       "hooks": {
+         "AfterTool": [{
+           "matcher": "*",
+           "hooks": [{ "name": "claude-mem", "type": "command", "command": "<path-to-hook-script>", "timeout": 5000 }]
+         }]
+       }
+     }
+     ```
+   - Note: `matcher` uses regex for tool events, exact string for lifecycle events. `"*"` or `""` matches all.
+   - Hook groups support `sequential: boolean` (default false = parallel execution)
+   - Security: Project-level hooks are fingerprinted — if name/command changes, user is warned
+   - Context injection via `~/.gemini/GEMINI.md` (append claude-mem section with `<claude-mem-context>` tags, same pattern as CLAUDE.md)
+   - Settings hierarchy: project `.gemini/settings.json` > user `~/.gemini/settings.json` > system `/etc/gemini-cli/settings.json`
+
+3. **Register `gemini-cli` in `getPlatformAdapter()`** at `src/cli/adapters/index.ts`
+
+4. **Add Gemini CLI to installer IDE selection**
+
+### Verification
+
+- `npx claude-mem install --ide gemini-cli` merges hooks into `~/.gemini/settings.json`
+- Gemini CLI sessions are captured by the worker
+- `AfterTool` events produce observations with correct `tool_name`, `tool_input`, `tool_response`
+- `GEMINI.md` gets claude-mem context section
+- Existing Gemini CLI settings are preserved (merge, not overwrite)
+- Verify `session_id` from base input is used for session tracking
+
+### Anti-patterns
+
+- Do NOT overwrite `~/.gemini/settings.json` — must deep merge
+- Do NOT map all 11 events — the 6 skipped events would produce noise, not signal
+- Do NOT use `type: "runtime"` — that's for internal extensions only; use `type: "command"`
+- Advisory hooks (SessionStart, SessionEnd, PreCompress, Notification) cannot block — don't set `decision` or `continue` fields on them
+
+---
+
+## Phase 4: OpenCode Integration (Tier 1 — Plugin-Based)
+
+**Why next**: 110k stars, richest plugin ecosystem. OpenCode plugins are JS/TS modules auto-loaded from plugin directories. OpenCode also has a Claude Code compatibility fallback (reads `~/.claude/CLAUDE.md` if no global `AGENTS.md` exists, controllable via `OPENCODE_DISABLE_CLAUDE_CODE_PROMPT=1`).
+
+### Verified Plugin API (from `packages/plugin/src/index.ts`)
+
+**Plugin signature:**
+```typescript
+import { type Plugin, tool } from "@opencode-ai/plugin"
+
+export const ClaudeMemPlugin: Plugin = async (ctx) => {
+  // ctx: { client, project, directory, worktree, serverUrl, $ }
+  return { /* hooks object */ }
+}
+```
+
+**PluginInput type (6 properties, not 4):**
+```typescript
+type PluginInput = {
+  client: ReturnType<typeof createOpencodeClient>  // OpenCode SDK client
+  project: Project                                   // Current project info
+  directory: string                                  // Current working directory
+  worktree: string                                   // Git worktree path
+  serverUrl: URL                                     // Server URL
+  $: BunShell                                        // Bun shell API
+}
+```
+
+**Two hook mechanisms (important distinction):**
+
+1. **Direct interceptor hooks** — keys on the returned `Hooks` object, receive `(input, output)` allowing mutation:
+   - `tool.execute.before`: `(input: { tool, sessionID, callID }, output: { args })`
+   - `tool.execute.after`: `(input: { tool, sessionID, callID, args }, output: { title, output, metadata })`
+   - `shell.env`, `chat.message`, `chat.params`, `chat.headers`, `permission.ask`, `command.execute.before`
+   - Experimental: `experimental.session.compacting`, `experimental.chat.messages.transform`, `experimental.chat.system.transform`
+
+2. **Bus event catch-all** — generic `event` hook, receives `{ event }` where `event.type` is the event name:
+   - `session.created`, `session.compacted`, `session.deleted`, `session.idle`, `session.error`, `session.status`, `session.updated`, `session.diff`
+   - `message.updated`, `message.part.updated`, `message.part.removed`, `message.removed`
+   - `file.edited`, `file.watcher.updated`
+   - `command.executed`, `todo.updated`, `installation.updated`, `server.connected`
+   - `permission.asked`, `permission.replied`
+   - `lsp.client.diagnostics`, `lsp.updated`
+   - `tui.prompt.append`, `tui.command.execute`, `tui.toast.show`
+   - Total: **27 bus events** across **12 categories**
+
+**Custom tool registration (CORRECTED — name is the key, not positional arg):**
+```typescript
+return {
+  tool: {
+    claude_mem_search: tool({
+      description: "Search claude-mem memory database",
+      args: { query: tool.schema.string() },
+      async execute(args, context) {
+        // context: { sessionID, messageID, agent, directory, worktree, abort, metadata, ask }
+        const response = await fetch(`http://localhost:37777/api/search?q=${encodeURIComponent(args.query)}`)
+        return await response.text()
+      },
+    }),
+  },
+}
+```
+
+### What to implement
+
+1. **Create OpenCode plugin** at `src/integrations/opencode-plugin/index.ts`:
+   - Export a `Plugin` function receiving full `PluginInput` context
+   - Use **direct interceptor** `tool.execute.after` for tool observation capture (gives `tool`, `args`, `output`)
+   - Use **bus event catch-all** `event` for session lifecycle:
+
+   | Mechanism | Event | Map to claude-mem |
+   |-----------|-------|-------------------|
+   | interceptor | `tool.execute.after` | `observation` (tool name + args + output) |
+   | bus event | `session.created` | `session-init` |
+   | bus event | `message.updated` | `observation` (assistant messages) |
+   | bus event | `session.compacted` | `summary` |
+   | bus event | `file.edited` | `observation` (file changes) |
+   | bus event | `session.deleted` | `session-end` |
+
+   - Register `claude_mem_search` custom tool using correct `tool({ description, args, execute })` API
+   - Hit `localhost:37777` API endpoints from the plugin
+
+2. **Build the plugin** in the esbuild pipeline → `dist/opencode-plugin/index.js`
+
+3. **Create OpenCode setup in installer** (two options, prefer file-based):
+   - **Option A (file-based):** Copy plugin to `~/.config/opencode/plugins/claude-mem.ts` (auto-loaded at startup)
+   - **Option B (npm-based):** Add to `~/.config/opencode/opencode.json` under `"plugin"` array: `["claude-mem"]`
+   - Config also supports JSONC (`opencode.jsonc`) and legacy `config.json`
+   - Context injection: Append to `~/.config/opencode/AGENTS.md` (or create it) with `<claude-mem-context>` tags
+   - Additional context via `"instructions"` config key (supports file paths, globs, remote URLs)
+
+4. **Add OpenCode to installer IDE selection**
+
+### OpenCode Verification
+
+- `npx claude-mem install --ide opencode` registers the plugin (file or npm)
+- OpenCode loads the plugin on next session
+- `tool.execute.after` interceptor produces observations with `tool`, `args`, `output`
+- Bus events (`session.created`, `session.deleted`) handle session lifecycle
+- `claude_mem_search` custom tool works in OpenCode sessions
+- Context is injected via AGENTS.md
+
+### OpenCode Anti-patterns
+
+- Do NOT try to use OpenCode's `session.diff` for full capture — it's a summary diff, not raw data
+- Do NOT use `tool('name', schema, handler)` — wrong signature. Name is the key in the `tool:{}` map
+- Do NOT assume bus events have the same `(input, output)` mutation pattern — they only receive `{ event }`
+- OpenCode plugins run in Bun — the plugin CAN use Bun APIs (unlike the npx CLI itself)
+- Do NOT hardcode `~/.config/opencode/` — respect `OPENCODE_CONFIG_DIR` env var if set
+
+---
+
+## Phase 5: Windsurf Integration (Tier 1 — Hook-Based)
+
+**Why next**: 11 Cascade hooks, ~1M users. Hook architecture uses JSON stdin with a consistent envelope format.
+
+### Verified Windsurf Hook Events (from docs.windsurf.com/windsurf/cascade/hooks)
+
+**Naming pattern**: `pre_`/`post_` prefix + 5 action categories, plus 2 standalone post-only events.
+
+| Event | Can Block? | Map to claude-mem | Use |
+|-------|-----------|-------------------|-----|
+| `pre_user_prompt` | Yes | `session-init` + `context` | Start session, inject context |
+| `pre_read_code` | Yes | — | Skip (pre-execution, can block file reads) |
+| `post_read_code` | No | — | Skip (too noisy, file reads are frequent) |
+| `pre_write_code` | Yes | — | Skip (pre-execution, can block writes) |
+| `post_write_code` | No | `observation` | Code generation |
+| `pre_run_command` | Yes | — | Skip (pre-execution, can block commands) |
+| `post_run_command` | No | `observation` | Shell command execution |
+| `pre_mcp_tool_use` | Yes | — | Skip (pre-execution, can block MCP calls) |
+| `post_mcp_tool_use` | No | `observation` | MCP tool results |
+| `post_cascade_response` | No | `observation` | Full AI response |
+| `post_setup_worktree` | No | — | Skip (informational) |
+
+**Mapped**: 5 of 11 events (all post-action). **Skipped**: 4 pre-hooks (blocking-capable, pre-execution) + 2 low-value post-hooks.
+
+### Verified Stdin Payload Schema
+
+**Common envelope (all hooks):**
+```json
+{
+  "agent_action_name": "string",
+  "trajectory_id": "string",
+  "execution_id": "string",
+  "timestamp": "ISO 8601 string",
+  "tool_info": { /* event-specific payload */ }
+}
+```
+
+**Event-specific `tool_info` payloads:**
+
+| Event | `tool_info` fields |
+|-------|-------------------|
+| `pre_user_prompt` | `{ user_prompt: string }` |
+| `pre_read_code` / `post_read_code` | `{ file_path: string }` |
+| `pre_write_code` / `post_write_code` | `{ file_path: string, edits: [{ old_string: string, new_string: string }] }` |
+| `pre_run_command` / `post_run_command` | `{ command_line: string, cwd: string }` |
+| `pre_mcp_tool_use` | `{ mcp_server_name: string, mcp_tool_name: string, mcp_tool_arguments: {} }` |
+| `post_mcp_tool_use` | `{ mcp_server_name: string, mcp_tool_name: string, mcp_tool_arguments: {}, mcp_result: string }` |
+| `post_cascade_response` | `{ response: string }` (markdown) |
+| `post_setup_worktree` | `{ worktree_path: string, root_workspace_path: string }` |
+
+**Exit codes:** `0` = success, `2` = block (pre-hooks only; stderr shown to agent), any other = non-blocking warning.
+
+### What to implement
+
+1. **Create Windsurf platform adapter** at `src/cli/adapters/windsurf.ts`:
+   - Normalize Windsurf's hook input format to `NormalizedHookInput`
+   - Common envelope: `agent_action_name`, `trajectory_id`, `execution_id`, `timestamp`, `tool_info`
+   - Map: `trajectory_id` → `sessionId`, `tool_info` fields per event type
+   - For `post_write_code`: `tool_info.file_path` + `tool_info.edits` → file change observation
+   - For `post_run_command`: `tool_info.command_line` + `tool_info.cwd` → command observation
+   - For `post_mcp_tool_use`: `tool_info.mcp_tool_name` + `tool_info.mcp_tool_arguments` + `tool_info.mcp_result` → tool observation
+   - For `post_cascade_response`: `tool_info.response` → full AI response observation
+
+2. **Create Windsurf hooks installer** at `src/services/integrations/WindsurfHooksInstaller.ts`:
+   - Write hooks to `~/.codeium/windsurf/hooks.json` (user-level, for global coverage)
+   - Per-workspace override at `.windsurf/hooks.json` if user chooses workspace-level install
+   - Config format (verified):
+     ```json
+     {
+       "hooks": {
+         "post_write_code": [{
+           "command": "<path-to-hook-script>",
+           "show_output": false,
+           "working_directory": "<optional>"
+         }]
+       }
+     }
+     ```
+   - Note: Tilde expansion (`~`) is NOT supported in `working_directory` — use absolute paths
+   - Merge order: cloud → system → user → workspace (all hooks at all levels execute)
+   - Context injection via `.windsurf/rules/claude-mem-context.md` (workspace-level; Windsurf rules are workspace-scoped)
+   - Rule limits: 6,000 chars per file, 12,000 chars total across all rules
+
+3. **Register `windsurf` in `getPlatformAdapter()`** at `src/cli/adapters/index.ts`
+
+4. **Add Windsurf to installer IDE selection**
+
+### Windsurf Verification
+
+- `npx claude-mem install --ide windsurf` creates hooks config at `~/.codeium/windsurf/hooks.json`
+- Windsurf sessions are captured by the worker via post-action hooks
+- `trajectory_id` is used as session identifier
+- Context is injected via `.windsurf/rules/claude-mem-context.md` (under 6K char limit)
+- Existing hooks.json is preserved (merge, not overwrite)
+
+### Windsurf Anti-patterns
+
+- Do NOT use fabricated event names (`post_search_code`, `post_lint_code`, `on_error`, `pre_tool_execution`) — they don't exist
+- Do NOT assume Windsurf's stdin JSON matches Claude Code's — it uses `tool_info` envelope, not flat fields
+- Do NOT use tilde (`~`) in `working_directory` — not supported, use absolute paths
+- Do NOT exceed 6K chars in the context rule file — Windsurf truncates beyond that
+- Pre-hooks can block actions (exit 2) — only use post-hooks for observation capture
+
+---
+
+## Phase 6: Codex CLI Integration (Tier 1 — Hook + Transcript)
+
+### Dedup strategy
+
+Codex has both a `notify` hook (real-time) and transcript files (complete history). Use **transcript watching only** — it's more complete and avoids the complexity of dual capture paths. The `notify` hook is a simpler mechanism that doesn't provide enough granularity to justify maintaining two integration paths. If transcript watching proves insufficient, add the notify hook later.
+
+### What to implement
+
+1. **Create Codex transcript schema** — the sample in `src/services/transcripts/config.ts` is already production-quality. Verify against current Codex CLI JSONL format and update if needed.
+
+2. **Create Codex setup in installer**:
+   - Write transcript-watch config to `~/.claude-mem/transcript-watch.json`
+   - Set up watch for `~/.codex/sessions/**/*.jsonl` using existing CODEX_SAMPLE_SCHEMA
+   - Context injection via `.codex/AGENTS.md` (Codex reads this natively)
+   - Must merge with existing `config.toml` if it exists (read → parse → merge → write)
+
+3. **Add Codex CLI to installer IDE selection**
+
+### Verification
+
+- `npx claude-mem install --ide codex` creates transcript watch config
+- Codex sessions appear in claude-mem database
+- `AGENTS.md` updated with context after sessions
+- Existing `config.toml` is preserved
+
+---
+
+## Phase 7: OpenClaw Integration (Tier 1 — Plugin-Based)
+
+**Plugin is already fully built** at `openclaw/src/index.ts` (~1000 lines). Has event hooks, SSE observation feed, MEMORY.md sync, slash commands. Only wiring into the installer is needed.
+
+### What to implement
+
+1. **Wire OpenClaw into the npx installer**:
+   - Detect `~/.openclaw/` directory
+   - Copy pre-built plugin from `openclaw/dist/` (built in Phase 2) to OpenClaw plugins location
+   - Register in `~/.openclaw/openclaw.json` under `plugins.claude-mem`
+   - Configure worker port, project name, syncMemoryFile
+   - Optionally prompt for observation feed setup (channel type + target ID)
+
+2. **Add OpenClaw to IDE selection TUI** with hint about messaging channel support
+
+### Verification
+
+- `npx claude-mem install --ide openclaw` registers the plugin
+- OpenClaw gateway loads the plugin on restart
+- Observations are recorded from OpenClaw sessions
+- MEMORY.md syncs to agent workspaces
+
+### Anti-patterns
+
+- Do NOT rebuild the OpenClaw plugin from source at install time — it ships pre-built from Phase 2
+- Do NOT modify the plugin's event handling — it's battle-tested
+
+---
+
+## Phase 8: MCP-Based Integrations (Tier 2)
+
+**These get the MCP server for free** — it already exists at `plugin/scripts/mcp-server.cjs`. The installer just needs to write the right config files per IDE.
+
+MCP-only integrations provide: search tools + context injection. They do NOT capture transcripts or tool usage in real-time.
+
+### What to implement
+
+1. **Copilot CLI MCP setup**:
+   - Write MCP config to `~/.copilot/config` (merge, not overwrite)
+   - Context injection: `.github/copilot-instructions.md`
+   - Detection: `copilot` command in PATH
+
+2. **Antigravity MCP setup**:
+   - Write MCP config to `~/.gemini/antigravity/mcp_config.json` (merge, not overwrite)
+   - Context injection: `~/.gemini/GEMINI.md` (shared with Gemini CLI) and/or `.agent/rules/claude-mem-context.md`
+   - Detection: `~/.gemini/antigravity/` exists
+   - Note: Antigravity has NO hook system — MCP is the only integration path
+
+3. **Goose MCP setup**:
+   - Write MCP config to `~/.config/goose/config.yaml` (YAML merge — use a lightweight YAML parser or write the block manually if config doesn't exist)
+   - Detection: `~/.config/goose/` exists OR `goose` in PATH
+   - Note: Goose co-developed MCP with Anthropic, so MCP support is excellent
+
+4. **Crush MCP setup**:
+   - Write MCP config to Crush's JSON config
+   - Detection: `crush` in PATH
+
+5. **Roo Code MCP setup**:
+   - Write MCP config to `.roo/` or workspace settings
+   - Context injection: `.roo/rules/claude-mem-context.md`
+   - Detection: Check for VS Code extension directory containing `roo-code`
+
+6. **Warp MCP setup**:
+   - Warp uses `WARP.md` in project root for context injection (similar to CLAUDE.md)
+   - MCP servers configured via Warp Drive UI, but also via config files
+   - Detection: `~/.warp/` exists OR `warp` in PATH
+   - Note: Warp is a terminal replacement (~26k stars), not just a CLI tool — multi-agent orchestration with management UI
+
+7. **For each**: Add to installer IDE detection and selection
+
+### Config merging strategy
+
+JSON configs: Read → parse → deep merge → write back. YAML configs (Goose): If file exists, read and append the MCP block. If not, create from template. Avoid pulling in a full YAML parser library — write the MCP block as a string append with proper indentation if the format is predictable.
+
+### Verification
+
+- Each IDE can search claude-mem via MCP tools
+- Context files are written to IDE-specific locations
+- Existing configs are preserved
+
+### Anti-patterns
+
+- MCP-only integrations do NOT capture transcripts — don't claim "full integration"
+- Do NOT overwrite existing config files — always merge
+- Do NOT add a heavy YAML parser dependency for one integration
+
+---
+
+## Phase 9: Remove Old Installer
+
+This is a **full replacement**, not a deprecation.
+
+### What to implement
+
+1. Remove `claude-mem-installer` npm package (unpublish or mark deprecated with message pointing to `npx claude-mem`)
+2. Update `install/public/install.sh` → redirect to `npx claude-mem`
+3. Remove `installer/` directory from the repository (it's replaced by `src/npx-cli/`)
+4. Update docs site to reflect the new install command
+5. Update README.md install instructions
+
+---
+
+## Phase 10: Final Verification
+
+### All platforms (macOS, Linux, Windows)
+
+1. `npm run build` succeeds, produces `dist/cli/index.js` and `openclaw/dist/index.js`
+2. `node dist/cli/index.js install` works clean (no prior install)
+3. Auto-detects installed IDEs correctly per platform
+4. `npx claude-mem start/stop/status/search` all work
+5. `npx claude-mem update` updates correctly
+6. `npx claude-mem uninstall` cleans up all IDE configs
+7. `npx claude-mem version` prints version
+8. `npx claude-mem start` before install shows helpful error
+9. No Bun dependency at install time
+
+### Per-integration verification
+
+| Integration | Type | Captures Sessions | Search via MCP | Context Injection |
+|-------------|------|-------------------|----------------|-------------------|
+| Claude Code | Plugin | Yes (hooks) | Yes | CLAUDE.md |
+| Gemini CLI | Hooks | Yes (AfterTool, AfterAgent) | Yes (via hook) | GEMINI.md |
+| OpenCode | Plugin | Yes (tool.execute.after, message.updated) | Yes (custom tool) | AGENTS.md / rules |
+| Windsurf | Hooks | Yes (post_cascade_response, etc.) | Yes (via hook) | .windsurf/rules/ |
+| Codex CLI | Transcript | Yes (JSONL watcher) | No (passive only) | .codex/AGENTS.md |
+| OpenClaw | Plugin | Yes (event hooks) | Yes (slash commands) | MEMORY.md |
+| Copilot CLI | MCP | No | Yes | copilot-instructions.md |
+| Antigravity | MCP | No | Yes | .agent/rules/ |
+| Goose | MCP | No | Yes | MCP context |
+| Crush | MCP | No | Yes | Skills |
+| Roo Code | MCP | No | Yes | .roo/rules/ |
+| Warp | MCP | No | Yes | WARP.md |
+
+---
+
+## Priority Order & Impact
+
+| Phase | IDE/Tool | Integration Type | Stars/Users | Effort |
+|-------|----------|-----------------|-------------|--------|
+| 1-2 | (infrastructure) | npx CLI + build pipeline | All users | Medium |
+| 3 | Gemini CLI | Hooks (Tier 1) | ~95k stars | Medium (near-identical to Claude Code) |
+| 4 | OpenCode | Plugin (Tier 1) | ~110k stars | Medium (rich plugin SDK) |
+| 5 | Windsurf | Hooks (Tier 1) | ~1M users | Medium |
+| 6 | Codex CLI | Transcript (Tier 3) | Growing (OpenAI) | Low (schema already exists) |
+| 7 | OpenClaw | Plugin (Tier 1) — pre-built | ~196k stars | Low (wire into installer) |
+| 8 | Copilot CLI, Antigravity, Goose, Crush, Warp, Roo Code | MCP (Tier 2) | 20M+ combined | Low per IDE |
+| 9 | (remove old installer) | — | — | Low |
+| 10 | (final verification) | — | — | Low |
+
+## Out of Scope
+
+- **Removing Bun as runtime dependency**: Worker still requires Bun for `bun:sqlite`. Runtime commands delegate to Bun; install commands don't need it.
+- **JetBrains plugin**: Requires Kotlin/Java development — different ecosystem entirely.
+- **Zed extension**: WASM sandbox limits feasibility.
+- **Neovim/Emacs plugins**: Niche audiences, complex plugin ecosystems (Lua/Elisp). Could be added later via MCP (gptel supports it).
+- **Amazon Q / Kiro**: Amazon Q Developer CLI has been sunsetted in favor of Kiro (proprietary, no public extensibility API yet). Revisit when Kiro opens up.
+- **Aider**: Niche audience, writes Markdown transcripts (not JSONL), would require a markdown parser mode in the watcher. Add if demand materializes.
+- **Continue.dev**: Small user base relative to other MCP tools. Can be added as a Tier 2 MCP integration later if requested.
+- **Toad / Qwen Code / Oh-my-pi**: Too early-stage or too niche. Monitor for growth.
+- **OpenClaw plugin development**: The plugin is already complete. Only installer wiring is in scope.

.windsurf/rules/claude-mem-context.md

@@ -0,0 +1,5 @@
+# Memory Context from Past Sessions
+
+*No context yet. Complete your first session and context will appear here.*
+
+Use claude-mem's MCP search tools for manual memory queries.

CLAUDE.md

@@ -14,6 +14,10 @@ Claude-mem is a Claude Code plugin providing persistent memory across sessions.
 
 **Search Skill** (`plugin/skills/mem-search/SKILL.md`) - HTTP API for searching past work, auto-invoked when users ask about history
 
+**Planning Skill** (`plugin/skills/make-plan/SKILL.md`) - Orchestrator instructions for creating phased implementation plans with documentation discovery
+
+**Execution Skill** (`plugin/skills/do/SKILL.md`) - Orchestrator instructions for executing phased plans using subagents
+
 **Chroma** (`src/services/sync/ChromaSync.ts`) - Vector embeddings for semantic search
 
 **Viewer UI** (`src/ui/viewer/`) - React interface at http://localhost:37777, built to `plugin/ui/viewer.html`

README.md

@@ -1,5 +1,3 @@
-
-
 <h1 align="center">
   <br>
   <a href="https://github.com/thedotmack/claude-mem">
@@ -14,12 +12,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> •
@@ -29,10 +29,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> •
@@ -72,13 +74,40 @@
 
 <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>
+<table align="center">
+  <tr>
+    <td 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="500"
+          >
+        </picture>
+      </a>
+    </td>
+    <td align="center">
+      <a href="https://www.star-history.com/#thedotmack/claude-mem&Date">
+        <picture>
+          <source
+            media="(prefers-color-scheme: dark)"
+            srcset="https://api.star-history.com/image?repos=thedotmack/claude-mem&type=date&theme=dark&legend=top-left"
+          />
+          <source
+            media="(prefers-color-scheme: light)"
+            srcset="https://api.star-history.com/image?repos=thedotmack/claude-mem&type=date&legend=top-left"
+          />
+          <img
+            alt="Star History Chart"
+            src="https://api.star-history.com/image?repos=thedotmack/claude-mem&type=date&legend=top-left"
+            width="500"
+          />
+        </picture>
+      </a>
+    </td>
+  </tr>
+</table>
 
 <p align="center">
   <a href="#quick-start">Quick Start</a> •
@@ -98,15 +127,44 @@
 
 ## Quick Start
 
-Start a new Claude Code session in the terminal and enter the following commands:
+Install with a single command:
 
-```
-> /plugin marketplace add thedotmack/claude-mem
-
-> /plugin install claude-mem
+```bash
+npx claude-mem install
 ```
 
-Restart Claude Code. Context from previous sessions will automatically appear in new sessions.
+Or install for Gemini CLI (auto-detects `~/.gemini`):
+
+```bash
+npx claude-mem install --ide gemini-cli
+```
+Or install for OpenCode:
+
+```bash
+npx claude-mem install --ide opencode
+```
+
+Or install from the plugin marketplace inside Claude Code:
+
+```bash
+/plugin marketplace add thedotmack/claude-mem
+
+/plugin install claude-mem
+```
+
+Restart Claude Code or Gemini CLI. 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. Always install via `npx claude-mem install` or 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:**
 
@@ -125,11 +183,12 @@ 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
 
 - **[Installation Guide](https://docs.claude-mem.ai/installation)** - Quick start & advanced installation
+- **[Gemini CLI Setup](https://docs.claude-mem.ai/gemini-cli/setup)** - Dedicated guide for Google's Gemini CLI integration
 - **[Usage Guide](https://docs.claude-mem.ai/usage/getting-started)** - How Claude-Mem works automatically
 - **[Search Tools](https://docs.claude-mem.ai/usage/search-tools)** - Query your project history with natural language
 - **[Beta Features](https://docs.claude-mem.ai/beta-features)** - Try experimental features like Endless Mode
@@ -194,7 +253,6 @@ 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)
 
 **Example Usage:**
 
@@ -228,6 +286,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
@@ -236,6 +305,45 @@ Settings are managed in `~/.claude-mem/settings.json` (auto-created with default
 
 See the **[Configuration Guide](https://docs.claude-mem.ai/configuration)** for all available settings and examples.
 
+### Mode & Language Configuration
+
+Claude-Mem supports multiple workflow modes and languages via the `CLAUDE_MEM_MODE` setting.
+
+This option controls both:
+- The workflow behavior (e.g. code, chill, investigation)
+- The language used in generated observations
+
+#### How to Configure
+
+Edit your settings file at `~/.claude-mem/settings.json`:
+
+```json
+{
+  "CLAUDE_MEM_MODE": "code--zh"
+}
+```
+
+Modes are defined in `plugin/modes/`. To see all available modes locally:
+
+```bash
+ls ~/.claude/plugins/marketplaces/thedotmack/plugin/modes/
+```
+
+#### Available Modes
+
+| Mode | Description |
+|------------|-------------------------|
+| `code` | Default English mode |
+| `code--zh` | Simplified Chinese mode |
+| `code--ja` | Japanese mode |
+
+Language-specific modes follow the pattern `code--[lang]` where `[lang]` is the ISO 639-1 language code (e.g., `zh` for Chinese, `ja` for Japanese, `es` for Spanish).
+
+> Note: `code--zh` (Simplified Chinese) is already built-in — no additional installation or plugin update is required.
+
+#### After Changing Mode
+
+Restart Claude Code to apply the new mode configuration.
 ---
 
 ## Development
@@ -299,8 +407,16 @@ See the [LICENSE](LICENSE) file for full details.
 - **Documentation**: [docs/](docs/)
 - **Issues**: [GitHub Issues](https://github.com/thedotmack/claude-mem/issues)
 - **Repository**: [github.com/thedotmack/claude-mem](https://github.com/thedotmack/claude-mem)
+- **Official X Account**: [@Claude_Memory](https://x.com/Claude_Memory)
+- **Official Discord**: [Join Discord](https://discord.com/invite/J4wttp9vDu)
 - **Author**: Alex Newman ([@thedotmack](https://github.com/thedotmack))
 
 ---
 
 **Built with Claude Agent SDK** | **Powered by Claude Code** | **Made with TypeScript**
+
+---
+
+### What About $CMEM?
+
+$CMEM is a solana token created by a 3rd party without Claude-Mem's prior consent, but officially embraced by the creator of Claude-Mem (Alex Newman, @thedotmack). The token acts as a community catalyst for growth and a vehicle for bringing real-time agent data to the developers and knowledge workers that need it most. $CMEM: 2TsmuYUrsctE57VLckZBYEEzdokUF8j8e1GavekWBAGS

WARP.md

@@ -0,0 +1,7 @@
+<claude-mem-context>
+# claude-mem: Cross-Session Memory
+
+*No context yet. Complete your first session and context will appear here.*
+
+Use claude-mem's MCP search tools for manual memory queries.
+</claude-mem-context>

bunfig.toml

@@ -0,0 +1,7 @@
+[test]
+# Force each test file into its own worker process.
+# Prevents mock.module() calls (which are permanent within a worker)
+# from leaking across test files in parallel runs.
+# Note: smol=true increases test startup time by spawning one Bun process per file.
+# See: https://github.com/thedotmack/claude-mem/issues/1299
+smol = true

cursor-hooks/CLAUDE.md

@@ -1,131 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Dec 29, 2025
-
-**save-file-edit.sh**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34270 | 10:45 PM | 🔵 | Save File Edit Hook Captures File Modifications as Tool Observations | ~495 |
-
-**session-summary.sh**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34268 | 10:44 PM | 🔵 | Session Summary Hook Generates Summaries and Updates Context on Stop | ~498 |
-
-**save-observation.sh**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34267 | 10:44 PM | 🔵 | Save Observation Hook Captures MCP and Shell Executions | ~494 |
-
-**context-inject.sh**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34266 | 10:44 PM | 🔵 | Context Inject Hook Refreshes Memory Context Before Prompt Submission | ~498 |
-| #34165 | 9:41 PM | 🔵 | Context Injection Hook Implementation for Cursor | ~466 |
-
-**session-init.sh**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34264 | 10:43 PM | 🔵 | Session Init Hook Initializes Sessions on Prompt Submission | ~514 |
-
-**common.sh**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34261 | 10:43 PM | 🔵 | Cursor Hooks Common Shell Library Provides Core Utilities | ~381 |
-| #34237 | 10:31 PM | 🔄 | Removed arbitrary array index validation from json_get function | ~421 |
-
-**STANDALONE-SETUP.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34258 | 10:39 PM | ✅ | Updated STANDALONE-SETUP.md to recommend user-level installation | ~265 |
-| #34257 | " | 🔵 | Claude-Mem Command Reference for Cursor Integration | ~245 |
-| #34256 | " | ✅ | Updated STANDALONE-SETUP.md to recommend user-level installation | ~305 |
-| #34252 | 10:38 PM | 🔵 | Cursor Hooks Installation and Worker Setup Process | ~258 |
-| #34224 | 10:14 PM | ✅ | Completed Bun Migration by Updating All Windows Commands | ~392 |
-| #34223 | " | ✅ | Updated Windows Installation Commands to Use Bun | ~354 |
-| #34222 | 10:13 PM | ✅ | Updated Quick Reference Table to Use Bun Commands | ~361 |
-| #34221 | " | ✅ | Updated Step 5 Status Check Command to Use Bun | ~353 |
-| #34220 | " | ✅ | Updated Step 4 Worker Start Command to Use Bun | ~360 |
-| #34219 | 10:12 PM | ✅ | Updated Step 3 Hook Installation Commands to Use Bun | ~322 |
-| #34218 | " | ✅ | Updated STANDALONE-SETUP Step 1 Commands to Use Bun Instead of NPM | ~357 |
-| #34217 | " | ✅ | Updated STANDALONE-SETUP Prerequisites to Require Bun Runtime | ~341 |
-| #34215 | 10:08 PM | 🔵 | Retrieved Detailed Cursor Integration Implementation History | ~676 |
-| #34214 | 10:07 PM | 🔵 | Cursor Integration Feature Set Discovered via Memory Search | ~427 |
-
-**QUICKSTART.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34255 | 10:39 PM | ✅ | Quickstart Documentation Reordered to Recommend User-Level Installation First | ~265 |
-| #34251 | 10:38 PM | 🔵 | Quickstart Documentation Shows CLI-Based Installation Method | ~257 |
-| #34225 | 10:14 PM | ✅ | Updated QUICKSTART Worker Restart Command to Use Bun | ~308 |
-
-**README.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34254 | 10:38 PM | ✅ | Updated README to recommend user-level installation over project-level | ~345 |
-| #34253 | " | 🔵 | Cursor hooks installation documented with quick install CLI and manual options | ~327 |
-| #34250 | " | 🔵 | Documentation references installation types and project-level concepts | ~311 |
-| #34226 | 10:14 PM | ✅ | Updated README Quick Install Commands to Use Bun | ~311 |
-
-**install.sh**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34249 | 10:37 PM | ✅ | Install Script Usage Message Updated to Recommend User-Level Installation | ~256 |
-| #34248 | " | ✅ | Marked user-level installation as recommended in install script | ~255 |
-| #34246 | " | ✅ | Simplified path rewriting logic after enterprise mode removal | ~291 |
-| #34245 | " | ✅ | Simplified conditional logic after removing enterprise installation code | ~266 |
-| #34244 | 10:36 PM | ✅ | Removed enterprise installation mode from cursor-hooks installer | ~298 |
-| #34243 | " | ✅ | Removed enterprise installation option from Cursor hooks installer | ~292 |
-| #34242 | " | 🔵 | Cursor hooks installation script copies and configures hooks with path adjustments | ~387 |
-| #34240 | 10:33 PM | 🔵 | Cursor hooks installation paths and requirements vary by deployment mode | ~312 |
-| #34239 | " | 🔵 | Cursor hooks installation supports enterprise mode | ~240 |
-| #34233 | 10:26 PM | ⚖️ | Implemented PR 493 fixes with mixed necessity and complexity trade-offs | ~610 |
-| #34232 | " | 🔵 | PR 493 review identified security and concurrency issues requiring fixes | ~560 |
-| #34228 | 10:21 PM | 🔴 | Fixed sed portability issue in install.sh | ~318 |
-
-**common.ps1**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34238 | 10:31 PM | 🔄 | Rollback complete: simplified over-engineered concurrency and validation code | ~434 |
-| #34231 | 10:25 PM | 🔴 | Fixed race conditions and security vulnerabilities in Cursor integration | ~562 |
-
-**hooks.json**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34184 | 9:51 PM | 🔵 | Cursor Hooks Configuration Schema | ~375 |
-
-### Dec 31, 2025
-
-**session-init.sh**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34675 | 3:37 PM | 🔵 | API Endpoint /api/sessions/init Expects contentSessionId Parameter | ~401 |
-
-### Jan 5, 2026
-
-**CLAUDE.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #38078 | 9:54 PM | ✅ | CLAUDE.md Documentation Cleanup - 1,233 Lines Removed Across 18 Files | ~590 |
-
-**INTEGRATION.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #37995 | 9:01 PM | 🔵 | CLAUDE_MEM_WORKER_HOST setting implementation pattern | ~304 |
-
-**README.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #37990 | 9:00 PM | 🔵 | CLAUDE_MEM_WORKER_HOST setting used across 19 files | ~289 |
-
-### Jan 7, 2026
-
-**CLAUDE.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #38195 | 7:35 PM | ✅ | Context-hook enhanced with promotional footer and user-message-hook removed from SessionStart | ~376 |
-| #38194 | " | 🔵 | Working tree contains 10 modified files ready for commit | ~303 |
-</claude-mem-context>

docs/CLAUDE.md

@@ -3,5 +3,81 @@
 
 <!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
 
-*No recent activity*
+### Nov 6, 2025
+
+| ID | Time | T | Title | Read |
+|----|------|---|-------|------|
+| #4241 | 11:19 PM | 🟣 | Object-Oriented Architecture Design Document Created | ~662 |
+| #4240 | 11:11 PM | 🟣 | Worker Service Rewrite Blueprint Created | ~541 |
+| #4239 | 11:07 PM | 🟣 | Comprehensive Worker Service Performance Analysis Document Created | ~541 |
+| #4238 | 10:59 PM | 🔵 | Overhead Analysis Document Checked | ~203 |
+
+### Nov 7, 2025
+
+| ID | Time | T | Title | Read |
+|----|------|---|-------|------|
+| #4609 | 6:33 PM | ✅ | PR #69 Successfully Merged to Main Branch | ~516 |
+| #4600 | 6:31 PM | 🟣 | Added Worker Service Documentation Suite | ~441 |
+| #4597 | " | 🔄 | Worker Service Refactored to Object-Oriented Architecture | ~473 |
+
+### Nov 8, 2025
+
+| ID | Time | T | Title | Read |
+|----|------|---|-------|------|
+| #5539 | 10:20 PM | 🔵 | Harsh critical audit of context-hook reveals systematic anti-patterns | ~3154 |
+| #5497 | 9:29 PM | 🔵 | Harsh critical audit of context-hook reveals systematic anti-patterns | ~2815 |
+| #5495 | 9:28 PM | 🔵 | Context Hook Audit Reveals Project Anti-Patterns | ~660 |
+| #5476 | 9:17 PM | 🔵 | Critical Code Audit Identified 14 Anti-Patterns in Context Hook | ~887 |
+| #5391 | 8:45 PM | 🔵 | Critical Code Quality Audit of Context Hook Implementation | ~720 |
+| #5150 | 7:37 PM | 🟣 | Troubleshooting Skill Added to Claude-Mem Plugin | ~427 |
+
+### Nov 9, 2025
+
+| ID | Time | T | Title | Read |
+|----|------|---|-------|------|
+| #6161 | 11:55 PM | 🔵 | YC W26 Application Research and Preparation Completed for Claude-Mem | ~1628 |
+| #6155 | 11:47 PM | ✅ | Comprehensive Y Combinator Winter 2026 Application Notes Created | ~1045 |
+| #5979 | 7:58 PM | 🔵 | Smart Contextualization Feature Architecture | ~560 |
+| #5971 | 7:49 PM | 🔵 | Hooks Reference Documentation Structure | ~448 |
+| #5929 | 7:08 PM | ✅ | Documentation Updates for v5.4.0 Skill-Based Search Migration | ~604 |
+| #5927 | " | ✅ | Updated Configuration Documentation for Skill-Based Search | ~497 |
+| #5920 | 7:05 PM | ✅ | Renamed Architecture Documentation File Reference | ~271 |
+
+### Nov 18, 2025
+
+| ID | Time | T | Title | Read |
+|----|------|---|-------|------|
+| #11515 | 8:22 PM | 🔵 | Smart Contextualization Architecture Retrieved with Command Hook Pattern Details | ~502 |
+
+### Dec 8, 2025
+
+| ID | Time | T | Title | Read |
+|----|------|---|-------|------|
+| #22294 | 9:43 PM | 🔵 | Documentation Site Structure Located | ~359 |
+
+### Dec 12, 2025
+
+| ID | Time | T | Title | Read |
+|----|------|---|-------|------|
+| #24430 | 8:27 PM | ✅ | Removed Final Platform Check Reference from Linux Section | ~320 |
+| #24429 | " | ✅ | Final Platform Check Reference Removal from Linux Section | ~274 |
+| #24428 | " | ✅ | Corrected Second Line Number Reference for Migration Marker Logic | ~267 |
+| #24427 | 8:26 PM | ✅ | Updated Line Number Reference for PM2 Cleanup Implementation | ~260 |
+| #24426 | " | ✅ | Removed Platform Check from Manual Marker Deletion Scenario | ~338 |
+| #24425 | " | ✅ | Removed Platform Check from Fresh Install Scenario Flow | ~314 |
+| #24424 | 8:25 PM | ✅ | Renumbered Manual Marker Deletion Scenario | ~285 |
+| #24423 | " | ✅ | Renumbered Fresh Install Scenario | ~243 |
+| #24422 | " | ✅ | Removed Obsolete Windows Platform Detection Scenario | ~311 |
+| #24421 | " | ✅ | Removed Platform Check from macOS Migration Documentation | ~294 |
+| #24420 | 8:24 PM | ✅ | Platform Check Removed from Migration Documentation | ~288 |
+| #24417 | 8:16 PM | ✅ | Code Reference Example Updated to Reflect Actual Cross-Platform Implementation | ~366 |
+| #24416 | " | ✅ | Architecture Decision Documentation Updated to Reflect Cross-Platform PM2 Cleanup Rationale | ~442 |
+| #24415 | 8:15 PM | ✅ | Migration Marker Lifecycle Documentation Updated for Unified Cross-Platform Behavior | ~463 |
+| #24414 | " | ✅ | Platform Comparison Table Updated to Reflect Unified Cross-Platform Migration | ~351 |
+| #24413 | " | ✅ | Windows Platform-Specific Documentation Completely Rewritten for Unified Migration | ~428 |
+| #24412 | " | ✅ | User Experience Timeline Updated for Cross-Platform PM2 Cleanup | ~291 |
+| #24411 | 8:14 PM | ✅ | Migration Marker Lifecycle Documentation Updated for All Platforms | ~277 |
+| #24410 | " | ✅ | Marker File Platform Behavior Documentation Updated for Unified Migration | ~282 |
+| #24409 | " | ✅ | Migration Steps Documentation Updated for Cross-Platform PM2 Cleanup | ~278 |
+| #24408 | 8:13 PM | ✅ | PM2 Migration Documentation Updated to Remove Windows Platform Check | ~280 |
 </claude-mem-context>

docs/PR-SHIPPING-REPORT.md

@@ -0,0 +1,213 @@
+# Claude-Mem PR Shipping Report
+*Generated: 2026-02-04*
+
+## Executive Summary
+
+6 PRs analyzed for shipping readiness. **1 is ready to merge**, 4 have conflicts, 1 is too large for easy review.
+
+| PR | Title | Status | Recommendation |
+|----|-------|--------|----------------|
+| **#856** | Idle timeout for zombie processes | ✅ **MERGEABLE** | **Ship it** |
+| #700 | Windows Terminal popup fix | ⚠️ Conflicts | Rebase, then ship |
+| #722 | In-process worker architecture | ⚠️ Conflicts | Rebase, high impact |
+| #657 | generate/clean CLI commands | ⚠️ Conflicts | Rebase, then ship |
+| #863 | Ragtime email investigation | 🔍 Needs review | Research pending |
+| #464 | Sleep Agent Pipeline (contributor) | 🔴 Too large | Request split or dedicated review |
+
+---
+
+## Ready to Ship
+
+### PR #856: Idle Timeout for Zombie Observer Processes
+**Status:** ✅ MERGEABLE (no conflicts)
+
+| Metric | Value |
+|--------|-------|
+| Additions | 928 |
+| Deletions | 171 |
+| Files | 8 |
+| Risk | Low-Medium |
+
+**What it does:**
+- Adds 3-minute idle timeout to `SessionQueueProcessor`
+- Prevents zombie observer processes that were causing 13.4GB swap usage
+- Processes exit gracefully after inactivity instead of waiting forever
+
+**Why ship it:**
+- Fixes real user-reported issue (79 zombie processes)
+- Well-tested (11 new tests, 440 lines of test coverage)
+- Clean implementation, preventive approach
+- Supersedes PR #848's reactive cleanup
+- No conflicts, ready to merge
+
+**Review notes:**
+- 1 Greptile bot comment (addressed)
+- Race condition fix included
+- Enhanced logging added
+
+---
+
+## Needs Rebase (Have Conflicts)
+
+### PR #700: Windows Terminal Popup Fix
+**Status:** ⚠️ CONFLICTING
+
+| Metric | Value |
+|--------|-------|
+| Additions | 187 |
+| Deletions | 399 |
+| Files | 8 |
+| Risk | Medium |
+
+**What it does:**
+- Eliminates Windows Terminal popup by removing spawn-based daemon
+- Worker `start` command becomes daemon directly (no child spawn)
+- Removes `restart` command (users do `stop` then `start`)
+- Net simplification: -212 lines
+
+**Breaking changes:**
+- `restart` command removed
+
+**Review status:**
+- ✅ 1 APPROVAL from @volkanfirat (Jan 15, 2026)
+
+**Action needed:** Resolve conflicts, then ready to ship.
+
+---
+
+### PR #722: In-Process Worker Architecture
+**Status:** ⚠️ CONFLICTING
+
+| Metric | Value |
+|--------|-------|
+| Additions | 869 |
+| Deletions | 4,658 |
+| Files | 112 |
+| Risk | High |
+
+**What it does:**
+- Hook processes become the worker (no separate daemon spawning)
+- First hook that needs worker becomes the worker
+- Eliminates Windows spawn issues ("NO SPAWN" rule)
+- 761 tests pass
+
+**Architectural impact:** HIGH
+- Fundamentally changes worker lifecycle
+- Hook processes stay alive (they ARE the worker)
+- First hook wins port 37777, others use HTTP
+
+**Action needed:** Resolve conflicts. Consider relationship with PR #700 (both touch worker architecture).
+
+---
+
+### PR #657: Generate/Clean CLI Commands
+**Status:** ⚠️ CONFLICTING
+
+| Metric | Value |
+|--------|-------|
+| Additions | 1,184 |
+| Deletions | 5,057 |
+| Files | 104 |
+| Risk | Medium |
+
+**What it does:**
+- Adds `claude-mem generate` and `claude-mem clean` CLI commands
+- Fixes validation bugs (deleted folders recreated from stale DB)
+- Fixes Windows path handling
+- Adds automatic shell alias installation
+- Disables subdirectory CLAUDE.md files by default
+
+**Breaking changes:**
+- Default behavior change: folder CLAUDE.md now disabled by default
+
+**Action needed:** Resolve conflicts, complete Windows testing.
+
+---
+
+## Needs Attention
+
+### PR #863: Ragtime Email Investigation
+**Status:** 🔍 Research pending
+
+Research agent did not return results. Manual review needed.
+
+---
+
+### PR #464: Sleep Agent Pipeline (Contributor: @laihenyi)
+**Status:** 🔴 Too large for effective review
+
+| Metric | Value |
+|--------|-------|
+| Additions | 15,430 |
+| Deletions | 469 |
+| Files | 73 |
+| Wait time | 37+ days |
+| Risk | High |
+
+**What it does:**
+- Sleep Agent Pipeline with memory tiering
+- Supersession detection
+- Session Statistics API (`/api/session/:id/stats`)
+- StatusLine + PreCompact hooks
+- Context Generator improvements
+- Self-healing CI workflow
+
+**Concerns:**
+| Issue | Details |
+|-------|---------|
+| 🔴 Size | 15K+ lines is too large for effective review |
+| 🔴 SupersessionDetector | Single file with 1,282 additions |
+| 🟡 No tests visible | Test plan checkboxes unchecked |
+| 🟡 Self-healing CI | Auto-fix workflow could cause infinite commit loops |
+| 🟡 Serena config | Adds `.serena/` tooling |
+
+**Recommendation:**
+1. **Option A:** Request contributor split into 4-5 smaller PRs
+2. **Option B:** Allocate dedicated review time (several hours)
+3. **Option C:** Cherry-pick specific features (hooks, stats API)
+
+**Note:** Contributor has been waiting 37+ days. Deserves response either way.
+
+---
+
+## Shipping Strategy
+
+### Phase 1: Quick Wins (This Week)
+1. **Merge #856** — Ready now, fixes real user issue
+2. **Rebase #700** — Has approval, Windows fix needed
+3. **Rebase #657** — Useful CLI commands
+
+### Phase 2: Architecture (Careful Review)
+4. **Review #722** — High impact, conflicts with #700 approach?
+   - Both PRs eliminate spawning but in different ways
+   - May need to pick one approach
+
+### Phase 3: Contributor PR
+5. **Respond to #464** — Options:
+   - Ask for split
+   - Schedule dedicated review
+   - Cherry-pick subset
+
+### Phase 4: Investigation
+6. **Manual review #863** — Ragtime email feature
+
+---
+
+## Conflict Resolution Order
+
+Since multiple PRs have conflicts, suggested rebase order:
+
+1. **#856** (merge first — no conflicts)
+2. **#700** (rebase onto main after #856)
+3. **#657** (rebase onto main after #700)
+4. **#722** (rebase last — may conflict with #700 architecturally)
+
+---
+
+## Summary
+
+| Ready | Conflicts | Needs Work |
+|-------|-----------|------------|
+| 1 PR (#856) | 3 PRs (#700, #722, #657) | 2 PRs (#464, #863) |
+
+**Immediate action:** Merge #856, then rebase the conflict PRs in order.

docs/SESSION_ID_ARCHITECTURE.md

@@ -23,14 +23,14 @@ Claude-mem uses **two distinct session IDs** to track conversations and memory:
                            ↓
 ┌─────────────────────────────────────────────────────────────┐
 │ 2. SDKAgent starts, checks hasRealMemorySessionId           │
-│    const hasReal = memorySessionId !== null                 │
+│    const hasReal = !!memorySessionId                        │
 │    → FALSE (it's NULL)                                      │
 │    → Resume NOT used (fresh SDK session)                    │
 └─────────────────────────────────────────────────────────────┘
                            ↓
 ┌─────────────────────────────────────────────────────────────┐
 │ 3. First SDK message arrives with session_id                │
-│    updateMemorySessionId(sessionDbId, "sdk-gen-abc123")     │
+│    ensureMemorySessionIdRegistered(sessionDbId, "sdk-gen-abc123") │
 │                                                              │
 │    Database state:                                          │
 │    ├─ content_session_id: "user-session-123"               │
@@ -38,45 +38,43 @@ Claude-mem uses **two distinct session IDs** to track conversations and memory:
 └─────────────────────────────────────────────────────────────┘
                            ↓
 ┌─────────────────────────────────────────────────────────────┐
-│ 4. Subsequent prompts use resume                            │
-│    const hasReal = memorySessionId !== null                 │
-│    → TRUE (it's not NULL)                                   │
+│ 4. Subsequent prompts may use resume                        │
+│    const shouldResume =                                      │
+│      !!memorySessionId && lastPromptNumber > 1 && !forceInit│
+│    → TRUE only for continuation prompts in the same runtime │
 │    → Resume parameter: { resume: "sdk-gen-abc123" }         │
 └─────────────────────────────────────────────────────────────┘
 ```
 
 ### Observation Storage
 
-**CRITICAL**: Observations are stored with `contentSessionId`, NOT the captured SDK `memorySessionId`.
+**CRITICAL**: Observations are stored with the real `memorySessionId`, NOT `contentSessionId`.
 
 ```typescript
-// SDKAgent.ts line 332-333
-this.dbManager.getSessionStore().storeObservation(
-  session.contentSessionId,  // ← contentSessionId, not memorySessionId!
-  session.project,
-  obs,
-  // ...
-);
+// SessionStore.ts
+storeObservation(memorySessionId, project, observation, ...);
 ```
 
-Even though the parameter is named `memorySessionId`, it receives `contentSessionId`. This means:
+This means:
 
 - Database column: `observations.memory_session_id`
-- Stored value: `contentSessionId` (the user's session ID)
+- Stored value: the captured or synthesized `memorySessionId`
 - Foreign key: References `sdk_sessions.memory_session_id`
 
-The observations are linked to the session via `contentSessionId`, which remains constant throughout the session lifecycle.
+Observation storage is blocked until a real `memorySessionId` is registered in `sdk_sessions`.
+This is why `SDKAgent` persists the SDK-returned `session_id` immediately through
+`ensureMemorySessionIdRegistered(...)` before any observation insert can succeed.
 
 ## Key Invariants
 
 ### 1. NULL-Based Detection
 
 ```typescript
-const hasRealMemorySessionId = session.memorySessionId !== null;
+const hasRealMemorySessionId = !!session.memorySessionId;
 ```
 
-- When `memorySessionId === null` → Not yet captured
-- When `memorySessionId !== null` → Real SDK session captured
+- When `memorySessionId` is falsy → Not yet captured
+- When `memorySessionId` is truthy → Real SDK session captured
 
 ### 2. Resume Safety
 
@@ -86,12 +84,20 @@ const hasRealMemorySessionId = session.memorySessionId !== null;
 // ❌ FORBIDDEN - Would resume user's session instead of memory session!
 query({ resume: contentSessionId })
 
-// ✅ CORRECT - Only resume when we have real memory session ID
+// ✅ CORRECT - Only resume for a continuation prompt in a valid runtime
 query({
-  ...(hasRealMemorySessionId && { resume: memorySessionId })
+  ...(
+    !!memorySessionId &&
+    lastPromptNumber > 1 &&
+    !forceInit &&
+    { resume: memorySessionId }
+  )
 })
 ```
 
+`memorySessionId` is necessary but not sufficient.
+Worker restart and crash-recovery paths may still carry a persisted ID while forcing a fresh INIT run.
+
 ### 3. Session Isolation
 
 - Each `contentSessionId` maps to exactly one database session
@@ -103,7 +109,8 @@ query({
 - Observations reference `sdk_sessions.memory_session_id`
 - Initially, `sdk_sessions.memory_session_id` is NULL (no observations can be stored yet)
 - When SDK session ID is captured, `sdk_sessions.memory_session_id` is set to the real value
-- Observations are stored using `contentSessionId` and remain retrievable via `contentSessionId`
+- Observations are stored using that real `memory_session_id`
+- Queries can still find the session from `content_session_id`, but observation rows themselves stay keyed by `memory_session_id`
 
 ## Testing Strategy
 
@@ -116,8 +123,8 @@ The test suite validates all critical invariants:
 ### Test Categories
 
 1. **NULL-Based Detection** - Validates `hasRealMemorySessionId` logic
-2. **Observation Storage** - Confirms observations use `contentSessionId`
-3. **Resume Safety** - Prevents `contentSessionId` from being used for resume
+2. **Observation Storage** - Confirms observations use real `memorySessionId` values after registration
+3. **Resume Safety** - Prevents `contentSessionId` and stale INIT sessions from being used for resume
 4. **Cross-Contamination Prevention** - Ensures session isolation
 5. **Foreign Key Integrity** - Validates cascade behavior
 6. **Session Lifecycle** - Tests create → capture → resume flow
@@ -141,14 +148,14 @@ bun test --verbose
 ### ❌ Using memorySessionId for observations
 
 ```typescript
-// WRONG - Don't use the captured SDK session ID
-storeObservation(session.memorySessionId, ...)
+// WRONG - Don't store observations before memorySessionId is available
+storeObservation(session.contentSessionId, ...)
 ```
 
 ### ❌ Resuming without checking for NULL
 
 ```typescript
-// WRONG - memorySessionId could be NULL!
+// WRONG - memorySessionId alone is not enough
 if (session.memorySessionId) {
   query({ resume: session.memorySessionId })
 }
@@ -166,14 +173,14 @@ const resumeId = session.memorySessionId
 ### ✅ Storing observations
 
 ```typescript
-// Always use contentSessionId
-storeObservation(session.contentSessionId, project, obs, ...)
+// Only store after a real memorySessionId has been captured or synthesized
+storeObservation(session.memorySessionId, project, obs, ...)
 ```
 
 ### ✅ Checking for real memory session ID
 
 ```typescript
-const hasRealMemorySessionId = session.memorySessionId !== null;
+const hasRealMemorySessionId = !!session.memorySessionId;
 ```
 
 ### ✅ Using resume parameter
@@ -182,7 +189,12 @@ const hasRealMemorySessionId = session.memorySessionId !== null;
 query({
   prompt: messageGenerator,
   options: {
-    ...(hasRealMemorySessionId && { resume: session.memorySessionId }),
+    ...(
+      hasRealMemorySessionId &&
+      session.lastPromptNumber > 1 &&
+      !session.forceInit &&
+      { resume: session.memorySessionId }
+    ),
     // ... other options
   }
 })
@@ -234,6 +246,6 @@ WHERE s.content_session_id = 'your-session-id';
 ## References
 
 - **Implementation**: `src/services/worker/SDKAgent.ts` (lines 72-94)
-- **Database Schema**: `src/services/sqlite/SessionStore.ts` (line 95-104)
+- **Session Store**: `src/services/sqlite/SessionStore.ts`
 - **Tests**: `tests/session_id_usage_validation.test.ts`
 - **Related Tests**: `tests/session_id_refactor.test.ts`

docs/architecture-overview.md

@@ -0,0 +1,140 @@
+# claude-mem Architecture Overview
+
+## System Layers
+
+```text
++-----------------------------------------------------------+
+|  Claude Code (host)                                       |
+|  +-- Hook System (5 events)                               |
+|  +-- MCP Client (search tools)                            |
++-----------------------------------------------------------+
+|  CLI Layer (Bun)                                          |
+|  +-- bun-runner.js (Node->Bun bridge)                     |
+|  +-- hook-command.ts (orchestrator)                        |
+|  +-- handlers/ (context, session-init, observation,        |
+|                 summarize, session-complete)               |
++-----------------------------------------------------------+
+|  Worker Daemon (Express, port 37777)                      |
+|  +-- SessionManager (session lifecycle)                   |
+|  +-- SDKAgent (Claude Agent SDK)                          |
+|  +-- SearchManager (search orchestration)                 |
+|  +-- ProcessRegistry (subprocess management)              |
+|  +-- ChromaSync (embedding synchronization)               |
++-----------------------------------------------------------+
+|  Storage Layer                                            |
+|  +-- SQLite (claude-mem.db) -- structured data            |
+|  +-- ChromaDB (chroma.sqlite3) -- vector embeddings       |
+|  +-- MCP Server (interface for Claude Code)               |
++-----------------------------------------------------------+
+```
+
+## Hook Lifecycle
+
+| Event | Handler | What it does | Timeout |
+|-------|---------|-------------|---------|
+| Setup | setup.sh | Install system dependencies | 300s |
+| SessionStart | smart-install.js + context | Install deps + start worker + inject context | 60s |
+| UserPromptSubmit | session-init | Register session + start SDK agent + semantic injection | 60s |
+| PostToolUse | observation | Capture tool usage -> enqueue in worker | 120s |
+| Summary | summarize | Request session summary from SDK agent | 120s |
+| SessionEnd | session-complete | End session + drain pending messages | 30s |
+
+## Data Flow
+
+```text
+User prompt -> session-init -> /api/sessions/init + /api/context/semantic
+  |
+Tool use -> observation -> /api/sessions/observations
+  |                              |
+  |                    PendingMessageStore.enqueue()
+  |                              |
+  |                    SDKAgent.startSession()
+  |                              |
+  |                    Claude Agent SDK -> ResponseProcessor
+  |                              |
+  |                    +-- storeObservations() -> SQLite
+  |                    +-- chromaSync.sync() -> ChromaDB
+  |                    +-- broadcastObservation() -> SSE/UI
+  |
+Stop -> summarize -> /api/sessions/summarize
+     -> session-complete -> /api/sessions/complete + drain
+```
+
+## Key Patterns
+
+### CLAIM-CONFIRM (PendingMessageStore)
+
+```text
+enqueue()           -> INSERT status='pending'
+claimNextMessage()  -> UPDATE status='processing' (atomic)
+confirmProcessed()  -> DELETE (success)
+markFailed()        -> UPDATE status='failed' (retry < 3)
+
+Self-healing: messages in 'processing' for >60s reset to 'pending'
+```
+
+### Circuit-Breaker (SessionRoutes)
+
+```text
+Generator crash -> retry 1 (1s) -> retry 2 (2s) -> retry 3 (4s)
+  -> consecutiveRestarts > 3 -> CIRCUIT-BREAKER
+  -> markAllSessionMessagesAbandoned(sessionDbId)
+  -> Stop. No infinite loop.
+```
+
+Counter resets to 0 when generator completes work naturally.
+
+### Graceful Degradation (hook-command.ts)
+
+```text
+Transport errors (ECONNREFUSED, timeout, 5xx) -> exit 0 (never block Claude Code)
+Client bugs (4xx, TypeError, ReferenceError)  -> exit 2 (blocking, needs fix)
+```
+
+The worker being unavailable NEVER blocks the user's Claude Code session.
+
+### Deduplication (observations)
+
+```text
+SHA256(memory_session_id + title + narrative)[:16] -> content_hash (16 hex chars)
+If hash exists within 30s window -> return existing ID (no insert)
+```
+
+### Two Types of Session ID
+
+- `contentSessionId` — from Claude Code, invariant during the session
+- `memorySessionId` — from SDK Agent, changes on each worker restart
+
+The conversion between them is handled by SessionStore and is critical for FK constraints.
+
+## Storage
+
+### SQLite (claude-mem.db)
+
+| Table | Key fields | Purpose |
+|-------|-----------|---------|
+| sdk_sessions | content_session_id, memory_session_id, status | Session lifecycle |
+| observations | memory_session_id, type, title, narrative, content_hash | Tool usage observations |
+| session_summaries | memory_session_id, request, learned, completed | Session summaries |
+| user_prompts | content_session_id, prompt_text | User prompt history |
+| pending_messages | session_db_id, status, message_type | CLAIM-CONFIRM queue |
+| observation_feedback | observation_id, signal_type | Usage tracking |
+
+### ChromaDB (chroma.sqlite3)
+
+Vector embeddings for semantic search. Each observation generates multiple documents:
+
+```text
+obs_{id}_narrative  -> main text
+obs_{id}_fact_0     -> first fact
+obs_{id}_fact_1     -> second fact
+...
+```
+
+Accessed via chroma-mcp (MCP process), communication over stdio.
+
+## Process Management
+
+- **ProcessRegistry:** Tracks all Claude SDK subprocesses, manages PID lifecycle
+- **Orphan Reaper (5min):** Kills processes with no active session
+- **GracefulShutdown:** 7-step shutdown (PID file, children, HTTP server, sessions, MCP, DB, force-kill)

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/context/CLAUDE.md

@@ -1,77 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Nov 13, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #7806 | 4:54 PM | 🔵 | PR #101 Enhancement: Continuation Prompt Token Reduction | ~634 |
-
-### Nov 16, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #9976 | 11:35 PM | 🔵 | Endless Mode Architecture Plan Documented | ~661 |
-| #9967 | 11:18 PM | ⚖️ | Endless Mode Architecture: Immutable Storage with Ephemeral Transform | ~217 |
-
-### Nov 17, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #10131 | 1:22 AM | 🔵 | Endless Mode Token Economics Analysis Output: Complete Infrastructure Impact | ~542 |
-| #10130 | " | ✅ | Integration of Actual Compute Savings Analysis into Main Execution Flow | ~258 |
-| #10129 | " | 🔵 | Prompt Caching Economics: User Cost vs. Anthropic Compute Cost Divergence | ~451 |
-| #10126 | 1:19 AM | 🔴 | Fix Return Statement Variable Names in playTheTapeThrough Function | ~313 |
-| #10125 | " | ✅ | Redesign Timeline Display to Show Fresh/Cached Token Breakdown and Real Dollar Costs | ~501 |
-| #10124 | " | ✅ | Replace Estimated Cost Model with Actual Caching-Based Costs in Anthropic Scale Analysis | ~516 |
-| #10123 | " | ✅ | Pivot Session Length Comparison Table from Token to Cost Metrics | ~413 |
-| #10122 | " | ✅ | Add Dual Reporting: Token Count vs Actual Cost in Comparison Output | ~410 |
-| #10121 | 1:18 AM | ✅ | Apply Prompt Caching Cost Model to Endless Mode Calculation Function | ~501 |
-| #10120 | " | ✅ | Integrate Prompt Caching Cost Calculations into Without-Endless-Mode Function | ~426 |
-| #10119 | " | ✅ | Display Prompt Caching Pricing in Initial Calculator Output | ~297 |
-| #10118 | " | ✅ | Add Prompt Caching Pricing Model to Token Economics Calculator | ~316 |
-| #10115 | 1:15 AM | 🟣 | Token Economics Calculator for Endless Mode Sessions | ~465 |
-| #10013 | 12:13 AM | 🔵 | Duplicate Agent SDK TypeScript Reference Documentation | ~340 |
-| #10012 | " | 🔵 | Agent SDK TypeScript API Reference Complete | ~349 |
-
-### Nov 18, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #11738 | 11:51 PM | ⚖️ | Comprehensive Architecture Document Created for Phase 1 | ~868 |
-| #11711 | 11:44 PM | 🔵 | Language Model Tool Documentation Index | ~282 |
-| #11710 | " | 🔵 | Language Model Tool API Implementation Guide | ~718 |
-| #11709 | 11:43 PM | 🔵 | Comprehensive Copilot Extension Implementation Plan | ~624 |
-| #11708 | " | 🔵 | VS Code Chat Sample Documentation Unavailable | ~327 |
-| #11707 | " | 🔵 | VS Code Language Model API Structure and Capabilities | ~515 |
-| #11705 | " | ⚖️ | VS Code Extension Development Planning Phase Initiated | ~327 |
-| #11206 | 3:01 PM | 🔵 | mem-search skill architecture and migration details retrieved in full format | ~538 |
-
-### Nov 25, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #15538 | 8:36 PM | 🔵 | Context Document for Landing Page Refinements | ~381 |
-| #15314 | 5:04 PM | 🔵 | Endless Mode Documentation Post Retrieved with 156 Lines | ~671 |
-
-### Dec 20, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #31257 | 8:58 PM | ⚖️ | Eight Conflict Detection Hypotheses Evaluated with Simulation Results | ~525 |
-| #31256 | " | 🔵 | Supersession vs Conflict Detection Feature Analysis | ~515 |
-
-### Dec 30, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34520 | 2:34 PM | 🔵 | V2 Example Code Demonstrates All Key Patterns | ~537 |
-
-### Jan 7, 2026
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #38209 | 7:39 PM | 🔵 | Claude Code Hooks System Architecture and Usage | ~491 |
-</claude-mem-context>

docs/context/agent-sdk-v2-preview.md

@@ -32,7 +32,7 @@ For simple single-turn queries where you don't need to maintain a session, use `
 import { unstable_v2_prompt } from '@anthropic-ai/claude-agent-sdk'
 
 const result = await unstable_v2_prompt('What is 2 + 2?', {
-  model: 'claude-sonnet-4-5-20250929'
+  model: 'claude-sonnet-4-6-20250929'
 })
 console.log(result.result)
 ```
@@ -45,7 +45,7 @@ import { query } from '@anthropic-ai/claude-agent-sdk'
 
 const q = query({
   prompt: 'What is 2 + 2?',
-  options: { model: 'claude-sonnet-4-5-20250929' }
+  options: { model: 'claude-sonnet-4-6-20250929' }
 })
 
 for await (const msg of q) {
@@ -71,7 +71,7 @@ The example below creates a session, sends "Hello!" to Claude, and prints the te
 import { unstable_v2_createSession } from '@anthropic-ai/claude-agent-sdk'
 
 await using session = unstable_v2_createSession({
-  model: 'claude-sonnet-4-5-20250929'
+  model: 'claude-sonnet-4-6-20250929'
 })
 
 await session.send('Hello!')
@@ -97,7 +97,7 @@ import { query } from '@anthropic-ai/claude-agent-sdk'
 
 const q = query({
   prompt: 'Hello!',
-  options: { model: 'claude-sonnet-4-5-20250929' }
+  options: { model: 'claude-sonnet-4-6-20250929' }
 })
 
 for await (const msg of q) {
@@ -123,7 +123,7 @@ This example asks a math question, then asks a follow-up that references the pre
 import { unstable_v2_createSession } from '@anthropic-ai/claude-agent-sdk'
 
 await using session = unstable_v2_createSession({
-  model: 'claude-sonnet-4-5-20250929'
+  model: 'claude-sonnet-4-6-20250929'
 })
 
 // Turn 1
@@ -177,7 +177,7 @@ async function* createInputStream() {
 
 const q = query({
   prompt: createInputStream(),
-  options: { model: 'claude-sonnet-4-5-20250929' }
+  options: { model: 'claude-sonnet-4-6-20250929' }
 })
 
 for await (const msg of q) {
@@ -217,7 +217,7 @@ function getAssistantText(msg: SDKMessage): string | null {
 
 // Create initial session and have a conversation
 const session = unstable_v2_createSession({
-  model: 'claude-sonnet-4-5-20250929'
+  model: 'claude-sonnet-4-6-20250929'
 })
 
 await session.send('Remember this number: 42')
@@ -235,7 +235,7 @@ session.close()
 
 // Later: resume the session using the stored ID
 await using resumedSession = unstable_v2_resumeSession(sessionId!, {
-  model: 'claude-sonnet-4-5-20250929'
+  model: 'claude-sonnet-4-6-20250929'
 })
 
 await resumedSession.send('What number did I ask you to remember?')
@@ -254,7 +254,7 @@ import { query } from '@anthropic-ai/claude-agent-sdk'
 // Create initial session
 const initialQuery = query({
   prompt: 'Remember this number: 42',
-  options: { model: 'claude-sonnet-4-5-20250929' }
+  options: { model: 'claude-sonnet-4-6-20250929' }
 })
 
 // Get session ID from any message
@@ -276,7 +276,7 @@ console.log('Session ID:', sessionId)
 const resumedQuery = query({
   prompt: 'What number did I ask you to remember?',
   options: {
-    model: 'claude-sonnet-4-5-20250929',
+    model: 'claude-sonnet-4-6-20250929',
     resume: sessionId
   }
 })
@@ -304,7 +304,7 @@ Sessions can be closed manually or automatically using [`await using`](https://w
 import { unstable_v2_createSession } from '@anthropic-ai/claude-agent-sdk'
 
 await using session = unstable_v2_createSession({
-  model: 'claude-sonnet-4-5-20250929'
+  model: 'claude-sonnet-4-6-20250929'
 })
 // Session closes automatically when the block exits
 ```
@@ -315,7 +315,7 @@ await using session = unstable_v2_createSession({
 import { unstable_v2_createSession } from '@anthropic-ai/claude-agent-sdk'
 
 const session = unstable_v2_createSession({
-  model: 'claude-sonnet-4-5-20250929'
+  model: 'claude-sonnet-4-6-20250929'
 })
 // ... use the session ...
 session.close()

docs/i18n/CLAUDE.md

@@ -1,38 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Dec 12, 2025
-
-**README.ar.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #24246 | 2:43 AM | 🟣 | Comprehensive Translation System Added with 22 Language READMEs | ~386 |
-
-**README.zh.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #24241 | 2:35 AM | ✅ | Internationalized README Files Moved to Dedicated i18n Directory | ~284 |
-
-### Dec 22, 2025
-
-**README.ja.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #31948 | 8:08 PM | ✅ | Batch Updated All Translation READMEs with Language Navigation | ~400 |
-
-**README.zh.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #31947 | 8:07 PM | ✅ | Added Language Navigation Menu to Chinese Translation README | ~412 |
-| #31945 | 8:06 PM | 🟣 | Multi-language navigation added to internationalized README files | ~386 |
-| #31942 | 8:01 PM | 🔵 | Internationalization Documentation Coverage | ~315 |
-
-### Dec 28, 2025
-
-**README.*.md**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #33540 | 10:55 PM | 🔵 | Grep search found mem-search references in internationalized documentation | ~577 |
-</claude-mem-context>

docs/i18n/README.ar.md

@@ -1,5 +1,4 @@
-🌐 هذه ترجمة آلية. نرحب بالتصحيحات من المجتمع!
-
+<section dir="rtl">
 <h1 align="center">
   <br>
   <a href="https://github.com/thedotmack/claude-mem">
@@ -14,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> •
@@ -33,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> •
@@ -43,7 +44,8 @@
   <a href="README.no.md">🇳🇴 Norsk</a>
 </p>
 
-<h4 align="center">نظام ضغط الذاكرة المستمرة المبني لـ <a href="https://claude.com/claude-code" target="_blank">Claude Code</a>.</h4>
+<h4 align="center">أداة إضافية لـ <a href="https://claude.com/claude-code" target="_blank">Claude Code</a> تعمل على أتمتة تسجيل معلومات الجلسات السابقه، وضغطها, ثم حقن السياق ذي الصلة في الجلسات المستقبلية.
+</h4>
 
 <p align="center">
   <a href="LICENSE">
@@ -80,25 +82,27 @@
   </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 من الحفاظ على استمرارية المعرفة حول المشاريع حتى بعد انتهاء الجلسات أو إعادة الاتصال.
+  <a href="#بداية-سريعة">بداية سريعة</a> •
+  <a href="#كيف-يعمل">كيف يعمل</a> •
+  <a href="#أدوات-البحث-mcp-search-tools">أدوات البحث</a> •
+  <a href="#المستندات">التوثيق</a> •
+  <a href="#الإعدادات">الإعدادات</a> •
+  <a href="#استكشاف-الأخطاء-وإصلاحها">استكشاف الأخطاء وإصلاحها</a> •
+  <a href="#الترخيص-license">الترخيص</a>
+</p>
+
+<p align="center"  dir="rtl">
+Claude-Mem هو نظام متطور مصمم لضغط وحفظ الذاكرة لسياق عمل Claude Code. وظيفته الأساسية هي جعل "كلود" يتذكر ما فعله في جلسات العمل السابقة بسلاسة، عبر تسجيل تحركاته، وإنشاء ملخصات ذكية، واستدعائها في الجلسات المستقبلية. هذا يضمن عدم ضياع سياق المشروع حتى لو أغلقت البرنامج وفتحته لاحقاً.
 </p>
 
 ---
 
-## البدء السريع
+## بداية سريعة 
 
-ابدأ جلسة Claude Code جديدة في الطرفية وأدخل الأوامر التالية:
+للبدء، افتح "Claude Code" في مبنى الأوامر (Terminal) واكتب الأوامر التالية:
+<div dir="ltr"  align="left">
 
 ```
 > /plugin marketplace add thedotmack/claude-mem
@@ -106,32 +110,34 @@
 > /plugin install claude-mem
 ```
 
-أعد تشغيل Claude Code. سيظهر السياق من الجلسات السابقة تلقائيًا في الجلسات الجديدة.
+</div>
+
+بمجرد إعادة تشغيل Claude Code، سيتم استدعاء السياق من الجلسات السابقة تلقائيا عند الحاجة.
 
 **الميزات الرئيسية:**
 
-- 🧠 **ذاكرة مستمرة** - يبقى السياق عبر الجلسات
-- 📊 **الكشف التدريجي** - استرجاع الذاكرة بطبقات مع رؤية تكلفة الرموز
-- 🔍 **بحث قائم على المهارات** - استعلم عن تاريخ مشروعك باستخدام مهارة mem-search
-- 🖥️ **واجهة مستخدم ويب** - بث الذاكرة المباشر على http://localhost:37777
-- 💻 **مهارة Claude Desktop** - ابحث في الذاكرة من محادثات Claude Desktop
-- 🔒 **التحكم في الخصوصية** - استخدم وسوم `<private>` لاستبعاد المحتوى الحساس من التخزين
-- ⚙️ **إعدادات السياق** - تحكم دقيق في السياق الذي يتم حقنه
-- 🤖 **تشغيل تلقائي** - لا يتطلب تدخلاً يدويًا
-- 🔗 **الاستشهادات** - رجوع إلى الملاحظات السابقة باستخدام المعرفات (الوصول عبر http://localhost:37777/api/observation/{id} أو عرض الكل في عارض الويب على http://localhost:37777)
-- 🧪 **قناة تجريبية** - جرّب الميزات التجريبية مثل Endless Mode عبر تبديل الإصدار
+- 🧠 **ذاكرة مستديمه**:  سياق عملك لا ينتهي بانتهاء الجلسة، بل ينتقل معك للجلسة التالية.
+- 📊 **الكشف التدريجي** (Progressive Disclosure): نظام ذكي يستدعي المعلومات على طبقات، مما يمنحك رؤية واضحة لاستهلاك الـ "Tokens" (التكلفة).
+- 🔍 **بحث سريع** - استعلم عن سجل مشروعك باستخدام خاصية `mem-search`.
+- 🖥️ **واجهة مستخدم ويب** - رؤية معلومات الذاكرة مع  تحديث فوري عبر المتصفح من خلال الرابط: http://localhost:37777
+- 💻 **تكامل مع Claude Desktop** - إمكانية البحث في الذاكرة مباشرة من واجهة Claude المكتبية
+- 🔒 **التحكم في الخصوصية** - دعم وسم `<private>` لمنع النظام من تخزين أي معلومات حساسة.
+- ⚙️ **إعدادات السياق** - تحكم دقيق في السياق (context) التي سيتم حقنها في سياق المحادثة.
+- 🤖 **أتمتة كاملة:** - النظام يعمل في الخلفية دون الحاجة لتدخل يدوي منك.
+- 🔗 **الاستشهادات** - رجوع إلى الملاحظات السابقة باستخدام (http://localhost:37777/api/observation/{id} أو عرض جميع المعلومات على http://localhost:37777)
+- 🧪 **مزايا التجريبيه** - تجربة مميزات مثل "الوضع اللانهائي" (Endless Mode).
 
 ---
 
-## التوثيق
+## المستندات 
 
-📚 **[عرض التوثيق الكامل](docs/)** - تصفح مستندات markdown على GitHub
+📚 **[عرض التوثيق الكامل](https://docs.claude-mem.ai/)** - تصفح على الموقع الرسمي
 
 ### البدء
 
 - **[دليل التثبيت](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/usage/search-tools)** - استعلم عن سجل مشروعك بلغتك
 - **[الميزات التجريبية](https://docs.claude-mem.ai/beta-features)** - جرّب الميزات التجريبية مثل Endless Mode
 
 ### أفضل الممارسات
@@ -142,9 +148,9 @@
 ### البنية المعمارية
 
 - **[نظرة عامة](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-evolution)** - تطور المعمارية من v3 إلى v5
+- **[بنية برامج الربط (Hooks)](https://docs.claude-mem.ai/hooks-architecture)** - كيف يستخدم Claude-Mem خطافات دورة الحياة
+- **[مرجع برامج الربط (Hooks)](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
@@ -161,24 +167,23 @@
 
 **المكونات الأساسية:**
 
-1. **5 خطافات دورة الحياة** - SessionStart، UserPromptSubmit، PostToolUse، Stop، SessionEnd (6 سكريبتات خطافات)
-2. **تثبيت ذكي** - فاحص التبعيات المخزنة مؤقتًا (سكريبت ما قبل الخطاف، ليس خطاف دورة حياة)
+1. **5 برامج ربط (Hooks)** - SessionStart، UserPromptSubmit، PostToolUse، Stop، SessionEnd
+2. **تثبيت ذكي** - فاحص التبعيات المخزنة مؤقتًا
 3. **خدمة العامل** - HTTP API على المنفذ 37777 مع واجهة مستخدم عارض الويب و10 نقاط نهاية للبحث، تديرها Bun
 4. **قاعدة بيانات SQLite** - تخزن الجلسات، الملاحظات، الملخصات
 5. **مهارة mem-search** - استعلامات اللغة الطبيعية مع الكشف التدريجي
-6. **قاعدة بيانات المتجهات Chroma** - البحث المختلط الدلالي + الكلمات المفتاحية لاسترجاع السياق الذكي
+6. **قاعدة بيانات المتجهات Chroma** - البحث الدلالي الهجين + الكلمات المفتاحية لاسترجاع السياق الذكي
 
 انظر [نظرة عامة على البنية المعمارية](https://docs.claude-mem.ai/architecture/overview) للتفاصيل.
 
 ---
 
-## مهارة mem-search
-
+## أدوات البحث (MCP Search Tools)
 يوفر Claude-Mem بحثًا ذكيًا من خلال مهارة mem-search التي تُستدعى تلقائيًا عندما تسأل عن العمل السابق:
 
 **كيف يعمل:**
 - فقط اسأل بشكل طبيعي: *"ماذا فعلنا في الجلسة الأخيرة؟"* أو *"هل أصلحنا هذا الخطأ من قبل؟"*
-- يستدعي Claude تلقائيًا مهارة mem-search للعثور على السياق ذي الصلة
+- يستدعي Claude تلقائيًا خاصية mem-search للعثور على السياق ذي الصلة
 
 **عمليات البحث المتاحة:**
 
@@ -193,7 +198,7 @@
 9. **الجدول الزمني حسب الاستعلام** - البحث عن الملاحظات والحصول على سياق الجدول الزمني حول أفضل تطابق
 10. **مساعدة API** - الحصول على توثيق API البحث
 
-**أمثلة على استعلامات اللغة الطبيعية:**
+**أمثلة على الاستعلامات:**
 
 ```
 "What bugs did we fix last session?"
@@ -219,8 +224,7 @@
 
 - **Node.js**: 18.0.0 أو أعلى
 - **Claude Code**: أحدث إصدار مع دعم الإضافات
-- **Bun**: بيئة تشغيل JavaScript ومدير العمليات (يُثبت تلقائيًا إذا كان مفقودًا)
-- **uv**: مدير حزم Python للبحث المتجهي (يُثبت تلقائيًا إذا كان مفقودًا)
+- **Bun & uv**: (يتم تثبيتهما تلقائياً) لإدارة العمليات والبحث المتجه.
 - **SQLite 3**: للتخزين المستمر (مدمج)
 
 ---
@@ -241,7 +245,7 @@
 
 ## استكشاف الأخطاء وإصلاحها
 
-إذا واجهت مشكلات، صِف المشكلة لـ Claude وستقوم مهارة troubleshoot تلقائيًا بتشخيصها وتوفير الإصلاحات.
+إذا واجهت مشكلة، اشرحها لـ Claude وسيقوم بتشغيل خاصية troubleshoot لإصلاحها ذاتياً.
 
 انظر **[دليل استكشاف الأخطاء وإصلاحها](https://docs.claude-mem.ai/troubleshooting)** للمشكلات الشائعة والحلول.
 
@@ -250,27 +254,29 @@
 ## تقارير الأخطاء
 
 أنشئ تقارير أخطاء شاملة باستخدام المولّد الآلي:
+<div align=left>
 
 ```bash
 cd ~/.claude/plugins/marketplaces/thedotmack
 npm run bug-report
 ```
+</div>
 
 ## المساهمة
 
 المساهمات مرحب بها! يُرجى:
 
-1. عمل Fork للمستودع
-2. إنشاء فرع ميزة
+1. عمل Fork للمشروع (Repository)
+2. إنشاء فرع (branch)
 3. إجراء التغييرات مع الاختبارات
-4. تحديث التوثيق
+4. تحديث المستندات عند الحاجه
 5. تقديم Pull Request
 
 انظر [دليل التطوير](https://docs.claude-mem.ai/development) لسير عمل المساهمة.
 
 ---
 
-## الترخيص
+## الترخيص (License)
 
 هذا المشروع مرخص بموجب **ترخيص GNU Affero العام الإصدار 3.0** (AGPL-3.0).
 
@@ -298,4 +304,6 @@ npm run bug-report
 
 ---
 
-**مبني باستخدام Claude Agent SDK** | **مدعوم بواسطة Claude Code** | **صُنع باستخدام TypeScript**
+**مبني باستخدام Claude Agent SDK** | **مدعوم بواسطة Claude Code** | **صُنع باستخدام TypeScript**
+
+</section>

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/production-guide.md

@@ -0,0 +1,111 @@
+# claude-mem Production Guide
+
+Practical guide based on 23 days of production usage with 3,400+ observations across two physical servers and 8 projects.
+
+## Recommended Settings
+
+| Setting | Default | Recommended | Why |
+|---------|---------|-------------|-----|
+| CLAUDE_MEM_MAX_CONCURRENT_AGENTS | 2 | 3 | Better throughput without overload |
+| CLAUDE_MEM_SEMANTIC_INJECT | true | true | Relevant context >> recent context |
+| CLAUDE_MEM_SEMANTIC_INJECT_LIMIT | 5 | 5 | Sweet spot for token cost vs coverage |
+| CLAUDE_MEM_TIER_ROUTING_ENABLED | true | true | ~52% cost savings, no quality loss |
+
+## Health Monitoring
+
+### Key metrics to watch
+
+| Metric | Healthy | Warning | Action |
+|--------|---------|---------|--------|
+| pending_messages (pending) | 0-5 | >10 | Check worker logs, may need restart |
+| pending_messages (failed) | 0 | >0 growing | Circuit-breaker may be tripping |
+| sdk_sessions (active) | 0-3 | >5 stuck | Orphan sessions, worker restart |
+| WAL size | <10 MB | >20 MB | Run `PRAGMA wal_checkpoint(TRUNCATE)` |
+| Chroma size | Growing slowly | Sudden jump | Check for sync loops |
+| Errors/day in logs | 0-2 | >10 | Investigate log patterns |
+
+### Quick health check
+
+```bash
+# Check worker status
+curl -s http://127.0.0.1:37777/api/health | python3 -m json.tool
+
+# Check database stats
+sqlite3 ~/.claude-mem/claude-mem.db "
+  SELECT 'observations' as metric, COUNT(*) as value FROM observations
+  UNION ALL SELECT 'summaries', COUNT(*) FROM session_summaries
+  UNION ALL SELECT 'pending', COUNT(*) FROM pending_messages WHERE status='pending'
+  UNION ALL SELECT 'active_sessions', COUNT(*) FROM sdk_sessions WHERE status='active';
+"
+```
+
+## Multi-Machine Setup
+
+If running claude-mem on multiple machines, use `claude-mem-sync` to keep observations in sync:
+
+```bash
+claude-mem-sync push <remote-host>    # local -> remote
+claude-mem-sync pull <remote-host>    # remote -> local
+claude-mem-sync sync <remote-host>    # bidirectional
+claude-mem-sync status <remote-host>  # compare counts
+```
+
+Deduplication is by `(created_at, title)` — safe to run repeatedly.
+
+## Growth Expectations
+
+Based on active daily development usage:
+
+| Metric | Per day | Per month | Notes |
+|--------|---------|-----------|-------|
+| Observations | ~120 | ~3,600 | Varies with coding activity |
+| Summaries | ~40 | ~1,200 | One per session |
+| SQLite | ~0.8 MB | ~24 MB | ~5 KB per observation |
+| Chroma | ~4 MB | ~120 MB | ~50 KB per observation (embeddings) |
+
+## Common Issues and Solutions
+
+### Summarize error loop
+
+**Symptom:** Repeated `[ERROR] Missing last_assistant_message` in logs.
+**Cause:** Transcript with no assistant messages triggers summary attempt that fails repeatedly.
+**Fix:** PR #1566 — skip summary when transcript is empty.
+
+### Chroma sync failures
+
+**Symptom:** `[ERROR] Batch add failed... IDs already exist`
+**Cause:** MCP timeout during add leaves partial writes; retry fails on existing IDs.
+**Fix:** PR #1566 — fallback to delete+add reconciliation.
+
+### Port conflict on startup
+
+**Symptom:** `Worker failed to start... Is port 37777 in use?`
+**Cause:** Two sessions starting simultaneously — HTTP check is non-atomic (TOCTOU race).
+**Fix:** PR #1566 — atomic socket bind on Unix.
+
+### Orphaned pending messages
+
+**Symptom:** `pending_messages` table growing with old entries for completed sessions.
+**Cause:** SIGTERM kills generator before queue is drained.
+**Fix:** PR #1567 — drain after deleteSession().
+
+### Context not relevant to current topic
+
+**Symptom:** Claude receives observations about CSS when you're asking about authentication.
+**Cause:** Default recency-based injection selects most recent, not most relevant.
+**Fix:** PR #1568 — semantic injection via Chroma on every prompt.
+
+## Log Analysis Tips
+
+```bash
+# Count errors by day
+grep '\[ERROR\]' ~/.claude-mem/logs/claude-mem-*.log | \
+  sed 's/\[20[0-9][0-9]-[0-9][0-9]-/\n&/g' | \
+  grep -oP '^\[20\d{2}-\d{2}-\d{2}' | sort | uniq -c
+
+# Find circuit-breaker trips
+grep 'circuit\|Circuit\|ABANDONED\|abandoned' ~/.claude-mem/logs/claude-mem-*.log
+
+# Check pending message health
+grep 'CLAIMED\|CONFIRMED\|FAILED\|ABANDONED' ~/.claude-mem/logs/claude-mem-$(date +%Y-%m-%d).log | tail -20
+```

docs/public/CLAUDE.md

@@ -85,92 +85,4 @@ npx mintlify dev
 
 **Simple Rule**:
 - `/docs/public/` = Official user documentation (Mintlify .mdx files) ← YOU ARE HERE
-- `/docs/context/` = Internal docs, plans, references, audits
-
-
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Nov 18, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #11206 | 3:01 PM | 🔵 | mem-search skill architecture and migration details retrieved in full format | ~538 |
-
-### Nov 21, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #13221 | 2:01 AM | 🔴 | Fixed broken markdown link to Viewer UI documentation | ~316 |
-| #13220 | 2:00 AM | 🔴 | Escaped HTML less-than symbol in universal architecture timeout documentation | ~316 |
-| #13216 | 1:54 AM | ✅ | Universal Architecture Added to Navigation | ~330 |
-| #13215 | " | 🟣 | Universal AI Memory Architecture Documentation Created | ~732 |
-| #13213 | 1:50 AM | 🔵 | Introduction Page Content and Recent v6.0.0 Release | ~495 |
-| #13212 | " | 🔵 | Architecture Evolution Documentation Structure | ~408 |
-| #13211 | " | 🔵 | Mintlify Documentation Site Configuration | ~430 |
-| #13209 | 1:48 AM | 🔵 | Public Documentation Structure and Guidelines | ~383 |
-
-### Nov 25, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #14994 | 2:22 PM | ✅ | Version Channel Section Added to Configuration Documentation | ~301 |
-| #14993 | " | ✅ | Beta Features Added to Documentation Navigation | ~188 |
-| #14992 | 2:21 PM | 🟣 | Beta Features Documentation Page Created | ~488 |
-| #14991 | " | 🔵 | Mintlify Navigation Structure and Documentation Groups | ~394 |
-| #14989 | " | 🔵 | Installation Documentation with Quick Start and Verification Steps | ~383 |
-| #14988 | " | 🔵 | Configuration Documentation Structure and Environment Variables | ~338 |
-
-### Nov 26, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #16190 | 10:22 PM | 🔵 | RAGTIME Search Retrieved Five Observations About Claude-Mem vs RAG Architecture | ~637 |
-
-### Dec 3, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #19884 | 9:42 PM | 🔵 | Configuration system and environment variables | ~701 |
-| #19878 | 9:40 PM | 🔵 | Installation process and system architecture | ~486 |
-
-### Dec 8, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #22335 | 10:26 PM | 🔵 | Mintlify documentation configuration analyzed | ~534 |
-| #22311 | 9:47 PM | 🔵 | Comprehensive Hooks Architecture Documentation Review | ~263 |
-| #22297 | 9:43 PM | 🔵 | Mintlify Documentation Framework Configuration | ~446 |
-| #22294 | " | 🔵 | Documentation Site Structure Located | ~359 |
-
-### Dec 9, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #23179 | 10:44 PM | ✅ | Removed explanatory reasons from tool exclusion documentation | ~297 |
-
-### Dec 15, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #27038 | 6:02 PM | 🔵 | 95% token reduction claims found only in private experimental documents, not in main public docs | ~513 |
-| #27037 | " | 🔵 | Branch switching functionality exists in SettingsRoutes with UI switcher removal intent | ~463 |
-| #26986 | 5:24 PM | ✅ | Updated Endless Mode latency warning in beta features documentation | ~299 |
-
-### Dec 29, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #33938 | 6:27 PM | 🔵 | Relevant CLAUDE.md Context Identified for PR #492 | ~435 |
-| #33750 | 12:25 AM | ✅ | Documentation Update: Removed Version Number from Architecture Evolution | ~281 |
-
-### Jan 7, 2026
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #38233 | 7:42 PM | ✅ | Renumbered SessionEnd Hook from 6 to 5 | ~315 |
-| #38229 | 7:41 PM | ✅ | Renumbered PostToolUse Hook from 4 to 3 | ~278 |
-| #38225 | " | ✅ | Updated Hook Count Description in Hooks Architecture Documentation | ~352 |
-</claude-mem-context>
+- `/docs/context/` = Internal docs, plans, references, audits

docs/public/architecture/CLAUDE.md

@@ -1,38 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Nov 18, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #11206 | 3:01 PM | 🔵 | mem-search skill architecture and migration details retrieved in full format | ~538 |
-
-### Nov 21, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #13218 | 1:58 AM | 🔴 | Escaped HTML special character in MDX documentation | ~261 |
-
-### Dec 3, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #19891 | 9:43 PM | 🔵 | Seven hook scripts across five lifecycle events | ~713 |
-
-### Dec 15, 2025
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #27040 | 6:03 PM | 🔵 | Comprehensive search confirms no 95% claims exist in main branch public documentation | ~508 |
-| #27037 | 6:02 PM | 🔵 | Branch switching functionality exists in SettingsRoutes with UI switcher removal intent | ~463 |
-
-### Jan 7, 2026
-
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #38221 | 7:41 PM | ✅ | Removed User Message Hook Documentation Section | ~339 |
-| #38218 | 7:40 PM | ✅ | Updated Hook Configuration Documentation to Match Implementation | ~382 |
-| #38212 | " | 🔵 | 5-Stage Hook Lifecycle Architecture for Memory Agent | ~668 |
-</claude-mem-context>

docs/public/architecture/hooks.mdx

@@ -860,7 +860,7 @@ async startSession(session: ActiveSession, worker?: any) {
   const queryResult = query({
     prompt: messageGenerator,
     options: {
-      model: 'claude-sonnet-4-5',
+      model: 'claude-sonnet-4-6',
       disallowedTools: ['Bash', 'Read', 'Write', ...],  // Observer-only
       abortController: session.abortController
     }

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/CLAUDE.md

@@ -1,51 +0,0 @@
-<claude-mem-context>
-# Recent Activity
-
-<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
-
-### Dec 29, 2025
-
-**gemini-setup.mdx**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34346 | 11:11 PM | 🟣 | Gemini Free Tier Integration Guide | ~413 |
-| #34337 | 11:10 PM | 🔵 | Cursor Documentation Available | ~161 |
-| #34331 | 11:05 PM | 🔴 | Fixed Broken Links in cursor/gemini-setup.mdx | ~253 |
-| #34326 | 11:04 PM | 🔵 | Broken Links in Cursor Gemini Setup Documentation | ~324 |
-| #34320 | 11:03 PM | 🔵 | Mintlify Broken Links Detected in Documentation | ~292 |
-| #34215 | 10:08 PM | 🔵 | Retrieved Detailed Cursor Integration Implementation History | ~676 |
-| #34214 | 10:07 PM | 🔵 | Cursor Integration Feature Set Discovered via Memory Search | ~427 |
-| #34148 | 9:28 PM | 🟣 | Cursor IDE Integration with Cross-Platform Hooks and Documentation | ~514 |
-| #34112 | 9:07 PM | 🟣 | Committed Cursor Public Documentation to Repository | ~427 |
-| #34106 | 9:05 PM | 🟣 | Created Cursor-Specific Gemini Setup Guide | ~563 |
-
-**index.mdx**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34339 | 11:10 PM | 🟣 | Cursor IDE Integration with Persistent Memory | ~394 |
-| #34335 | 11:06 PM | 🟣 | Mintlify Documentation Linting Successfully Completed | ~409 |
-| #34330 | 11:05 PM | 🔴 | Fixed Remaining Broken Links in cursor/index.mdx Next Steps Section | ~284 |
-| #34329 | " | 🔴 | Fixed Broken Links in cursor/index.mdx Detailed Guides Section | ~269 |
-| #34325 | 11:04 PM | 🔵 | Multiple Broken Links in Cursor Index Documentation | ~329 |
-| #34216 | 10:08 PM | 🔵 | Additional Cursor Integration Details Retrieved for Post Writing | ~600 |
-| #34105 | 9:05 PM | 🟣 | Created Cursor Integration Landing Page | ~522 |
-
-**openrouter-setup.mdx**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34332 | 11:05 PM | 🔴 | Fixed Broken Links in cursor/openrouter-setup.mdx | ~283 |
-| #34324 | 11:04 PM | 🔵 | Broken Link Syntax Identified in Cursor Documentation | ~329 |
-| #34107 | 9:06 PM | 🟣 | Created Cursor-Specific OpenRouter Setup Guide | ~573 |
-
-**cursor**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #34322 | 11:03 PM | 🔵 | Cursor Directory Files Confirmed to Exist | ~224 |
-
-### Jan 4, 2026
-
-**gemini-setup.mdx**
-| ID | Time | T | Title | Read |
-|----|------|---|-------|------|
-| #36751 | 12:32 AM | 🔵 | Gemini-Related Files Located Across Project | ~242 |
-</claude-mem-context>

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

@@ -39,6 +39,7 @@
           "usage/openrouter-provider",
           "usage/gemini-provider",
           "usage/search-tools",
+          "usage/knowledge-agents",
           "usage/claude-desktop",
           "usage/private-tags",
           "usage/export-import",
@@ -57,12 +58,21 @@
           "cursor/openrouter-setup"
         ]
       },
+      {
+        "group": "Gemini CLI Integration",
+        "icon": "terminal",
+        "pages": [
+          "gemini-cli/setup"
+        ]
+      },
       {
         "group": "Best Practices",
         "icon": "lightbulb",
         "pages": [
           "context-engineering",
-          "progressive-disclosure"
+          "progressive-disclosure",
+          "file-read-gate",
+          "smart-explore-benchmark"
         ]
       },
       {
@@ -73,7 +83,8 @@
           "modes",
           "development",
           "troubleshooting",
-          "platform-integration"
+          "platform-integration",
+          "openclaw-integration"
         ]
       },
       {

docs/public/file-read-gate.mdx

@@ -0,0 +1,180 @@
+---
+title: "File Read Gate"
+description: "How claude-mem intercepts file reads to save tokens using observation history"
+---
+
+# File Read Gate
+
+## What It Is
+
+The File Read Gate is a **PreToolUse hook** that intercepts Claude's `Read` tool calls. When Claude tries to read a file that has prior observations in the database, the gate blocks the read and instead shows a compact timeline of past work on that file. Claude then decides the cheapest path to get the context it needs.
+
+This is a concrete implementation of [progressive disclosure](/progressive-disclosure) -- show what exists first, let the agent decide what to fetch.
+
+---
+
+## How It Works
+
+```
+Claude calls Read("src/services/worker-service.ts")
+         ↓
+   PreToolUse hook fires
+         ↓
+   File size < 1,500 bytes? ──→ Allow read (timeline costs more than file)
+         ↓ No
+   Project excluded? ──→ Allow read
+         ↓ No
+   Query worker: GET /api/observations/by-file
+         ↓
+   No observations found? ──→ Allow read
+         ↓ Has observations
+   Deduplicate (1 per session)
+   Rank by specificity
+   Limit to 15
+         ↓
+   DENY read with timeline
+```
+
+When the gate fires, Claude sees a message like this:
+
+```
+Current: 2026-04-07 3:25pm PDT
+Read blocked: This file has prior observations. Choose the cheapest path:
+- Already know enough? The timeline below may be all you need (semantic priming).
+- Need details? get_observations([IDs]) -- ~300 tokens each.
+- Need current code? smart_outline("path") for structure (~1-2k tokens),
+  smart_unfold("path", "<symbol>") for a specific function (~400-2k tokens).
+- Need to edit? Use smart tools for line numbers, then sed via Bash.
+
+### Apr 5, 2026
+42301 2:15pm  Fixed database connection pooling
+42298 1:50pm  Refactored worker startup sequence
+
+### Mar 28, 2026
+41890 4:30pm  Added health check endpoint
+```
+
+---
+
+## The Decision Tree
+
+Claude has four options after seeing the timeline, ordered from cheapest to most expensive:
+
+| Option | Token Cost | When to Use |
+|--------|-----------|-------------|
+| **Semantic priming** | 0 extra | Timeline titles tell Claude enough to proceed |
+| **get_observations([IDs])** | ~300 each | Need specific details from past work |
+| **smart_outline / smart_unfold** | ~1-2k | Need current code structure or a specific function |
+| **Full file read** | 5k-50k | File has changed significantly since observations |
+
+In practice, most file reads resolve at the semantic priming or get_observations level, saving thousands of tokens per interaction.
+
+---
+
+## Current Date/Time for Temporal Reasoning
+
+The timeline includes the current date and time as its first line:
+
+```
+Current: 2026-04-07 3:25pm PDT
+```
+
+This lets Claude reason about how recent the observations are relative to now. For example:
+
+- **Observations from today** -- likely still accurate, semantic priming is safe
+- **Observations from last week** -- probably accurate, get_observations for details
+- **Observations from months ago** -- file may have changed, consider smart_outline or full read
+
+The timestamp format matches the session start context header (`YYYY-MM-DD time timezone`), so Claude sees consistent temporal markers throughout its session.
+
+---
+
+## Token Economics
+
+A typical source file costs **5,000-50,000 tokens** to read in full. The File Read Gate replaces that with:
+
+| Component | Tokens |
+|-----------|--------|
+| Timeline header + instructions | ~120 |
+| 15 observation entries | ~250 |
+| **Total timeline** | **~370** |
+
+If Claude needs more detail, it fetches individual observations at ~300 tokens each. Even fetching 3 observations totals ~1,270 tokens -- still a **75-97% savings** over reading the full file.
+
+### Real-World Example
+
+Without the gate (reading `worker-service.ts`):
+```
+Read: 18,000 tokens
+```
+
+With the gate:
+```
+Timeline:       370 tokens
++ 2 observations: 600 tokens
+Total:          970 tokens (95% savings)
+```
+
+---
+
+## Specificity Ranking
+
+Not all observations about a file are equally relevant. The gate scores each observation by how specifically it relates to the target file:
+
+| Signal | Score Bonus |
+|--------|------------|
+| File was **modified** (not just read) | +2 |
+| Observation covers **3 or fewer** total files | +2 |
+| Observation covers **4-8** total files | +1 |
+| Observation covers **9+** files (survey-like) | +0 |
+
+Higher-scoring observations appear first in the timeline. An observation where the file was the primary modification target ranks above one where the file was incidentally read alongside 20 others.
+
+---
+
+## Configuration
+
+### Small File Bypass
+
+Files smaller than **1,500 bytes** always pass through the gate without interception. At that size, the timeline (~370 tokens) would cost more than reading the file directly. This threshold is hardcoded in `src/cli/handlers/file-context.ts`.
+
+### Project Exclusions
+
+Projects matching patterns in `CLAUDE_MEM_EXCLUDED_PROJECTS` skip the gate entirely. Configure this in `~/.claude-mem/settings.json`:
+
+```json
+{
+  "CLAUDE_MEM_EXCLUDED_PROJECTS": "/tmp/*,/scratch/*"
+}
+```
+
+### How to Disable the Gate
+
+The File Read Gate is implemented as a PreToolUse hook on the `Read` tool matcher. To disable it, remove the `Read` matcher entry from the hooks configuration:
+
+1. Open your Claude Code settings:
+   ```
+   ~/.claude/settings.json
+   ```
+
+2. Find the claude-mem hooks section under `hooks.PreToolUse` and remove the entry with the `Read` matcher.
+
+Alternatively, if you want to keep the gate installed but bypass it for a specific read, Claude can ask you to allow the read -- the gate's deny decision is presented to the user, who can override it.
+
+<Note>
+Disabling the gate means Claude will read full files every time, which increases token usage but ensures it always sees the latest code. This is a reasonable choice for small projects or when observations are sparse.
+</Note>
+
+---
+
+## How It Fits Together
+
+The File Read Gate is one piece of claude-mem's layered context strategy:
+
+1. **Session Start**: Inject timeline of recent observations (layer 1 -- metadata)
+2. **File Read Gate**: Intercept reads with observation history (layer 1 -- metadata)
+3. **get_observations**: Fetch specific observation details on demand (layer 2 -- details)
+4. **smart_outline / smart_unfold**: Read current code structure efficiently (layer 3 -- source)
+5. **Full file read**: Last resort when everything else is insufficient
+
+Each layer is progressively more expensive. The gate ensures Claude starts at the cheapest layer and escalates only when needed.

docs/public/gemini-cli/setup.mdx

@@ -0,0 +1,192 @@
+---
+title: "Gemini CLI Setup"
+description: "Add persistent memory to Gemini CLI with claude-mem"
+---
+
+# Gemini CLI Setup
+
+> **Give Gemini CLI persistent memory across sessions.**
+
+Gemini CLI starts every session from scratch. Claude-mem changes that by capturing observations, decisions, and patterns — then injecting relevant context into each new session.
+
+<Info>
+**How it works:** Claude-mem installs lifecycle hooks into Gemini CLI that capture tool usage, agent responses, and session events. A local worker service extracts semantic observations and injects relevant history at session start.
+</Info>
+
+## Prerequisites
+
+- [Gemini CLI](https://github.com/google-gemini/gemini-cli) installed and configured
+- [Node.js](https://nodejs.org/) 18+
+- The `~/.gemini` directory must exist (created by Gemini CLI on first run)
+
+## Installation
+
+### Step 1: Install claude-mem
+
+```bash
+npx claude-mem install
+```
+
+The installer will:
+1. Auto-detect Gemini CLI (checks for `~/.gemini` directory)
+2. Prompt you to select **Gemini CLI** from the IDE picker
+3. Install 8 lifecycle hooks into `~/.gemini/settings.json`
+4. Inject context configuration into `~/.gemini/GEMINI.md`
+5. Start the worker service
+
+### Step 2: Configure an AI provider
+
+Claude-mem needs an AI provider to extract observations from your sessions. Choose one:
+
+<Tabs>
+  <Tab title="Gemini API (Free)">
+    The simplest option — use Gemini's own API for observation extraction:
+
+    1. Get a free API key from [Google AI Studio](https://aistudio.google.com/apikey)
+    2. Add it to your settings:
+
+    ```bash
+    mkdir -p ~/.claude-mem
+    cat > ~/.claude-mem/settings.json << 'EOF'
+    {
+      "CLAUDE_MEM_PROVIDER": "gemini",
+      "CLAUDE_MEM_GEMINI_API_KEY": "YOUR_API_KEY"
+    }
+    EOF
+    ```
+
+    <Tip>
+    **Free tier:** 1,500 requests/day with `gemini-2.5-flash-lite`. Enable billing on Google Cloud for 4,000 RPM without charges.
+    </Tip>
+  </Tab>
+  <Tab title="Claude SDK">
+    If you have a Claude API key:
+
+    ```bash
+    mkdir -p ~/.claude-mem
+    cat > ~/.claude-mem/settings.json << 'EOF'
+    {
+      "CLAUDE_MEM_PROVIDER": "claude"
+    }
+    EOF
+    ```
+
+    Set your API key via environment variable:
+    ```bash
+    export ANTHROPIC_API_KEY="your-key"
+    ```
+  </Tab>
+  <Tab title="OpenRouter">
+    For access to 100+ models:
+
+    ```bash
+    mkdir -p ~/.claude-mem
+    cat > ~/.claude-mem/settings.json << 'EOF'
+    {
+      "CLAUDE_MEM_PROVIDER": "openrouter",
+      "CLAUDE_MEM_OPENROUTER_API_KEY": "YOUR_KEY"
+    }
+    EOF
+    ```
+  </Tab>
+</Tabs>
+
+### Step 3: Verify installation
+
+```bash
+# Check worker is running
+npx claude-mem status
+
+# Check hooks are installed — look for claude-mem entries
+cat ~/.gemini/settings.json | grep claude-mem
+```
+
+Open http://localhost:37777 to see the memory viewer.
+
+### Step 4: Start using Gemini CLI
+
+Launch Gemini CLI normally. Claude-mem works in the background:
+
+```bash
+gemini
+```
+
+On session start, you'll see claude-mem context injected with your recent observations and project history.
+
+## What gets captured
+
+Claude-mem registers 8 of Gemini CLI's 11 lifecycle hooks:
+
+| Hook | Purpose |
+|------|---------|
+| **SessionStart** | Injects memory context into the session |
+| **SessionEnd** | Marks session complete, triggers summary |
+| **PreCompress** | Captures session summary before compression |
+| **Notification** | Records system events (permissions, etc.) |
+| **BeforeAgent** | Captures user prompts |
+| **AfterAgent** | Records full agent responses |
+| **BeforeTool** | Logs tool invocations before execution |
+| **AfterTool** | Captures tool results after execution |
+
+Three model-level hooks (BeforeModel, AfterModel, BeforeToolSelection) are intentionally skipped — they fire per-LLM-call and are too noisy for memory capture.
+
+## Troubleshooting
+
+### Hooks not firing
+
+1. Verify hooks exist in settings:
+   ```bash
+   cat ~/.gemini/settings.json
+   ```
+   You should see entries like `"SessionStart"`, `"AfterTool"`, etc. with claude-mem commands.
+
+2. Restart Gemini CLI after installation.
+
+3. Re-run the installer:
+   ```bash
+   npx claude-mem install
+   ```
+
+### Worker not running
+
+```bash
+# Check status
+npx claude-mem status
+
+# View logs
+npx claude-mem logs
+
+# Restart worker
+npx claude-mem restart
+```
+
+### No context appearing at session start
+
+1. Ensure the worker is running (check http://localhost:37777)
+2. You need at least one previous session with observations for context to appear
+3. Check your AI provider is configured in `~/.claude-mem/settings.json`
+
+### Raw escape codes in output
+
+If you see characters like `[31m` or `[0m` in the session context, your claude-mem version may need updating:
+
+```bash
+npx claude-mem install
+```
+
+This was fixed in v10.6.3+ — the Gemini CLI adapter now strips ANSI color codes automatically.
+
+## Uninstalling
+
+```bash
+npx claude-mem uninstall
+```
+
+This removes hooks from `~/.gemini/settings.json` and cleans up `~/.gemini/GEMINI.md`.
+
+## Next Steps
+
+- [Gemini Provider](/usage/gemini-provider) — Configure the Gemini AI provider for observation extraction
+- [Configuration](/configuration) — All settings options
+- [Search Tools](/usage/search-tools) — Search your memory from within sessions
+- [Troubleshooting](/troubleshooting) — Common issues and solutions

docs/public/installation.mdx

@@ -7,20 +7,35 @@ description: "Install Claude-Mem plugin for persistent memory across sessions"
 
 ## Quick Start
 
-Install Claude-Mem directly from the plugin marketplace:
+### Option 1: npx (Recommended)
+
+Install and configure Claude-Mem with a single command:
+
+```bash
+npx claude-mem install
+```
+
+The interactive installer will:
+- Detect your installed IDEs (Claude Code, Cursor, Gemini CLI, Windsurf, etc.)
+- Copy plugin files to the correct locations
+- Register the plugin with Claude Code
+- Install all dependencies (including Bun and uv)
+- Auto-start the worker service
+
+### Option 2: Plugin Marketplace
+
+Install Claude-Mem directly from the plugin marketplace inside Claude Code:
 
 ```bash
 /plugin marketplace add thedotmack/claude-mem
 /plugin install claude-mem
 ```
 
-That's it! The plugin will automatically:
-- Download prebuilt binaries (no compilation needed)
-- Install all dependencies (including SQLite binaries)
-- Configure hooks for session lifecycle management
-- Auto-start the worker service on first session
+Both methods will automatically configure hooks and start the worker service. Start a new Claude Code session and you'll see context from previous sessions automatically loaded.
 
-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.
+> Always install via `npx claude-mem install` or the `/plugin` commands above.
 
 ## System Requirements