agentvibes 2.2.1 → 2.2.2

package/linkedin/vibe-coding-and-pulseaudio.md

@@ -0,0 +1,121 @@
+# Vibe Coding: How PulseAudio Can Give Your Remote SSH Session a Voice!
+
+My mornings and late evenings are when I'm at my creative peak. I like to use this time for things that are fun—or at least that I think are fun. Since I recently created AgentVibes (a way to make my computer speak back to me), I wanted to solve a limitation I was experiencing while working on a remote server. That curiosity led me down the PulseAudio rabbit hole, and what I discovered fundamentally changed how I code with AI.
+
+## What is "Vibe Coding"?
+
+According to Gene Kim, a researcher and author featured in the DORA report, **"vibe coding"** is defined as any form of coding where you don't type out code by hand. Instead of manual typing, the code emerges from an **iterative conversation with an AI**.
+
+This is the future of software development. Not replacing developers, but amplifying our capabilities through natural dialogue.
+
+## If We're Going to Have a Conversation, Let's Use Voice
+
+When I discovered whisper typing several months ago, it fundamentally changed the way I use my computer. Rather than typing everything to my AI assistant, I now **talk** using whisper typing. The speed, the naturalness, the flow—it was transformative.
+
+But then a thought struck me: **If I can talk to my computer, why can't it talk back?**
+
+That question led me to create [**AgentVibes**](https://github.com/paulpreibisch/AgentVibes)—a plugin for Claude Code that brings professional text-to-speech narration to your AI coding sessions. Your AI assistant can now acknowledge your requests, confirm task completion, and provide feedback through voice.
+
+Imagine this workflow:
+- You speak your coding request using whisper typing
+- Your AI assistant acknowledges with voice: "I'll refactor that authentication module for you"
+- You continue working while hearing real-time progress updates
+- The AI confirms: "Refactoring complete, all tests passing"
+
+This is vibe coding at its finest—a natural, conversational flow between human and AI.
+
+## The Remote Server Problem
+
+But I discovered a limitation. Since text-to-speech typically executes on the computer you're programming on, **what happens when you're programming on a remote machine via SSH?**
+
+This is the reality for many developers:
+- Cloud development environments
+- Powerful remote servers
+- Team shared infrastructure
+- Corporate VDI setups
+
+The audio plays on the remote server—where you can't hear it. The conversational flow breaks down. The vibe is lost.
+
+## Enter PulseAudio: The Hidden Hero
+
+I went to task trying to figure out if there was a way to somehow play audio from a remote machine onto my local machine. That's when I was introduced to the true capabilities of **PulseAudio**.
+
+Now, I've been a Linux user for many years and have used PulseAudio forever. But little did I know that **PulseAudio can actually stream audio over a network**, allowing a client to play audio from a remote server.
+
+This completely blew my mind. 🤯
+
+Here's what makes this powerful:
+
+### The Architecture
+```
+Remote Linux Server (PulseAudio)
+    ↓ SSH Reverse Tunnel
+Windows Client (WSL/RDP Audio)
+    ↓
+Local Speakers 🔊
+```
+
+### What This Enables
+- Run AgentVibes on your remote server
+- Hear TTS announcements on your local speakers
+- Maintain the conversational flow of vibe coding
+- Work from anywhere with full audio feedback
+
+I'll tell you, I was **floored** that this was even possible.
+
+## The Game-Changing Impact
+
+The ability to have your AI assistant **acknowledge what you've typed and provide vocal confirmation** really does change the game when vibe coding.
+
+Here's why it matters:
+
+**1. Cognitive Offloading**
+You don't need to constantly check the terminal to see if your AI understood. Voice acknowledgment lets you focus on problem-solving.
+
+**2. Natural Flow State**
+Conversations have rhythm. When both parties speak and listen, you stay in flow. Text-only breaks that rhythm.
+
+**3. Active Guidance with Voice Feedback**
+Vibe coding doesn't mean you stop paying attention—quite the opposite. You're actively guiding the AI through the implementation, reviewing its decisions, and course-correcting in real-time. Voice acknowledgment keeps you in the loop while your hands stay free to sketch architecture, review documentation, or reference other code. The conversation is continuous, and if you're an experienced developer, the depth and precision of that conversation becomes truly transformative.
+
+**4. Reduced Context Switching**
+No need to constantly alt-tab between terminal and code. Your ears keep you updated.
+
+## Try It Yourself
+
+Want to experience vibe coding with remote audio? I've documented the entire setup process.
+
+**Check out AgentVibes:**
+📦 GitHub: [github.com/paulpreibisch/AgentVibes](https://github.com/paulpreibisch/AgentVibes)
+
+**Remote Audio Setup Guide:**
+📚 Complete documentation: [Remote Audio Setup](https://github.com/paulpreibisch/AgentVibes/blob/master/docs/remote-audio-setup.md)
+
+The setup includes:
+- Automated scripts for Linux and Windows
+- PulseAudio network configuration
+- SSH tunnel setup
+- Troubleshooting guides
+- VS Code Remote-SSH integration
+
+It took me a morning to figure out, but now you can set it up in 10 minutes.
+
+## The Bigger Picture
+
+This journey taught me something important: **The best developer tools emerge from solving real problems in your own workflow.**
+
+I didn't set out to become a PulseAudio expert. I just wanted my AI assistant to talk back when I'm working on remote servers. The solution required diving deep into audio streaming, SSH tunneling, and network protocols—but the result is worth it.
+
+Vibe coding isn't just about AI generating code. It's about creating an **environment where human and AI collaborate naturally**—through conversation, through voice, through continuous feedback loops.
+
+And sometimes, that requires discovering that the tools you've been using for years have hidden superpowers you never knew existed.
+
+---
+
+**What's your experience with AI-assisted development? Have you tried vibe coding? Let's discuss in the comments!**
+
+#VibeCoding #AI #DeveloperTools #SoftwareEngineering #PulseAudio #RemoteDevelopment #DevOps #AIAssisted #ClaudeCode #OpenSource
+
+---
+
+*P.S. - If you found this interesting, check out the AgentVibes project on GitHub. It's open source, supports multiple TTS providers (including free Piper TTS), and has 30+ professional AI voices. Star the repo if you find it useful!* ⭐

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "agentvibes",
-  "version": "2.2.1",
+  "version": "2.2.2",
   "description": "Now your AI Agents can finally talk back! Professional TTS voice for Claude Code and Claude Desktop (via MCP) with multi-provider support.",
   "homepage": "https://agentvibes.org",
   "keywords": [

package/scripts/audio-tunnel.config

@@ -0,0 +1,17 @@
+# AgentVibes Audio Tunnel Configuration
+# Personal configuration - DO NOT COMMIT
+
+# Remote server hostname (from your ~/.ssh/config)
+REMOTE_HOST="ubuntu-rdp"
+
+# Tunnel port (default: 14713)
+TUNNEL_PORT="14713"
+
+# PulseAudio socket path (WSL default)
+PULSE_SOCKET="/mnt/wslg/PulseServer"
+
+# Log file for automatic fixes
+AUTO_FIX_LOG="/tmp/audio-tunnel-autofix.log"
+
+# Healthcheck interval in minutes (for cron setup)
+CHECK_INTERVAL="5"

package/sonar

@@ -0,0 +1,141 @@
+#!/usr/bin/env bash
+#
+# SonarQube Analysis Wrapper Script
+# Run SonarCloud analysis on the AgentVibes project
+#
+
+set -euo pipefail
+
+# Colors for output
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+CYAN='\033[0;36m'
+NC='\033[0m' # No Color
+
+# Configuration
+PROJECT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+STORAGE_DIR="$PROJECT_DIR/.sonarqube-storage"
+CONTAINER_NAME="sonarqube-mcp-server-agentvibes"
+IMAGE_NAME="mcp/sonarqube"
+
+# Check required environment variables
+check_env_vars() {
+    local missing=0
+
+    # Use AgentVibes-prefixed environment variables
+    if [[ -z "${AGENTVIBES_SONARQUBE_TOKEN:-}" ]]; then
+        echo -e "${RED}❌ AGENTVIBES_SONARQUBE_TOKEN is not set${NC}"
+        missing=1
+    fi
+
+    if [[ -z "${AGENTVIBES_SONARQUBE_ORG:-}" ]]; then
+        echo -e "${RED}❌ AGENTVIBES_SONARQUBE_ORG is not set${NC}"
+        missing=1
+    fi
+
+    if [[ -z "${AGENTVIBES_SONARQUBE_PROJECT:-}" ]]; then
+        echo -e "${RED}❌ AGENTVIBES_SONARQUBE_PROJECT is not set${NC}"
+        missing=1
+    fi
+
+    if [[ $missing -eq 1 ]]; then
+        echo -e "\n${YELLOW}💡 Set these environment variables in ~/.zshrc:${NC}"
+        echo "   export AGENTVIBES_SONARQUBE_TOKEN='your-token'"
+        echo "   export AGENTVIBES_SONARQUBE_ORG='paulpreibisch'"
+        echo "   export AGENTVIBES_SONARQUBE_PROJECT='AgentVibes'"
+        echo -e "\n${YELLOW}Then reload: source ~/.zshrc${NC}"
+        exit 1
+    fi
+
+    # Set standard variable names for Docker container
+    export SONARQUBE_TOKEN="${AGENTVIBES_SONARQUBE_TOKEN}"
+    export SONARQUBE_ORG="${AGENTVIBES_SONARQUBE_ORG}"
+    export SONARQUBE_PROJECT="${AGENTVIBES_SONARQUBE_PROJECT}"
+}
+
+# Check if Docker is available
+check_docker() {
+    if ! command -v docker &> /dev/null; then
+        echo -e "${RED}❌ Docker is not available${NC}"
+        echo -e "${YELLOW}💡 Please start Docker Desktop or enable Docker in WSL2${NC}"
+        exit 1
+    fi
+
+    if ! docker info &> /dev/null; then
+        echo -e "${RED}❌ Docker daemon is not running${NC}"
+        echo -e "${YELLOW}💡 Please start Docker Desktop${NC}"
+        exit 1
+    fi
+}
+
+# Create storage directory if it doesn't exist
+setup_storage() {
+    if [[ ! -d "$STORAGE_DIR" ]]; then
+        echo -e "${CYAN}📁 Creating storage directory...${NC}"
+        mkdir -p "$STORAGE_DIR"
+    fi
+}
+
+# Pull the latest image if needed
+pull_image() {
+    if ! docker images | grep -q "mcp/sonarqube"; then
+        echo -e "${CYAN}📦 Pulling SonarQube MCP image...${NC}"
+        docker pull "$IMAGE_NAME" || {
+            echo -e "${RED}❌ Failed to pull image${NC}"
+            echo -e "${YELLOW}💡 Make sure you have access to the mcp/sonarqube image${NC}"
+            exit 1
+        }
+    fi
+}
+
+# Stop any existing container
+cleanup() {
+    if docker ps -a | grep -q "$CONTAINER_NAME"; then
+        echo -e "${CYAN}🧹 Cleaning up existing container...${NC}"
+        docker rm -f "$CONTAINER_NAME" &> /dev/null || true
+    fi
+}
+
+# Run the analysis
+run_analysis() {
+    echo -e "${GREEN}🚀 Starting SonarCloud analysis...${NC}"
+    echo -e "${CYAN}   Organization: ${SONARQUBE_ORG}${NC}"
+    echo -e "${CYAN}   Project: ${SONARQUBE_PROJECT}${NC}"
+    echo -e "${CYAN}   URL: https://sonarcloud.io${NC}"
+    echo ""
+
+    docker run -i \
+        --name "$CONTAINER_NAME" \
+        --rm \
+        -e "SONARQUBE_TOKEN=${SONARQUBE_TOKEN}" \
+        -e "SONARQUBE_URL=https://sonarcloud.io" \
+        -e "SONARQUBE_ORG=${SONARQUBE_ORG}" \
+        -e "SONARQUBE_PROJECT=${SONARQUBE_PROJECT}" \
+        -v "${STORAGE_DIR}:/storage" \
+        "$IMAGE_NAME" "$@"
+}
+
+# Main execution
+main() {
+    echo -e "${CYAN}═══════════════════════════════════════════${NC}"
+    echo -e "${CYAN}   SonarQube Analysis - AgentVibes${NC}"
+    echo -e "${CYAN}═══════════════════════════════════════════${NC}"
+    echo ""
+
+    check_env_vars
+    check_docker
+    setup_storage
+    pull_image
+    cleanup
+    run_analysis "$@"
+
+    echo ""
+    echo -e "${GREEN}✅ Analysis complete!${NC}"
+    echo -e "${CYAN}🔗 View results: https://sonarcloud.io/project/overview?id=${SONARQUBE_PROJECT}${NC}"
+}
+
+# Handle Ctrl+C gracefully
+trap cleanup EXIT
+
+main "$@"