Replace happy-demo.sh with happy-launcher.sh everywhere

- Update Makefile targets to use happy-launcher.sh
- Make `stop` target stop daemon and cleanup all slots
- Update start-server.sh to wrap happy-launcher.sh
- Update .devcontainer/Makefile server target
- Expand QUICKSTART in README with full self-hosting steps:
  - Create account in webapp
  - Get secret key
  - Install CLI on dev machines
  - Authenticate with backup key
  - Start daemon
  - Optional voice assistant setup
- Update all documentation to reference happy-launcher.sh

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: rrnewton

.devcontainer/Makefile

@@ -115,7 +115,7 @@ server:
 		-v `pwd`/home:/root \
 		-v `pwd`/..:$(WORKDIR) \
 		$(PORTS_SERVER) $(FULLTAG) \
-		bash -c "cd $(WORKDIR) && ./happy-demo.sh start && tail -f /dev/null"
+		bash -c "cd $(WORKDIR) && ./happy-launcher.sh start-backend && tail -f /dev/null"
 
 AGENT_LAYERS = Dockerfile.claude Dockerfile.copilot
 # Dockerfile.gemini

DEBUG_WEB_AUTH.md

@@ -69,15 +69,15 @@ Then when you submit the secret key:
 **Solutions:**
 1. The secret key might be from a different account
 2. Run `node scripts/setup-test-credentials.mjs` to generate a fresh account
-3. Check server logs: `./happy-demo.sh logs server`
+3. Check server logs: `./happy-launcher.sh logs server`
 
 ### If you see network error or CORS error
 
 **Problem:** Can't connect to the server.
 
 **Solutions:**
 1. Check server is running: `curl http://localhost:3005`
-2. Restart server: `./happy-demo.sh restart`
+2. Restart server: `./happy-launcher.sh restart`
 
 ### If logs show different bytes length (not 32)
 

DEPENDENCIES.md

@@ -94,7 +94,7 @@ This document tracks all dependencies installed during the self-hosted setup pro
 ### e2e-demo.sh
 - **Location**: `/e2e-demo.sh`
 - **Purpose**: Complete e2e demo script that shows the full self-hosted flow
-- **Dependencies**: setup-postgres.sh, happy-demo.sh, setup-test-credentials.mjs
+- **Dependencies**: setup-postgres.sh, happy-launcher.sh, setup-test-credentials.mjs
 - **Usage**: `./e2e-demo.sh`
 
 ## Environment Variables

E2E_TESTING.md

@@ -14,7 +14,7 @@ For headless e2e testing, we've created a script that automates the entire authe
 
 ```bash
 # 1. Start all services
-./happy-demo.sh start
+./happy-launcher.sh start
 
 # 2. Setup test credentials (automated, no interaction needed)
 node scripts/setup-test-credentials.mjs
@@ -54,7 +54,7 @@ The `happy` directory contains an Expo React Native app that supports web deploy
 ### 1. Start the Services
 
 ```bash
-./happy-demo.sh start
+./happy-launcher.sh start
 ```
 
 This starts:
@@ -106,7 +106,7 @@ Open `http://localhost:8081` in a text-based web browser (or any browser):
 In another terminal:
 
 ```bash
-./happy-demo.sh cli
+./happy-launcher.sh cli
 ```
 
 Or directly:
@@ -159,14 +159,14 @@ Key endpoints used in tests:
 
 ### Server not responding
 ```bash
-./happy-demo.sh status    # Check all services
-./happy-demo.sh logs server  # View server logs
+./happy-launcher.sh status    # Check all services
+./happy-launcher.sh logs server  # View server logs
 ```
 
 ### Authentication timeout
 - Verify server URL in web client matches CLI config
 - Check that both are using `http://localhost:3005`
-- Ensure `.env` file exists in happy-server (run `./happy-demo.sh start` to create it)
+- Ensure `.env` file exists in happy-server (run `./happy-launcher.sh start` to create it)
 
 ### Database connection errors
 ```bash
@@ -178,8 +178,8 @@ cd happy-server && yarn migrate
 
 ### Clean slate
 ```bash
