agentvibes 5.11.2 → 5.12.0-alpha.0

package/.agentvibes/config.json

@@ -1,17 +1,3 @@
 {
-  "setupCompleted": true,
-  "thumbsUp": [
-    "en_US-libritts-high::Oscar-9",
-    "en_US-libritts-high::Adam-10"
-  ],
-  "favorites": [
-    "en_US-libritts-high::Oscar-9",
-    "en_US-libritts-high::Adam-10"
-  ],
-  "backgroundMusic": {
-    "enabled": false
-  },
-  "ttsEngine": "elevenlabs",
-  "language": "en",
-  "voice": "en_US-libritts-high::Adam-12"
+  "setupCompleted": true
 }

package/.claude/activation-instructions

@@ -1,54 +1,54 @@
-# BMAD Agent Activation Instructions
-
-When a BMAD agent activates, follow these steps EXACTLY:
-
-## STEP 3.5a: Create BMAD Context File (CRITICAL)
-
-**IMMEDIATELY after agent identification, create the context file:**
-
-```bash
-echo "$AGENT_ID" > .bmad-agent-context
-```
-
-Where `$AGENT_ID` is one of:
-- `pm` (Product Manager)
-- `dev` (Developer)
-- `qa` (QA)
-- `architect` (Architect)
-- `po` (Product Owner)
-- `analyst` (Analyst)
-- `sm` (Scrum Master)
-- `ux-expert` (UX Expert)
-- `bmad-master` (BMAD Master)
-- `bmad-orchestrator` (Orchestrator)
-
-**Example:**
-```bash
-# For Product Manager agent
-echo "pm" > .bmad-agent-context
-```
-
-This file allows AgentVibes to:
-1. Detect which BMAD agent is active
-2. Look up the correct voice mapping
-3. Automatically speak questions using the agent's assigned voice
-
-## STEP 10: Clean Up on Exit
-
-**Before exiting the agent, remove the context file:**
-
-```bash
-rm -f .bmad-agent-context
-```
-
-This ensures voice switching only happens when an agent is active.
-
-## Why This Matters
-
-Without the `.bmad-agent-context` file:
-- AgentVibes cannot detect which agent is active
-- Questions won't be spoken automatically
-- Voice switching won't work
-- The BMAD voice plugin becomes non-functional
-
-**This is MANDATORY for BMAD voice integration to work!**
+# BMAD Agent Activation Instructions
+
+When a BMAD agent activates, follow these steps EXACTLY:
+
+## STEP 3.5a: Create BMAD Context File (CRITICAL)
+
+**IMMEDIATELY after agent identification, create the context file:**
+
+```bash
+echo "$AGENT_ID" > .bmad-agent-context
+```
+
+Where `$AGENT_ID` is one of:
+- `pm` (Product Manager)
+- `dev` (Developer)
+- `qa` (QA)
+- `architect` (Architect)
+- `po` (Product Owner)
+- `analyst` (Analyst)
+- `sm` (Scrum Master)
+- `ux-expert` (UX Expert)
+- `bmad-master` (BMAD Master)
+- `bmad-orchestrator` (Orchestrator)
+
+**Example:**
+```bash
+# For Product Manager agent
+echo "pm" > .bmad-agent-context
+```
+
+This file allows AgentVibes to:
+1. Detect which BMAD agent is active
+2. Look up the correct voice mapping
+3. Automatically speak questions using the agent's assigned voice
+
+## STEP 10: Clean Up on Exit
+
+**Before exiting the agent, remove the context file:**
+
+```bash
+rm -f .bmad-agent-context
+```
+
+This ensures voice switching only happens when an agent is active.
+
+## Why This Matters
+
+Without the `.bmad-agent-context` file:
+- AgentVibes cannot detect which agent is active
+- Questions won't be spoken automatically
+- Voice switching won't work
+- The BMAD voice plugin becomes non-functional
+
+**This is MANDATORY for BMAD voice integration to work!**

