agentvibes 3.0.0 → 3.2.0

package/src/installer.js

@@ -71,6 +71,27 @@ const packageJson = JSON.parse(
 );
 const VERSION = packageJson.version;
 
+/**
+ * Detect if running on Android/Termux environment
+ * @returns {boolean} True if running on Termux/Android
+ */
+function isTermux() {
+  return fsSync.existsSync('/data/data/com.termux');
+}
+
+/**
+ * Detect if running on Android/Termux and display message
+ * @returns {boolean} True if running on Termux/Android
+ */
+function detectAndNotifyTermux() {
+  if (isTermux()) {
+    console.log(chalk.green('\n📱 Android environment detected!'));
+    console.log(chalk.cyan('   Installing specialized libraries for Termux...\n'));
+    return true;
+  }
+  return false;
+}
+
 /**
  * Create header and footer for installer pages
  * @param {string} pageTitle - Title of current page
@@ -345,10 +366,23 @@ async function collectConfiguration(options = {}) {
     verbosity: 'high'
   };
 
+  // Detect Android/Termux environment
+  const isAndroid = isTermux();
+  if (isAndroid) {
+    detectAndNotifyTermux();
+  }
+
   if (options.yes) {
     // Non-interactive mode - use defaults
-    config.provider = process.platform === 'darwin' ? 'macos' : 'piper';
-    config.defaultVoice = process.platform === 'darwin' ? 'Samantha' : 'en_US-ryan-high';
+    // On Termux, always use piper (via proot-distro)
+    if (isAndroid) {
+      config.provider = 'piper';
+      config.defaultVoice = 'en_US-lessac-medium';
+      config.isTermux = true;
+    } else {
+      config.provider = process.platform === 'darwin' ? 'macos' : 'piper';
+      config.defaultVoice = process.platform === 'darwin' ? 'Samantha' : 'en_US-ryan-high';
+    }
     const homeDir = process.env.HOME || process.env.USERPROFILE;
     config.piperPath = path.join(homeDir, '.claude', 'piper-voices');
     return config;
@@ -901,19 +935,18 @@ function showWelcome() {
  * Shown during install and update commands
  */
 function getReleaseInfoBoxen() {
-  return chalk.cyan.bold('📦 AgentVibes v3.0.0 - Cross-Platform Remote Audio\n\n') +
+  return chalk.cyan.bold('📦 AgentVibes v3.2.0 - Clawdbot Integration\n\n') +
     chalk.green.bold('🎙️ WHAT\'S NEW:\n\n') +
-    chalk.cyan('AgentVibes v3.0.0 introduces the termux-ssh TTS provider, enabling true mobile-first\n') +
-    chalk.cyan('interactive conversations with Claude Code. Route TTS audio to your Android device via\n') +
-    chalk.cyan('SSH—whether coding locally on your laptop or on remote servers—and have hands-free,\n') +
-    chalk.cyan('voice-driven conversations with Claude using just your phone. Transforms how developers\n') +
-    chalk.cyan('interact with AI assistants.\n\n') +
+    chalk.cyan('AgentVibes v3.2.0 introduces seamless integration with Clawdbot, the revolutionary AI\n') +
+    chalk.cyan('assistant accessible via any instant messenger. With this release, Clawdbot users get\n') +
+    chalk.cyan('professional TTS with 50+ voices, remote SSH audio support for server deployments, and\n') +
+    chalk.cyan('zero-configuration setup—just install AgentVibes and the Clawdbot skill is ready.\n\n') +
     chalk.green.bold('✨ KEY HIGHLIGHTS:\n\n') +
-    chalk.gray('   📱 Mobile-First AI Conversations - Fully interactive conversations with Claude Code\n') +
-    chalk.gray('   💻 Local + Remote Development - Works for local coding and remote server development\n') +
-    chalk.gray('   🌐 Tailscale Integration - Internet-wide access without port forwarding\n') +
-    chalk.gray('   🎥 Demo Video - Watch it in action: https://youtu.be/ngLiA_KQtTA\n') +
-    chalk.gray('   🎯 Full MCP Compatibility - Complete integration with all MCP workflows\n\n') +
+    chalk.gray('   🤖 Clawdbot Integration - Native TTS support for Clawdbot AI assistant framework\n') +
+    chalk.gray('   💬 Messenger Platforms - Works with WhatsApp, Telegram, Discord via Clawdbot\n') +
+    chalk.gray('   🔊 Remote SSH Audio - Perfect for Clawdbot on remote servers with PulseAudio\n') +
+    chalk.gray('   📦 Simple Install - Just `npx agentvibes install` and it works\n') +
+    chalk.gray('   🛡️ SonarCloud Fixes - Quality gate workflow improvements and documentation\n\n') +
     chalk.gray('📖 Full Release Notes: RELEASE_NOTES.md\n') +
     chalk.gray('🌐 Website: https://agentvibes.org\n') +
     chalk.gray('📦 Repository: https://github.com/paulpreibisch/AgentVibes\n\n') +
@@ -2101,7 +2134,14 @@ async function checkAndInstallPiper(targetDir, options) {
       }
 
       if (installPiper) {
-        console.log(chalk.cyan('\n📦 Installing Piper TTS...\n'));
+        // Check if we're on Termux/Android
+        if (isTermux()) {
+          console.log(chalk.green('\n📱 Android environment detected!'));
+          console.log(chalk.cyan('📦 Installing Piper TTS with Termux-specific setup...\n'));
+          console.log(chalk.gray('   This will install proot-distro and set up Piper in a Debian environment.\n'));
+        } else {
+          console.log(chalk.cyan('\n📦 Installing Piper TTS...\n'));
+        }
         const piperInstallerPath = path.join(targetDir, '.claude', 'hooks', 'piper-installer.sh');
 
         try {
@@ -2114,13 +2154,19 @@ async function checkAndInstallPiper(targetDir, options) {
           console.log(chalk.yellow('\n⚠️  Piper installation failed or was cancelled'));
           console.log(chalk.gray('   You can install it later by running:'));
           console.log(chalk.cyan(`   ${piperInstallerPath}`));
-          console.log(chalk.gray('   Or manually: pipx install piper-tts\n'));
+          if (isTermux()) {
+            console.log(chalk.gray('   On Termux, this will use proot-distro for installation.\n'));
+          } else {
+            console.log(chalk.gray('   Or manually: pipx install piper-tts\n'));
+          }
         }
       } else {
         console.log(chalk.yellow('\n⚠️  Skipping Piper installation'));
         console.log(chalk.gray('   You can install it later by running:'));
         console.log(chalk.cyan(`   ${targetDir}/.claude/hooks/piper-installer.sh`));
-        console.log(chalk.gray('   Or manually: pipx install piper-tts\n'));
+        if (!isTermux()) {
+          console.log(chalk.gray('   Or manually: pipx install piper-tts\n'));
+        }
       }
     }
   } catch (error) {
@@ -3917,10 +3963,18 @@ program
     program.outputHelp();
   });
 
