mirror of https://github.com/getpaseo/paseo.git synced 2026-11-10 18:35:17 +00:00

Files

T

Mohamed Boudra 5ed1f8d108 feat(timeline): apply conversation rewinds without replacing history

Rewinding a prompt used to rotate the timeline epoch, so every open
client refetched and remounted the whole chat. A rewind is now a
retirement: the daemon keeps the rewound turn stored but outside the
conversation, and capable clients remove the rows that started in
[retireFromSeq, seq) in place. Catch-up pages carry the retirements in
their span. Clients without the timeline_rewind_operations capability
get the old replacement shape.

The daemon retires only what the provider actually removed. Providers
report the boundary they kept. A failure known to change nothing keeps
the conversation. Any other failure leaves the rewind open and refuses
prompts until reloading the agent proves the outcome from the
provider's replayed prompts. A recorded cut whose save failed is
committed by the next prompt or the reload, which resumes the rewound
session.

Plugin providers complete session.revert without saying what they
removed. Paseo then reloads the session itself and judges the outcome
from the replay, so a no-op completion is not taken as a cut.

The app anchors each row at the seq it started at, because a late
update moves a row's latest seq into the rewound range. The app also
refuses pages served before the newest retirement it has seen, then
refetches them.

Known limits:
- The automatic plugin settle shows the agent as restoring briefly.
- An empty or mismatched plugin replay leaves the rewind unresolved.
  Fork the chat to recover.
- A plugin's failed revert still needs a manual reload.
- An open rewind lives in memory, so a daemon restart drops it.

2026-11-10 10:16:13 +01:00

scripts

fix(server): read Codex history in pages instead of one whole-thread reply (#8171 )

2026-10-30 12:57:21 +07:00

src

feat(timeline): apply conversation rewinds without replacing history

2026-11-10 10:16:13 +01:00

.env.example

Let voice mode TTS use the model and voice an OpenAI-compatible server serves (#6060 )

2026-10-14 05:10:35 +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

fix(terminal): preserve 10,000 rows with direct ANSI replay (#8282 )

2026-10-31 10:51:45 +07:00

README.md

chore: reformat codebase with oxfmt

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

tsconfig.scripts.json

Terminals survive daemon restarts, crashes and updates (#7644 )

2026-10-28 18:04:29 +07:00

tsconfig.server.json

Terminals survive daemon restarts, crashes and updates (#7644 )

2026-10-28 18:04:29 +07:00

tsconfig.server.typecheck.json

Fix repo typecheck failures

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

vitest.config.ts

Make full CI finish sooner: eight browser shards, split Windows server job, cancel superseded runs (#7275 )

2026-10-18 13:52:54 +07: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