get-claudia 1.40.0 → 1.40.1

package/memory-daemon/claudia_memory/__main__.py

@@ -180,11 +180,21 @@ def run_daemon(mcp_mode: bool = True, debug: bool = False, project_id: str = Non
     if project_id:
         logger.info(f"Project isolation enabled: {project_id}")
 
-    # Acquire lockfile before touching the database -- prevents concurrent
-    # daemon instances from both writing to the same SQLite file, which is
-    # the root cause of "database disk image is malformed" errors.
     config = get_config()
-    _acquire_daemon_lock(Path(config.db_path).parent / "claudia.lock")
+
+    if not mcp_mode:
+        # Only enforce singleton for the standalone background daemon.
+        # The lock prevents two long-running background processes from
+        # concurrently running scheduled jobs (decay, consolidation) against
+        # the same SQLite file, which caused "database disk image is malformed"
+        # errors.
+        #
+        # MCP servers are ephemeral, session-bound processes spawned by Claude
+        # Code. They must NOT compete for the same lock as a running standalone
+        # daemon (e.g., installed via LaunchAgent/systemd). SQLite WAL mode
+        # handles concurrent read/write access safely across processes.
+        _acquire_daemon_lock(Path(config.db_path).parent / "claudia.lock")
+
     _check_and_repair_database(Path(config.db_path))
 
     # Set up signal handlers

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-claudia",
-  "version": "1.40.0",
+  "version": "1.40.1",
   "description": "An AI assistant who learns how you work.",
   "keywords": [
     "claudia",

package/template-v2/.claude/hooks/hooks.json

@@ -14,9 +14,9 @@
         ],
         "on_missing_me": "trigger_onboarding",
         "memory_verification": {
-          "step_1_check_tools": "BEFORE anything else, verify you have access to memory.* MCP tools. If no memory tools are available, inform the user: 'Memory daemon not connected. Run the /diagnose command or check ~/.claudia/daemon-stderr.log for errors.'",
+          "step_1_check_tools": "BEFORE anything else, verify you have access to mcp__claudia-memory__* tools (check your available tools list). If no memory tools are available: (1) Do NOT fall back to plugin:episodic-memory, mcp__plugin_episodic-memory_*, or any other memory search tool as a substitute — these give inferior, unrelated results and mask the real problem. (2) Tell the user: 'My memory tools are not registered in this session. The daemon likely just auto-restarted — please restart Claude Code (close and reopen the window) to reconnect. Your context files are preserved.' (3) Continue with context files only (context/me.md, etc.) until restarted.",
           "step_2_health_check": "Call memory.session (operation=\"context\"). If it fails or returns an error, the daemon may be crashed. Suggest: 'Memory daemon may need restart. Check: curl http://localhost:3848/health'",
-          "fallback": "If memory tools unavailable, proceed with markdown-only mode but WARN the user that memories won't persist."
+          "fallback": "If mcp__claudia-memory__* tools are not available: (1) Do NOT use plugin:episodic-memory or any other memory search tool as a substitute. (2) Tell the user: 'My memory tools are not registered in this session. The daemon may have just restarted — please restart Claude Code to reconnect. Your context files are preserved.' (3) Read context files directly (context/me.md, context/commitments.md, context/learnings.md, context/patterns.md, context/waiting.md) as the fallback. Make clear to the user they are in degraded mode with no semantic search or cross-session learning."
         },
         "enhanced_memory": {
           "context_load": "Call memory.session (operation=\"context\") to get a formatted context block with recent memories, commitments, and unsummarized session alerts.",
@@ -74,7 +74,7 @@
   ],
   "notes": {
     "implementation": "These hooks define intended behaviors. Claude Code will execute them as behavioral guidelines rather than traditional script execution.",
-    "memory_verification": "CRITICAL: At session start, verify memory tools are available BEFORE proceeding. If memory.* tools don't appear in available tools, the daemon isn't connected. This is a hard requirement for full Claudia functionality.",
+    "memory_verification": "CRITICAL: At session start, verify mcp__claudia-memory__* tools are available BEFORE proceeding. If tools don't appear, do NOT use plugin:episodic-memory as a substitute. Tell the user to restart Claude Code — the daemon auto-restarts but MCP tools only register at session start. Fall back to context files only (context/me.md, etc.) in the meantime.",
     "session_start": "At session start: (1) Verify memory tools available, (2) Call memory.session (operation=\"context\"), (3) Read context files, (4) Check for unsummarized sessions. If me.md is missing, trigger onboarding.",
     "session_end": "Before session ends, Claudia should generate a session summary (enhanced memory) or update context files (markdown fallback). The summary includes both a free-form narrative and structured extractions.",
     "first_run": "The absence of context/me.md signals a first-run scenario requiring onboarding.",

package/template-v2/.claude/hooks/session-health-check.py

@@ -102,9 +102,17 @@ def check_health():
                 pass
             if restarted:
                 status_msg = _get_status_summary()
-                msg = "Memory daemon was stopped but has been restarted automatically."
+                msg = (
+                    "IMPORTANT: Memory daemon was stopped and has been auto-restarted. "
+                    "However, the memory MCP tools (mcp__claudia-memory__*) are NOT available in this session "
+                    "because MCP tools connect at session start, before the restart happened. "
+                    "Tell the user: 'The memory daemon was just restarted. Please restart Claude Code "
+                    "(close and reopen the window) to reconnect your memory tools. "
+                    "Your context files are preserved.' "
+                    "Do NOT use plugin:episodic-memory as a substitute."
+                )
                 if status_msg:
-                    msg = f"{msg} {status_msg}"
+                    msg = f"{msg} Daemon status: {status_msg}"
                 print(json.dumps({"additionalContext": msg}))
                 return
             context_parts.append(
@@ -138,9 +146,17 @@ def check_health():
                 pass
             if restarted:
                 status_msg = _get_status_summary()
-                msg = "Memory daemon was stopped but has been restarted automatically."
+                msg = (
+                    "IMPORTANT: Memory daemon was stopped and has been auto-restarted. "
+                    "However, the memory MCP tools (mcp__claudia-memory__*) are NOT available in this session "
+                    "because MCP tools connect at session start, before the restart happened. "
+                    "Tell the user: 'The memory daemon was just restarted. Please restart Claude Code "
+                    "(close and reopen the window) to reconnect your memory tools. "
+                    "Your context files are preserved.' "
+                    "Do NOT use plugin:episodic-memory as a substitute."
+                )
                 if status_msg:
-                    msg = f"{msg} {status_msg}"
+                    msg = f"{msg} Daemon status: {status_msg}"
                 print(json.dumps({"additionalContext": msg}))
                 return
             context_parts.append(

package/template-v2/.claude/hooks/session-health-check.sh

@@ -79,9 +79,9 @@ except Exception:
     pass
 " <<< "$STATUS_JSON" 2>/dev/null)
       fi
-      MSG="Memory daemon was stopped but has been restarted automatically."
+      MSG="IMPORTANT: Memory daemon was stopped and has been auto-restarted. However, the memory MCP tools (mcp__claudia-memory__*) are NOT available in this session because MCP tools connect at session start, before the restart happened. Tell the user: 'The memory daemon was just restarted. Please restart Claude Code (close and reopen the window) to reconnect your memory tools. Your context files are preserved.' Do NOT use plugin:episodic-memory as a substitute."
       if [ -n "$STATUS_SUMMARY" ]; then
-        MSG="$MSG $STATUS_SUMMARY"
+        MSG="$MSG Daemon status: $STATUS_SUMMARY"
       fi
       STATUS_ESC=$(echo "$MSG" | sed 's/"/\\"/g')
       echo "{\"additionalContext\": \"$STATUS_ESC\"}"
@@ -116,9 +116,9 @@ except Exception:
     pass
 " <<< "$STATUS_JSON" 2>/dev/null)
       fi
-      MSG="Memory daemon was stopped but has been restarted automatically."
+      MSG="IMPORTANT: Memory daemon was stopped and has been auto-restarted. However, the memory MCP tools (mcp__claudia-memory__*) are NOT available in this session because MCP tools connect at session start, before the restart happened. Tell the user: 'The memory daemon was just restarted. Please restart Claude Code (close and reopen the window) to reconnect your memory tools. Your context files are preserved.' Do NOT use plugin:episodic-memory as a substitute."
       if [ -n "$STATUS_SUMMARY" ]; then
-        MSG="$MSG $STATUS_SUMMARY"
+        MSG="$MSG Daemon status: $STATUS_SUMMARY"
       fi
       STATUS_ESC=$(echo "$MSG" | sed 's/"/\\"/g')
       echo "{\"additionalContext\": \"$STATUS_ESC\"}"

package/template-v2/.claude/rules/memory-availability.md

@@ -0,0 +1,51 @@
+# Memory Availability Rule
+
+This rule is always active and applies to every session.
+
+---
+
+## When Memory Tools Are Missing
+
+If `mcp__claudia-memory__*` tools are **not listed in your available tools**, follow these rules strictly:
+
+### Do NOT substitute with other memory tools
+
+Do not use any of the following as a replacement for missing memory tools:
+- `plugin:episodic-memory` / `mcp__plugin_episodic-memory_*`
+- Any other cross-session memory or search tool not in the `mcp__claudia-memory__*` family
+
+These tools access a different, unrelated memory system. Using them gives the user the wrong memories, masks the real connectivity problem, and creates confusion about what Claudia actually knows.
+
+### Do tell the user clearly
+
+Say something like:
+
+> "My memory tools aren't connected in this session. The daemon is likely running but the MCP connection isn't registered yet. To fix this, restart Claude Code (close and reopen the window). Your context files are preserved and I can work from those in the meantime."
+
+### Do fall back to context files only
+
+Read the following files directly as the fallback:
+- `context/me.md`
+- `context/commitments.md`
+- `context/learnings.md`
+- `context/patterns.md`
+- `context/waiting.md`
+
+Make clear to the user they are in degraded mode: no semantic search, no pattern detection, no cross-session learning. This is the honest and correct behavior.
+
+### The fix is one action
+
+The user only needs to do one thing: **restart Claude Code**. The daemon auto-restarts via launchctl/systemctl. There is no command to type. Just close and reopen the Claude Code window.
+
+---
+
+## Why This Matters
+
+The most common cause of missing memory tools is not a crashed daemon but a **registration timing issue**: the daemon was restarted (auto or manually) after the current Claude Code session started. MCP tools connect at session initialization, not dynamically. The daemon is up; the tools just aren't registered yet.
+
+Silently using `plugin:episodic-memory` as a fallback:
+1. Gives the wrong data (different memory system, different scope)
+2. Makes it look like memory is working when it isn't
+3. Prevents the user from knowing they need to restart
+
+Always be transparent about the degraded state.

package/template-v2/.claude/skills/diagnose/SKILL.md

@@ -63,7 +63,7 @@ Use the appropriate command set below (macOS/Linux or Windows).
 **macOS/Linux:**
 
 ```bash
-# Check if daemon process is running
+# Check if daemon process is running (and whether in standalone mode)
 ps aux | grep claudia_memory | grep -v grep
 
 # Check health endpoint
@@ -75,6 +75,11 @@ tail -20 ~/.claudia/daemon-stderr.log 2>/dev/null || echo "No daemon log found"
 # Check database exists and has data
 ls -la ~/.claudia/memory/*.db 2>/dev/null || echo "No database found"
 sqlite3 ~/.claudia/memory/claudia.db "SELECT COUNT(*) as memories FROM memories; SELECT COUNT(*) as entities FROM entities;" 2>/dev/null || echo "Cannot query database"
+
+# Check for standalone/MCP conflict (pre-v1.36 issue)
+# If you see a process with --standalone AND no MCP tools, this is the cause
+STANDALONE_RUNNING=$(ps aux | grep "claudia_memory.*standalone" | grep -v grep | wc -l | tr -d ' ')
+echo "Standalone daemon processes: $STANDALONE_RUNNING"
 ```
 
 **Windows (PowerShell):**
@@ -188,6 +193,24 @@ powershell -ExecutionPolicy Bypass -File memory-daemon\scripts\install.ps1
 2. Restart Claude Code (this restarts the MCP server)
 3. Check logs: `Get-Content -Tail 50 "$env:USERPROFILE\.claudia\daemon-stderr.log"`
 
+### Issue: Standalone daemon running but MCP tools not registered (pre-v1.36)
+
+**Symptoms:** Daemon process running with `--standalone`, health endpoint healthy, 0 memory tools in Claude Code
+
+**Cause (pre-v1.36):** The LaunchAgent/systemd service starts the daemon with `--standalone`, which acquires a singleton lock. When Claude Code spawns the MCP server, it hits the same lock, sees another daemon running, and exits immediately (exit code 0). Claude Code sees the clean exit and thinks the MCP server started, but no tools register.
+
+**Fix:** Upgrade Claudia to v1.36+ where this conflict is resolved:
+```bash
+npx get-claudia .
+```
+After upgrading, restart Claude Code. The MCP server no longer competes with the standalone daemon's lock.
+
+**If upgrade isn't possible:** Restart Claude Code. If tools still don't register, stop the standalone daemon temporarily:
+```bash
+launchctl unload ~/Library/LaunchAgents/com.claudia.memory.plist
+```
+Then restart Claude Code (which will spawn the MCP server cleanly). Note: background jobs won't run until you reload the LaunchAgent.
+
 ### Issue: .mcp.json uses wrong entry point
 
 **Detection:** Check the `args` array in `.mcp.json` for the `claudia-memory` server. If it says `claudia_memory.mcp.server` instead of `claudia_memory`, it bypasses project isolation, the health server, and background scheduling.