package/.claude/commands/agent-vibes-bmad-voices.md

@@ -1,117 +1,117 @@
----
-command: agent-vibes:bmad-party
-description: Control BMAD party mode voice integration (enable/disable/status)
-handler: bash .claude/hooks/bmad-party-manager.sh
----
-
-Enable or disable BMAD party mode voice integration where each agent speaks with their unique voice during multi-agent conversations.
-
-## Usage
-
-- `/agent-vibes:bmad-party` - Show current status
-- `/agent-vibes:bmad-party status` - Show current status
-- `/agent-vibes:bmad-party enable` - Enable party mode voices
-- `/agent-vibes:bmad-party disable` - Disable party mode voices
-
-## What is Party Mode Voice Integration?
-
-When BMAD's party mode (`/bmad:core:workflows:party-mode`) is active, multiple agents collaborate on your questions. With this feature enabled, each agent speaks their responses with their unique assigned voice:
-
-- **Winston (Architect)** speaks with Michael's voice
-- **John (PM)** speaks with Jessica Anne Bogart's voice
-- **Amelia (Dev)** speaks with Matthew Schmitz's voice
-- And so on...
-
-## Auto-Enable Behavior
-
-**This feature is automatically enabled when:**
-1. BMAD v6 is installed (`.bmad/_cfg/agent-manifest.csv` exists)
-2. AgentVibes BMAD voice plugin is enabled
-
-**No manual configuration needed!** Just run party mode and each agent will speak with their voice.
-
-## How to Disable
-
-If you prefer party mode without voice switching:
-
-```bash
-/agent-vibes:bmad-party disable
-```
-
-This creates `.agentvibes/bmad/bmad-party-mode-disabled.flag` to opt-out.
-
-## How It Works
-
-The integration detects agent responses in the format:
-
-```
-[Agent Name]: Their dialogue here
-```
-
-When detected, it:
-1. Extracts the agent's display name (e.g., "Winston", "John")
-2. Maps it to their agent ID using `.bmad/_cfg/agent-manifest.csv`
-3. Looks up their voice from `.agentvibes/bmad/bmad-voices.md`
-4. Speaks their dialogue with that specific voice
-
-## Example
-
-**Before (silent text):**
-```
-[Winston]: I recommend microservices for scalability
-[John]: But monolith is faster to market for MVP
-[Amelia]: I can implement either approach
-```
-
-**After (with voices):**
-```
-[Winston speaks with Michael voice]: I recommend microservices for scalability
-[John speaks with Jessica Anne Bogart voice]: But monolith is faster to market for MVP
-[Amelia speaks with Matthew Schmitz voice]: I can implement either approach
-```
-
-## Voice Mappings
-
-See current agent-to-voice mappings:
-```bash
-/agent-vibes:bmad status
-```
-
-Edit voice assignments in:
-```
-.agentvibes/bmad/bmad-voices.md
-```
-
-## Requirements
-
-- BMAD v6-alpha or later
-- AgentVibes with BMAD plugin enabled
-- Piper or Piper TTS TTS provider configured
-
-## Troubleshooting
-
-**Party mode voices not working?**
-
-1. Check BMAD is installed: `ls .bmad/_cfg/agent-manifest.csv`
-2. Check voice plugin enabled: `ls .agentvibes/bmad/bmad-voices-enabled.flag`
-3. Check party mode not disabled: `ls .agentvibes/bmad/bmad-party-mode-disabled.flag`
-4. View status: `/agent-vibes:bmad-party status`
-
-**Wrong voices playing?**
-
-Check voice mappings: `/agent-vibes:bmad status`
-
-Edit mappings in: `.claude/config/bmad-voices.md`
-
-## Related Commands
-
-- `/bmad:core:workflows:party-mode` - Start BMAD party mode
-- `/agent-vibes:bmad` - Manage BMAD voice plugin
-- `/agent-vibes:switch` - Change your default voice
-- `/agent-vibes:provider` - Switch TTS provider
-
----
-
-**Implementation:** Issue #33
-**Auto-enabled:** Yes (for BMAD users)
-**Opt-out:** Available via disable command
+---
+command: agent-vibes:bmad-party
+description: Control BMAD party mode voice integration (enable/disable/status)
+handler: bash .claude/hooks/bmad-party-manager.sh
+---
+
+Enable or disable BMAD party mode voice integration where each agent speaks with their unique voice during multi-agent conversations.
+
+## Usage
+
+- `/agent-vibes:bmad-party` - Show current status
+- `/agent-vibes:bmad-party status` - Show current status
+- `/agent-vibes:bmad-party enable` - Enable party mode voices
+- `/agent-vibes:bmad-party disable` - Disable party mode voices
+
+## What is Party Mode Voice Integration?
+
+When BMAD's party mode (`/bmad:core:workflows:party-mode`) is active, multiple agents collaborate on your questions. With this feature enabled, each agent speaks their responses with their unique assigned voice:
+
+- **Winston (Architect)** speaks with Michael's voice
+- **John (PM)** speaks with Jessica Anne Bogart's voice
+- **Amelia (Dev)** speaks with Matthew Schmitz's voice
+- And so on...
+
+## Auto-Enable Behavior
+
+**This feature is automatically enabled when:**
+1. BMAD v6 is installed (`.bmad/_cfg/agent-manifest.csv` exists)
+2. AgentVibes BMAD voice plugin is enabled
+
+**No manual configuration needed!** Just run party mode and each agent will speak with their voice.
+
+## How to Disable
+
+If you prefer party mode without voice switching:
+
+```bash
+/agent-vibes:bmad-party disable
+```
+
+This creates `.agentvibes/bmad/bmad-party-mode-disabled.flag` to opt-out.
+
+## How It Works
+
+The integration detects agent responses in the format:
+
+```
+[Agent Name]: Their dialogue here
+```
+
+When detected, it:
+1. Extracts the agent's display name (e.g., "Winston", "John")
+2. Maps it to their agent ID using `.bmad/_cfg/agent-manifest.csv`
+3. Looks up their voice from `.agentvibes/bmad/bmad-voices.md`
+4. Speaks their dialogue with that specific voice
+
+## Example
+
+**Before (silent text):**
+```
+[Winston]: I recommend microservices for scalability
+[John]: But monolith is faster to market for MVP
+[Amelia]: I can implement either approach
+```
+
+**After (with voices):**
+```
+[Winston speaks with Michael voice]: I recommend microservices for scalability
+[John speaks with Jessica Anne Bogart voice]: But monolith is faster to market for MVP
+[Amelia speaks with Matthew Schmitz voice]: I can implement either approach
+```
+
+## Voice Mappings
+
+See current agent-to-voice mappings:
+```bash
+/agent-vibes:bmad status
+```
+
+Edit voice assignments in:
+```
+.agentvibes/bmad/bmad-voices.md
+```
+
+## Requirements
+
+- BMAD v6-alpha or later
+- AgentVibes with BMAD plugin enabled
+- Piper or Piper TTS TTS provider configured
+
+## Troubleshooting
+
+**Party mode voices not working?**
+
+1. Check BMAD is installed: `ls .bmad/_cfg/agent-manifest.csv`
+2. Check voice plugin enabled: `ls .agentvibes/bmad/bmad-voices-enabled.flag`
+3. Check party mode not disabled: `ls .agentvibes/bmad/bmad-party-mode-disabled.flag`
+4. View status: `/agent-vibes:bmad-party status`
+
+**Wrong voices playing?**
+
+Check voice mappings: `/agent-vibes:bmad status`
+
+Edit mappings in: `.claude/config/bmad-voices.md`
+
+## Related Commands
+
+- `/bmad:core:workflows:party-mode` - Start BMAD party mode
+- `/agent-vibes:bmad` - Manage BMAD voice plugin
+- `/agent-vibes:switch` - Change your default voice
+- `/agent-vibes:provider` - Switch TTS provider
+
+---
+
+**Implementation:** Issue #33
+**Auto-enabled:** Yes (for BMAD users)
+**Opt-out:** Available via disable command

