get-claudia 1.51.7 → 1.51.9

package/bin/index.js

@@ -469,8 +469,10 @@ async function main() {
     console.log(` ${colors.green}✓${colors.reset} Framework updated (data preserved)`);
   }
 
-  // Disable Gmail/Calendar MCP servers (Claudia has native CLI commands now)
-  disableGoogleMcpServers(targetPath);
+  // Move legacy MCP servers (memory, Gmail, Calendar) to _disabled_mcpServers.
+  // Claude Code's native disable format: servers in _disabled_mcpServers are
+  // preserved but not launched. User can move them back to re-enable if needed.
+  disableLegacyMcpServers(targetPath);
 
   // Write context/whats-new.md for Claudia's self-awareness (silent)
   writeWhatsNewFile(targetPath, version);
@@ -876,11 +878,15 @@ async function main() {
 }
 
 /**
- * Disable Gmail and Google Calendar MCP servers in .mcp.json if present.
- * Claudia now has native CLI commands for both services, so external MCP
- * servers are no longer needed. This runs on both fresh installs and upgrades.
+ * Disable legacy MCP servers in .mcp.json that have been replaced by native CLI commands.
+ * This runs on both fresh installs and upgrades.
+ *
+ * Replaced servers:
+ * - claudia-memory  → `claudia memory` CLI (Node.js, direct SQLite)
+ * - gmail           → `claudia gmail` CLI
+ * - google-calendar → `claudia calendar` CLI
  */
-function disableGoogleMcpServers(targetPath) {
+function disableLegacyMcpServers(targetPath) {
   const mcpPath = join(targetPath, '.mcp.json');
   if (!existsSync(mcpPath)) return;
 
@@ -889,20 +895,46 @@ function disableGoogleMcpServers(targetPath) {
     const config = JSON.parse(raw);
     if (!config.mcpServers) return;
 
-    const googleKeys = ['gmail', 'google-calendar', 'google_calendar', 'googleCalendar'];
-    let changed = false;
+    // Map of MCP server keys to their CLI replacement description.
+    // These servers are superseded by native CLI commands and should not
+    // be launched by Claude Code. We MOVE them from mcpServers into the
+    // _disabled_mcpServers top-level key, which is Claude Code's native
+    // disable format (used by the /mcp toggle UI). This preserves the
+    // full config so the user can move it back to re-enable if needed.
+    const legacyServers = {
+      'claudia-memory':    'claudia memory CLI',
+      'claudia_memory':    'claudia memory CLI',
+      'gmail':             'claudia google login',
+      'google-calendar':   'claudia google login',
+      'google_calendar':   'claudia google login',
+      'googleCalendar':    'claudia google login',
+    };
 
-    for (const key of googleKeys) {
-      if (config.mcpServers[key] && !config.mcpServers[key]._disabled) {
-        config.mcpServers[key]._disabled = true;
-        config.mcpServers[key]._replaced_by = 'claudia google login';
+    let changed = false;
+    const disabled = [];
+
+    for (const [key, replacement] of Object.entries(legacyServers)) {
+      if (config.mcpServers[key]) {
+        // Ensure _disabled_mcpServers exists as a top-level sibling
+        if (!config._disabled_mcpServers) config._disabled_mcpServers = {};
+
+        // Preserve full server config, strip our old _disabled flag if present
+        const serverConfig = { ...config.mcpServers[key] };
+        delete serverConfig._disabled;
+        delete serverConfig._replaced_by;
+        serverConfig._replaced_by = replacement;
+        config._disabled_mcpServers[key] = serverConfig;
+
+        // Remove from active servers so Claude Code won't launch it
+        delete config.mcpServers[key];
         changed = true;
+        disabled.push(key);
       }
     }
 
     if (changed) {
       writeFileSync(mcpPath, JSON.stringify(config, null, 2) + '\n');
-      console.log(` ${colors.yellow}→${colors.reset} Disabled Gmail/Calendar MCP servers (replaced by ${colors.cyan}claudia google login${colors.reset})`);
+      console.log(` ${colors.yellow}→${colors.reset} Disabled legacy MCP: ${disabled.join(', ')} (moved to _disabled_mcpServers)`);
     }
   } catch {
     // Not valid JSON or can't read -- skip silently

package/package.json

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

package/template-v2/CLAUDE.md

@@ -214,17 +214,22 @@ What would you like to start with?
 
 ### 2. Relationships as Context
 
-People are my primary organizing unit. When someone is mentioned:
+People are my primary organizing unit. **When someone is mentioned, by name OR by relationship ("my wife", "my boss", "my client Sarah", "the investor"), I ALWAYS query memory first before asking the user.** I never ask for information I might already know.
 
-1. Check if I have context in `people/[name].md`
-2. Surface relevant history if it helps
-3. Offer to create a file if this person seems important
+Lookup order:
+1. `claudia memory recall "<name or relationship>" --project-dir "$PWD"` to resolve who they mean
+2. `claudia memory about "<entity name>" --project-dir "$PWD"` for full context (email, role, history)
+3. Check `people/[name].md` for additional context
+4. Only ask the user if memory returns nothing
+
+**The rule: search before asking.** If someone says "email my wife," I look up who their wife is and her email address. I don't ask "What's your wife's email?" when I might already have it.
 
 What I track about people:
 - Communication preferences and style
 - What matters to them
 - Your history with them
 - Current context (projects, concerns, opportunities)
+- Contact details (email, phone, handles)
 - Notes from past interactions
 
 ### 3. Commitment Tracking