mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-19 23:05:21 +00:00
* fix(server): notify once while an agent's finish is unread Since v0.16.0, a turn that an agent starts on its own cleared the agent's unread "finished" attention. Every such turn that then ended raised a new "finished" notification. A Claude Code agent that reacts to each event of a Monitor or a background task starts one turn per event, so the user got a notification every few seconds. A turn that the agent starts on its own now clears only error attention, which is what the earlier change intended. An unread finish stays unread, so the next finish does not notify again. After the user reads the agent, the next finish notifies as before. A prompt from the user still clears all attention. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(server): notify a repeat finish the user was not told about The previous commit kept an unread finish across turns that an agent starts on its own, and the agent manager then sent no attention for the later finishes. Suppose the user had the agent on screen for the first finish. The app keeps that finish unread, and no notification is sent while the agent is on screen. After the user left, no later finish notified at all. The agent manager now reports each finish, and marks a finish that repeats an unread finish. The websocket server owns delivery, so it records whether it delivered a notification for the unread finish. A repeat notifies only when nothing was delivered for it yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(server): key the notified unread finish by its attention timestamp The websocket server recorded only that it had notified for some finish of an agent. Mark as unread starts a new unread finish without an attention event, so a later repeat used the record of an older finish that the user had already read, and sent nothing. The attention callback now carries the timestamp of the agent's current unread attention, which identifies the unread finish. The server stores the timestamp it notified for, and suppresses a finish only when it belongs to that same unread finish. This replaces the repeatsUnreadFinish flag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.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