package/.claude/commands/agent-vibes-rdp.md

@@ -1,24 +1,24 @@
----
-scope: user
-description: Configure RDP mode for optimized audio over remote desktop (on/off/status)
----
-
-Configure AgentVibes RDP mode for optimized audio streaming over remote desktop connections.
-
-RDP mode reduces audio bandwidth by:
-- Converting to mono (1 channel instead of 2)
-- Lowering sample rate to 22kHz (from 44.1kHz)
-- Limiting bitrate to 64kbps
-
-Usage:
-- `/agent-vibes:rdp on` - Enable RDP mode
-- `/agent-vibes:rdp off` - Disable RDP mode
-- `/agent-vibes:rdp status` - Check current status
-
-When enabled, this setting persists across sessions by creating a config file.
-
-IMPORTANT: After changing RDP mode, you must either:
-1. Restart Claude Code, OR
-2. Run: `source ~/.bashrc` (or equivalent for your shell)
-
-This is necessary because the AGENTVIBES_RDP_MODE environment variable needs to be set in your shell session.
+---
+scope: user
+description: Configure RDP mode for optimized audio over remote desktop (on/off/status)
+---
+
+Configure AgentVibes RDP mode for optimized audio streaming over remote desktop connections.
+
+RDP mode reduces audio bandwidth by:
+- Converting to mono (1 channel instead of 2)
+- Lowering sample rate to 22kHz (from 44.1kHz)
+- Limiting bitrate to 64kbps
+
+Usage:
+- `/agent-vibes:rdp on` - Enable RDP mode
+- `/agent-vibes:rdp off` - Disable RDP mode
+- `/agent-vibes:rdp status` - Check current status
+
+When enabled, this setting persists across sessions by creating a config file.
+
+IMPORTANT: After changing RDP mode, you must either:
+1. Restart Claude Code, OR
+2. Run: `source ~/.bashrc` (or equivalent for your shell)
+
+This is necessary because the AGENTVIBES_RDP_MODE environment variable needs to be set in your shell session.

