vibecodingmachine-cli 2026.3.9-907 → 2026.3.10-1547

package/src/utils/agent-selector.js

@@ -1,50 +1,50 @@
-/**
- * Centralized agent selection logic
- * Respects provider preferences order and ensures DRY principle
- */
-
-const { getProviderPreferences } = require('./provider-registry');
-
-/**
- * Get the effective agent based on provider preferences and options
- * @param {Object} options - Command line options (may include ide)
- * @param {Array} providerDefinitions - Array of provider definitions
- * @param {Map} providerDefinitionMap - Map of provider definitions by ID
- * @returns {Object} - { effectiveAgent: string, providerDef: Object }
- */
-async function getEffectiveAgent(options = {}, providerDefinitions, providerDefinitionMap) {
-  const prefs = await getProviderPreferences();
-  
-  // Get all available providers in the order specified in preferences
-  const availableProviders = [];
-  for (const id of prefs.order) {
-    if (prefs.enabled[id] !== false && providerDefinitionMap.has(id)) {
-      availableProviders.push(id);
-    }
-  }
-  
-  // If no providers are available, use the first one from definitions as fallback
-  if (availableProviders.length === 0) {
-    availableProviders.push(providerDefinitions[0]?.id || 'claude-code');
-  }
-  
-  // Use the first available provider by default, unless overridden by options
-  let effectiveAgent = options.ide || availableProviders[0];
-  
-  // If the requested agent isn't available, use the first available one
-  if (!availableProviders.includes(effectiveAgent)) {
-    effectiveAgent = availableProviders[0];
-  }
-  
-  const providerDef = providerDefinitionMap.get(effectiveAgent);
-  
-  return {
-    effectiveAgent,
-    providerDef,
-    availableProviders
-  };
-}
-
-module.exports = {
-  getEffectiveAgent
-};
+/**
+ * Centralized agent selection logic
+ * Respects provider preferences order and ensures DRY principle
+ */
+
+const { getProviderPreferences } = require('./provider-registry');
+
+/**
+ * Get the effective agent based on provider preferences and options
+ * @param {Object} options - Command line options (may include ide)
+ * @param {Array} providerDefinitions - Array of provider definitions
+ * @param {Map} providerDefinitionMap - Map of provider definitions by ID
+ * @returns {Object} - { effectiveAgent: string, providerDef: Object }
+ */
+async function getEffectiveAgent(options = {}, providerDefinitions, providerDefinitionMap) {
+  const prefs = await getProviderPreferences();
+  
+  // Get all available providers in the order specified in preferences
+  const availableProviders = [];
+  for (const id of prefs.order) {
+    if (prefs.enabled[id] !== false && providerDefinitionMap.has(id)) {
+      availableProviders.push(id);
+    }
+  }
+  
+  // If no providers are available, use the first one from definitions as fallback
+  if (availableProviders.length === 0) {
+    availableProviders.push(providerDefinitions[0]?.id || 'claude-code');
+  }
+  
+  // Use the first available provider by default, unless overridden by options
+  let effectiveAgent = options.ide || availableProviders[0];
+  
+  // If the requested agent isn't available, use the first available one
+  if (!availableProviders.includes(effectiveAgent)) {
+    effectiveAgent = availableProviders[0];
+  }
+  
+  const providerDef = providerDefinitionMap.get(effectiveAgent);
+  
+  return {
+    effectiveAgent,
+    providerDef,
+    availableProviders
+  };
+}
+
+module.exports = {
+  getEffectiveAgent
+};

package/src/utils/asset-cleanup.js

