Nicholas Maglowsch SalgueiroandGitHub
c59b47b8a6
* fix(server): report Claude runtime death instead of sitting idle When the Claude Code CLI process dies on its own — crash, OOM kill, host suspend — nothing in the daemon observes it unless a turn happens to be in flight. The query pump only reports a failure while it is draining a turn, so an idle agent's stream just ends: the agent stays `idle`, indistinguishable from a healthy resumable one. Everything the agent parked inside that process dies with it. Background Bash shells, `Monitor` watches and workflows all live in the CLI process, so the completion notification that would have woken the agent back up never arrives. The work is silently gone and the user finds out much later, if at all. The stale handles are never dropped either, so writes keep going to a dead transport for as long as the daemon lives (#2472). Watch the spawned child at the single seam it is already handed over (`onChildProcess`). When it exits between turns, drop the dead query/input handles so the next write spawns a fresh process, and emit `turn_failed` — the manager already routes a non-foreground `turn_failed` to `error` plus a timeline entry. A death mid-turn is left alone. The pump already waits for stderr to flush and reports the real cause; reporting here first would replace that with a bare exit code. Intentional teardown stays quiet. All three sites that retire a process detach the child handle first: `close()` sets `closed`, and `ensureQuery()` and `handleMissingResumedConversation()` null `childProcess` before ending stdin. Fixes #2472 * fix(server): tree-kill the retired process on missing-resume recovery The missing-resumed-conversation path ends the child's stdin but never tree-killed it, so MCP children of the retired claude process could outlive it as orphans. Every other teardown path already does this; do it here too. Reported by Greptile on #2910.
Voice Assistant
A voice-controlled terminal assistant that runs as a single local service.
Quick Start
# Install dependencies
npm install
# Copy environment variables
cp .env.example .env
# Edit .env and add your API keys (OpenAI, Deepgram)
# Run development servers
npm run dev
# Open browser to http://localhost:5173
Architecture
- Express Server (port 3000) - Serves API and built UI in production
- Vite Dev Server (port 5173) - Hot-reload React UI in development
- WebSocket (
/ws) - Real-time bidirectional communication - Agent - STT → LLM → TTS pipeline with terminal control
- Daemon - tmux-based terminal management (in-process)
Development
# Run both servers (recommended)
npm run dev
# Or run separately:
npm run dev:server # Express on port 3000
npm run dev:ui # Vite on port 5173
# Type checking
npm run typecheck
# Build for production
npm run build
# Start production server
npm start
Project Status
✅ Completed (Phases 1-2):
- Package setup and configuration
- Express server with WebSocket
- React UI with Vite
- WebSocket client with ping/pong testing
⏳ In Progress (Phase 3):
- Terminal control (tmux integration)
📋 Planned (Phases 4-9):
- LLM integration (OpenAI GPT-4)
- Agent orchestrator
- Speech-to-Text (Deepgram)
- Text-to-Speech (OpenAI)
- Audio streaming
- UI polish
See IMPLEMENTATION_PLAN.md for complete details.
Environment Variables
OPENAI_API_KEY=your-openai-key-here # GPT-4 and TTS
DEEPGRAM_API_KEY=your-deepgram-key-here # Streaming STT
STT_MODEL=whisper-1 # Optional: override to gpt-4o-transcribe, etc.
STT_CONFIDENCE_THRESHOLD=-3.0 # Optional: reject low-confidence clips
STT_DEBUG_AUDIO_DIR=.stt-debug # Optional: persist raw dictation audio for debugging
PASEO_HOME=~/.paseo # Runtime state directory (agents/, etc.)
PASEO_LISTEN=127.0.0.1:6767 # Listen address (host:port or /path/to/socket)
PASEO_HOME defaults to ~/.paseo and isolates runtime artifacts like agents/. PASEO_LISTEN controls the daemon listen address. For blue/green testing you can run a parallel server without touching production state:
PASEO_HOME=~/.paseo-blue PASEO_LISTEN=127.0.0.1:7777 npm run dev
Tech Stack
- Server: Express, TypeScript, ws (WebSocket)
- Client: React 18, Vite, TypeScript
- Terminal: tmux (via child_process)
- AI: OpenAI (LLM + TTS), Deepgram (STT)
Testing
Currently manual testing via:
- Start servers:
npm run dev - Open http://localhost:5173
- Test WebSocket connection (green status indicator)
- Click "Send Ping" button to test communication
More testing guidance as features are implemented.
License
MIT