chore: bump version to 11.0.1

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

.claude-plugin/marketplace.json

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

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

@@ -1,68 +1,5 @@
 # Memory Context from Past Sessions
 
-The following context is from claude-mem, a persistent memory system that tracks your coding sessions.
+*No context yet. Complete your first session and context will appear here.*
 
-# $CMEM claude-mem 2026-04-03 6:48pm PDT
-
-Legend: 🎯session 🔴bugfix 🟣feature 🔄refactor ✅change 🔵discovery ⚖️decision
-Format: ID TIME TYPE TITLE
-Fetch details: get_observations([IDs]) | Search: mem-search skill
-
-Stats: 50 obs (18,868t read) | 401,168t work | 95% savings
-
-### Apr 3, 2026
-62994 1:47p 🔴 Merge Commit Finalized on thedotmack/npx-gemini-cli Branch
-62995 1:48p 🔵 Worker Running but Health Endpoint Doesn't Accept POST
-62996 " 🔵 Worker Health Endpoint Returns Detailed Status via GET
-62997 1:49p 🔵 Worker Service Timeout and Shutdown Behavior in worker-service.ts
-62998 " 🔵 claude-mem Hook Architecture Defined in plugin/hooks/hooks.json
-62999 " 🔵 Session Idle Timeout Architecture: Two-Tier System in claude-mem
-63000 " 🔵 Orphan Reaper Runs Every 30 Seconds; Sessions Orphaned After 6 Hours
-63001 1:51p 🔵 POST /api/sessions/complete Removes Sessions from Active Map to Unblock Orphan Reaper
-63002 1:52p 🔵 Stop Hook Summarize Flow: Extracts Last Assistant Message from Transcript
-63004 " 🔵 POST /api/sessions/summarize: Privacy Check Before Queuing SDK Agent
-63005 " 🔵 SessionManager.deleteSession Verifies Subprocess Exit to Prevent Zombies
-63007 " 🔵 deleteSession: 4-Step Teardown with Generator and Subprocess Timeouts
-63008 1:53p 🔵 Queue Depth Always Read from Database; Generator Restarts Capped at 3
-63009 " 🔴 Fixed Lost Summaries: session-complete Now Waits for Pending Work Before Deleting Session
-63010 1:54p 🔴 SessionEnd Hook Timeout Increased to 180s
-63014 2:00p 🔵 claude-mem Hook Architecture and Exit Code System
-63015 2:01p 🔵 SessionEnd Hook Has a 1.5s Default Timeout Controlled by Environment Variable
-63016 2:02p 🔴 Stop Hook Now Owns Full Session Lifecycle: Summarize → Poll → Complete
-63017 " 🔵 Missing /api/sessions/status Route — Only DB-ID Variant Exists
-63018 2:03p 🔴 Added /api/sessions/status Route Registration to SessionRoutes
-63020 " 🟣 Added handleStatusByClaudeId Handler for GET /api/sessions/status
-63022 " 🔄 Removed Pending-Work Polling from /api/sessions/complete — Moved to Stop Hook
-63024 " 🔄 SessionEnd Hook Reverted to Fast Fire-and-Forget (2s Timeout)
-63026 2:04p 🔵 claude-mem hooks.json Full Hook Lifecycle Configuration
-63027 2:05p ✅ Push to Pull Request
-63028 " 🔵 Pre-Push State: claude-mem Repository Changes
-63029 " 🔴 Fix Lost Summaries: Move Summary Wait into Stop Hook
-63035 2:11p ✅ Testing Plan Created for tmux-cli npx Installation Flows
-63036 2:12p 🔵 claude-mem Supports 13 npx Installation Flows Across IDE Integrations
-63037 " 🔵 Detailed Integration Strategies for All 13 claude-mem npx Installation Flows
-63038 2:13p ✅ NPX Install Flow Test Plan Document Created
-63039 " ✅ 12 TODO Tasks Created for npx Install Flow Testing
-63040 2:19p 🟣 Comprehensive Test Suite Requested for Claude-Mem CLI
-63041 2:20p 🔵 NPX Install Flow Test Plan Exists for 12 IDE Integrations
-63042 " 🟣 Phase 2 E2E Runtime Testing Added to NPX Install Test Plan
-63043 " ✅ Test Tasks Updated with Phase 2 E2E Runtime Steps for 5 IDE Flows
-63044 " ✅ All Remaining Test Tasks (6–12) Updated with Phase 2 E2E Runtime Steps
-63079 6:31p ⚖️ Test Execution via Subagents Using /do Command
-63080 6:32p 🔵 IDE Auto-Detection Module in claude-mem
-63081 " 🔵 Install Command Architecture with Multi-IDE Dispatch
-63082 " 🔵 MCP Integrations Module for 6 IDEs
-63083 " 🔵 Cursor, Windsurf, and Gemini CLI Hook-Based Integrations
-63084 " 🔵 OpenCode, OpenClaw, and Codex CLI Installers
-63085 6:33p 🔵 tmux-cli Available for Automated Testing
-63086 " 🔵 NPX Install Flow Test Plan — 12 IDE Flows
-63087 6:34p 🟣 Detailed Test Execution Plan Created for NPX Install Flows
-63103 6:47p 🔵 NPX Install Fails for Windsurf IDE with Missing rxjs Dependency
-63104 " 🔵 Windsurf Install Failure Was a Dependency Ordering Race
-63105 " 🟣 claude-mem Gemini CLI Integration: 8 Hooks Registered
-63106 " 🟣 claude-mem OpenCode Integration: Plugin File + AGENTS.md Context
-
-Access 401k tokens of past work via get_observations([IDs]) or mem-search skill.
-
----
-*Auto-updated by claude-mem after each session. Use MCP search tools for detailed queries.*
+Use claude-mem's MCP search tools for manual memory queries.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem",
-  "version": "10.7.1",
+  "version": "11.0.1",
   "description": "Memory compression system for Claude Code - persist context across sessions",
   "keywords": [
     "claude",

plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem",
-  "version": "10.7.1",
+  "version": "11.0.1",
   "description": "Persistent memory system for Claude Code - seamlessly preserve context across sessions",
   "author": {
     "name": "Alex Newman"

plugin/modes/code.json

@@ -87,8 +87,8 @@
     "system_identity": "You are a Claude-Mem, a specialized observer tool for creating searchable memory FOR FUTURE SESSIONS.\n\nCRITICAL: Record what was LEARNED/BUILT/FIXED/DEPLOYED/CONFIGURED, not what you (the observer) are doing.\n\nYou do not have access to tools. All information you need is provided in <observed_from_primary_session> messages. Create observations from what you observe - no investigation needed.",
     "spatial_awareness": "SPATIAL AWARENESS: Tool executions include the working directory (tool_cwd) to help you understand:\n- Which repository/project is being worked on\n- Where files are located relative to the project root\n- How to match requested paths to actual execution paths",
     "observer_role": "Your job is to monitor a different Claude Code session happening RIGHT NOW, with the goal of creating observations and progress summaries as the work is being done LIVE by the user. You are NOT the one doing the work - you are ONLY observing and recording what is being built, fixed, deployed, or configured in the other session.",
-    "recording_focus": "WHAT TO RECORD\n--------------\nFocus on deliverables and capabilities:\n- What the system NOW DOES differently (new capabilities)\n- What shipped to users/production (features, fixes, configs, docs)\n- Changes in technical domains (auth, data, UI, infra, DevOps, docs)\n\nUse verbs like: implemented, fixed, deployed, configured, migrated, optimized, added, refactored\n\n✅ GOOD EXAMPLES (describes what was built):\n- \"Authentication now supports OAuth2 with PKCE flow\"\n- \"Deployment pipeline runs canary releases with auto-rollback\"\n- \"Database indexes optimized for common query patterns\"\n\n❌ BAD EXAMPLES (describes observation process - DO NOT DO THIS):\n- \"Analyzed authentication implementation and stored findings\"\n- \"Tracked deployment steps and logged outcomes\"\n- \"Monitored database performance and recorded metrics\"",
-    "skip_guidance": "WHEN TO SKIP\n------------\nSkip routine operations:\n- Empty status checks\n- Package installations with no errors\n- Simple file listings\n- Repetitive operations you've already documented\n- If file related research comes back as empty or not found\n- **No output necessary if skipping.**",
+    "recording_focus": "WHAT TO RECORD\n--------------\nFocus on durable technical signal:\n- What the system NOW DOES differently (new capabilities)\n- What shipped to users/production (features, fixes, configs, docs)\n- Changes in technical domains (auth, data, UI, infra, DevOps, docs)\n- Concrete debugging or investigative findings from logs, traces, queue state, database rows, and code-path inspection\n\nUse verbs like: implemented, fixed, deployed, configured, migrated, optimized, added, refactored, discovered, confirmed, traced\n\n✅ GOOD EXAMPLES (describes what was built or learned):\n- \"Authentication now supports OAuth2 with PKCE flow\"\n- \"Deployment pipeline runs canary releases with auto-rollback\"\n- \"Database indexes optimized for common query patterns\"\n- \"Observation queue for claude-mem session timed out waiting for an agent pool slot\"\n- \"Fallback processing abandoned pending messages after Gemini and OpenRouter returned 404\"\n\n❌ BAD EXAMPLES (describes observation process - DO NOT DO THIS):\n- \"Analyzed authentication implementation and stored findings\"\n- \"Tracked deployment steps and logged outcomes\"\n- \"Monitored database performance and recorded metrics\"",
+    "skip_guidance": "WHEN TO SKIP\n------------\nSkip routine operations:\n- Empty status checks\n- Package installations with no errors\n- Simple file listings with no follow-on finding\n- Repetitive operations you've already documented\n- File related research that comes back empty or not found\n\nIf skipping, return an empty response only. Do not explain the skip in prose.",
     "type_guidance": "**type**: MUST be EXACTLY one of these 6 options (no other values allowed):\n      - bugfix: something was broken, now fixed\n      - feature: new capability or functionality added\n      - refactor: code restructured, behavior unchanged\n      - change: generic modification (docs, config, misc)\n      - discovery: learning about existing system\n      - decision: architectural/design choice with rationale",
     "concept_guidance": "**concepts**: 2-5 knowledge-type categories. MUST use ONLY these exact keywords:\n      - how-it-works: understanding mechanisms\n      - why-it-exists: purpose or rationale\n      - what-changed: modifications made\n      - problem-solution: issues and their fixes\n      - gotcha: traps or edge cases\n      - pattern: reusable approach\n      - trade-off: pros/cons of a decision\n\n    IMPORTANT: Do NOT include the observation type (change/discovery/decision) as a concept.\n    Types and concepts are separate dimensions.",
     "field_guidance": "**facts**: Concise, self-contained statements\nEach fact is ONE piece of information\n      No pronouns - each fact must stand alone\n      Include specific details: filenames, functions, values\n\n**files**: All files touched (full paths from project root)",
@@ -122,4 +122,4 @@
     "summary_format_instruction": "Respond in this XML format:",
     "summary_footer": "IMPORTANT! DO NOT do any work right now other than generating this next PROGRESS SUMMARY - and remember that you are a memory agent designed to summarize a DIFFERENT claude code session, not this one.\n\nNever reference yourself or your own actions. Do not output anything other than the summary content formatted in the XML structure above. All other output is ignored by the system, and the system has been designed to be smart about token usage. Please spend your tokens wisely on useful summary content.\n\nThank you, this summary will be very useful for keeping track of our progress!"
   }
-}
+}

plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-plugin",
-  "version": "10.7.1",
+  "version": "11.0.1",
   "private": true,
   "description": "Runtime dependencies for claude-mem bundled hooks",
   "type": "module",

src/npx-cli/commands/ide-detection.ts

@@ -116,7 +116,8 @@ export function detectInstalledIDEs(): IDEInfo[] {
       id: 'cursor',
       label: 'Cursor',
       detected: existsSync(join(home, '.cursor')),
-      supported: false,
+      supported: true,
+      hint: 'hooks + MCP integration',
     },
     {
       id: 'copilot-cli',

src/npx-cli/commands/install.ts

@@ -135,9 +135,22 @@ async function setupIDEs(selectedIDEs: string[]): Promise<string[]> {
         break;
       }
 
-      case 'cursor':
-        log.warn('Cursor: integration not yet implemented. Skipping.');
+      case 'cursor': {
+        const { installCursorHooks, configureCursorMcp } = await import('../../services/integrations/CursorHooksInstaller.js');
+        const cursorResult = await installCursorHooks('user');
+        if (cursorResult === 0) {
+          const mcpResult = configureCursorMcp('user');
+          if (mcpResult === 0) {
+            log.success('Cursor: hooks + MCP installed.');
+          } else {
+            log.success('Cursor: hooks installed (MCP setup failed — run `npx claude-mem cursor mcp` to retry).');
+          }
+        } else {
+          log.error('Cursor: hook installation failed.');
+          failedIDEs.push(ideId);
+        }
         break;
+      }
 
       case 'gemini-cli': {
         const { installGeminiCliHooks } = await import('../../services/integrations/GeminiCliHooksInstaller.js');

src/sdk/parser.ts

@@ -75,7 +75,7 @@ export function parseObservations(text: string, correlationId?: string): ParsedO
     const cleanedConcepts = concepts.filter(c => c !== finalType);
 
     if (cleanedConcepts.length !== concepts.length) {
-      logger.error('PARSER', 'Removed observation type from concepts array', {
+      logger.debug('PARSER', 'Removed observation type from concepts array', {
         correlationId,
         type: finalType,
         originalConcepts: concepts,

src/sdk/prompts.ts

@@ -116,7 +116,11 @@ export function buildObservationPrompt(obs: Observation): string {
   <occurred_at>${new Date(obs.created_at_epoch).toISOString()}</occurred_at>${obs.cwd ? `\n  <working_directory>${obs.cwd}</working_directory>` : ''}
   <parameters>${JSON.stringify(toolInput, null, 2)}</parameters>
   <outcome>${JSON.stringify(toolOutput, null, 2)}</outcome>
-</observed_from_primary_session>`;
+</observed_from_primary_session>
+
+Return either one or more <observation>...</observation> blocks, or an empty response if this tool use should be skipped.
+Concrete debugging findings from logs, queue state, database rows, session routing, or code-path inspection count as durable discoveries and should be recorded.
+Never reply with prose such as "Skipping", "No substantive tool executions", or any explanation outside XML. Non-XML text is discarded.`;
 }
 
 /**
@@ -235,4 +239,4 @@ ${mode.prompts.format_examples}
 ${mode.prompts.footer}
 
 ${mode.prompts.header_memory_continued}`;
-} 
+} 

src/services/worker/agents/ResponseProcessor.ts

@@ -68,6 +68,19 @@ export async function processAgentResponse(
   const observations = parseObservations(text, session.contentSessionId);
   const summary = parseSummary(text, session.sessionDbId);
 
+  if (
+    text.trim() &&
+    observations.length === 0 &&
+    !summary &&
+    !/<observation>|<summary>|<skip_summary\b/.test(text)
+  ) {
+    const preview = text.length > 200 ? `${text.slice(0, 200)}...` : text;
+    logger.warn('PARSER', `${agentName} returned non-XML response; observation content was discarded`, {
+      sessionId: session.sessionDbId,
+      preview
+    });
+  }
+
   // Convert nullable fields to empty strings for storeSummary (if summary exists)
   const summaryForStore = normalizeSummaryForStorage(summary);
 

src/shared/SettingsDefaultsManager.ts

@@ -121,7 +121,7 @@ export class SettingsDefaultsManager {
     CLAUDE_MEM_EXCLUDED_PROJECTS: '',  // Comma-separated glob patterns for excluded project paths
     CLAUDE_MEM_FOLDER_MD_EXCLUDE: '[]',  // JSON array of folder paths to exclude from CLAUDE.md generation
     // Semantic Context Injection (per-prompt via Chroma vector search)
-    CLAUDE_MEM_SEMANTIC_INJECT: 'true',              // Inject relevant past observations on every UserPromptSubmit
+    CLAUDE_MEM_SEMANTIC_INJECT: 'false',             // Inject relevant past observations on every UserPromptSubmit (experimental, disabled by default)
     CLAUDE_MEM_SEMANTIC_INJECT_LIMIT: '5',           // Top-N most relevant observations to inject per prompt
     // Tier Routing (model selection by queue complexity)
     CLAUDE_MEM_TIER_ROUTING_ENABLED: 'true',         // Route observations to models by complexity

tests/sdk/prompts.test.ts

@@ -0,0 +1,20 @@
+import { describe, expect, it } from 'bun:test';
+
+import { buildObservationPrompt } from '../../src/sdk/prompts.js';
+
+describe('buildObservationPrompt', () => {
+  it('instructs the observer to avoid prose skip responses', () => {
+    const prompt = buildObservationPrompt({
+      id: 1,
+      tool_name: 'exec_command',
+      tool_input: JSON.stringify({ cmd: 'pwd' }),
+      tool_output: JSON.stringify({ output: '/repo' }),
+      created_at_epoch: Date.now(),
+      cwd: '/repo',
+    });
+
+    expect(prompt).toContain('Return either one or more <observation>...</observation> blocks, or an empty response');
+    expect(prompt).toContain('Concrete debugging findings from logs, queue state, database rows, session routing, or code-path inspection');
+    expect(prompt).toContain('Never reply with prose such as "Skipping", "No substantive tool executions"');
+  });
+});

tests/worker/agents/response-processor.test.ts

@@ -212,6 +212,36 @@ describe('ResponseProcessor', () => {
     });
   });
 
+  describe('non-XML observer responses', () => {
+    it('warns when the observer returns prose that will be discarded', async () => {
+      const session = createMockSession();
+      const responseText = 'Skipping — repeated log scan with no new findings.';
+
+      await processAgentResponse(
+        responseText,
+        session,
+        mockDbManager,
+        mockSessionManager,
+        mockWorker,
+        100,
+        null,
+        'TestAgent'
+      );
+
+      expect(logger.warn).toHaveBeenCalledWith(
+        'PARSER',
+        'TestAgent returned non-XML response; observation content was discarded',
+        expect.objectContaining({
+          sessionId: 1,
+          preview: responseText
+        })
+      );
+      const [, , observations, summary] = mockStoreObservations.mock.calls[0];
+      expect(observations).toHaveLength(0);
+      expect(summary).toBeNull();
+    });
+  });
+
   describe('parsing summary from XML response', () => {
     it('should parse summary from response', async () => {
       const session = createMockSession();