-program.parse(process.argv);
+/* c8 ignore start - CLI entry point, tested via subprocess */
+// Only run CLI if this file is being executed directly
+if (import.meta.url === `file://${process.argv[1]}`) {
+  program.parse(process.argv);
 
-// Show help if no command provided
-if (process.argv.slice(2).length === 0) {
-  showWelcome();
-  program.outputHelp();
+  // Show help if no command provided
+  if (process.argv.slice(2).length === 0) {
+    showWelcome();
+    program.outputHelp();
+  }
 }
+/* c8 ignore stop */
+
+// Export functions for testing
+export { isTermux, detectAndNotifyTermux };

package/.bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md

@@ -1,112 +0,0 @@
-# Brainstorm Project - Workflow Instructions
-
-```xml
-<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>Communicate all responses in {communication_language}</critical>
-<critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with project-specific context</critical>
-<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
-<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
-
-<workflow>
-
-  <step n="1" goal="Validate workflow readiness" tag="workflow-status">
-    <action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
-
-    <check if="status file not found">
-      <output>No workflow status file found. Brainstorming is optional - you can continue without status tracking.</output>
-      <action>Set standalone_mode = true</action>
-    </check>
-
-    <check if="status file found">
-      <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-      <action>Parse workflow_status section</action>
-      <action>Check status of "brainstorm-project" workflow</action>
-      <action>Get project_level from YAML metadata</action>
-      <action>Find first non-completed workflow (next expected workflow)</action>
-
-      <check if="brainstorm-project status is file path (already completed)">
-        <output>⚠️ Brainstorming session already completed: {{brainstorm-project status}}</output>
-        <ask>Re-running will create a new session. Continue? (y/n)</ask>
-        <check if="n">
-          <output>Exiting. Use workflow-status to see your next step.</output>
-          <action>Exit workflow</action>
-        </check>
-      </check>
-
-      <check if="brainstorm-project is not the next expected workflow (anything after brainstorm-project is completed already)">
-        <output>⚠️ Next expected workflow: {{next_workflow}}. Brainstorming is out of sequence.</output>
-        <ask>Continue with brainstorming anyway? (y/n)</ask>
-        <check if="n">
-          <output>Exiting. Run {{next_workflow}} instead.</output>
-          <action>Exit workflow</action>
-        </check>
-      </check>
-
-      <action>Set standalone_mode = false</action>
-    </check>
-  </step>
-
-  <step n="2" goal="Load project brainstorming context">
-    <action>Read the project context document from: {project_context}</action>
-    <action>This context provides project-specific guidance including:
-      - Focus areas for project ideation
-      - Key considerations for software/product projects
-      - Recommended techniques for project brainstorming
-      - Output structure guidance
-    </action>
-  </step>
-
-  <step n="3" goal="Invoke core brainstorming with project context">
-    <action>Execute the CIS brainstorming workflow with project context</action>
-    <invoke-workflow path="{core_brainstorming}" data="{project_context}">
-      The CIS brainstorming workflow will:
-      - Present interactive brainstorming techniques menu
-      - Guide the user through selected ideation methods
-      - Generate and capture brainstorming session results
-      - Save output to: {output_folder}/brainstorming-session-results-{{date}}.md
-    </invoke-workflow>
-  </step>
-
-  <step n="4" goal="Update status and complete" tag="workflow-status">
-    <check if="standalone_mode != true">
-      <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
-      <action>Find workflow_status key "brainstorm-project"</action>
-      <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
-      <action>Update workflow_status["brainstorm-project"] = "{output_folder}/bmm-brainstorming-session-{{date}}.md"</action>
-      <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-      <action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
-      <action>Determine next agent from path file based on next workflow</action>
-    </check>
-
-    <output>**✅ Brainstorming Session Complete, {user_name}!**
-
-**Session Results:**
-
-- Brainstorming results saved to: {output_folder}/bmm-brainstorming-session-{{date}}.md
-
-{{#if standalone_mode != true}}
-**Status Updated:**
-
-- Progress tracking updated
-
-**Next Steps:**
-
-- **Next required:** {{next_workflow}} ({{next_agent}} agent)
-- **Optional:** You can run other analysis workflows (research, product-brief) before proceeding
-
-Check status anytime with: `workflow-status`
-{{else}}
-**Next Steps:**
-
-Since no workflow is in progress:
-
-- Refer to the BMM workflow guide if unsure what to do next
-- Or run `workflow-init` to create a workflow path and get guided next steps
-{{/if}}
-    </output>
-  </step>
-
-</workflow>
-```

package/.bmad/bmm/workflows/1-analysis/brainstorm-project/project-context.md

@@ -1,25 +0,0 @@
-# Project Brainstorming Context
-
-This context guide provides project-specific considerations for brainstorming sessions focused on software and product development.
-
-## Session Focus Areas
-
-When brainstorming for projects, consider exploring:
-
-- **User Problems and Pain Points** - What challenges do users face?
-- **Feature Ideas and Capabilities** - What could the product do?
-- **Technical Approaches** - How might we build it?
-- **User Experience** - How will users interact with it?
-- **Business Model and Value** - How does it create value?
-- **Market Differentiation** - What makes it unique?
-- **Technical Risks and Challenges** - What could go wrong?
-- **Success Metrics** - How will we measure success?
-
-## Integration with Project Workflow
-
-Brainstorming sessions typically feed into:
-
-- **Product Briefs** - Initial product vision and strategy
-- **PRDs** - Detailed requirements documents
-- **Technical Specifications** - Architecture and implementation plans
-- **Research Activities** - Areas requiring further investigation

package/.bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml

@@ -1,26 +0,0 @@
-# Brainstorm Project Workflow Configuration
-name: "brainstorm-project"
-description: "Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/.bmad/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Module path and component files
-installed_path: "{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm-project"
-template: false
-instructions: "{installed_path}/instructions.md"
-
-# Context document for project brainstorming
-project_context: "{installed_path}/project-context.md"
-
-# CORE brainstorming workflow to invoke
-core_brainstorming: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml"
-
-standalone: true