-./happy-demo.sh cleanup --clean-logs  # Stop everything and clean logs
-./happy-demo.sh start                 # Fresh start
+./happy-launcher.sh cleanup --clean-logs  # Stop everything and clean logs
+./happy-launcher.sh start                 # Fresh start
 ```
 
 ## Architecture

Makefile

@@ -233,16 +233,16 @@ server: build
 	@echo ""
 	@./start-server.sh
 
-# Stop all services
+# Stop all services (all slots)
 stop:
 	@echo "=== Stopping all services ==="
-	@./happy-demo.sh cleanup
-	@pkill -f 'expo start' 2>/dev/null || true
+	@./happy-cli/bin/happy.mjs daemon stop 2>/dev/null || true
+	@./happy-launcher.sh cleanup --all-slots
 	@echo "All services stopped"
 
 # View server logs
 logs:
-	@./happy-demo.sh logs server
+	@./happy-launcher.sh logs server
 
 # Run CLI with local server (uses default ~/.happy credentials)
 cli:
@@ -265,7 +265,7 @@ e2e-test: build
 	@echo ""
 	@echo "=== Running E2E Test (isolated credentials) ==="
 	@echo ""
-	@./happy-demo.sh cleanup --clean-logs
+	@./happy-launcher.sh cleanup --clean-logs
 	@./e2e-web-demo.sh
 
 # Inspect webapp with headless browser (requires webapp to be running)

README.md

@@ -4,6 +4,8 @@ This repository contains a working self-hosted setup of Happy (server + CLI) wit
 
 ## QUICKSTART: Self Hosting
 
+### Step 0: Build and Launch Services
+
 Run your own Happy instance with two containers - one for the webapp and one for the server:
 
 ```bash
@@ -17,12 +19,58 @@ make server
 make web
 ```
 
-Then open http://localhost:8081 in your browser.
-
 **Other container options:**
 - `make root` - Interactive shell with no ports forwarded
 - `make root-all-ports` - Interactive shell with both ports (8081 + 3005) forwarded
 
+### Step 1: Create an Account
+
+1. Open http://localhost:8081 in your browser
+2. Click "Create Account"
+3. Optionally add a recognizable username in Account settings
+
+### Step 2: View Your Secret Key
+
+1. Go to Account settings in the webapp
+2. Find and copy your secret backup key (format: `XXXXX-XXXXX-...`)
+
+### Step 3: Install the CLI on Development Machines
+
+On each machine where you want to run Claude with Happy:
+
+```bash
+# Clone and install the fork
+git clone --depth=1 https://github.com/rrnewton/happy-cli.git /usr/local/happy
+cd /usr/local/happy
+npm install
+npm run build
+npm install -g .
+```
+
+### Step 4: Authenticate the CLI
+
+Use the secret key from Step 2 to authenticate:
+
+```bash
+happy auth login --backup-key <YOUR-SECRET-KEY>
+```
+
+### Step 5: Start the Daemon
+
+```bash
+happy daemon start
+```
+
+The daemon connects your machine to the Happy server, allowing remote control from the webapp.
+
+### Step 6: (Optional) Voice Assistant Setup
+
+For ElevenLabs voice assistant integration:
+1. Go to Account > Voice Assistant in the webapp
+2. Click "Get API Key" to create an ElevenLabs API key with required permissions
+3. Enter your API key and save credentials
+4. Use "Find Agent" or "Create/Update Agent" to set up the voice agent
+
 ## Getting Started
 
 ### Build and Run Container
@@ -117,10 +165,10 @@ See [WEB_CLIENT_GUIDE.md](WEB_CLIENT_GUIDE.md) for detailed instructions.
 ### Start Services
 
 ```bash
-./happy-demo.sh start    # Start all services
-./happy-demo.sh status   # Check what's running
-./happy-demo.sh stop     # Stop services
-./happy-demo.sh cleanup  # Stop everything including databases
+./happy-launcher.sh start    # Start all services
+./happy-launcher.sh status   # Check what's running
+./happy-launcher.sh stop     # Stop services
+./happy-launcher.sh cleanup  # Stop everything including databases
 ```
 
 ### Setup Test Credentials
@@ -176,10 +224,12 @@ export HAPPY_SERVER_URL=http://localhost:3005
 
 ## Key Scripts
 
-### happy-demo.sh
+### happy-launcher.sh
 Main control script for managing services:
-- `start` - Start all services
-- `stop` - Stop happy-server and MinIO
+- `start` - Start all services (backend + webapp)
+- `start-backend` - Start only backend services
+- `start-webapp` - Start only the webapp
+- `stop` - Stop happy-server, webapp, and MinIO
 - `cleanup` - Stop everything including databases
 - `status` - Show service status
 - `logs <service>` - View logs
@@ -213,14 +263,14 @@ All ports are automatically forwarded when using the devcontainer.
 
 ### Server not responding
 ```bash
-./happy-demo.sh status          # Check all services
-./happy-demo.sh logs server     # View server logs
+./happy-launcher.sh status          # Check all services
+./happy-launcher.sh logs server     # View server logs
 ```
 
 ### Clean slate
 ```bash
-./happy-demo.sh cleanup --clean-logs   # Stop everything and clean logs
-./happy-demo.sh start                  # Fresh start
+./happy-launcher.sh cleanup --clean-logs   # Stop everything and clean logs
+./happy-launcher.sh start                  # Fresh start
 ```
 
 ### Database issues

SELF_HOSTED_SETUP.md

@@ -124,7 +124,7 @@ set -e
 echo "=== Happy Real Authentication Demo ==="
 
 # Step 1: Start services
-./happy-demo.sh start
+./happy-launcher.sh start
 
 # Step 2: Start web client
 echo "Starting web client..."
@@ -228,7 +228,7 @@ happy auth
 
 1. **Start services**:
    ```bash
