mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-19 23:05:21 +00:00
* fix(server): move updatedAt when archiving an agent that is only in storage Archiving a loaded agent sets its updatedAt to the archive time (markRecordArchived). Archiving an agent that is only in storage, which is also how a parent's archive reaches its children, kept the old updatedAt. Lists sorted by updated_at, such as History, then left a just-archived agent where its last turn put it, sometimes days back, and clients paging such a list by time never reached it. archiveSnapshotUnlocked now records the archive time as updatedAt too. Co-authored-by: RoundRedDot <roundreddot@gmail.com> * fix(server): keep updatedAt from moving back when an archive is restored Archiving a stored-only agent now sets updatedAt to the archive time. When the archive time is earlier than the record's updatedAt, as when a failed send or resume puts an agent's original archive back after unarchiving it, updatedAt stays where it is. Clients drop agent updates that are older than the one they hold, so moving it back left them showing the agent active. Co-authored-by: luke <luopeihuan@gmail.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(server): keep updatedAt from moving back when a loaded agent's archive is restored The rule that archiving never moves updatedAt backwards now lives in buildArchivedAgentRecord, which both archive paths use. A failed send that resumed the agent before a later loading step failed puts its original archive back through the loaded path, which had the same backwards move. The workspace archive stamp test now uses stamps taken after the agents' activity, as real archive stamps are. Co-authored-by: luke <luopeihuan@gmail.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * refactor(server): require the archive time when building an archived agent buildArchivedAgentRecord no longer accepts an archive that leaves updatedAt unset, the gap #9920 came through, and its tests now assert the rule: a later archive time moves updatedAt, an earlier one keeps it. Co-authored-by: luke <luopeihuan@gmail.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: luke <luopeihuan@gmail.com> Co-authored-by: RoundRedDot <roundreddot@gmail.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