puter/paseo

Fork 0

mirror of https://github.com/getpaseo/paseo.git synced 2026-10-23 09:42:53 +00:00

Files

T

History

b85b44aea1 Show a host's new version after its daemon restarts (#5351 )

* Show a host's new version after its daemon restarts

The app wrote a host's server info into the session store only when a
client was first mounted, and a reconnect reuses the same client, so
after a daemon upgrade or restart the host page and version checks kept
the old version until the app restarted.

The host runtime now projects the client's current server info into the
session store on every connection change, keeping the last known value
while disconnected. The React mount effect that duplicated this write is
removed.

Closes #5236

Co-authored-by: Leonid <127580858+bashrusakh@users.noreply.github.com>

* Keep a caller-owned test daemon home across startup retries

A failed start removed the home even with cleanup disabled, so a retry on a
taken port came back with a new serverId. The host restart spec now drives a
restartable host daemon helper that owns its port, home, and teardown.

* Remove only the test daemon dirs a failed start created

A failed attempt now removes the temp home and static dirs it created and
leaves caller-supplied ones, so cleanup: false no longer leaks per retry.

* Use function declarations in the test daemon helpers

* test(app): cover host versions across daemon disconnect and reconnect

The host settings badge retains its last known version during a transport failure; the help menu should show the replacement version after reconnect without changing another host.

---------

Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com>
Co-authored-by: Leonid <127580858+bashrusakh@users.noreply.github.com>
Co-authored-by: Mohamed Boudra <boudra.moha@gmail.com>

2026-09-28 17:40:41 +01:00

scripts

fix(opencode): support v2 with automatic version selection (#5198 )

2026-09-26 17:18:31 +02:00

src

Show a host's new version after its daemon restarts (#5351 )

2026-09-28 17:40:41 +01:00

.env.example

Use separate OpenAI endpoints for speech-to-text and text-to-speech (#1823 )

2026-06-30 10:00:27 +02:00

.gitignore

server(codex): normalize file paths, truncate large diffs, and drop turn/diff/updated telemetry

2026-02-06 11:51:59 +07:00

AGENTS.md

refactor(agent): add wait_for_agent tool and simplify prompt sending API

2025-11-03 11:47:15 +01:00

CLAUDE.md

Speed up cold diffs and wrapped text measurement (#4676 )

2026-09-11 08:07:01 +02:00

package.json

feat(usage): usage sources as built-in plugins, following the session's account (#5465 )

2026-09-28 16:36:34 +01:00

README.md

chore: reformat codebase with oxfmt

2026-04-23 21:44:48 +07:00

tsconfig.scripts.json

Align script TypeScript lib with server build

2026-05-05 18:54:29 +07:00

tsconfig.server.json

2026-08-02 00:56:05 +08:00

tsconfig.server.typecheck.json

Fix repo typecheck failures

2025-11-15 20:17:47 +01:00

vitest.config.ts

Launch a terminal instead of a chat from New workspace (#2941 )

2026-08-07 14:08:22 +08:00

README.md

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