-   ./happy-demo.sh start
+   ./happy-launcher.sh start
    ```
 
 2. **Start web client** (in separate terminal):

SETUP_COMPLETE.md

@@ -125,14 +125,14 @@ All dependencies have been added to `.devcontainer/Dockerfile.project`. When you
 
 1. Install PostgreSQL, Redis, lsof, and wget
 2. Download and install MinIO server and client
-3. Copy the `happy-demo.sh` control script to `/workspace/`
+3. Copy the `happy-launcher.sh` control script to `/workspace/`
 
 After rebuilding, you'll still need to:
-1. Run `happy-demo.sh start` to start all services
+1. Run `happy-launcher.sh start` to start all services
 2. Set up the database: Create the `handy` database and run migrations
 3. Configure MinIO: Create the `happy` bucket
 
 Or simply use the quick start:
 ```bash
-./happy-demo.sh start
+./happy-launcher.sh start
 ```

WEB_CLIENT_GUIDE.md

@@ -15,7 +15,7 @@ The Happy web client provides a browser-based interface to:
 ### 1. Start All Services
 
 ```bash
-./happy-demo.sh start
+./happy-launcher.sh start
 ```
 
 This starts:
@@ -177,7 +177,7 @@ export HAPPY_SERVER_URL=http://localhost:3005
 ### Web client can't connect to server
 
 Check that:
-1. happy-server is running: `./happy-demo.sh status`
+1. happy-server is running: `./happy-launcher.sh status`
 2. Server URL is correct in web client environment variables
 3. No firewall is blocking port 3005
 
@@ -226,8 +226,8 @@ Priority order for server URL:
 ### Authentication fails in web browser
 
 Check:
-1. Server logs: `./happy-demo.sh logs server`
-2. Database is running: `./happy-demo.sh status`
+1. Server logs: `./happy-launcher.sh logs server`
+2. Database is running: `./happy-launcher.sh status`
 3. Try creating fresh test credentials: `node scripts/setup-test-credentials.mjs`
 4. See "Invalid secret key" troubleshooting section above
 

start-server.sh

@@ -3,21 +3,13 @@
 # Start Happy Server (infrastructure only)
 # This script starts all backend services without creating test accounts or sessions
 # Use this for normal development work
+#
+# This is a thin wrapper around happy-launcher.sh
 
 set -e
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 
-# Colors for output
-GREEN='\033[0;32m'
-BLUE='\033[0;34m'
-CYAN='\033[0;36m'
-NC='\033[0m'
-
-info() { echo -e "${BLUE}[INFO]${NC} $1"; }
-success() { echo -e "${GREEN}[SUCCESS]${NC} $1"; }
-step() { echo -e "${CYAN}[STEP]${NC} $1"; }
-
 echo ""
 echo "=== Happy Server Startup ==="
 echo ""
@@ -29,50 +21,9 @@ echo "  - happy-server API (port 3005)"
 echo "  - happy webapp (port 8081)"
 echo ""
 
-# Step 1: Start backend services
-step "Step 1: Starting backend services..."
-./happy-demo.sh start
-success "Backend services started"
-echo ""
-
-# Step 2: Start web client
-step "Step 2: Starting Happy web client..."
-info "Building may take a minute on first run..."
-cd happy
-# Clear cache to ensure latest code
-rm -rf .expo/web node_modules/.cache 2>/dev/null || true
-yarn start:local-server > /tmp/happy-web.log 2>&1 &
-WEB_PID=$!
-cd ..
-echo "Web client PID: $WEB_PID"
-echo ""
+# Use happy-launcher.sh to start all services
+"$SCRIPT_DIR/happy-launcher.sh" start
 
-# Wait for web server to be ready
-info "Waiting for web server to start..."
-sleep 10
-for i in {1..12}; do
-    if curl -s http://localhost:8081 > /dev/null 2>&1; then
-        success "Web client is ready!"
-        break
-    fi
-    echo -n "."
-    sleep 5
-done
-echo ""
-
-echo ""
-echo "=== Server Started ==="
-echo ""
-success "API Server:  http://localhost:3005"
-success "Web Client:  http://localhost:8081"
-success "MinIO Console: http://localhost:9001 (minioadmin/minioadmin)"
-echo ""
-echo "To use the CLI (defaults to ~/.happy):"
-echo "  HAPPY_SERVER_URL=http://localhost:3005 ./happy-cli/bin/happy.mjs"
-echo ""
-echo "To authenticate a new CLI:"
-echo "  1. Run CLI and scan QR code with webapp"
-echo "  2. Or use 'make setup-credentials' to auto-create credentials"
 echo ""
 echo "Useful commands:"
 echo "  make stop               # Stop all services"