mirror of
https://github.com/getpaseo/paseo.git
synced 2026-07-29 12:01:31 +00:00
b2229a28b9
* fix(server): reset session ID on query restart to prevent overwrite crash When ensureQuery() restarts a query, the old claudeSessionId was retained. If the new query landed on a different Claude session (e.g. after a hook or reconnect), captureSessionIdFromMessage() would detect the mismatch and throw a fatal "session ID overwrite" error, killing the agent mid-turn. Reset claudeSessionId and persistence during query restart so the new session can establish its own identity cleanly. Closes #200 * fix(server): recover from session ID overwrite and load projects instantly - Reset claudeSessionId unconditionally before every new query creation, not just on explicit restarts. Fixes unrecoverable crash loop where a pump failure left stale session ID, causing every subsequent query to immediately throw the overwrite error again. - Decouple fetch_workspaces_request from reconciliation: serve registry snapshot immediately instead of awaiting git operations on all workspaces. Background reconciliation runs after response is sent and pushes workspace_update events for any changed workspaces (e.g. stale worktrees getting archived). * fix(server): auto-resume Claude session after overwrite error to preserve history When the query pump dies (e.g. after a session ID overwrite error), preserve claudeSessionId so the next query automatically passes resume: sessionId to the Claude SDK. Claude responds with the same session ID, the overwrite check passes, and the conversation history is intact. Previously claudeSessionId was reset unconditionally before every new query, causing the next query to start a fresh session and lose the conversation. Now it is only reset for explicit restarts (queryRestartNeeded), where a fresh session is the intended behavior. * fix(server): reset session ID before throwing overwrite error to break retry loop When the overwrite error fired, claudeSessionId was left set to the old value. Our auto-resume fix then passed resume: oldSessionId on every retry, Claude returned yet another new session ID each time, and the overwrite error looped indefinitely (same "Existing" UUID across all failures in the log). Fix: reset claudeSessionId = null in both captureSessionIdFromMessage and handleSystemMessage before throwing, so the next query starts a fresh session instead of looping on a dead resume target. Auto-resume still works for legitimate pump failures (network drops etc.) since those exit without throwing, leaving claudeSessionId intact. * fix(server): accept session ID change mid-stream instead of failing the turn Hooks can cause Claude to restart with a new session ID mid-turn. Previously both captureSessionIdFromMessage and handleSystemMessage threw a CRITICAL error when the session ID changed, failing the turn and leaving the user with an error message on what should have been a transparent hook execution. Now both paths log a warning and accept the new session ID, allowing the turn to continue uninterrupted through hook-triggered subprocess restarts.
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