@@ -1,60 +1,60 @@
-const fs = require('fs-extra');
-const path = require('path');
-
-/**
- * Scans the assets directory and removes 0-byte PNG files
- * This is a mitigation for an issue where empty PNG files are mysteriously created
- */
-async function cleanupBrokenAssets() {
-    try {
-        // Find assets directory - assuming we are in packages/cli/src/utils
-        // and assets is at root of repo, but simpler to look relative to where VCM runs
-        // effectively, we look for 'assets' in the current working directory as CWD is usually the repo root or where the CLI is run
-        // Better: define path relative to the project root if possible, or CWD if that's how it's structured.
-        // Based on previous search, assets/ is at the root of the repo.
-        // However, when installed, strict paths matters.
-        // But for the user's workspace context, iterating 'assets/' in CWD (repo root) is correct for their dev environment.
-        // Let's try to be smart about finding specific 'assets' dir if we can, but CWD is a safe start for the CLI tool which is often run from root.
-
-        // Actually, looking at previous grep, `assets/` was checked specifically. 
-        // Let's just check `assets` in process.cwd() as a primary target.
-
-        const assetsDir = path.join(process.cwd(), 'assets');
-
-        if (!await fs.pathExists(assetsDir)) {
-            return; // No assets dir, nothing to clean
-        }
-
-        const files = await fs.readdir(assetsDir);
-        let removedCount = 0;
-
-        for (const file of files) {
-            if (file.toLowerCase().endsWith('.png')) {
-                const filePath = path.join(assetsDir, file);
-                try {
-                    const stats = await fs.stat(filePath);
-                    if (stats.size === 0) {
-                        await fs.remove(filePath);
-                        removedCount++;
-                    }
-                } catch (err) {
-                    // Ignore errors accessing specific files
-                }
-            }
-        }
-
-        if (removedCount > 0) {
-            // Only log if we actually did something, to keep noise down
-            // But maybe we want to know? The plan said "verification: verify removed".
-            // We can use a debug flag or just log.
-            // Let's log to console for now as it's a CLI tool.
-            // console.log(chalk.gray(`Cleaned up ${removedCount} broken (0-byte) asset files.`));
-        }
-
-    } catch (error) {
-        // Silently fail to avoid disrupting startup
-        // console.error('Asset cleanup failed:', error);
-    }
-}
-
-module.exports = { cleanupBrokenAssets };
+const fs = require('fs-extra');
+const path = require('path');
+
+/**
+ * Scans the assets directory and removes 0-byte PNG files
+ * This is a mitigation for an issue where empty PNG files are mysteriously created
+ */
+async function cleanupBrokenAssets() {
+    try {
+        // Find assets directory - assuming we are in packages/cli/src/utils
+        // and assets is at root of repo, but simpler to look relative to where VCM runs
+        // effectively, we look for 'assets' in the current working directory as CWD is usually the repo root or where the CLI is run
+        // Better: define path relative to the project root if possible, or CWD if that's how it's structured.
+        // Based on previous search, assets/ is at the root of the repo.
+        // However, when installed, strict paths matters.
+        // But for the user's workspace context, iterating 'assets/' in CWD (repo root) is correct for their dev environment.
+        // Let's try to be smart about finding specific 'assets' dir if we can, but CWD is a safe start for the CLI tool which is often run from root.
+
+        // Actually, looking at previous grep, `assets/` was checked specifically. 
+        // Let's just check `assets` in process.cwd() as a primary target.
+
+        const assetsDir = path.join(process.cwd(), 'assets');
+
+        if (!await fs.pathExists(assetsDir)) {
+            return; // No assets dir, nothing to clean
+        }
+
+        const files = await fs.readdir(assetsDir);
+        let removedCount = 0;
+
+        for (const file of files) {
+            if (file.toLowerCase().endsWith('.png')) {
+                const filePath = path.join(assetsDir, file);
+                try {
+                    const stats = await fs.stat(filePath);
+                    if (stats.size === 0) {
+                        await fs.remove(filePath);
+                        removedCount++;
+                    }
+                } catch (err) {
+                    // Ignore errors accessing specific files
+                }
+            }
+        }
+
+        if (removedCount > 0) {
+            // Only log if we actually did something, to keep noise down
+            // But maybe we want to know? The plan said "verification: verify removed".
+            // We can use a debug flag or just log.
+            // Let's log to console for now as it's a CLI tool.
+            // console.log(chalk.gray(`Cleaned up ${removedCount} broken (0-byte) asset files.`));
+        }
+
+    } catch (error) {
+        // Silently fail to avoid disrupting startup
+        // console.error('Asset cleanup failed:', error);
+    }
+}
+
+module.exports = { cleanupBrokenAssets };

package/src/utils/auth.js

@@ -20,6 +20,12 @@ function generateCodeChallenge(verifier) { return crypto.createHash('sha256').up
 
 class CLIAuth {
   async isAuthenticated() {
+    // Check for IDE checking bypass flag
+    if (process.env.VCM_SKIP_AUTH === 'true') {
+      console.log('🔓 Authentication bypassed for IDE checking');
+      return true;
+    }
+    
     const isValid = await sharedAuth.isAuthenticated();
     if (isValid) {
       await this._updateUserActivity();