mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-19 23:05:21 +00:00
* Keep a finished reply visible when Claude starts a turn after a background command When a background command finishes while Claude is idle, Claude Code sends the task notification first and opens its own turn after it. The notification row was stored with no turn id. A row with no turn id joins the turn before it to the turn after it, so under Collapse turns the app showed both turns as one and folded the finished reply behind the summary row. The Claude provider now keeps a task notification that arrives between turns and emits it inside the turn Claude starts for it, so the row carries that turn's id. A notification no turn follows is emitted as before: when Claude reports idle (a command the user stopped), before the user's next message, and on close. Rows already stored without a turn id are not changed. Refs #10030. * Show a stopped background command's notification at once A stopped background command starts no Claude turn. While a background subagent is alive Claude also sends no idle, so the held row stayed hidden until the subagent finished and then took the subagent's wake-up turn id. Only task notifications Claude reacts to (completed or failed) wait for a turn now. A stopped one is emitted right away, as before. Refs #10030. * Keep a row that belongs to no turn out of the turns around it A turn starts with the user's message or the provider's own turn start (Claude's init). A background command's notification that arrives between turns starts nothing, so the daemon writes it with no turn ID. The shared turn rule read a missing ID as legacy history and let the row continue both neighbours. The reply before it and the turn after it then read as one turn, and Collapse turns folded the first reply. Now a row with no turn ID never continues a row that has one, so it cannot join two turns. History with no IDs at all keeps the trigger rule. The app's fold and the daemon's whole-turn paging share the rule. This replaces the earlier Claude provider hold, which had to guess from the notification's status whether Claude would start a turn for it. Refs #10030 * Give a background task's notification the turn it starts A background task's notification that arrives while no turn runs starts a turn. Claude's next run belongs to it unless Claude announces another start first: a later notification starts the next turn, and a queued command (the user's message, a scheduled wake-up) starts its own. When Claude does not respond, the notification is a turn in itself. So a reply Claude writes for a finished background command shares the notification's turn, and the reply before it stays in its own turn and stays visible under Collapse turns. A stopped command's row shows at once as its own turn, and the agent stays idle. Claude sends no frame for a Monitor event, so a run it starts for one belongs to the last notification before it. This replaces the shared turn-rule change, which drew the notification as a turn between the two. Refs #10030 * Keep a subagent's own job notification out of the main session's turns A background job a subagent started reports to that subagent, and Claude starts no main-session run for it. Its notification gave the next main-session run a new turn, so when it arrived between a main command's notification and Claude's reply to it, the reply was drawn in a different turn from the notification it answered. Refs #10030
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