ai-lens 0.8.111 → 0.8.112

package/.commithash

@@ -1 +1 @@
-c982dc2
+1411e25

package/CHANGELOG.md

@@ -2,6 +2,9 @@
 
 History of changes to the `ai-lens` CLI package on npm. New entries go on top. Format: `## X.Y.Z — YYYY-MM-DD`, followed by user-facing bullets.
 
+## 0.8.112 — 2026-06-23
+- feat: re-running `init --yes` no longer changes your MCP registration. On an already-set-up install it's left exactly as-is — if MCP is registered it stays (same scope), if it isn't it's left off — instead of being removed-and-re-added at user scope (which could migrate its scope, force it on, or drop it if the re-add failed). Fresh installs still register MCP; use `init --mcp-only` to deliberately (re)register.
+
 ## 0.8.111 — 2026-06-23
 - fix(status): case-fold project-filter-mismatch buckets on Windows
 - fix(client): tolerate Cursor Windows mojibake paths in project_filter

package/cli/init.js

@@ -66,6 +66,24 @@ export function importMode(flags = {}) {
   return 'prompt';                         // interactive: ask
 }
 
+// How the FULL init flow should handle the MCP registration. Returns:
+//   'skip'     — never touch MCP (today's --no-mcp behavior; existing reg left intact)
+//   'preserve' — existing install under --yes: leave MCP exactly as-is (no add/remove/migrate)
+//   'setup'    — fresh install under --yes, or interactive: register (onboarding / prompt)
+//
+// On an EXISTING install under --yes, MCP is ALWAYS preserved — neither --project-hooks
+// nor --mcp-scope re-registers it. This stops `setupMcpServers` (which removes at all
+// scopes then re-adds at one) from migrating an existing local/project registration to
+// `user`, force-adding MCP for someone who never had it, or leaving MCP removed-but-not-
+// re-added when the `claude mcp add` fails. The only explicit (re)register path is the
+// separate `--mcp-only` branch, which never reaches this gate.
+// "Existing install" = a prior auth token in config (read before this run authenticates).
+export function mcpSetupAction({ noMcp, auto, hasToken } = {}) {
+  if (noMcp) return 'skip';
+  if (auto && hasToken) return 'preserve';
+  return 'setup';
+}
+
 function getJson(url) {
   return new Promise((resolve, reject) => {
     const parsed = new URL(url);
@@ -1305,14 +1323,23 @@ export default async function init() {
   // --project-hooks installs hooks at project scope, so mirror that for the MCP:
   // default the scope to local and target the project .cursor/mcp.json (an explicit
   // --mcp-scope still wins; setupMcpServers maps scope → Cursor target).
-  if (!flags.noMcp) {
+  const mcpAction = mcpSetupAction({
+    noMcp: flags.noMcp,
+    auto,
+    hasToken: Boolean(currentConfig.authToken),
+  });
+  if (mcpAction === 'setup') {
     await setupMcpServers(serverUrl, {
       auto,
       mcpScope: flags.mcpScope,
       forcedScope: (flags.projectHooks && !flags.mcpScope) ? 'local' : null,
       projectRoot: flags.projectHooks ? resolve(process.cwd()) : null,
     });
+  } else if (mcpAction === 'preserve') {
+    // Existing install under --yes: leave the current MCP registration untouched.
+    info('  MCP: сохранён как есть (для (пере)регистрации — npx -y ai-lens init --mcp-only)');
   }
+  // 'skip' (--no-mcp) → do nothing; an existing registration is left intact.
 
   // Quick verification
   heading('Verification');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-lens",
-  "version": "0.8.111",
+  "version": "0.8.112",
   "type": "module",
   "description": "Centralized session analytics for AI coding tools",
   "bin": {