package/.claude/config/audio-effects.cfg

@@ -1,7 +1,7 @@
 
 llm:default|light||0.15|en_US-lessac-high||piper
-llm:claude-code|light|agent_vibes_chillwave_v2_loop.mp3|0.05||Agent Vibes local here|kokoro
-llm:copilot|light|agent_vibes_bossa_nova_v2_loop.mp3|0.15|en_US-libritts-high::Anna-11|Copilot here|piper
-llm:codex|light|agent_vibes_chillwave_v2_loop.mp3|0.15|en_US-lessac-high|Codex here|piper
-llm:hermes|light|agent_vibes_bachata_v1_loop.mp3|0.15|en_US-libritts-high::Leo-8|Hermes here|piper
-default||agent_vibes_arabic_v2_loop.mp3|0.30
+llm:claude-code|light|agent_vibes_chillwave_v2_loop.mp3|0.15|en_US-lessac-high||piper
+llm:copilot|light|agent_vibes_bossa_nova_v2_loop.mp3|0.15|en_US-libritts-high::Anna-11||piper
+llm:codex|light|agent_vibes_chillwave_v2_loop.mp3|0.15|en_US-lessac-high||piper
+llm:hermes|light|agent_vibes_bachata_v1_loop.mp3|0.15|en_US-libritts-high::Leo-8||piperdefault|reverb 70 50 100|agentvibes_soft_flamenco_loop.mp3|0.30
+default|reverb 90 90 100|agent_vibes_arabic_v2_loop.mp3|0.30

package/.claude/config/background-music-enabled.txt

@@ -1 +1 @@
-false
+false