agentvibes 3.0.0 → 3.2.0

package/.claude/commands/bmad/bmm/workflows/{create-wireframe.md → create-excalidraw-wireframe.md}

@@ -6,8 +6,8 @@ IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the c
 
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/frame-expert/create-wireframe/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/frame-expert/create-wireframe/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/.claude/commands/bmad/bmm/workflows/create-prd.md

@@ -0,0 +1,5 @@
+---
+description: 'Creates a comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/2-plan-workflows/prd/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/commands/bmad/bmm/workflows/create-product-brief.md

@@ -0,0 +1,5 @@
+---
+description: 'Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/1-analysis/product-brief/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/commands/bmad/bmm/workflows/create-story.md

@@ -1,5 +1,5 @@
 ---
-description: 'Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder'
+description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:

package/.claude/commands/bmad/bmm/workflows/create-tech-spec.md

@@ -0,0 +1,13 @@
+---
+description: 'Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/bmm/workflows/create-ux-design.md

@@ -1,13 +1,5 @@
 ---
-description: 'Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step.'
+description: 'Work with a peer UX Design expert to plan your applications UX patterns, look and feel.'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/commands/bmad/bmm/workflows/generate-project-context.md

@@ -0,0 +1,5 @@
+---
+description: 'Creates a concise project_context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/commands/bmad/bmm/workflows/{domain-research.md → quick-dev.md}

@@ -1,13 +1,13 @@
 ---
-description: 'Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects'
+description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/1-analysis/domain-research/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/1-analysis/domain-research/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/.claude/commands/bmad/bmm/workflows/research.md

@@ -1,13 +1,5 @@
 ---
-description: 'Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis'
+description: 'Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/1-analysis/research/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/1-analysis/research/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/1-analysis/research/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/commands/bmad/bmm/workflows/{story-context.md → sprint-status.md}

@@ -1,13 +1,13 @@
 ---
-description: 'Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story'
+description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/story-context/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/4-implementation/story-context/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/.claude/commands/bmad/bmm/workflows/testarch-atdd.md

@@ -0,0 +1,13 @@
+---
+description: 'Generate failing acceptance tests before implementation using TDD red-green-refactor cycle'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/atdd/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/atdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/bmm/workflows/testarch-automate.md

@@ -0,0 +1,13 @@
+---
+description: 'Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/automate/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/bmm/workflows/testarch-ci.md

@@ -0,0 +1,13 @@
+---
+description: 'Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/ci/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/ci/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/bmm/workflows/testarch-framework.md

@@ -0,0 +1,13 @@
+---
+description: 'Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/framework/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/bmm/workflows/testarch-nfr.md

@@ -0,0 +1,13 @@
+---
+description: 'Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/bmm/workflows/{prd.md → testarch-test-design.md}

@@ -1,13 +1,13 @@
 ---
-description: 'Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow.'
+description: 'Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/test-design/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/.claude/commands/bmad/bmm/workflows/testarch-test-review.md

@@ -0,0 +1,13 @@
+---
+description: 'Review test quality using comprehensive knowledge base and best practices validation'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/test-review/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/bmm/workflows/testarch-trace.md

@@ -0,0 +1,13 @@
+---
+description: 'Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/trace/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/trace/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/core/workflows/brainstorming-session.md

@@ -0,0 +1,5 @@
+---
+description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/config/tts-speech-rate.txt

@@ -0,0 +1 @@
+1.3

package/.claude/github-star-reminder.txt

@@ -1 +1 @@
-20260108
+20260127

package/.claude/hooks/audio-processor.sh

