mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-23 01:32:40 +00:00
paseo-bot[bot]
6d37f7fd9f
* Close agents before stopping the plugins that serve them A clean daemon shutdown stopped every plugin before it closed any agent. Stopping a plugin withdraws its provider registrations, which pushes an empty registration set through the agent provider registry, shuts the plugin provider client down, and closes each still-open session with `connectionClosed()`. That is reported as `session.runtime_failed` and translated to `turn_failed`, so an agent whose last turn had completed successfully was persisted with `lastError: "Provider connection closed"` and came back after a restart carrying a failure it never had. Stop tracking plugin provider registrations first so plugin teardown can no longer withdraw a provider from under an open agent, and stop the plugins themselves after `closeAllAgents()` and the provider runtime shutdown have already made every session terminal. Closing the sessions while their plugin is still running also means `session.close` now reaches the provider. Fixes #4877 * Bound each agent close so a silent provider cannot stall shutdown Closing an agent asks its provider to close the session and waits for the answer, and that request is only rejected when the provider runtime shuts down. With agents now closing before the runtime does, a provider that never answers `session.close` would leave `closeAllAgents()` waiting with nothing left to unblock it. Give each close a deadline. Whatever outlives it is abandoned and logged, and the provider runtime shutdown that runs next rejects the request that was still pending. Also type the test fixture's `send` input as `ProviderInput`. * Move the shutdown tests into the plugin lifecycle suite Both tests exercise plugin lifecycle against a real daemon, which lifecycle.e2e.test.ts already covers, so they go there rather than into a suite of their own. Drop the wall-clock assertion on how long stop() took. What the test establishes is that stop() returns at all, and the suite timeout is what enforces that; measuring elapsed time only added a second bound that a loaded machine could trip. --------- Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com>
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