mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-23 09:42:53 +00:00
paseo-bot[bot]andplatanus-kr
0708b8295c
* fix(server): name an imported Claude agent after its /rename Importing a Claude session named the agent after its first prompt even when the session had been renamed in the CLI, so the name had to be set again by hand. #4216 fixed the Import Session listing; the imported agent still kept the prompt. Read the last usable `custom-title` from the transcript and pass it as the imported config title. The record is re-emitted on every save, so searching backwards from the end of the file finds the current name without walking a transcript that can reach tens of megabytes. Only an explicit rename is carried over. Agents are named after their first prompt line since #1563, so adopting the generated `ai-title` here would put that LLM summary back. Refs #2513 * refactor(server): drop unused generality from the Claude title reader readLastClaudeTitle took content, type and field so it could read both custom-title and ai-title records, which the listing needed before #4216 took that over. Only the custom-title read is left, so the two extra parameters are dead flexibility that also broke the single-object-parameter rule in packages/server/CLAUDE.md. Collapse it to readLastClaudeCustomTitle(content) and pull the record type into a constant so the needle and the type check share one literal. Hooks skipped: the repo-wide typecheck fails on two pre-existing Electron typing errors in packages/desktop/src/main.ts that reproduce with this change stashed. packages/server typecheck, lint and format all pass. * test(server): drive the real resume path in the import title tests The tests assigned an inline arrow function to client.resumeSession to keep Claude Code from spawning. Importing replays the transcript from disk and never starts a process, so the stub was never needed. Dropping it runs the real resume path, which is what docs/testing.md asks for, and removes the arrow assignment that docs/coding-standards.md rules out. Hooks skipped: the repo-wide typecheck fails on two pre-existing Electron typing errors in packages/desktop/src/main.ts that reproduce with this change stashed. packages/server typecheck, lint, format and the 83 claude tests pass. * fix(server): narrow the transcript read error instead of asserting it The ENOENT check cast the caught value to NodeJS.ErrnoException to reach `code`, which is the kind of assertion docs/coding-standards.md rules out: narrow with `if`, do not silence the compiler. Add the same local type guard pid-lock.ts already uses and test through it. Behaviour is unchanged. A value that is not an Error still falls through to the rethrow, exactly as reading `code` off the assertion did. Hooks skipped: the repo-wide typecheck fails on two pre-existing Electron typing errors in packages/desktop/src/main.ts that reproduce with this change stashed. packages/server typecheck, lint, format and the 83 claude tests pass. * fix(server): let claudeProjectDirSync resolve the Claude config dir The import title reader built the config dir itself through os.homedir(), but os is no longer imported here, so the fallback threw a ReferenceError whenever CLAUDE_CONFIG_DIR was unset. claudeProjectDirSync already resolves the same default. * test(server): give the import title helpers object parameters * fix(server): preserve imported session renames across history locations The import title reader must use the same provider environment and transcript lookup as history replay. Otherwise an imported session has its history but loses its explicit name when its configuration directory or project changed. Co-authored-by: platanus-kr <platanus.kr@gmail.com> --------- Co-authored-by: platanus-kr <platanus.kr@gmail.com> 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