@@ -306,13 +306,22 @@ main() {
     IFS='|' read -r _ sox_effects background_file bg_volume <<< "$config"
 
     # Temporary files (using explicit paths to avoid unbound variable issues)
+    # Use Termux-compatible temp directory if on Termux, otherwise standard /tmp
+    local TEMP_DIR
+    if [[ -d "/data/data/com.termux" ]]; then
+        # On Termux
+        TEMP_DIR="${TMPDIR:-${PREFIX}/tmp}"
+    else
+        # Standard Linux/macOS
+        TEMP_DIR="${TMPDIR:-/tmp}"
+    fi
     local temp_effects
     local temp_final
-    temp_effects="/tmp/agentvibes-effects-$$.wav"
-    temp_final="/tmp/agentvibes-final-$$.wav"
+    temp_effects="$TEMP_DIR/agentvibes-effects-$$.wav"
+    temp_final="$TEMP_DIR/agentvibes-final-$$.wav"
 
     # Clean up on exit using explicit paths
-    trap 'rm -f /tmp/agentvibes-effects-'"$$"'.wav /tmp/agentvibes-final-'"$$"'.wav' EXIT
+    trap 'rm -f "'"$TEMP_DIR"'/agentvibes-effects-'"$$"'.wav" "'"$TEMP_DIR"'/agentvibes-final-'"$$"'.wav"' EXIT
 
     # Step 1: Apply sox effects
     if [[ -n "$sox_effects" ]]; then

package/.claude/hooks/piper-installer.sh

@@ -58,6 +58,23 @@ echo ""
 PLATFORM="$(uname -s)"
 ARCH="$(uname -m)"
 
+# Check if running on Termux/Android first
+if [[ -d "/data/data/com.termux" ]]; then
+  echo "📱 Detected Termux/Android"
+  echo ""
+  echo "   Termux requires a special installation process using proot-distro."
+  echo "   Running Termux-specific installer..."
+  echo ""
+  SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+  if [[ -f "$SCRIPT_DIR/termux-installer.sh" ]]; then
+    exec "$SCRIPT_DIR/termux-installer.sh" "$@"
+  else
+    echo "❌ Error: termux-installer.sh not found"
+    echo "   Please download it from the AgentVibes repository"
+    exit 1
+  fi
+fi
+
 # Check if running on macOS, WSL, or Linux
 if [[ "$PLATFORM" == "Darwin" ]]; then
   IS_MACOS=true

package/.claude/hooks/play-tts-piper.sh

@@ -400,6 +400,10 @@ if [[ "${AGENTVIBES_TEST_MODE:-false}" != "true" ]] && [[ "${AGENTVIBES_NO_PLAYB
     # macOS: Use afplay (native macOS audio player)
     afplay "$TEMP_FILE" >/dev/null 2>&1 &
     PLAYER_PID=$!
+  elif [[ -n "${TERMUX_VERSION:-}" ]] || [[ -d "/data/data/com.termux" ]]; then
+    # Android/Termux: Use termux-media-player
+    termux-media-player play "$TEMP_FILE" >/dev/null 2>&1 &
+    PLAYER_PID=$!
   else
     # Linux/WSL: Prefer paplay (PulseAudio) for best WSL audio quality
     (paplay "$TEMP_FILE" || mpv "$TEMP_FILE" || aplay "$TEMP_FILE") >/dev/null 2>&1 &

package/.claude/hooks/termux-installer.sh

@@ -0,0 +1,224 @@
+#!/bin/bash
+#
+# AgentVibes Termux/Android Installer
+# Installs Piper TTS and dependencies for Android/Termux
+#
+# Usage: ./termux-installer.sh [--non-interactive]
+#
+# Requirements:
+#   - Termux app installed
+#   - termux-api package (for audio playback)
+#
+
+set -euo pipefail
+
+# Colors
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+NC='\033[0m' # No Color
+
+# Parse arguments
+NON_INTERACTIVE=false
+if [[ "$1" == "--non-interactive" ]]; then
+    NON_INTERACTIVE=true
+fi
+
+echo -e "${BLUE}"
+echo "╔════════════════════════════════════════════════════════════╗"
+echo "║     AgentVibes Termux/Android Installer                    ║"
+echo "║     TTS with Personality for AI Assistants                 ║"
+echo "╚════════════════════════════════════════════════════════════╝"
+echo -e "${NC}"
+
+# Detect if running on Termux
+if [[ ! -d "/data/data/com.termux" ]]; then
+    echo -e "${RED}Error: This installer is for Termux on Android only${NC}"
+    echo "For other platforms, use the standard installer."
+    exit 1
+fi
+
+echo -e "${GREEN}✓ Detected Termux environment${NC}"
+echo ""
+
+# Step 1: Update packages and install dependencies
+echo -e "${BLUE}[1/6] Installing system dependencies...${NC}"
+
+pkg update -y 2>/dev/null || true
+
+DEPS="proot-distro ffmpeg sox bc termux-api curl"
+for dep in $DEPS; do
+    if ! command -v "$dep" &> /dev/null && ! pkg list-installed 2>/dev/null | grep -q "^$dep/"; then
+        echo "  Installing $dep..."
+        pkg install -y "$dep" 2>/dev/null || echo "  Warning: Failed to install $dep"
+    else
+        echo -e "  ${GREEN}✓${NC} $dep already installed"
+    fi
+done
+
+echo ""
+
+# Step 2: Install proot-distro Debian
+echo -e "${BLUE}[2/6] Setting up proot-distro Debian...${NC}"
+
+if proot-distro list 2>/dev/null | grep -q "debian.*installed"; then
+    echo -e "  ${GREEN}✓${NC} Debian already installed in proot-distro"
+else
+    echo "  Installing Debian (this may take a few minutes)..."
+    proot-distro install debian 2>/dev/null || {
+        # Check if it's already installed despite error
+        if proot-distro list 2>/dev/null | grep -q "debian"; then
+            echo -e "  ${GREEN}✓${NC} Debian is available"
+        else
+            echo -e "${RED}  Error: Failed to install Debian${NC}"
+            exit 1
+        fi
+    }
+fi
+
+echo ""
+
+# Step 3: Download Piper binary inside Debian
+echo -e "${BLUE}[3/6] Installing Piper TTS in Debian proot...${NC}"
+
+PIPER_CHECK=$(proot-distro login debian -- ls /root/piper/piper 2>/dev/null || echo "not found")
+if [[ "$PIPER_CHECK" != "not found" ]]; then
+    echo -e "  ${GREEN}✓${NC} Piper binary already installed"
+else
+    echo "  Downloading Piper TTS binary..."
+    proot-distro login debian -- bash -c "
+        mkdir -p /root/piper /root/piper-voices
+        cd /root
+        curl -L -o piper.tar.gz 'https://github.com/rhasspy/piper/releases/download/2023.11.14-2/piper_linux_aarch64.tar.gz'
+        tar -xzf piper.tar.gz
+        rm piper.tar.gz
+        echo 'Piper installed successfully'
+    " 2>/dev/null || echo -e "${YELLOW}  Warning: Piper download may have issues${NC}"
+fi
+
+# Verify piper works
+PIPER_TEST=$(proot-distro login debian -- /root/piper/piper --help 2>/dev/null | head -1 || echo "failed")
+if [[ "$PIPER_TEST" == *"usage"* ]]; then
+    echo -e "  ${GREEN}✓${NC} Piper binary verified"
+else
+    echo -e "${YELLOW}  Warning: Piper verification failed, but may still work${NC}"
+fi
+
+echo ""
+
+# Step 4: Download voice model
+echo -e "${BLUE}[4/6] Downloading voice model...${NC}"
+
+VOICE_MODEL="en_US-lessac-medium"
+VOICES_DIR="$HOME/.claude/piper-voices"
+mkdir -p "$VOICES_DIR"
+
+if [[ -f "$VOICES_DIR/${VOICE_MODEL}.onnx" ]]; then
+    echo -e "  ${GREEN}✓${NC} Voice model already downloaded"
+else
+    echo "  Downloading ${VOICE_MODEL} (~63MB)..."
+
+    # Download to Termux location (accessible from both Termux and proot)
+    curl -L -o "$VOICES_DIR/${VOICE_MODEL}.onnx" \
+        "https://huggingface.co/rhasspy/piper-voices/resolve/main/en/en_US/lessac/medium/en_US-lessac-medium.onnx" \
+        2>/dev/null || echo -e "${YELLOW}  Warning: Voice download may have failed${NC}"
+
+    curl -L -o "$VOICES_DIR/${VOICE_MODEL}.onnx.json" \
+        "https://huggingface.co/rhasspy/piper-voices/resolve/main/en/en_US/lessac/medium/en_US-lessac-medium.onnx.json" \
+        2>/dev/null || true
+
+    if [[ -f "$VOICES_DIR/${VOICE_MODEL}.onnx" ]]; then
+        echo -e "  ${GREEN}✓${NC} Voice model downloaded"
+    fi
+fi
+
+echo ""
+
+# Step 5: Create piper wrapper script
+echo -e "${BLUE}[5/6] Creating Piper wrapper for Termux...${NC}"
+
+WRAPPER_PATH="/data/data/com.termux/files/usr/bin/piper"
+
+cat > "$WRAPPER_PATH" << 'WRAPPER_EOF'
+#!/bin/bash
+#
+# Piper TTS wrapper for Termux
+# Runs piper through proot-distro Debian
+#
+
+PIPER_DIR="/root/piper"
+
+# Build the piper command with proper quoting
+PIPER_CMD="cd $PIPER_DIR && LD_LIBRARY_PATH=. ./piper"
+
+# Add all arguments
+for arg in "$@"; do
+    PIPER_CMD="$PIPER_CMD \"$arg\""
+done
+
+# Run piper, filtering only the proot warning
+if [ -t 0 ]; then
+    # No stdin
+    proot-distro login debian -- bash -c "$PIPER_CMD" 2>&1 | grep -v "proot warning"
+else
+    # With stdin - need to pass it through
+    cat | proot-distro login debian -- bash -c "$PIPER_CMD" 2>&1 | grep -v "proot warning"
+fi
+WRAPPER_EOF
+
+chmod +x "$WRAPPER_PATH"
+echo -e "  ${GREEN}✓${NC} Piper wrapper created at $WRAPPER_PATH"
+
+echo ""
+
+# Step 6: Apply Termux-specific fixes
+echo -e "${BLUE}[6/6] Applying Termux-specific fixes...${NC}"
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+# Fix audio-processor.sh to use Termux temp directory
+AUDIO_PROCESSOR="$SCRIPT_DIR/audio-processor.sh"
+if [[ -f "$AUDIO_PROCESSOR" ]]; then
+    if grep -q 'temp_effects="/tmp/' "$AUDIO_PROCESSOR"; then
+        echo "  Patching audio-processor.sh for Termux temp directory..."
+        sed -i 's|temp_effects="/tmp/|temp_effects="${TMPDIR:-/data/data/com.termux/files/usr/tmp}/|g' "$AUDIO_PROCESSOR"
+        sed -i 's|temp_final="/tmp/|temp_final="${TMPDIR:-/data/data/com.termux/files/usr/tmp}/|g' "$AUDIO_PROCESSOR"
+        sed -i "s|trap 'rm -f /tmp/|trap 'rm -f \"\${TMPDIR:-/data/data/com.termux/files/usr/tmp}/|g" "$AUDIO_PROCESSOR"
+        echo -e "  ${GREEN}✓${NC} audio-processor.sh patched"
+    else
+        echo -e "  ${GREEN}✓${NC} audio-processor.sh already patched"
+    fi
+fi
+
+# Set default voice
+CLAUDE_DIR="$HOME/.claude"
+mkdir -p "$CLAUDE_DIR"
+if [[ ! -f "$CLAUDE_DIR/tts-voice.txt" ]]; then
+    echo "$VOICE_MODEL" > "$CLAUDE_DIR/tts-voice.txt"
+    echo -e "  ${GREEN}✓${NC} Default voice set to $VOICE_MODEL"
+fi
+
+# Set provider to piper
+if [[ ! -f "$CLAUDE_DIR/tts-provider.txt" ]]; then
+    echo "piper" > "$CLAUDE_DIR/tts-provider.txt"
+    echo -e "  ${GREEN}✓${NC} TTS provider set to piper"
+fi
+
+echo ""
+echo -e "${GREEN}════════════════════════════════════════════════════════════${NC}"
+echo -e "${GREEN}  Installation Complete!${NC}"
+echo -e "${GREEN}════════════════════════════════════════════════════════════${NC}"
+echo ""
+echo "  To test TTS:"
+echo "    echo 'Hello world' | piper -m ~/.claude/piper-voices/en_US-lessac-medium.onnx -f ~/test.wav"
+echo "    termux-media-player play ~/test.wav"
+echo ""
+echo "  To enable background music:"
+echo "    .claude/hooks/background-music-manager.sh on"
+echo ""
+echo "  Available background tracks:"
+echo "    .claude/hooks/background-music-manager.sh list"
+echo ""
+echo -e "${BLUE}Enjoy AgentVibes on Android! 🎤${NC}"
+echo ""