mirror of
https://github.com/getpaseo/paseo.git
synced 2026-07-29 12:01:31 +00:00
99440201bd
The Claude usage card showed only Session and Weekly. Anthropic moved model-scoped weekly limits out of the top-level `seven_day_<model>` keys into a `limits[]` array, and `seven_day_opus` / `seven_day_omelette` now return null, so the scoped bar silently disappeared. Nothing errored, so the card looked healthy while under-reporting. Scoped limits are now read from `limits[]`, restoring a `Weekly · Fable` bar. Session and all-models weekly keep coming from the top-level keys, which is also where the Claude CLI reads them from. A response mid-migration can describe one limit twice, as a legacy key and as a `limits[]` entry, so both shapes normalize into a single `ScopedLimit` and one predicate decides whether two are the same limit: same dimension, same id when both carry one, else same normalized name. That is the only comparison in the file. Comparing display labels would conflate a surface with a model of the same name, and collapse ids that differ only by punctuation. The `limits[]` entry supplies identity, since that is the shape the API is migrating towards. Its `percent` and `resets_at` are nullable, so each field falls back to the legacy twin rather than discarding a value the response did carry. Legacy scoped windows adopt the same id scheme, so `weekly_opus` becomes `weekly_model_opus`. Window ids are internal React keys, not user-facing, and unifying them is what lets a limit keep one id whichever shape of the response carried it. Two supporting changes: - `limits[]` entries are validated one at a time. The response goes through a single parse, so one malformed entry would otherwise throw and take the windows that already parsed with it. - The provider stores the logger it was already handed and warns when a response parses but yields no windows, when a scope resolves to no name, and when an entry is unparseable. This failure was silent at every level, which is why it went unnoticed. Warn rather than debug, because file logging defaults to info. Scoped windows render even at 0% and inactive, so a bar does not appear and disappear between refreshes. Closes #2302 Co-authored-by: Claude Opus 4.8 <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